>From looking at the sysklogd package in Ubuntu Hardy (1.5-1ubuntu1), this 
>appears to be fixed:
/etc/cron.daily/sysklogd saves the logs and then calls "/etc/init.d/sysklogd 
reload-or-restart".

In Dapper (sysklogd 1.4.1-17ubuntu7) (and Edgy) "reload-or-restart" is 
implemented as:
  restart|force-reload|reload-or-restart|reload)
    log_begin_msg "Restarting system log..."
    start-stop-daemon --stop --quiet --exec $binpath --pidfile $pidfile
    sleep 1
    start-stop-daemon --start --quiet --exec $binpath -- $SYSLOGD
    log_end_msg $?
    ;;

But already in Feisty it is:
  reload-or-restart)
    if running
    then
        $0 reload
    else
        $0 start
    fi
    ;;

There appear to be quite a lot of other fixes/improvements in the
current version's init script, so I think a SRU for Dapper makes a lot
of sense, given the impact.

Please note, that the linked Debian bug (#279120) is only slightly related, 
because it talks about SIGHUP for reloading already and that also does not 
appear to be the problem of Mike.
It appears however be the problem this bug was all about, also the comment from 
Kai (on Dapper).

Mike, the rotation in sysklogd works as follows: save the logs and after that 
send "kill -HUP". This applies to the logfiles given by "syslogd-listfiles 
--weekly" for the weekly syslog cron job and "syslogd-listfiles" for the daily 
one.
I don't know if a SIGHUP can get lost, at least the logs have been rotated 
before. (syslogd will write to the .0 (uncompressed file) until it creates the 
new one.)

Please look at the last line of /var/log/syslog and syslog.0 in case of syslogd 
restart failure.
Please also check, if "logrotate" or something similar is interfering.

I hope I did not cause additional confusion and I think other issues
separate from this problem should get attacked in a new bug to stay
focused.

** Changed in: sysklogd (Ubuntu)
   Importance: Undecided => High
       Status: Confirmed => Fix Released

-- 
syslog does not restart after rotating logfile
https://bugs.launchpad.net/bugs/49165
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to