Chat now with support
Chat with Support

syslog-ng Premium Edition 6.0.17 - Release Notes

Resolved issues

The following is a list of issues addressed in this release.

Table 1: Issues resolved in version 6.0.17
Resolved Issue Issue ID

Memory leak when using several MsSQL sources

SYSLOGDEV-4762

Reliable disk queue file corruption

SYSLOGDEV-4811

OpenSSL upgraded to 1.0.2s

SYSLOGDEV-4830

Table 2: Issues resolved in version 6.0.16
Resolved Issue Issue ID

OpenSSL has been upgraded to version 1.0.2r

SYSLOGDEV-4741

Mssql Latin2 to UTF8 conversion fix

SYSLOGDEV-4740

Crash during reverting back to old configuration on reload

SYSLOGDEV-4697

Special characters in SSL certificate prevent syslog-ng Agent for Windows from starting

SYSLOGDEV-4688

Crash when using SQL source

SYSLOGDEV-4685

Rare race condition causes a crash in sql destination

SYSLOGDEV-4662

Crash when stopping syslog-ng when the disk is full

SYSLOGDEV-4503

Empty disk queue truncate fix

SYSLOGDEV-4111

Table 3: Issues resolved in version 6.0.15
Resolved Issue Issue ID

Fix debug logging path using Windows Agent

SYSLOGDEV-4698

Fix possible crash in Windows Agent

SYSLOGDEV-4691

Improved GPO debug logging in Windows Agent

SYSLOGDEV-4686

File destination fd leak after reload when time-reap elapsed

SYSLOGDEV-4661

OpenSSL upgraded to 1.0.2q

SYSLOGDEV-4649

File descriptor leak fix using HDFS destination

SYSLOGDEV-4630

Possible segfault accessing internal name-value pair structures

SYSLOGDEV-4583

Table 4: Issues resolved in version 6.0.14
Resolved Issue Issue ID

Fix possible corrupt disk-queue creation

SYSLOGDEV-4588

Socket leak using udp destination with spoof_source enabled

SYSLOGDEV-4586

Logstore memory leak

SYSLOGDEV-4560

Updated syslog-ng-debun utilty

SYSLOGDEV-4553

Reading kernel logs on AIX

SYSLOGDEV-4494

Processed counter negative value

SYSLOGDEV-4479

Failed reload logged later

SYSLOGDEV-4404

Table 5: Issues resolved in version 6.0.13
Resolved Issue Issue ID

Windows Agent does not close all registry handles

SYSLOGDEV-4194

Crash in loggen when using the skip-tokens parameter

SYSLOGDEV-4328

Log message stuck in backlog using disk queue

SYSLOGDEV-4347

CAP_SYSLOG capability not detected correctly

When syslog-ng was running with only user privileges but with CAP_CHOWN capability enabled, the owner of the logstore file was not set correctly. This issue has been fixed.

SYSLOGDEV-4462

RedHat package signature

SYSLOGDEV-4463

Crash when systemd journal is not readable

SYSLOGDEV-4384

OpenSSL upgraded to 1.0.2p

SYSLOGDEV-4492
Table 6: Issues resolved in version 6.0.12
Resolved Issue Issue ID

Support cap_syslog capability

SYSLOGDEV-2848

New debug message when flow-control activates

SYSLOGDEV-3529

Logstore file owner not set correctly

SYSLOGDEV-3749

Incorrect file read using multi-line file source

SYSLOGDEV-3776

Fix include path on Windows platforms

SYSLOGDEV-3862

Crash when receiving too large message in debug mode

SYSLOGDEV-4074

Loggen crash when ssl is used with non-ssl RLTP server

SYSLOGDEV-4190

Crash when message is too long

SYSLOGDEV-4202

Template with file destination creates files instead of directories

SYSLOGDEV-4206

Minor fixes in SELinux installer script

SYSLOGDEV-4292

Log fd number on verbose level for program source/destination

SYSLOGDEV-4297

Messages from journald are not included in center statistics

SYSLOGDEV-4331

Core dump when trying to open a corrupt logstore

SYSLOGDEV-4337

Child process is not terminated with java destination

SYSLOGDEV-4338

JVM is not unloaded during syslog-ng reload

SYSLOGDEV-4339

Resolved issues

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 7: Known issues in version 6.0.16
Known Issue Issue ID

mssql destination: If creating the index fails, table is not created

When using the "text", "textn", or "image" data types, you must configure the "text size" parameter as described here, otherwise syslog-ng PE can consume huge amount of memory (2GB for each text, textn, and image column used), causing the insert operation to fail. Note that the "text", "textn" and "image" data types are obsolete.

Complete the following steps:

  1. Create a file called freetds.conf in <syslog-ng-installation-directory>/etc/

  2. Enter the following into the file:

    [global]
    text size = 64512
  3. Reload syslog-ng

SYSLOGDEV-4783
Table 8: [Category] known issues
Known Issue Issue ID
   
   
Table 9: Third-party known issues
Known Issue Issue ID
   
   

Product licensing

To enable a trial license

  1. Apply for a trial license at the syslog-ng website.
  2. Download the license and the installation package for your platform, then follow the installation instructions in the Administration Guide.

To enable a purchased commercial license

  1. Download the license and the installation package for your platform, then follow the installation instructions in the Administration Guide.

Upgrade and installation instructions

To install or upgrade syslog-ng Premium Edition, follow the instructions in the syslog-ng Premium Edition Administration Guide, or the Administrator Guide for syslog-ng Agent for Windows.

Related Documents