NXLog Windows Service crash on termination/stop

View thread

bosarebo

Hello!

We run NXLog version nxlog-3.2.1991-x86 on Windows Server 2016.

Thanks for a good and well documented product. However, we have an issue when closing down the NXLog service. Sometimes stopping the service fails with the following error message:

"Error 109: The pipe has been ended".

When this happens, no cache file is created (configcache.dat) and at startup the whole table is sent again.

It is easy to reproduce this issue. Just stop the service after 5 seconds of running. However, it also happens after run time of 24 hours.

On this machine we use NXLog for monitoring a table in MS SQL and send the content to syslog over TCP. We have not changed the default setting for table polling interval (every second). As a work around we will lower the polling interval to every 60 second.

Kind regards.

// Erik