Hello all, I found reference to this error for people using syslog-ng 1.4.x, but looking through the list archives, I don't see any reference to it recently. I start syslog-ng and after a few minutes, I get something similar to: syslog:io.c:263: failed assertion `i == nfds' I got this with syslog-ng 1.5 and 1.6 rc3. Both are using libol 0.3.10. This is on a base redhat 9 install. Any ideas? -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com
On Thu, Sep 04, 2003 at 02:58:31PM -0400, Dennis Skinner wrote:
Hello all,
I found reference to this error for people using syslog-ng 1.4.x, but looking through the list archives, I don't see any reference to it recently.
I start syslog-ng and after a few minutes, I get something similar to:
syslog:io.c:263: failed assertion `i == nfds'
I got this with syslog-ng 1.5 and 1.6 rc3. Both are using libol 0.3.10. This is on a base redhat 9 install.
Hmm.. this means that an I/O callback adds another fd to the main poll loop. Can you show your config file? -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
On Mon, 2003-09-08 at 12:51, Balazs Scheidler wrote:
Hmm.. this means that an I/O callback adds another fd to the main poll loop. Can you show your config file?
I think I am no longer getting this error with 1.6. (although I'm almost positive I got it the first time I ran it). Now it is working fine for a few minutes and then just stops logging. No error messages and the process does not die. It just stops functioning. Will do further testing tonight or tomorrow (got pulled away on another project). I am using same config file for 1.5 and 1.6. Here it is: ###### options { long_hostnames(off); sync(0); }; source s_local { internal(); unix-stream("/dev/log"); }; source s_kmsg { file("/proc/kmsg"); }; source s_beb_udp { udp(ip("10.1.2.3") port(514)); }; source s_feb_udp { udp(ip("192.168.1.2") port(514)); }; destination d_sort_program_host { file("/var/log/$HOST/$PROGRAM.$MONTH$DAY$YEAR" group("logs") perm(0640) create_dirs(yes) dir_perm(0750) ); }; destination d_sort_host { file("/var/log/$HOST/$MONTH$DAY$YEAR" group("logs") perm(0640) create_dirs(yes) dir_perm(0750) ); }; log { source(s_local); source(s_kmsg); destination(d_sort_program_host); }; log { source(s_beb_udp); destination(d_sort_program_host); }; log { source(s_feb_udp); destination(d_sort_host); }; ###### -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com
Ok, just got it again. If running without chroot, I get this: syslog-ng: io.c:270: io_iter: Assertion `i == nfds' failed. and it dies. If I use the chroot option, it will just stop logging, but not die. Thoughts? -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com
On Tue, Sep 09, 2003 at 11:08:04AM -0400, Dennis Skinner wrote:
On Mon, 2003-09-08 at 12:51, Balazs Scheidler wrote:
Hmm.. this means that an I/O callback adds another fd to the main poll loop. Can you show your config file?
I think I am no longer getting this error with 1.6. (although I'm almost positive I got it the first time I ran it). Now it is working fine for a few minutes and then just stops logging. No error messages and the process does not die. It just stops functioning. Will do further testing tonight or tomorrow (got pulled away on another project).
don't you happen to run syslog-ng reading /proc/kmsg and klogd at the same time? -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
On Wed, 2003-09-10 at 09:02, Balazs Scheidler wrote:
don't you happen to run syslog-ng reading /proc/kmsg and klogd at the same time?
That wouldn't be these, would it? source s_local { internal(); unix-stream("/dev/log"); }; source s_kmsg { file("/proc/kmsg"); }; I see /proc/kmsg, but is klogd the same as using /dev/log? Thanks! -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com
On Wed, 2003-09-10 at 12:27, Dennis Skinner wrote:
On Wed, 2003-09-10 at 09:02, Balazs Scheidler wrote:
don't you happen to run syslog-ng reading /proc/kmsg and klogd at the same time?
That wouldn't be these, would it?
source s_local { internal(); unix-stream("/dev/log"); }; source s_kmsg { file("/proc/kmsg"); };
I see /proc/kmsg, but is klogd the same as using /dev/log?
/proc/kmsg and klogd read the same thing. An ugly possible event: if you have both of these going on at the same time, a linux kernel could eventually run out of space writing to kmsg and be unable to dump the log. It will stall, but not crash, your system. The only way I found to free it was alt-scrollock from a console. Turn one of them off. I suggest turning off klogd and using /proc/kmsg in stead. -sv
On Wed, 2003-09-10 at 12:29, seth vidal wrote:
I see /proc/kmsg, but is klogd the same as using /dev/log?
/proc/kmsg and klogd read the same thing.
understood. but is using unix-stream("/dev/log") the same as klogd? is this redundant? source s_local { internal(); unix-stream("/dev/log"); }; source s_kmsg { file("/proc/kmsg"); }; I may be mistaken, but kmsg is for kernel messages right? And other apps use /dev/log. So, /dev/log would have info that kmsg doesn't. Or am I missing something? -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com
On Wed, 2003-09-10 at 18:42, Dennis Skinner wrote:
On Wed, 2003-09-10 at 12:29, seth vidal wrote:
I see /proc/kmsg, but is klogd the same as using /dev/log?
/proc/kmsg and klogd read the same thing.
understood. but is using unix-stream("/dev/log") the same as klogd?
is this redundant?
source s_local { internal(); unix-stream("/dev/log"); }; source s_kmsg { file("/proc/kmsg"); };
This is fine, both sources are needed, but you should not run klogd in addition to syslog-ng. -- Bazsi
On Thu, 2003-09-11 at 04:20, Balazs Scheidler wrote:
This is fine, both sources are needed, but you should not run klogd in addition to syslog-ng.
Ah! Now I understand. I commented out the /dev/log source and it has been working. That would be the one klogd is using. It all make sense now. Thanks! -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com
On Thu, 2003-09-11 at 11:17, Dennis Skinner wrote:
On Thu, 2003-09-11 at 04:20, Balazs Scheidler wrote:
This is fine, both sources are needed, but you should not run klogd in addition to syslog-ng.
Ah! Now I understand. I commented out the /dev/log source and it has been working. That would be the one klogd is using. It all make sense now.
man klogd search for /proc/kmsg that's what klogd is reading. -sv
participants (3)
-
Balazs Scheidler
-
Dennis Skinner
-
seth vidal