Marcin, I just had a look at the debug log you sent, but this file looks strange. Is it a combination from a log file and a partial debug log? In any case, can you send me just a plain debug log, right from the startup. The startup part - where I assume the problems show up - seems to be missing in the file you sent. Also, I don't see where the message in question is emitted in the debug log. I'd say that I need only the startup portion up until where the message first occurs and then, let's say, 10,000 more lines. That makes handling the debug log hopefully a bit easier.
Thanks, Rainer > -----Original Message----- > From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog- > boun...@lists.adiscon.com] On Behalf Of Marcin Miroslaw > Sent: Wednesday, August 03, 2011 10:51 PM > To: rsyslog@lists.adiscon.com > Subject: Re: [rsyslog] imudp activation failure - was: Remote > syslogging through a (broken) VPN > > Hello! > I'm makeing little bump up, because new behavior appears. Rsyslog(git) > logs many (about 1000) lines with message: > "rsyslogd: Cannot read proc file system: 9 - Bad file descriptor." > > All logs starts as below: > 2011-08-03T21:53:26.185038+02:00 serwerek rsyslogd: [origin > software="rsyslogd" swVersion="6.3.4" x-pid="23935" > x-info="http://www.rsyslog.com";] start > 2011-08-03T21:53:26.139975+02:00 serwerek rsyslogd-2184: action '*' > treated as ':omusrmsg:*' - please change syntax, '*' will not be > supported in the future [try http://www.rsyslog.com/e/2184 ] > 2011-08-03T21:53:26.140977+02:00 serwerek rsyslogd: imklog 6.3.4, log > source = /proc/kmsg started. > 2011-08-03T21:53:26.141044+02:00 serwerek rsyslogd: imudp: no listeners > could be started, input not activated. > : No such file or directory > 2011-08-03T21:53:26.141051+02:00 serwerek rsyslogd3: activation of > module imudp.so failed [try http://www.rsyslog.com/e/-3 ] > 2011-08-03T21:53:26.179159+02:00 serwerek rsyslogd-2040: fatal error on > disk queue 'action 1 queue[DA]', emergency switch to direct mode [try > http://www.rsyslog.com/e/2040 ] > 2011-08-03T21:53:26.185922+02:00 serwerek rsyslogd: Cannot read proc > file system: 9 - Bad file descriptor. > 2011-08-03T21:53:26.185936+02:00 serwerek rsyslogd: Cannot read proc > file system: 9 - Bad file descriptor. > 2011-08-03T21:53:26.185945+02:00 serwerek rsyslogd: Cannot read proc > file system: 9 - Bad file descriptor. > [again and again bad file descirptor] > > But it doesn't happen always, more often while OS is starting. > (rsyslog-5.6.5 works ok). I'm attaching log, unfortunatelly this log > was > created when rsyslog didn't throws messages "cannot read proc". It > contains only problem with module UDP. > > Regards, > Marcin. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
