Problems with syslog-ng use over a redireted port inside an SSH s ession
Hi, I'm using syslog-ng over redirected ports inside an SSH channel and whenever I HUP syslog-ng, the SSH channel closes. This appears to be a problem with syslog-ng, as if I kill -KILL syslog-ng, the channel remains in place. I copy logs over the channel using a perl script. This also may be suspect of course.. The channel seems to close when the script writes to the (possibly disrupted tcp) socket. If I don't write to the socket, the channel stays up.. I use the IO::Socket method $socket->can_write to attempt to find out if the socket is still writable but this does not show any problems but the channel dies anyway. Anyone else seeing this problem? 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
I'm using syslog-ng over redirected ports inside an SSH channel and whenever I HUP syslog-ng, the SSH channel closes.
This appears to be a problem with syslog-ng, as if I kill -KILL syslog-ng, the channel remains in place.
I copy logs over the channel using a perl script. This also may be suspect of course.. The channel seems to close when the script writes to the (possibly disrupted tcp) socket. If I don't write to the socket, the channel stays up.. I use the IO::Socket method $socket->can_write to attempt to find out if the socket is still writable but this does not show any problems but the channel dies anyway.
Anyone else seeing this problem?
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. -- 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