Hi, On 2014-10-20 08:01, Rainer Gerhards wrote: > I have an idea... some time ago we had problems that the child > process (the one backgrounded ) had problems signaling the parent > (startup process) that it finished initializing.
Sounds like this could be the problem. We are starting rsyslog with start-stop-daemon using the "--wait 1000" parameter: > Wait milliseconds after starting and check that daemon is still > running. Useful for daemons that check configuration after forking or > stopping race conditions where the pidfile is written out after > forking. Because this check doesn't kicks in, it seems like that the signaling did not occur yet... > It would be great if Whissi could try out any patch that will result > from that work... No problem. I am glad to help. That's why I set up a VM to reproduce the problem... On 2014-10-20 11:04, Rainer Gerhards wrote: > While implementing this, I think I have found a potential cause. > It's different from what I thought, but it can lead to non-signaling > the startup process, so that it hangs. In any case, I'll now also > change the way the communication is handled. I am half through in any > case ;) Sounds interesting. Give me a ping when there's something I can test. -Thomas _______________________________________________ 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.
