[syslog-ng-announce] syslog-ng Premium Edition 4 LTS (4.0.5) has been released

devel at balabit.hu devel at balabit.hu
Mon Mar 12 09:44:30 CET 2012

PACKAGE             : syslog-ng Premium Edition
VERSION             : 4 LTS (4.0.5)
SUMMARY             : new stable release
DATE                : Mar 9, 2012


  A new stable version of syslog-ng Premium Edition (4 LTS (4.0.5)) has been
  released. For a full description on stable and feature releases,
  see Section 2.16. Stable and feature releases of syslog-ng PE in The syslog-ng
  Premium Edition 4 LTS (4.0.5) Administrator Guide.


4 LTS (4.0.5)
  Fri, 09 Mar 2012 13:26:48 +0100

  Fixed issues:
    #25577: Fixed a syslog-ng deadlock in case of failed SQL transactions
    #24425: In rare cases, syslog-ng crashes on Solaris
    #24546: Memory leak when reading from disk buffer
    #24210: The lgstool tail command fails with an error message
    #22763: The trusted-keys() option is ignored if the value was not an SHA1 key
    #23297: SQL: messages lost from FIFO when reloading syslog-ng
    #23308: SQL: When shutting down syslog-ng, messages from FIFO are lost
    #23110: Debug logs of syslog-ng include every modification of the log messages
    #23176: syslog-ng removes the PRI value if it is 0
    #23409: Reading from files using the wildcard file source is slow
    #25963: syslog-ng does not start if the persist file is invalid
    #23114: A single log message is not sent using TLS, two messages are required
    #23418: Losing messages when flow-control is enabled
    #23555: syslog-ng crashes when the pad_size() is longer than the message
    #22636: The unix-stream and dgram drivers duplicate messages in some cases
    #25956: syslog-ng stops processing messages when the timestamping server is
    #25978: Receiving messages from obsolete network sources causes a segfault
    #25979: Rewrite: Attempting to rewrite a read-only field overwrites the
            MESSAGE field
    #25995: When reloading the configuration is not successful, syslog-ng can
            duplicate log messages
    #22693: In some cases the disk buffer file becomes unreadable
    #24580: If the flush_timeout() is low, the throttle option is not working
            for file destinations


        Deadlock detection:
        * The supervisor process of syslog-ng can automatically check if
          syslog-ng entered a deadlock and does not respond. If the syslog-ng
          process does not respond, the supervisor process restarts syslog-ng.
          By default, the supervisor process checks for timeouts every 300
          To modify this value, use the '--deadlock-check-timeout' or '-D'
          command-line option of syslog-ng

  For details on the fixed issues see our new issue tracking page at

  The documentation of syslog-ng 4 LTS, including the installation and user guides is
  available in PDF, HTML, and single-page HTML format at:

    For details on upgrading and possible upgrade paths, read Section 3.5.,
    Upgrading syslog-ng in the The syslog-ng Premium Edition 4 LTS Administrator Guide:

  Kind Regards,

  BalaBit IT Security


  Download the latest binaries from:


  Note that to download the binaries, you have to login into your MyBalaBit

  The documentation of the syslog-ng application is available in
  The syslog-ng Premium Edition 4 LTS (4.0.5) Administrator Guide at:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 199 bytes
Desc: not available
Url : http://lists.balabit.hu/pipermail/syslog-ng-announce/attachments/20120312/d27ec8fd/attachment.pgp 

More information about the syslog-ng-announce mailing list