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 hvae 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 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. Anyone has seen this before? any advice? TIA, Cheers, Arnau