On Wed, Apr 09, 2025 at 02:59:09PM +0000, hyuw77yckxszm...@firemail.cc wrote:
Running apt-get -V full-upgrade which updated atop - atop:amd64
(2.10.0-3, 2.11.1-1)
it finished with Error: Sub-process /usr/bin/dpkg returned an error
code (1)
Said also something not being able to convert todays logfile.
So you're upgrading from unstable, 2.10.0.3 to unstable, 2.11.1-1.
Right?
Ran it again later, same outcome. This time I looked, if it is
shutting down atop, while doing a conversion. It did not.
Backed up all atop logs, shut down atop manually. Ran apt again.
Now it complains after long pause, while running atopconvert, not
being able to convert yesterdays log.A
It would be incredibly helpful to have the verbatim output of all calls.
Tried manually converting yesterdays atop log. It finishes fine:
atopconvert /var/log/atop/oldsh/atop_20250408
/var/log/atop/oldsh/atop_20250408_newformat
Version of /var/log/atop/oldsh/atop_20250408: 2.10
Version of /var/log/atop/oldsh/atop_20250408_newformat: 2.11
Samples converted: 1441
Tried other logs also, they all converted fine. Trying atopconvert
on todays log said it is already at 2.11
Removed all atop logs, ran apt again and now it finally finishes
without complaints.
Can you reproduce the issue with the backed up logs? In that case, can
you run postinst configure with bash -x so that we can see what the
script actually tries to do?
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
