Security Compliance
SEM with Linux x64 agents show no logs
Linux 64 agent is installed, yet no logs are returned to the SEM. Across several servers ( CentOS 8 x64 / Ubuntu 15 x64 / Debian x64 ), only Apache logs can be accessed in SEM.
First published date
Last published date
Overview
The Linux 64 agent is installed, but no logs are returned to SEM. Across several servers ( CentOS 8 x64 / Ubuntu 15 x64 / Debian x64 ) only Apache logs can be accessed in Security Event Manager (formerly Log & Event Manager).
For example, a PAM connector configured for /var/log/auth.log. Valid information in auth.log is being written to it but not showing in the SEM Web Console. Connectors were part of profile, removed and tried individually with the same result. Connection is being established between the Manager and Agent. You can see stop/start in agent logs as well as in Management but no further logging information.
The agent is communicating and the agent is parsing some logs and sending some data to SEM. The remaining data isn't parsing locally. Perhaps the log format is the issue, however you have no unmatched data warnings.
Product section
Cause
Your logging settings include a nonstandard header format.
For example (line from auth.log.2):
Jun 5 06:25:04 cas2 CRON[5898]: pam_unix(cron:session): session closed for user root -> The log line is ignored (blackhole), but when the header timestamp is changed to a random Syslog time: 1234567890123 cas2 CRON[5898]: pam_unix(cron:session): session closed for user root -> Logline is correctly recognized as UserLogOff event
Resolution
Change logging to use syslog format. (There are logs with a non-standard header time stamp in access.log and error.log too.) After the timestamp is set correctly, the logs should be parsed to alert correctly or at least there should be some "New Tool Data."