Checkmk - version 2.2.0p18 - syslog-like message logging seems not to work

CMK version: 2.2.0p18
OS version: tested on Ubuntu server 22.04 and 23.10

`- fresh installation tested on ubuntu server 22.04 and 23.10

  • turn on syslog-like message logging submit the changes and make sure
    that the syslog services of the site are enabled (omd config sitename)

  • send some syslog teste messages:
    echo ‘<78>Jan 15 12:23:01 mytestserver01 myapplication: is working now.’ | nc -w 1 -u 514
    or:
    echo ‘This is no syslog message’ | nc -w 1 -u 514

  • make sure that the test syslog messages are seen on the system, using tcpdump:
    tcpdump port 514

  • if you send the syslog message from the own machine, make sure to monitor your loopback interface:
    tcpdump -i lo port 514

  • normaly you should now see a log file under your site ./var/mkevent/messages/somelogfile.log

the problem with version 2.2.0p18 was that the directory
“messages” under ./var/mkevent/ was not created and also no log files.
As soon as I installed 2.2.0p17 or earlier the messages directory was created and also the log files

see also: https://computer2know.de/checkmk-version-2.2.0p18-syslog-like-message-logging-seams-not-to-work:::957.html

@jodok.glabasna This might match the open issues you mentioned regarding the Event Console, or maybe it gives additional info that help troubleshooting.

@matthias1 there is a support case open with Checkmk regarding Event Console functionality, this might be the same issue.

1 Like

Hello @matthias1 ,

The fix is implemented and will be released as werk 14859 in the next patch-release p19

As a workaround you can: make a trivial change to the rules/rule packs (for example, edit description)
and activate the changes. Or reload the EC manually after the initial reload to apply the correct config.

1 Like