Release Notes › Known Issues › LogSensors and Listeners

LogSensors and Listeners

The following are the known issues related to the logsensors and listeners.

Repeated Events Appear in CA User Activity Reporting Module

Symptom:

CA User Activity Reporting Module receives repeated events when you reboot the event source computer from which the WMI logsensor is receiving events.

Solution:

This is a known issue. A fix for this issue will be available in a future release of CA User Activity Reporting Module.

User Credentials Authentication Fails on WMI LogSensor

Symptom:

CA User Activity Reporting Module fails to authenticate a user when you deploy a WMI logsensor to receive events from a local computer. The WMI logsensor is able to receive events from the local computer.

Solution:

This is default behavior. Microsoft Windows does not validate user credentials when you deploy a WMI logsensor on the local computer.

Connector Deployment Fails for a Cisco Router Integration

Symptom:

When you deploy a connector using the syslog listener for Cisco Router 12.1 or Cisco Router 12.2 integrations, the connector deployment fails intermittently.

Solution:

This is a known issue. A fix for this issue will be available in a future release of CA User Activity Reporting Module.

The Syslog Listener Restarts at Regular Intervals

Symptom:

When you enable the CPU throttling feature on Solaris computers, the syslog listener restarts at regular intervals.

Solution:

You can resolve this issue by disabling the CPU throttling feature.

Deployment of Connector Based on the Local Syslog LogSensor Fails on RHEL 6 32-bit Machines

Symptom:

When I deploy a connector that is based on the local syslog logsensor on an RHEL 6 32-bit machine, the deployment fails.

Solution:

To resolve the issue, update the path in Syslog conf File Path of the connector configuration page from /etc/syslog.conf to /etc/rsyslog.conf.