Werk #22958: Mangled messages starting with a number
| Component | Event Console | ||
| Title | Mangled messages starting with a number | ||
| Date | Nov 2, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
The Event Console took a number at the start of a message from its event pipe,
its event socket or syslog via TCP for an octet count. So
mkevent "2 disks failed" created the two events di and sks failed, and a
message like 500 errors in log held back the messages after it.
Now each line is a message. The event socket and syslog via TCP only take
octet counting if a syslog priority like <14> follows the number, the event
pipe takes none at all. Empty messages are dropped, and concurrent calls of
mkevent no longer mix up messages shorter than 4 KiB.
If you send octet-counted messages to the event socket or via TCP, make sure
each one starts with a syslog priority, as RFC 5424 requires. The default
templates of rsyslog do so, but a template of your own has to start with
<%PRI%>.