Are you dropping privileges? A common mistake is to use wrong file permissions, and this leads to exactly what you describe. Rainer
> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Radu Gheorghe > Sent: Tuesday, December 18, 2012 9:48 AM > To: rsyslog-users > Subject: Re: [rsyslog] rsyslog not working after receiving HUP signal > > Hi, > > I'm not sure what HUP does in 5.8, but maybe someone else can shed some > light on this. > > I think it would help to share the piece of the debug log that shows > what's > happening when you do a HUP on your machine. > > Also, a "workaround" would be to restart rsyslog instead of sending HUP > to > it. > > Best regards, > Radu > > > 2012/12/18 Arnau Bria <[email protected]> > > > Hi all, > > > > I've some SL 6.3 hosts and I'm noticing that some of them have some > > problems with rsyslog. After they rotate its logs, and they recieve > HUP > > signal, I have no more info in messages log file: > > > > > > # cat /etc/logrotate.d/syslog > > /var/log/cron > > /var/log/maillog > > /var/log/messages > > /var/log/secure > > /var/log/spooler > > { > > sharedscripts > > postrotate > > /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` > > 2> /dev/null || true endscript > > } > > > > # date > > Mon Dec 17 09:28:07 CET 2012 > > > > # tail /var/log/messages > > Dec 16 03:38:01 coresrv05 xinetd[23755]: EXIT: rsync status=0 > pid=6355 > > duration=0(sec) Dec 16 03:39:57 coresrv05 RTTEST: The actual > HTTP_HOST > > (172.17.16.27) does NOT match the configured WebDomain > > (rt-test.linux.crg.es). Perhaps you should Set($WebDomain, > > '172.17.16.27'); in RT_SiteConfig.pm, otherwise your internal links > may > > be broken. (/opt/rt4/sbin/../lib/RT/Interface/Web.pm:1193) Dec 17 > > > > If I restart the service I only see the restart message... nothing > else > > later: > > > > 09:23:07 coresrv05 kernel: Kernel logging (proc) stopped. Dec 17 > > 09:23:07 coresrv05 rsyslogd: [origin software="rsyslogd" > > swVersion="5.8.10" x-pid="1236" x-info="http://www.rsyslog.com";] > > exiting on signal 15. [...] > > > > > > Now I'm running syslog in debug mode, but I find no useful > information > > (at least, I do not understand it as useful :-) ). > > > > A reboot leaves syslog working fine, but I wouldn't like to reboot > all > > my hosts for this reason... > > Anyone has seen this before? any advice? > > > > rsyslog-5.8.10-2.el6.x86_64 > > > > TIA, > > Cheers, > > Arnau > > _______________________________________________ > > 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. _______________________________________________ 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.
