Bug ID 709874: qkview may hang on execution, and CTRL-C will remove helpful log files

Last Modified: Jul 03, 2019

Bug Tracker

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

Known Affected Versions:
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, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 15.0.0

Opened: Mar 12, 2018
Severity: 3-Major

Symptoms

If qkview executes a command that hangs, it too hangs, waiting for its spawned process to complete. Pressing CTRL-C aborts qkview, but doing so causes the temporary files qkview generates to be deleted.

Impact

qkview hangs. Subsequently pressing Ctrl-C to terminate the qkview process results in loss of log files. Without valid qkview data, there is limited ability to debug the issue.

Conditions

qkview calls a process that hangs.

Workaround

To retain logs lost when Ctrl-C terminates the qkview process: -- Run qkview with -v option. This shows the spawned process that is executing at the time of the hang. -- Once qkview hangs, in a different console session, copy the following files to a different location for subsequent retrieval and analysis: + /var/tmp/qkview_run.dat + /var/tmp/qkview_err.dat

Fix Information

None

Behavior Change