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/0 00: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 <pid of atopacctd> -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
