[syslog-ng] supervise/syslog-ng exits

[Balazs Scheidler]

On Mon, 2009-12-14 at 17:43 +0000, Kārlis Repsons wrote:
> On Monday 14 December 2009 07:07:37 Balazs Scheidler wrote:
> > On Fri, 2009-12-11 at 19:11 +0000, Kārlis Repsons wrote:
> > > People,
> > >
> > > I wonder why is there some two messages like this in errors log each day:
> > > supervise/syslog-ng[28806]: Daemon exited gracefully, not restarting;
> > > exitcode='0'
> > >
> > > ?
> > >
> > > What are the possible reasons and what should be done?
> > 
> > something has stopped syslog-ng. if it is intended, nothing needs to be
> > done, if it isn't, then you need to find out what stops syslog-ng.
> > 
> > the exitcode of 0 means that it was an intentional stop, not an abort or
> > a segfault.
> Is it necessarily syslog-ng itself? I have a problematic errors reporting 
> script connected to syslog-ng as a destination, maybe it exits and causes 
> this? Otherwise I wouldn't like this a lot, because just a minute ago was 
> "exit 0", but when I look, syslog-ng is working just fine... And no stop/start 
> of syslog-ng is logged. And that script WAS restarted. 
> Ok, at this point, I presume, its that script, which causes it...

The supervisor should only print this log message if syslog-ng itself
has finished. Can you confirm that this is not the case?

Thanks.


-- 
Bazsi