Release Notes › Known Issues › Agents and CA Adapters › syslog Services on UNIX Conflict

syslog Services on UNIX Conflict

Symptom:

CA Enterprise Log Manager receives no syslog events in the following scenario:

• Computer 1

  A CA Enterprise Log Manager server listening for syslog events from Computer 2.

• Computer 2

  A RHEL 4.0 computer with a local agent containing a syslog connector, and sending its events to the Computer 1 using the syslog listener.

• Computer 3

  A UNIX computer sending events to Computer 2 using the connector installed there.

In this case, the agent computer is unable to capture the events from Computer 3 because the OS syslog service and syslog connector are running on the same system.

Solution:

Stop the syslog service on Computer 2 to receive events from Computer 3 (the UNIX computer). You can also reconfigure the environment so the syslog services do not conflict on the same computer.