Bug#834226: atop: prevents clean and fast shutdown

2016-12-17 Thread Marc Haber 
tags #834226 pending
thanks

On Wed, Oct 26, 2016 at 11:30:42AM +0200, Marc Haber wrote:
> I'll forward this upstream.

Upstream's version 2.2.5 has some code to improve SIGTERM behavior. I
am closing this bug with the new upload. If the problem persists,
please feel free to re-open.

Greetings
Marc

Bug#834226: atop: prevents clean and fast shutdown

2016-10-26 Thread Marc Haber 
On Wed, Oct 26, 2016 at 11:26:37AM +0200, Vincent Lefevre wrote:
> On 2016-10-26 10:53:43 +0200, Marc Haber wrote:
> > Can you reproduce this? If so, I'd like you to attach an strace to the
> > atopacct process (strace -f -p  -s 2000 -o
> > strace.atopacctd) and attach the resulting file. I'd like to see
> > whether atopacctd gets the SIGTERM and how it reacts.
> 
> I've also added the -t option to get the time:

Great, thanks, I keep forgetting this.

> 910   11:22:14 recvfrom(5, 0x7ffe6905d290, 16000, 0, NULL, NULL) = ? 
> ERESTARTSYS (To be restarted if SA_RESTART is set)
> 910   11:22:29 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=1, 
> si_uid=0} ---
> 910   11:22:29 --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=1, 
> si_uid=0} ---
> 910   11:22:29 rt_sigreturn({mask=[]})  = 45
> 910   11:22:29 recvfrom(5,  
> 910   11:22:49 +++ killed by SIGKILL +++
> 
> Note that I had reduced the systemd timeout to 20 seconds.
> You can see it above.

So the process receives the SIGTERM and doesn't act on it.

And, incidentally, when trying to obtain an strace of an atopacctd
terminating properly, mine is not terminating as well, so my strace is
identical.

I'll forward this upstream.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#834226: atop: prevents clean and fast shutdown

2016-10-26 Thread Vincent Lefevre 
Hi Marc,

On 2016-10-26 10:53:43 +0200, Marc Haber wrote:
> Can you reproduce this? If so, I'd like you to attach an strace to the
> atopacct process (strace -f -p  -s 2000 -o
> strace.atopacctd) and attach the resulting file. I'd like to see
> whether atopacctd gets the SIGTERM and how it reacts.

I've also added the -t option to get the time:

910   11:22:14 recvfrom(5, 0x7ffe6905d290, 16000, 0, NULL, NULL) = ? 
ERESTARTSYS (To be restarted if SA_RESTART is set)
910   11:22:29 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=1, 
si_uid=0} ---
910   11:22:29 --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=1, 
si_uid=0} ---
910   11:22:29 rt_sigreturn({mask=[]})  = 45
910   11:22:29 recvfrom(5,  
910   11:22:49 +++ killed by SIGKILL +++

Note that I had reduced the systemd timeout to 20 seconds.
You can see it above.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#834226: atop: prevents clean and fast shutdown

2016-10-26 Thread Marc Haber 
Hi Vincent,

thanks for your help. You're most helpful.

On Wed, Oct 26, 2016 at 10:27:37AM +0200, Vincent Lefevre wrote:
> root@cventin:/home/vlefevre# ps -aef|grep atop
> root   908 1  0 10:17 ?00:00:00 /usr/sbin/atopacctd
> root   963 1  0 10:17 ?00:00:00 /usr/bin/atop -a -R -w 
> /var/log/atop/atop_20161026 600
> root  1897  1755  0 10:18 pts/000:00:00 grep atop
> root@cventin:/home/vlefevre# invoke-rc.d atopacct stop
> 
> This one takes time to stop. In the journal, I can see:
> 
> Oct 26 10:18:56 cventin systemd[1]: atopacct.service: State 'stop-sigterm' 
> timed out. Killing.
> Oct 26 10:18:56 cventin systemd[1]: atopacct.service: Killing process 908 
> (atopacctd) with signal SIGKILL.
> Oct 26 10:18:56 cventin systemd[1]: atopacct.service: Main process exited, 
> code=killed, status=9/KILL
> 
> So, there's a timeout (1'30" by default), then systemd kills it with kill 
> -KILL
> (thus without clean-up).

Can you reproduce this? If so, I'd like you to attach an strace to the
atopacct process (strace -f -p  -s 2000 -o
strace.atopacctd) and attach the resulting file. I'd like to see
whether atopacctd gets the SIGTERM and how it reacts.

> 1. The fact that atopacctd doesn't quit after SIGTERM. This is exactly
>the same issue as before.
> 
> 2. The "File exists" problem at start. Perhaps a consequence of (1)
>since there was no clean-up. But I don't think that this should
>cause atopacct to fail to start.

Issue (2) was already reported by Martin in #842136. We can ignore
this here.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#834226: atop: prevents clean and fast shutdown

2016-10-26 Thread Vincent Lefevre 
On 2016-10-26 09:42:29 +0200, Marc Haber wrote:
> Hi Vincent,
> 
> can you try stopping the atop daemons, verifying that they're really
> dead, and restart?

root@cventin:/home/vlefevre# ps -aef|grep atop
root   908 1  0 10:17 ?00:00:00 /usr/sbin/atopacctd
root   963 1  0 10:17 ?00:00:00 /usr/bin/atop -a -R -w 
/var/log/atop/atop_20161026 600
root  1897  1755  0 10:18 pts/000:00:00 grep atop
root@cventin:/home/vlefevre# invoke-rc.d atopacct stop

This one takes time to stop. In the journal, I can see:

Oct 26 10:18:56 cventin systemd[1]: atopacct.service: State 'stop-sigterm' 
timed out. Killing.
Oct 26 10:18:56 cventin systemd[1]: atopacct.service: Killing process 908 
(atopacctd) with signal SIGKILL.
Oct 26 10:18:56 cventin systemd[1]: atopacct.service: Main process exited, 
code=killed, status=9/KILL

So, there's a timeout (1'30" by default), then systemd kills it with kill -KILL
(thus without clean-up).

root@cventin:/home/vlefevre# invoke-rc.d atop stop
root@cventin:/home/vlefevre# ps -aef|grep atop
root  2087  1755  0 10:19 pts/000:00:00 grep atop
root@cventin:/home/vlefevre# invoke-rc.d atop start
root@cventin:/home/vlefevre# invoke-rc.d atopacct start
Job for atopacct.service failed because of unavailable resources or another 
system error.
See "systemctl status atopacct.service" and "journalctl -xe" for details.
invoke-rc.d: initscript atopacct, action "start" failed.
● atopacct.service - Atop process accounting daemon
   Loaded: loaded (/lib/systemd/system/atopacct.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: resources) since Wed 2016-10-26 10:19:36 CEST; 9ms 
ago
 Docs: man:atopacctd(8)
  Process: 2142 ExecStart=/usr/sbin/atopacctd (code=exited, status=0/SUCCESS)
 Main PID: 908 (code=killed, signal=KILL)

Oct 26 10:19:36 cventin systemd[1]: Starting Atop process accounting daemon...
Oct 26 10:19:36 cventin atopacctd[2142]: /run/pacct_shadow.d: File exists
Oct 26 10:19:36 cventin systemd[1]: atopacct.service: PID file 
/run/atopacctd.pid not readable (yet?) after start: No such file or directory
Oct 26 10:19:36 cventin systemd[1]: Failed to start Atop process accounting 
daemon.
Oct 26 10:19:36 cventin systemd[1]: atopacct.service: Unit entered failed state.
Oct 26 10:19:36 cventin systemd[1]: atopacct.service: Failed with result 
'resources'.

Isn't the problem due to the "File exists" error?

> Btw, this is a new issue, we should have a dedicated bug report for
> this. Failed with result 'resources' looks like a local issue though.

There are 2 issues:

1. The fact that atopacctd doesn't quit after SIGTERM. This is exactly
   the same issue as before.

2. The "File exists" problem at start. Perhaps a consequence of (1)
   since there was no clean-up. But I don't think that this should
   cause atopacct to fail to start.

> Is your system under load, runing with resource limits, having limited
> resources?

No.

> Can you reproduce the issue after rebooting?

This was just after a reboot.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#834226: atop: prevents clean and fast shutdown

2016-10-26 Thread Marc Haber 
Hi Vincent,

can you try stopping the atop daemons, verifying that they're really
dead, and restart?

Btw, this is a new issue, we should have a dedicated bug report for
this. Failed with result 'resources' looks like a local issue though.
Is your system under load, runing with resource limits, having limited
resources? Can you reproduce the issue after rebooting?

Greetings
Marc

On Wed, Oct 26, 2016 at 09:16:11AM +0200, Vincent Lefevre wrote:
> From: Vincent Lefevre <vinc...@vinc17.net>
> Subject: Re: Bug#834226: atop: prevents clean and fast shutdown
> To: Marc Haber <mh+debian-packa...@zugschlus.de>
> Cc: 834...@bugs.debian.org
> Date: Wed, 26 Oct 2016 09:16:11 +0200
> X-Mailer-Info: https://www.vinc17.net/mutt/
> User-Agent: Mutt/1.7.1-6826-vl-r91193 (2016-10-20)
> X-Spam-Score: (---) -3.2
> X-Spam-Report: torres.zugschlus.de  Content analysis details:   (-3.2
>  points, 5.0 required)   pts  rule name  description  
>  -- --- -1.3
>  RP_MATCHES_RCVDEnvelope sender domain matches handover relay
>  domain -1.9 BAYES_00   BODY: Bayes spam probability is 0 to 1%
>  [score: 0.]
> 
> On 2016-10-26 08:38:10 +0200, Marc Haber wrote:
> > This:
> > 
> > On Wed, Oct 26, 2016 at 02:18:24AM +0200, Vincent Lefevre wrote:
> > > Oct 26 02:15:36 cventin systemd[1]: atopacct.service: Failed with result 
> > > 'r...'.
> > > Hint: Some lines were ellipsized, use -l to show in full.
> > 
> > unfortunately stops when it gets interesting. Can you still obtain the
> > -l output?
> 
> Here I just need to increase the terminal window size.
> With a reinstallation of 2.2.4-1~exp1 just after reboot:
> 
> root@cventin:/home/vlefevre# apt install atop/experimental --reinstall
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Selected version '2.2.4-1~exp1' (Debian:experimental [amd64]) for 'atop'
> The following package was automatically installed and is no longer required:
>   linux-image-4.5.0-2-amd64
> Use 'apt autoremove' to remove it.
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 96 not upgraded.
> Need to get 0 B/138 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> (Reading database ... 508278 files and directories currently installed.)
> Preparing to unpack .../atop_2.2.4-1~exp1_amd64.deb ...
> Unpacking atop (2.2.4-1~exp1) over (2.2.4-1~exp1) ...
> Setting up atop (2.2.4-1~exp1) ...
> Job for atopacct.service failed because of unavailable resources or another 
> system error.
> See "systemctl status atopacct.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript atopacct, action "start" failed.
> ● atopacct.service - Atop process accounting daemon
>Loaded: loaded (/lib/systemd/system/atopacct.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: resources) since Wed 2016-10-26 08:59:31 CEST; 7ms 
> ago
>  Docs: man:atopacctd(8)
>   Process: 1987 ExecStart=/usr/sbin/atopacctd (code=exited, status=0/SUCCESS)
>  Main PID: 933 (code=killed, signal=KILL)
> 
> Oct 26 08:59:31 cventin systemd[1]: Starting Atop process accounting daemon...
> Oct 26 08:59:31 cventin atopacctd[1987]: /run/pacct_shadow.d: File exists
> Oct 26 08:59:31 cventin systemd[1]: atopacct.service: PID file 
> /run/atopacctd.pid not readable (yet?) after start: No such file or directory
> Oct 26 08:59:31 cventin systemd[1]: Failed to start Atop process accounting 
> daemon.
> Oct 26 08:59:31 cventin systemd[1]: atopacct.service: Unit entered failed 
> state.
> Oct 26 08:59:31 cventin systemd[1]: atopacct.service: Failed with result 
> 'resources'.
> dpkg: error processing package atop (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for systemd (231-9) ...
> Processing triggers for man-db (2.7.5-1) ...
> Errors were encountered while processing:
>  atop
> ==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) 
> ==
> 
> -  Show old opportunities as well as new ones: how-can-i-help --old  -
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> In the "journalctl -xe" output:
> 
> Oct 26 08:59:09 cventin systemd[1]: Reloading.
> Oct 26 08:59:10 cventin systemd[1]: apt-daily.timer: Adding 5h 45min 
> 58.793544s random time.
> Oct 26 08:59:10 cventin systemd[1]: Stopping Atop process accounting daemon...
> -- Subject: Unit atopacct.service has begun shutting down
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
>

Bug#834226: atop: prevents clean and fast shutdown

2016-10-26 Thread Vincent Lefevre 
On 2016-10-26 08:38:10 +0200, Marc Haber wrote:
> This:
> 
> On Wed, Oct 26, 2016 at 02:18:24AM +0200, Vincent Lefevre wrote:
> > Oct 26 02:15:36 cventin systemd[1]: atopacct.service: Failed with result 
> > 'r...'.
> > Hint: Some lines were ellipsized, use -l to show in full.
> 
> unfortunately stops when it gets interesting. Can you still obtain the
> -l output?

Here I just need to increase the terminal window size.
With a reinstallation of 2.2.4-1~exp1 just after reboot:

root@cventin:/home/vlefevre# apt install atop/experimental --reinstall
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '2.2.4-1~exp1' (Debian:experimental [amd64]) for 'atop'
The following package was automatically installed and is no longer required:
  linux-image-4.5.0-2-amd64
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 96 not upgraded.
Need to get 0 B/138 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 508278 files and directories currently installed.)
Preparing to unpack .../atop_2.2.4-1~exp1_amd64.deb ...
Unpacking atop (2.2.4-1~exp1) over (2.2.4-1~exp1) ...
Setting up atop (2.2.4-1~exp1) ...
Job for atopacct.service failed because of unavailable resources or another 
system error.
See "systemctl status atopacct.service" and "journalctl -xe" for details.
invoke-rc.d: initscript atopacct, action "start" failed.
● atopacct.service - Atop process accounting daemon
   Loaded: loaded (/lib/systemd/system/atopacct.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: resources) since Wed 2016-10-26 08:59:31 CEST; 7ms 
ago
 Docs: man:atopacctd(8)
  Process: 1987 ExecStart=/usr/sbin/atopacctd (code=exited, status=0/SUCCESS)
 Main PID: 933 (code=killed, signal=KILL)

Oct 26 08:59:31 cventin systemd[1]: Starting Atop process accounting daemon...
Oct 26 08:59:31 cventin atopacctd[1987]: /run/pacct_shadow.d: File exists
Oct 26 08:59:31 cventin systemd[1]: atopacct.service: PID file 
/run/atopacctd.pid not readable (yet?) after start: No such file or directory
Oct 26 08:59:31 cventin systemd[1]: Failed to start Atop process accounting 
daemon.
Oct 26 08:59:31 cventin systemd[1]: atopacct.service: Unit entered failed state.
Oct 26 08:59:31 cventin systemd[1]: atopacct.service: Failed with result 
'resources'.
dpkg: error processing package atop (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (231-9) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 atop
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) ==

-  Show old opportunities as well as new ones: how-can-i-help --old  -
E: Sub-process /usr/bin/dpkg returned an error code (1)

In the "journalctl -xe" output:

Oct 26 08:59:09 cventin systemd[1]: Reloading.
Oct 26 08:59:10 cventin systemd[1]: apt-daily.timer: Adding 5h 45min 58.793544s 
random time.
Oct 26 08:59:10 cventin systemd[1]: Stopping Atop process accounting daemon...
-- Subject: Unit atopacct.service has begun shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit atopacct.service has begun shutting down.
Oct 26 08:59:13 cventin systemd-timesyncd[831]: Synchronized to time server 
212.83.158.83:123 (2.debian.pool.ntp.org).
Oct 26 08:59:30 cventin systemd[1]: atopacct.service: State 'stop-sigterm' 
timed out. Killing.
Oct 26 08:59:30 cventin systemd[1]: atopacct.service: Killing process 933 
(atopacctd) with signal SIGKILL.
Oct 26 08:59:30 cventin systemd[1]: atopacct.service: Main process exited, 
code=killed, status=9/KILL
Oct 26 08:59:30 cventin systemd[1]: Stopped Atop process accounting daemon.
-- Subject: Unit atopacct.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit atopacct.service has finished shutting down.
Oct 26 08:59:30 cventin systemd[1]: atopacct.service: Unit entered failed state.
Oct 26 08:59:30 cventin systemd[1]: atopacct.service: Failed with result 
'signal'.
Oct 26 08:59:30 cventin systemd[1]: Reloading.
Oct 26 08:59:30 cventin systemd[1]: apt-daily.timer: Adding 11h 47min 2.92s 
random time.
Oct 26 08:59:30 cventin systemd[1]: Stopping Atop advanced performance 
monitor...
-- Subject: Unit atop.service has begun shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit atop.service has begun shutting down.
Oct 26 08:59:30 cventin systemd[1]: Stopped Atop advanced performance monitor.
-- Subject: Unit atop.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit atop.service has finished shutting down.
Oct 26 08:59:30 cventin systemd[1]: Reloading.
Oct 26 08:59:30 cventin systemd[1]: apt-daily.timer: Adding 2h 45min 11.176686s 
random time.
Oct 26 08:59:30 cventin systemd[1]:

Bug#834226: atop: prevents clean and fast shutdown

2016-10-26 Thread Marc Haber 
This:

On Wed, Oct 26, 2016 at 02:18:24AM +0200, Vincent Lefevre wrote:
> Oct 26 02:15:36 cventin systemd[1]: atopacct.service: Failed with result 
> 'r...'.
> Hint: Some lines were ellipsized, use -l to show in full.

unfortunately stops when it gets interesting. Can you still obtain the
-l output?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#834226: atop: prevents clean and fast shutdown

2016-10-25 Thread Vincent Lefevre 
On 2016-10-25 10:44:01 +0200, Marc Haber wrote:
> I have uploaded 2.2.4-1~exp1 to experimental. That version is a
> debugging release which has better logging. Can you please try to
> reproduce this issue?

I tried to upgrade, but it failed:

root@cventin:/home/vlefevre# apt install atop/experimental
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '2.2.4-1~exp1' (Debian:experimental [amd64]) for 'atop'
The following package was automatically installed and is no longer required:
  linux-image-4.5.0-2-amd64
Use 'apt autoremove' to remove it.
The following packages will be upgraded:
  atop
1 upgraded, 0 newly installed, 0 to remove and 96 not upgraded.
Need to get 138 kB of archives.
After this operation, 32.8 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian experimental/main amd64 atop amd64 
2.2.4-1~exp1 [138 kB]
Fetched 138 kB in 0s (1063 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n] 
(Reading database ... 508278 files and directories currently installed.)
Preparing to unpack .../atop_2.2.4-1~exp1_amd64.deb ...
Unpacking atop (2.2.4-1~exp1) over (2.2.3-1~exp1) ...
Setting up atop (2.2.4-1~exp1) ...
Installing new version of config file /etc/cron.d/atop ...
Installing new version of config file /etc/init.d/atop ...
Installing new version of config file /etc/init.d/atopacct ...
Installing new version of config file /etc/logrotate.d/psaccs_atop ...
Installing new version of config file /etc/logrotate.d/psaccu_atop ...
Job for atopacct.service failed because of unavailable resources or another 
system error.
See "systemctl status atopacct.service" and "journalctl -xe" for details.
invoke-rc.d: initscript atopacct, action "start" failed.
● atopacct.service - Atop process accounting daemon
   Loaded: loaded (/lib/systemd/system/atopacct.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: resources) since Wed 2016-10-26 02:15:36 CEST; 8ms 
ago
 Docs: man:atopacctd(8)
  Process: 7849 ExecStart=/usr/sbin/atopacctd (code=exited, status=0/SUCCESS)
 Main PID: 946 (code=killed, signal=KILL)

Oct 26 02:15:36 cventin systemd[1]: Starting Atop process accounting daemon...
Oct 26 02:15:36 cventin atopacctd[7849]: /run/pacct_shadow.d: File exists
Oct 26 02:15:36 cventin systemd[1]: atopacct.service: PID file /run/atopacc...ry
Oct 26 02:15:36 cventin systemd[1]: Failed to start Atop process accounting...n.
Oct 26 02:15:36 cventin systemd[1]: atopacct.service: Unit entered failed state.
Oct 26 02:15:36 cventin systemd[1]: atopacct.service: Failed with result 'r...'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package atop (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (231-9) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 atop
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help ) ==

-  Show old opportunities as well as new ones: how-can-i-help --old  -
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#834226: atop: prevents clean and fast shutdown

2016-10-25 Thread Marc Haber 
Hi,

I have uploaded 2.2.4-1~exp1 to experimental. That version is a
debugging release which has better logging. Can you please try to
reproduce this issue?

Greetings
Marc

On Tue, Aug 16, 2016 at 06:10:37PM +0200, Vincent Lefevre wrote:
> From: Vincent Lefevre <vinc...@vinc17.net>
> Subject: Bug#834226: atop: prevents clean and fast shutdown
> To: 834...@bugs.debian.org
> Reply-To: Vincent Lefevre <vinc...@vinc17.net>, 834...@bugs.debian.org
> Date: Tue, 16 Aug 2016 18:10:37 +0200
> X-Mailer-Info: https://www.vinc17.net/mutt/
> User-Agent: Mutt/1.6.2-6759-vl-r91193 (2016-08-10)
> 
> On 2016-08-13 13:02:53 +0200, Vincent Lefevre wrote:
> > Package: atop
> > Version: 2.2.3-1~exp1
> > Severity: important
> > 
> > Some atop daemon doesn't terminate at shutdown, so that with systemd,
> > I get various failures concerning the disks (I suppose that this is
> > related), then:
> > 
> > [  ***] A stop job is running for Atop proc...counting daemon (… / 1min 30s)
> > 
> > and I have to wait for 1 minute 30 seconds so that the shutdown can
> > be completed.
> 
> Here's what I get in the logs:
> 
> [...]
> Aug 16 18:01:18 zira systemd[1]: Stopping Atop advanced performance monitor...
> [...]
> Aug 16 18:01:18 zira systemd[1]: Stopped Atop advanced performance monitor.
> [...]
> Aug 16 18:01:18 zira systemd[1]: Stopping Atop process accounting daemon...
> [...]
> Aug 16 18:01:20 zira systemd[1]: Stopped Raise network interfaces.
> Aug 16 18:02:48 zira systemd[1]: atopacct.service: State 'stop-sigterm' timed 
> out. Killing.
> Aug 16 18:02:48 zira systemd[1]: atopacct.service: Killing process 2442 
> (atopacctd) with signal SIGKILL.
> Aug 16 18:02:48 zira systemd[1]: atopacct.service: Main process exited, 
> code=killed, status=9/KILL
> Aug 16 18:02:48 zira systemd[1]: Stopped Atop process accounting daemon.
> Aug 16 18:02:48 zira systemd[1]: atopacct.service: Unit entered failed state.
> Aug 16 18:02:48 zira systemd[1]: atopacct.service: Failed with result 
> 'signal'.
> Aug 16 18:02:48 zira systemd[1]: Stopped target Basic System.
> Aug 16 18:02:48 zira systemd[1]: Stopped target Paths.
> [...]
> 
> -- 
> Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#834226: atop: prevents clean and fast shutdown

2016-08-16 Thread Vincent Lefevre 
On 2016-08-13 13:02:53 +0200, Vincent Lefevre wrote:
> Package: atop
> Version: 2.2.3-1~exp1
> Severity: important
> 
> Some atop daemon doesn't terminate at shutdown, so that with systemd,
> I get various failures concerning the disks (I suppose that this is
> related), then:
> 
> [  ***] A stop job is running for Atop proc...counting daemon (… / 1min 30s)
> 
> and I have to wait for 1 minute 30 seconds so that the shutdown can
> be completed.

Here's what I get in the logs:

[...]
Aug 16 18:01:18 zira systemd[1]: Stopping Atop advanced performance monitor...
[...]
Aug 16 18:01:18 zira systemd[1]: Stopped Atop advanced performance monitor.
[...]
Aug 16 18:01:18 zira systemd[1]: Stopping Atop process accounting daemon...
[...]
Aug 16 18:01:20 zira systemd[1]: Stopped Raise network interfaces.
Aug 16 18:02:48 zira systemd[1]: atopacct.service: State 'stop-sigterm' timed 
out. Killing.
Aug 16 18:02:48 zira systemd[1]: atopacct.service: Killing process 2442 
(atopacctd) with signal SIGKILL.
Aug 16 18:02:48 zira systemd[1]: atopacct.service: Main process exited, 
code=killed, status=9/KILL
Aug 16 18:02:48 zira systemd[1]: Stopped Atop process accounting daemon.
Aug 16 18:02:48 zira systemd[1]: atopacct.service: Unit entered failed state.
Aug 16 18:02:48 zira systemd[1]: atopacct.service: Failed with result 'signal'.
Aug 16 18:02:48 zira systemd[1]: Stopped target Basic System.
Aug 16 18:02:48 zira systemd[1]: Stopped target Paths.
[...]

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#834226: atop: prevents clean and fast shutdown

2016-08-13 Thread Vincent Lefevre 
Package: atop
Version: 2.2.3-1~exp1
Severity: important

Some atop daemon doesn't terminate at shutdown, so that with systemd,
I get various failures concerning the disks (I suppose that this is
related), then:

[  ***] A stop job is running for Atop proc...counting daemon (… / 1min 30s)

and I have to wait for 1 minute 30 seconds so that the shutdown can
be completed.

This is reproducible, in particular with a shutdown just after the
boot.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages atop depends on:
ii  init-system-helpers  1.42
ii  initscripts  2.88dsf-59.8
ii  libc62.23-4
ii  libncurses5  6.0+20160625-1
ii  libtinfo56.0+20160625-1
ii  lsb-base 9.20160629
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages atop recommends:
ii  cron [cron-daemon]  3.0pl1-128

atop suggests no packages.

-- no debconf information