I found a year or more old reference to the same error and the solution back then was to switch the NXlog ouput from tcp to udp. The same change seems to have stopped the errors now. So it seems I can't currently use om_tcp in NXlog to send Windows logs. I'm not sure why udp works and tcp doesn't.
On Friday, May 1, 2015 at 4:29:49 PM UTC-7, Mark Moorcroft wrote: > > > This morning I was seeing bunches of errors in the server.log. I think I > tracked them to a syslog/tcp input. My rsyslog entry on the client is as > follows. > > > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
