rsyslog is crashing on me at some point. I'm getting ready to run it under gdb to see where, but I thought I'd report this here first. It just stop s running, and, afaik, doesn't drop a core. Basically, I just need a front-end rsyslog server to decrypt the incoming data and pass it on. If I do unencrypted, I don't believe it crashes. I've seen some "overflow" messages shortly before crashing, so perhaps we're overflowing somewhere. I'll probably also do a valgrind pass on it. I'll let you know what I find, or, if someone sees something wrong with my conf file that would cause a problem, please let me know.
I'm also simply invoking rsyslog as rsyslogd -c4 thx I've tried: 5.3.5 5.2.0 4.4.2 4.5.7 with the following conf file: $DefaultNetStreamDriver gtls $DefaultNetStreamDriverCAFile /export/rsyslog/certs/ca.pem $DefaultNetStreamDriverCertFile /export/rsyslog/certs/cert.pem $DefaultNetStreamDriverKeyFile /export/rsyslog/certs/key.pem $WorkDirectory /export/rsyslog/spool $ActionQueueType LinkedList $ActionQueueFileName rsyslog-fwd $ActionResumeRetryCount -1 $ActionQueueSaveOnShutdown on $ModLoad imtcp $ModLoad imuxsock $ModLoad lmnsd_gtls $InputTCPServerStreamDriverMode 1 $InputTCPServerStreamDriverAuthMode anon $InputTCPServerRun 80 *.* @syslog.ooma.com:514 _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
