Well, in essence rsyslog is told to terminate and so it does. Maybe a script sending sigkill?
Sent from phone, thus brief. Am 03.12.2013 19:59 schrieb "Trent Creekmore" <[email protected]>: > > This on CentOS 64 using the provided repo which as version 5.8.10 and on > the > rsyslog repo using version 7.4.6. > > SELinux is not enabled and no modifications to the configuration file has > been done. > > Not sure why this is happening. > > I have put the debug output to pastebin using version 7.4.6: > > > http://pastebin.com/psnau6sY > > > > _______________________________________________ > 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. > _______________________________________________ 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.
