Bug ID 463715: syscalld logs erroneous and benign timeout messages

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.2

Opened: May 22, 2014
Severity: 3-Major
Related AskF5 Article:
K15979

Symptoms

The syscalld timeout mechanism might cause premature logging of OPERATION_TIMEOUT messages.

Impact

The system posts the message: syscalld[21190]: 0127000a:3: OPERATION_TIMEOUT 'command' may be hung or taking a long time. This may cause some operations, such as establishing CMI trust, to fail and need to be launched again.

Conditions

No specific configuration is required.

Workaround

None

Fix Information

syscalld's timeout mechanism no longer emits an OPERATION_TIMEOUT message, unless the message appropriately reflects the condition of the system.

Behavior Change