On 8/1/2013 5:49 PM, DMF Lists wrote: > I'm setup to ship windows logs to a central linux host running nxlog via > native > transport which then ships it off to logstash via generic TCP. If logstash > backs up or > dies and it's caught immediately and restarted, the nxlog transport chain > seems to > survive. However, if logstash is stopped for a long period of time ie a few > hours, not > all windows nxlog clients will reconnect properly. The nxlog logs just show > the > following mutiple times: > > 2013-03-27 14:49:59 ERROR couldn't connect to tcp socket on logger1:514 No > connection > could be made because the target machine actively refused it. > 2013-03-27 14:50:00 INFO reconnecting in 10 seconds > > Once I restart the nxlog client on the windows side, it starts logging again. > Any thoughts?
I believe this is a use case for pm_buffer - http://nxlog-ce.sourceforge.net/nxlog-docs/en/nxlog-reference-manual.html#pm_buffer. You just need to figure out how much disk storage to reserve for your worst case. Regards, Mark -- Mark D. Nagel, CCIE #3177 <mna...@willingminds.com> Principal Consultant, Willing Minds LLC (http://www.willingminds.com) cell: 949-279-5817, desk: 714-495-4001, fax: 714-646-8277 ** For faster support response time, please ** email supp...@willingminds.com or call 714-495-4000 ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
