Package: atop Version: 2.2.6-2 Severity: minor On Thu, Jan 19, 2017 at 01:02:16PM +0100, Marc Haber wrote: > On Thu, Jan 19, 2017 at 12:35:33PM +0100, Jan Niehusmann wrote: > > First I noticed that the installation failed because process accounting > > was not running. (I used the 'echo "99 99 30" >/proc/sys/kernel/acct' > > command to test the jessie version, before, to make sure that I can still > > reproduce the bug.) > > Home-Made issue or #833997?
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
