Package: atop Version: 2.2.6-2 Severity: minor The process accounting didn't run because I actively stopped it. (echo "99 99 30" >/proc/sys/kernel/acct means that process accounting stops whenever less then 99% of the target fs are free.) So that's not surprising. But I think that atop still should be upgradable cleanly, in such a situation. The chain of events is: - I paused process accounting using the mentioned command - I started the upgrade - postinst tries to start atopacct (invoke-rc.d atopacct start, generated by dh_installinit - atopacct waits for new accounting entries to appear, fails after some timeout - invoke-rc.d returns failure, breaking the update So it really looks like a different bug. -> new ticket opened. Set the severity to minor, as it's probably difficult to trigger under normal circumstances. Jan
tags #851875 upstream forwarded #851875 atoptool.nl retitle #851875 atopacctd does not start gracefully if process accounting is stopped thanks
Hi, can you verify that this issue still applies to the current version of atop, 2.6.0? I would appreciate that. Greetings Marc
Hi, can you verify that this issue still applies to the current version of atop, 2.6.0? I would appreciate that. Greetings Marc
No answer in 18 months. I intend to close this by the End of August 2022. Greetings Marc
No answer in 18 months. I intend to close this by the End of August 2022. Greetings Marc
Sorry - got the message 18 months ago, put it on my TODO list, and well what should I say, the TODO lists seems to be LIFO not FIFO.... :-) However, I just tried to reproduce the issue. At least "apt reinstall atop" works even if the process accounting is disabled. So I guess the bug has been fixed in the mean time. Jan
Version: 2.7.1-1 Closing the bug then. Thanks for reporting back. Greetings Marc