On Oct 6, 2014 11:00 PM, "Michael Grant" <mgr...@grant.org> wrote: > > I think I've tracked this down to rsyslogd being updated a few days ago and it not restarting. > > So I tried to restart it by hand with /etc/init.d/rsyslogd restart but it failed to stop. So trying to understand why it didn't stop, I tried running start-stop-daemon manually and here's what I see: > > # start-stop-daemon -v --stop --retry=TERM/30/KILL/5 --pidfile /var/run/rsyslogd.pid --exec /usr/sbin/rsyslogd > No /usr/sbin/rsyslogd found running; none killed. > # ps ax | grep /usr/sbin/rsyslogd > 3401 ? Sl 2:36 /usr/sbin/rsyslogd -c5 > 9922 pts/3 S+ 0:00 grep -i --color /usr/sbin/rsyslogd > # more /var/run/rsyslogd.pid > 3401 > > Why would start-stop-daemon not be able to find /usr/sbin/rsysogd? It's spelled properly, it's pid is properly in the pid file. (Sure, I can kill it by hand but I really want to know why start-stop-daemon can't kill it because there is probably some underlying problem that needs solving!) > > On Mon, Oct 6, 2014 at 8:06 PM, Joe <j...@jretrading.com> wrote: >> >> On Mon, 6 Oct 2014 19:51:38 +0100 >> Michael Grant <mgr...@grant.org> wrote: >> >> > When logrotate fired this month, almost all of my logs remain at zero >> > length and the .1 log continues to grow. For example: >> > >> > ls -l /var/log >> > ... >> > -rw-r----- 1 root adm 0 Oct 5 06:25 messages >> > -rw-r----- 1 root adm 4938 Oct 6 06:56 messages.1 >> > ... >> > -rw-r----- 1 root adm 0 Oct 1 06:25 syslog >> > -rw-r----- 1 root adm 15767734 Oct 6 13:17 syslog.1 >> > >> > I'm running debian wheezy 7.6 on two separate systems. >> > >> > I'm guessing that logrotate didn't complete to restart the daemons. >> > When I run logrotate -dv, I see no errors. >> > >> > I update both with cron-apt and I would not be surprised if one of the >> > updates caused this but I'm not sure. >> > >> > Has anyone else seen this? Any idea how to fix it so this works next >> > month? >> >> Mine rotate every day, and seem to be doing so quite happily, but they >> are on a server and it's run by the default cron system. >> >> Have you tried running logrotate manually without -d? It's possible an >> update has caused a permissions issue somewhere, and you may get clues >> from the console. >> >> -- >> Joe >> >> >> -- >> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org >> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org >> Archive: https://lists.debian.org/20141006200646.394fc...@jresid.jretrading.com > >
Hi Michael, If I understood correctly, the only issue was actually that the daemon wasn't running at all; so when it tried to stop it, there wasn't anything to stop. Hopefully it is running by now :-)
