This affects the current development track for Saucy. I have a minimal server install of 64-bit 13.10 and since logrotate ran at 0630 there have been no updates to any log files. Restarting rsyslog hasn't improved things. some log files seem to be owned by "messagebus:adm", rsylog is user "syslog" and only a member of "syslog" group.
# date Thu Aug 22 14:11:59 BST 2013 # ls -altr /var/log/ total 1700 drwxr-xr-x 2 root root 4096 May 24 2012 sysstat drwxr-xr-x 2 ntp ntp 4096 Apr 4 23:25 ntpstats drwxr-xr-x 2 root root 4096 Apr 25 19:07 fsck drwxr-xr-x 2 root root 4096 Apr 25 19:07 apt drwxr-xr-x 3 root root 4096 Apr 25 19:14 installer drwxr-xr-x 2 root root 4096 Apr 25 19:14 news drwxr-xr-x 2 landscape root 4096 Apr 25 19:14 landscape drwxr-xr-x 2 root root 4096 Apr 25 19:14 ConsoleKit drwxr-xr-x 2 root root 4096 Apr 25 19:16 unattended-upgrades -rw-r----- 1 messagebus adm 0 Apr 26 17:14 ufw.log -rw-r----- 1 messagebus adm 0 Apr 26 17:14 mail.log -rw-r----- 1 messagebus adm 0 Apr 26 17:14 mail.err -rw-rw---- 1 root utmp 0 Apr 26 17:14 btmp -rw-r--r-- 1 root root 0 Apr 26 17:14 bootstrap.log -rw-r--r-- 1 root root 0 Apr 26 17:14 boot.log -rw-r----- 1 root adm 0 Apr 26 17:14 boot -rw-r----- 1 messagebus adm 0 Apr 26 17:14 auth.log -rw-r--r-- 1 root root 0 Apr 26 17:14 aptitude -rw-r----- 1 root adm 4667 Aug 21 01:31 dmesg.4.gz -rw-r----- 1 root adm 4744 Aug 21 02:57 dmesg.3.gz -rw-r----- 1 root adm 4663 Aug 21 03:26 dmesg.2.gz drwxr-xr-x 4 root root 4096 Aug 21 04:24 dist-upgrade -rw-r----- 1 root adm 4704 Aug 21 04:27 dmesg.1.gz drwxr-x--- 2 root adm 4096 Aug 21 04:37 apache2 -rw-r----- 1 root adm 11817 Aug 21 04:46 dmesg.0 -rw-r--r-- 1 root root 285844 Aug 21 04:56 udev -rw-r----- 1 root adm 12150 Aug 21 04:57 dmesg drwxr-xr-x 15 root root 4096 Aug 21 05:06 .. -rw-r--r-- 1 root root 32064 Aug 21 06:52 faillog drwxr-xr-x 2 root root 4096 Aug 21 07:17 dnssec-tools -rw-r----- 1 messagebus adm 82150 Aug 21 18:25 kern.log -rw-rw-r-- 1 root utmp 25344 Aug 22 04:47 wtmp -rw-rw-r-- 1 root utmp 292584 Aug 22 04:47 lastlog -rw-r--r-- 1 root root 417434 Aug 22 04:48 dpkg.log -rw-r--r-- 1 root root 14003 Aug 22 04:48 alternatives.log drwxr-xr-x 2 root root 4096 Aug 22 06:29 upstart -rw-r----- 1 messagebus adm 741465 Aug 22 06:29 syslog.1 -rw-r----- 1 messagebus adm 0 Aug 22 06:29 syslog drwxr-xr-x 15 root root 4096 Aug 22 06:29 . # tail -1 /var/log/syslog.1 Aug 22 05:29:03 hush rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2647" x-info="http://www.rsyslog.com";] rsyslogd was HUPed # ls -altr /proc/$(pidof rsyslogd)/fd/ total 0 dr-xr-xr-x 8 syslog syslog 0 Aug 22 14:04 .. dr-x------ 2 root root 0 Aug 22 14:05 . lr-x------ 1 root root 64 Aug 22 14:05 4 -> /proc/kmsg lrwx------ 1 root root 64 Aug 22 14:05 3 -> socket:[59553] lrwx------ 1 root root 64 Aug 22 14:05 0 -> socket:[59551] ** Changed in: rsyslog (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/940030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
