[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [leafnode-list] Logging Stopped; restart syslog needed



On Fri, 04 Jul 2003 18:14:56 +0200, Matthias Andree wrote
> "Mike Vanecek" <leaf_list@xxxxxxxxxxxxx> writes:
> 
> > I use to get entries in my newslog whenever texpire, fetchnews, and so on did
> > their activities. However, ever since the logs rotated on 1 July, no entries
> > were going to my newslog. The last entries, as shown below, were made on July
> > 1 before the rotation. Everything is running as it should except no logging. I
> > restarted xinetd, but it did not help. I then restarted syslog (service syslog
> > restart) and news started logging again.
> 
> [...]
> 
> > # Newslog
> > /var/log/newslog  {
> >     missingok
> >     compress
> >     size 2M
> >     rotate 3
> >     create 0660 root news
> > }
> 
> This doesn't send SIGHUP to syslogd, does it?

No, but I changed the execution order around so that this one is rotated
before the call to rotate syslog (which does do a syslog restart). We will see
what happens next month ...

> 
> Most syslogd implementations will close their files and reopen them 
> as they receive SIGHUP, so chances are that either your syslog 
> logged to a file that logrotate or newsyslog or what it's called had 
> just deleted, so it got lost at syslogd restart (not that any 
> process except debugfs or syslogd could have accessed it), or it has 
> logged to newslog.1.gz, after the compressed data (to figure, try 
> "tail newslog.1.gz").

Nothing was logged after 1 Jul (I posted that info in the first post). The
logging just stopped without anything being indicated in any of the logs.

> A careful log rotation software will rename the file away, send 
> SIGHUP to syslogd, sleep a while until the new file has been written 
> to, and only then compress the old log.

I am using standard RH 9 stuff. I guess I could put the above entry in with
/etc/logrotate.d/syslog ... That would probably resolve it.

> 
> -- 
> Matthias Andree
> 
> -- 
> leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
> To unsubscribe, send mail with "unsubscribe" in the subject to the list

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list