writing to /dev/log hungs system
hi since time to time all applications hung that write to syslog, and i cannot ^C ^Z ^\ them ;( i cannot su to root and kill syslog-ng too. this has happened several times over several machines i've turned off dns lookups, since i guessed dns downtime affects this, but that did not help the problem, when it's arisen, gets solved by some 6 hours i guess the hung arises on high flood to syslog here's some strace too: socket(PF_UNIX, SOCK_DGRAM, 0) = 3 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 connect(3, {sin_family=AF_UNIX, path="/dev/log"}, 16) = -1 EPROTOTYPE (Protocol wrong type for socket) close(3) = 0 socket(PF_UNIX, SOCK_STREAM, 0) = 3 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 connect(3, {sin_family=AF_UNIX, path="/dev/log"}, 16 <HUNGS HERE> i'm using syslog-ng 1.4.17 os is linux, redhat based kernel varies, but mostly 2.4.18 (redhat patches) config options: options { long_hostnames(off); sync(0); use_dns (no); use_fqdn (no); }; source src { pipe("/proc/kmsg"); unix-stream("/dev/log"); internal(); }; -- glen
On Thu, Feb 20, 2003 at 01:49:55PM +0200, Elan Ruusamäe wrote:
hi
since time to time all applications hung that write to syslog, and i cannot ^C ^Z ^\ them ;( i cannot su to root and kill syslog-ng too.
this has happened several times over several machines i've turned off dns lookups, since i guessed dns downtime affects this, but that did not help
the problem, when it's arisen, gets solved by some 6 hours
i guess the hung arises on high flood to syslog ...
source src { pipe("/proc/kmsg"); unix-stream("/dev/log"); internal(); };
you are probably running syslog-ng and klogd at the same time and both of them are reading /proc/kmsg. see the FAQ entry about this. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
Elan Ruusamäe