RE: [syslog-ng] Problems with syslog-ng use over a redireted port inside an SSH s ession
Hi
-----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Subject: Re: [syslog-ng] Problems with syslog-ng use over a redireted port inside an SSH s ession
I'm using syslog-ng over redirected ports inside an SSH channel and whenever I HUP syslog-ng, the SSH channel closes
Maybe you should try to handle the SIGPIPE signal in your perl script? though SIGPIPE should occur only on output, reading from a broken socket should result in an EPIPE to be returned.
Well that's what I would have thought, the child process _is_ writing the socket but does not recieve any such signal (or appears not to..) The child lives on and when it next writes the socket, the channel drops and then it dies. Netcat dies imediately when syslog-ng is HUPPED, which points again at the script of course.. I'll capture the ssh (openssh 2.1) debug output and I can post the key bits of the script if you think it would help? And I'll add a trap for SIGPIPE. Thanks for the responce. ciao dave ---- Dave Edwards mailto:david.edwards@eds.com Ph: +61 8 83015720 EDS Network Support Glenside, South Australia ---- PGP Fingerprint: B9C0 AB83 F18B CE88 C167 67B9 6AB2 C630 3DC9 ACC2
Subject: Re: [syslog-ng] Problems with syslog-ng use over a redireted port inside an SSH s ession
I'm using syslog-ng over redirected ports inside an SSH channel and whenever I HUP syslog-ng, the SSH channel closes
Maybe you should try to handle the SIGPIPE signal in your perl script? though SIGPIPE should occur only on output, reading from a broken socket should result in an EPIPE to be returned.
Well that's what I would have thought, the child process _is_ writing the socket but does not recieve any such signal (or appears not to..) The child lives on and when it next writes the socket, the channel drops and then it dies.
Netcat dies imediately when syslog-ng is HUPPED, which points again at the script of course..
I'll capture the ssh (openssh 2.1) debug output and I can post the key bits of the script if you think it would help?
And I'll add a trap for SIGPIPE.
syslog-ng closes TCP connections when a SIGHUP is received, but you can change this behaviour with the keep-alive option. destination all { tcp("loghost" port(1514) keep-alive(yes)); }; -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
participants (2)
-
Balazs Scheidler
-
Edwards, David