Nxlog stops sending data to a route if another route is actively rejecting connections


#1 kond_nxlog (Last updated )

Nxlog stops sending data to a route if another route is actively rejecting connections.

The other output stops sending data after a while (from a few minutes to a day), although TCP-connection is supported.

We use 2 routes at the same time with 1 input.

There is our nxlog config: “The in1 module is used by both routes. ”

Planforms: Windows 2016/2019 and Windows 2022

nxlog.conf

<Route r1>
    Path    in => out1
</Route>

<Route r2> Path in => out2 </Route>

Logs:

2024-11-21 13:28:53 INFO nxlog-ce-3.2.2329 started
2024-11-21 13:28:53 INFO connecting to Graylogserver:12523
2024-11-21 13:28:53 INFO connecting to Graylogserver:12527
2024-11-21 13:28:54 INFO reconnecting in 1 seconds
2024-11-21 13:28:54 ERROR couldn't connect to tcp socket on Graylogserver:12523; No connection could be made because the target machine actively refused it.
2024-11-21 13:28:55 INFO connecting to Graylogserver:12523 2024-11-21 13:28:56 INFO reconnecting in 2 seconds 2024-11-21 13:28:56 ERROR couldn't connect to tcp socket on Graylogserver:12523; No connection could be made because the target machine actively refused it.
2024-11-21 13:28:58 INFO connecting to Graylogserver:12523

#2 alexander.lifanov@nxlog.org Nxlog ✓

This is an expected behavior: https://docs.nxlog.co/userguide/intro/buffering-and-flow-control.html 
Check the last picture of that page, it's exactly your case.
It does not matter if the route is the same or another. The module is the same anyway.