Hi Nicolas, > > Also thanks for trying this out. I think I now know where the problem is > > rooted. It's probably due to the different startup sequence in rsyslog > > v7. I will investigate, hopefully this week. Pls ping me if you haven't > > heard back by next Wednesday.
Unfortunately, I was wrong in regard to the root cause. I have analyzed it now, but the situation does not occur :-( So we are back to troubleshooting. To aid this, I have improved support debug logging in background mode. You can now use: $ export RSYSLOG_DEBUG="debug " $ export RSYSLOG_DEBUGLOG="/path/to/debug.log" $ rsyslogd ...your usual options... This will make rsyslogd auto-background (assuming you do NOT use -n inside your option set!) AND write debug information to debug.log. Writing to debug.log will continue even after the process has auto-backgrounded itself. Most importantly, we can now see what happens with the relp listener. Please note that I also tried to reproduce your problem, but it never happened in my environment. To use the new debug support, you need to apply this patch: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=0114b531b38b16db98b04b680017d6c758987fd9 you need to apply it on top of the current v7-stable. I probably need a full debug log to make sense out of it. Feel free to mail it to me privately. Looking forward to your feedback. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
