On Wed, 10 Jan 2018, Marc Haber wrote:
> On Wed, Jan 10, 2018 at 09:19:51AM +0100, Cristian Ionescu-Idbohrn wrote:
> > On Tue, 9 Jan 2018, Marc Haber wrote:
> > >
> > > I have never seen that. Are you running your systemd in some debug mode?
> >
> > Not that I know of. Pid 1 command line is:
> >
> > /lib/systemd/systemd --system --deserialize 24
> >
> > Is there anything else I can check or watch?
>
> Nothing that is inside my systemd foo.
My systemd fu is limited too.
> All my systems just work, and
> your bug report is the first (and only) one about this issue.
Someone must be the first ;) Do you have your `cron' mail sent to
user root? Do you read it?
I have local postfix smtp on this box which forwards root mails to my
account on another box.
> Did the issue appear with atop 2.3.0, or are you having this with older
> versions as well?
See, this box recently came installed with stretch (init=systemd) and
quickly upgraded (by me) to buster. I have no previous experience
with the systemd+atop combination.
Looking at /lib/systemd/system/atop.service, I see:
ExecStart=/usr/share/atop/atop.daily
KillSignal=SIGUSR2
and looking at /usr/share/atop/atop.daily I see:
kill -USR2 `cat $PIDFILE` # final sample and terminate
and try to make sense of it. What process is systemd sending SIGUSR2
to? atop.daily? But atop.daily doesn't catch that signal, does
it? The script is obviously sending SIGUSR2 to the running atop
daemon.
Also, this might also be relevant:
/var/log/syslog.1
-----------------
Jan 10 00:00:01 debian CRON[30253]: (root) CMD (if [ -d "/run/systemd/system"
]; then systemctl restart --quiet atop; else /usr/share/atop/atop.daily \& ; fi)
Jan 10 00:00:01 debian systemd[1]: atop.service: Trying to enqueue job
atop.service/restart/replace
Jan 10 00:00:01 debian systemd[1]: atop.service: Installed new job
atop.service/restart as 28664
Jan 10 00:00:01 debian systemd[1]: atop.service: Enqueued job
atop.service/restart as 28664
Jan 10 00:00:01 debian systemd[1]: atop.service: Changed running -> stop-sigterm
Jan 10 00:00:01 debian systemd[1]: Received SIGCHLD from PID 3225 (atop).
Jan 10 00:00:01 debian systemd[1]: Child 3225 (atop) died (code=exited,
status=0/SUCCESS)
Jan 10 00:00:01 debian systemd[1]: atop.service: Child 3225 belongs to
atop.service
Jan 10 00:00:01 debian systemd[1]: atop.service: Main process exited,
code=exited, status=0/SUCCESS
Jan 10 00:00:01 debian systemd[1]: atop.service: Changed stop-sigterm -> dead
Jan 10 00:00:01 debian systemd[1]: atop.service: Job atop.service/restart
finished, result=done
Jan 10 00:00:01 debian systemd[1]: atop.service: Converting job
atop.service/restart -> atop.service/start
Jan 10 00:00:01 debian systemd[1]: atop.service: Passing 0 fds to service
Jan 10 00:00:01 debian systemd[1]: atop.service: About to execute:
/usr/share/atop/atop.daily
Jan 10 00:00:01 debian systemd[1]: atop.service: Forked
/usr/share/atop/atop.daily as 30255
Jan 10 00:00:01 debian systemd[1]: atop.service: Changed dead -> running
Jan 10 00:00:01 debian systemd[1]: atop.service: Job atop.service/start
finished, result=done
Jan 10 00:00:01 debian systemd[30255]: atop.service: Executing:
/usr/share/atop/atop.daily
Jan 10 00:00:04 debian systemd[1]: Received SIGCHLD from PID 30263 (atop.daily).
Jan 10 00:00:04 debian systemd[1]: Child 30263 (atop.daily) died (code=exited,
status=0/SUCCESS)
Jan 10 00:00:04 debian systemd[1]: atop.service: Child 30263 belongs to
atop.service
/var/log/auth.log
-----------------
Jan 10 00:00:01 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10511
reply_cookie=0 error-name=n/a error-message=n/a
Jan 10 00:00:01 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10512
reply_cookie=0 error-name=n/a error-message=n/a
Jan 10 00:00:01 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10514
reply_cookie=0 error-name=n/a error-message=n/a
Jan 10 00:00:01 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10515
reply_cookie=0 error-name=n/a error-message=n/a
Jan 10 00:00:01 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10518
reply_cookie=0 error-name=n/a error-message=n/a
Jan 10 00:00:01 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10519
reply_cookie=0 error-name=n/a error-message=n/a
Jan 10 00:00:04 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10520
reply_cookie=0 error-name=n/a error-message=n/a
Jan 10 00:00:04 debian systemd-logind[952]: Got message type=signal sender=:1.1
destination=n/a object=/org/freedesktop/systemd1/unit/atop_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10521
reply_cookie=0 error-name=n/a error-message=n/a
Cheers,
--
Cristian
