I got the complete debug log. A potential issue may be that the RELP client can not connect to the server (did firewall drop connection request)? At least this is where the code hangs. This may be the result of some data race that occurred previously.
Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Rainer Gerhards > Sent: Wednesday, March 30, 2011 2:53 PM > To: rsyslog-users > Subject: Re: [rsyslog] Rsyslog doesn't terminate after kill -15 > > Well, three things: > > 1) the worker hangs, but the debug log is not complete enough to know > why > 2) you are pressing ctl-c 5 times, what will trigger the actual abort > (but > don't mind, it would very probably not have been able to recover) > 3) I strongly think the root cause is the same as in this bug tracker: > http://bugzilla.adiscon.com/show_bug.cgi?id=238 > You are reporting a race condition and memory corruption there, and if > this > happens all kinds of strange things can happen. > > I may be wrong with 3), but I need a complete debug log to at least > have a > chance to try that. You can mail me a complete log if you like. Pleas > zip/tar > before sending. > > Rainer > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Marcin Miroslaw > > Sent: Wednesday, March 30, 2011 2:28 PM > > To: [email protected] > > Subject: Re: [rsyslog] Rsyslog doesn't terminate after kill -15 > > > > I've started rsyslogd without backgrounding him, after hit ctrl+c i > > got: > > > > [...] > > 5980.477298473:9790a960: strm 0x176c7d78: file 3 write wrote 206 > bytes > > 5980.477310792:9790a960: strm 0x17958838: file > > 15(/var/log/apache2/error_log) closing > > 5980.477337492:9790a960: main Q: entry added, size now log 9028, phys > > 9060 entries > > 5980.477347958:9790a960: main Q: EnqueueMsg advised worker start > > 5980.477356981:9790a960: Terminating main queue... > > 5980.477366048:9790a960: main Q: initiating worker thread shutdown > > sequence > > 5980.477376322:9790a960: main Q: trying shutdown of regular workers > > 5980.477447838:9790a960: sent SIGTTIN to worker thread 0x9584eb70 > > 5980.477460078:9790a960: main Q:Reg: waiting 1499ms on worker thread > > termination, 1 still running > > 5981.977455494:9790a960: main Q:Reg: timeout waiting on worker thread > > termination > > 5981.977487009:9790a960: sent SIGTTIN to worker thread 0x9584eb70 > > 5981.977500445:9790a960: main Q: regular shutdown timed out on > primary > > queue (this is OK) > > 5981.977509906:9790a960: main Q: setting EnqOnly mode > > 5981.977520053:9790a960: main Q: trying immediate shutdown of regular > > workers (if any) > > 5981.977532050:9790a960: sent SIGTTIN to worker thread 0x9584eb70 > > 5981.977543146:9790a960: main Q:Reg: waiting 1000ms on worker thread > > termination, 1 still running > > 5982.977598860:9790a960: main Q:Reg: timeout waiting on worker thread > > termination > > 5982.977628445:9790a960: sent SIGTTIN to worker thread 0x9584eb70 > > 5982.977641142:9790a960: main Q: immediate shutdown timed out on > > primary > > queue (this is acceptable and triggers cancellation) > > 5982.977650982:9790a960: main Q: checking to see if we need to cancel > > any worker threads of the primary queue > > 5982.977662054:9790a960: sent SIGTTIN to worker thread 0x9584eb70, > > giving it a chance to terminate > > 5982.987739596:9790a960: cooperative worker termination failed, using > > cancellation... > > 5982.987751923:9790a960: wti 0x176a9d10: canceling worker thread > > > > ^C6175.499130974:9790a960: DoDie called. > > ^C6177.569066745:9790a960: DoDie called. > > ^C6178.119066849:9790a960: DoDie called. > > ^C6178.509119532:9790a960: DoDie called. > > RELP/10.10.10.256178.509150207:9790a960: > > > > > > > > Signal 6 (SIGABRT) occured, execution must be terminated. > > > > > > > > 6178.533316523:9790a960: Mutex log for all known mutex operations: > > 6178.533329944:9790a960: If the call trace is empty, you may want to > > ./configure --enable-rtinst > > 6178.533338708:9790a960: > > > > To submit bug reports, visit http://www.rsyslog.com/bugs > > > > 6178.533352061:9790a960: > > > > To submit bug reports, visit http://www.rsyslog.com/bugs > > > > Terminated > > > > > > I can't reproduce problem in all tries. It depend on <something more> > > or > > it's a little randomly :( > > But problem isn't nice, logrotate can't do its job, because rsyslogd > > isn't properly restarted. I suspect that sometimes doesn't write to > > file > > defined in way: > > :programname, isequal, "named" /var/log/named/named.log > > > > > > & ~ > > > > Regards! > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
