This article applies to BoKS Manager 7.0.0.


This hotfix addresses two issues concerning BoKS syslog integration:

  1. When relaying BoKS log messages from the BoKS Master to a syslog server without TLS support enabled, the log messages are sent in RFC5425 format (i.e the message length + a space (" ") character are inserted before the actual message). However messages sent to a syslog server without TLS support enabled should be in RFC5424 format (i.e. without the message length and the space character).
  2. No UDP support exists for relaying BoKS log messages to a syslog server.

Resolution / Workaround

To resolve these issues, apply hotfix HFBM-0105, available for download from the HelpSystems Community Portal.

With this hotfix:

  1. Relaying over TCP without TLS support is now done using the RFC5424 message format. A new ENV variable, BLOGSD_SYSLOG_USERFC5425 has been added. If enabled, the relaying will be forced to use the RFC5425 format.
  2. UDP support is enabled using the new BLOGSD_SYSLOG_UDP ENV variable. This is disabled by default. Note, if enabling UDP support in BoKS, the syslog server must also be configured to handle UDP.

For more information, please see the BoKS ENV.4 man page.
This hotfix includes an updated boks_blogsd binary and ENV.4 man page solving these issues.


This hotfix was verified using the rsyslog and syslog-ng syslog servers. The syslog-ng server (ver. 3.6.4) required RFC5425 when relaying over TCP without TLS enabled. In this case "BLOGSD_SYSLOG_USERFC5425=on" was added in the BoKS ENV file on the BoKS Master.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018