Hi, We have several internal tests for modules including om_tcp and this would immediately catch such an issue. The absence of a socket close would not cause connection problems, though IMO this is done properly. Your connection reset problems are most likely caused by the accepting side.
Regards, Botond On Tue, 2 Jul 2013 10:57:05 +0300 cagil ozturk <[email protected]> wrote: > Hi All, > > Is there a bug for tcp send messages within nxlog? I configured nxlog to > take logs from tcp with im_tcp module and routed the tcp inputs to tcp > output however it is impossible to send tcp output. I tried so many times > with linux, windows and different port numbers and nothing helped. I > inspected om_tcp.c and I suspect that the problem is caused by the absence > for socket close. I could'nt solved the problem yet. Here is the nxlog > log error: > - ERROR couldn't connect to tcp socket on 10.240.97.77:8081;Connection > refused > > And my nxlog configuration: > > <Extension _syslog> > Module xm_syslog > </Extension> > > <Extension _xml> > Module xm_xml > </Extension> > > <Input in1> > Module im_tcp > Port 111 > Host 0.0.0.0 > </Input> > > <Output out1> > Module om_tcp > Host 10.240.97.77 > Port 8081 > </Output> > <Route 1> > Path in1 => out1 > </Route> ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ nxlog-ce-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
