Your message dated Mon, 10 Jul 2006 12:02:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line syslog-ng log infitely an accept() problem
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: syslog-ng
Version: 1.6.5-2.2
Severity: grave
Justification: renders package unusable
The syslog daemon randomly bug and log infinitely the same message in
/var/log/syslog about a call to accept() on a non socket.
This is a strace of the process when it bugs.
poll([{fd=2, events=POLLOUT, revents=POLLOUT}, {fd=8, events=0}, {fd=6,
events=0}, {fd=7, events=0}, {fd=4, events=POLLIN}, {fd=3,
events=POLLIN}, {fd=1, events=POLLIN, revents=POLLIN}], 7, 100
) = 2
write(2, "<43>Jun 13 10:59:36 smtp03 syslo"..., 97) = 97
accept(1, 0xbfffda90, [256]) = -1 ENOTSOCK (Socket operation
on non-socket)
getpid() = 573
time(NULL) = 1150189176
time(NULL) = 1150189176
poll([{fd=2, events=POLLOUT, revents=POLLOUT}, {fd=8, events=0}, {fd=6,
events=0}, {fd=7, events=0}, {fd=4, events=POLLIN}, {fd=3,
events=POLLIN}, {fd=1, events=POLLIN, revents=POLLIN}], 7, 100
) = 2
write(2, "<43>Jun 13 10:59:36 smtp03 syslo"..., 97) = 97
accept(1, 0xbfffda90, [256]) = -1 ENOTSOCK (Socket operation
on non-socket)
getpid() = 573
time(NULL) = 1150189176
time(NULL) = 1150189176
With lsof, I can see that the file descriptor "1" is open on /dev/null.
I have in my configuration only one source without /dev/null:
source s_all {
internal();
unix-stream("/dev/log");
file("/proc/kmsg" log_prefix("kernel: "));
udp();
};
And there is no reference ton /dev/null in my configuration file so i
don't know why it tries to use it.
Moreover 16 servers have the same configuration file and 4 an other one
but the bug happens on the 20 machines newly installed.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.29-1-p4-smp-ole
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages syslog-ng depends on:
ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an
ii util-linux 2.12p-4sarge1 Miscellaneous system utilities
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.9.11-1
On Mon, Jul 10, 2006 at 11:32:44AM +0200, Frédéric Matray wrote:
> Sorry, I can't try the unstable package because it's for our mail
> cluster in production.
> However, I built a package based on the version 1.6.11 and i haven't got
> the problem anymore.
Thanks; in that case, I'm marking it as closed in unstable, at least, as it's
probably fixed by upstream after the version in sarge.
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
