Hi, I kinda remember seeing similar issues before, but I don't know exactly what the problem was. I'd suggest trying a newer syslog-ng version (3.5 is rather old and somewhat buggy), and maybe also trying to set the persist-name() option of the destination (see https://github.com/balabit/syslog-ng/issues/1275 ). HTH, Robert On Thu, Feb 15, 2018 at 6:53 PM, Garry De Toffoli <dtgarry@hotmail.com> wrote:

Hello,

I have configured syslog.ng OSE version 3.5.3 to log to a MSSQL destination and that all works well.

However when I have specified 2 MSSQL destination, same SQL Server, same table on different database, syslog-ng have problem to insert on database, both on the first and on the second.

Some time will insert, sometimes not.

On /var/log/syslog I have found some lines reporting error CREATE TABLE on the second database,

Restarting the service, *sudo service syslog-ng restart,* takes a long time.

When I comment out the destination of the 2nd database, syslog-ng run very well.

Is it a limit of the OSE version? Or may be an error on the configuration file?

See attached my configuration file.

Thank you for the patience.

-----------------------

Garry De Toffoli

-----------------------

____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/? product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq