SYSLOG Check Failed after updating to cPanel 60

[esarant]

Hello,

After my cPanel updated to v60 I started getting the following error:

Code: Select all

Time:  Wed Oct 12 14:36:40 2016 +0300
Error: Failed to detect code [2lLywsZYL97Y2LtXMcwEIm] in SYSLOG_LOG [/var/log/messages]

SYSLOG may not be running correctly on <...>

Running /scripts/restartsrv_rsyslogd --status displays that the rsyslog service is indeed running.

CentOS: 7
CSF: 9.24

Any idea why I get this error?

Thank you.

[Elizine]

Check if the Rsyslogd is running

Code: Select all

/scripts/restartsrv_rsyslogd --status

[NRVDigital]

I have the same issue, and I've checked the rsyslog is running. How can I disable these notices?

[fingerprn]

I had the same problem (but I'm not sure if it was triggered by an update) and confirmed that Rsyslogd was running. Looked all over the web for an answer the best I could find was:

Open etc/csf/csf.conf

Set SYSLOG_CHECK to 0.

Restart LFD/CSF

Not an ideal solution, but it stops the warnings. Obviously, don't use this if Rsyslogd isn't actually running. This seems to be a common problem, so I hope someone will actually figure it out.

[billread]

Investigating this, I googled "SYSLOG system.journal" and found this:

http://www.selftaughtlinux.com/solved-l ... ck-failed/

I followed the instructions, except for the last part about commenting out #$IncludeConfig /etc/rsyslog.d/*.conf

Then tested it.

Essentially, I discovered that the code used by the SYSLOG check was never in /var/log/messages, but it WAS in /var/log/journal/system.journal. Thinking that I needed to tell the SYSLOG check to look there, I discovered this "fix". Basically, this fix makes sure that the code used as part of the check hits messages rather than system.journal.