I agree, it looks strange (very strange indeed). I am checking if it could be related to the root cause (or just be a debug-level artifact that slipped through - that may be the case, because discard is the only action which does NOT have any strings at all). Anyhow, it provides me at least another clue where to look at.
Thanks Rainer > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:rsyslog- > [EMAIL PROTECTED] On Behalf Of Patrick von der Hagen > Sent: Monday, September 10, 2007 2:39 PM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog 1.19.5 released > > Am Freitag, den 07.09.2007, 19:20 +0200 schrieb Patrick von der Hagen: > [...] > > Crash of 1.19.5 after less than 30 minutes. Stack-trace seems to be > > quite "normal", however, I've been lucky and captured some > > strace-information. Not sure wheter that could be helpful. > I compiled 1.19.5 with "--enable-debug" now and got the following > problems: > > Sep 10 14:24:26 mail11 rsyslogd:could not load module > '/usr/local/lib/rsyslog/ommysql.so', > dlopen: /usr/local/lib/rsyslog/ommysql.so: cannot open shared object > file: No such file or directory > Sep 10 14:24:26 mail11 rsyslogd:the last error occured > in /etc/rsyslog.conf, line 29 > > No idea why it tries "/usr/local/lib", the lib has been installed to > "/lib" or "/opt/rsyslog/lib/rsyslog/". Hmmm, "/lib" is from > 1.18.something, I didn't tidy up properly. > > Anyway, I currently don't use logging to MySQL, so I uncommented > "$ModLoad MySQL". > > > Next try: > [EMAIL PROTECTED] log]# /opt/rsyslog/sbin/rsyslogd -r514 -d > [...] > 1084229952: Lone worker is running... > 1084229952: Called fprintlog, logging to builtin-file > (/home/local/log/all) > 1084229952: programname filter 'rsyslogd' does not match 'spamd' > Filter: check for property 'msg' (value ' prefork: child states: > BBBBBBBIIBBBBBBB ') contains 'prefork: child states': TRUE > 1084229952: Called fprintlog, logging to builtin-discardrsyslogd: > omdiscard.c:70: doAction: Assertion `ppString != ((void *)0)' failed. > Aborted > > > That's getting a little bit strange now, it has been caused by this > rsyslog.conf-lines: > !spamd > :msg, contains, "prefork: child states" ~ > > > Some other crashes relate to other lines, all of them end with "~". So > I > uncommented all of them. > > Those problems are strange, but if those issues were related to my > "normal" rsyslog-crashes, rsyslog would not have been able to run up to > two hours and would certainly have crashed almost instantly. > > It's been running for several minutes now... > > -- > CU, > Patrick. > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
