Bug ID 484453: Messages logged when registering with LOP daemon (lopd) or CAN daemon (cand)

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
11.1.0, 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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8

Fixed In:
12.0.0, 11.6.1, 11.5.2, 11.5.1 HF6, 11.4.1 HF9

Opened: Oct 14, 2014
Severity: 2-Critical
Related Article:
K15853

Symptoms

When the log filter is configured to filter at the 'Informational' log level, the logs can get filled with 'client /var/run/lopd.chmand.lopuns already registered' messages when registering with either the Lights Out Processor daemon (lopd) or the CAN daemon (cand). These messages appear in the log every two seconds on systems with lopd, or every 20 seconds on systems with cand.

Impact

Logs fill with messages. These messages are related to communication with the Lights Out Processor daemon (lopd) or with the CAN daemon (cand), and are completely benign, so you can safely ignore them.

Conditions

This occurs when using a remote syslog logging filter with the 'Severity' field set to 'Informational'.

Workaround

Change the remote syslog logging level to 'Notice'.

Fix Information

Reduced the log level for registering with the LOP (lights out processor) and CAN daemon (cand) to the debug level.

Behavior Change