Fixed bugs in syslog-ng Premium Edition 6.0.1 (4231947)

Fixed bugs in syslog-ng Premium Edition 6.0.1

This article lists the bugs fixed in syslog-ng Premium Edition 6.0.1.

Released: Fri, 29 Jul 2016


  Fixes:

    #SYSLOGMT-775  When installed in a custom directory on Solaris 10, syslog-ng PE cannot read its configuration file
    #SYSLOGMT-768  syslog-ng PE periodically crashes on Windows 2012 when using logstore files
    #SYSLOGMT-765  Special long incoming message can break the journal file
    #SYSLOGMT-761  syslog-ng PE crashes when the license limit is reached and the client uses RLTP
    #SYSLOGMT-755  The '--syntax-only' command-line check does not work on Windows platforms
    #SYSLOGMT-752  When using disk-based buffering, the throttle() option is not working during syslog-ng reloads
    #SYSLOGMT-742  Cannot run multiple syslog-ng PE instances on Solaris
    #SYSLOGMT-739  Cannot run multiple syslog-ng PE instances on Solaris
    #SYSLOGMT-733  SDATA parameters are truncated after 255 characters
    #SYSLOGMT-723  Reading UTF-16-encoded files with a wildcard file source fails
    #SYSLOGMT-717  Possible values of the cipher-suite() option do not work
    #SYSLOGMT-716  The output of 'pdbtool match' is incorrect
    #SYSLOGMT-714  syslog-ng Agent for Windows crashes regularly if a source file is moved and recreated
    #SYSLOGMT-696  If a logstore becomes corrupted, syslog-ng enters a consistency-checking loop
    #SYSLOGMT-667  syslog-ng crashes if there is an error during RLTP TLS connection setup
    #SYSLOGMT-647  Event Source names on the Windows Agent interface do not match the actual Source names
    #SYSLOGMT-643  If syslog-ng cannot parse a log message, the error message is too general