Bug ID 669585: The tmsh sys log filter is unable to display information in uncompressed log files.

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP None(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1

Fixed In:
14.1.0, 14.0.0, 13.1.0.2

Opened: Jun 16, 2017
Severity: 3-Major

Symptoms

You notice missing log information when reviewing system logs using the tmsh show sys log command.

Impact

Unable to view the full range of backup log information.

Conditions

One or more of the BIG-IP sytem backup log files, designated with .1, .2, etc are not compressed. Note: Backup log files should end with the .gz extension. For example, ltm.1.gz. You use the tmsh show sys log command to view log information for one or more days in the past.

Workaround

To log in to the Advanced shell (bash). To ensure all backup logs for a particular log type are compressed, use the following command syntax: gzip /var/log/<log>.* For example, to compress the full set of backup logs for the ltm log type, type the following command: Note: The following message is expected if the log file is already compressed: gzip: /var/log/<log>.gz already has .gz suffix -- unchanged' gzip /var/log/ltm.*

Fix Information

Increased flexibility of log reading mechanism, to look for both compressed (ending in .gz) and uncompressed (ending in .#) log files.

Behavior Change