[Pkg-xen-devel] Bug#932759: Bug#932759: After upgrade from stretch to buster, removal of obsolete xen 4.8 packages seems to trigger shutdown of xenconsoled

niek niek at niek.org
Tue Jul 23 15:07:26 BST 2019


On 22-7-2019 18:57, Hans van Kranenburg wrote:
> Hi niek,
> 
> Thanks for the report!
> 
> On 7/22/19 8:32 PM, niek wrote:
>> Package:  xen-hypervisor-4.11-amd64
>> Version: 4.11.1+92-g6c33308a8d-2
>>
>> What happened:
>> - upgraded Debian Xen Dom0 from stretch to buster and rebooted, as
>> described in
>> https://www.debian.org/releases/buster/amd64/release-notes/ch-upgrading.en.html
>>
>> - started some Linux pv domu without problems
>>
>> - removed obsolete packages with 'apt autoremove'. This removed (among
>> others)
>> xen-hypervisor-4.8-amd64:amd64 (4.8.5+shim4.10.2+xsa282-1+deb9u11),
>> libxen-4.8:amd64 (4.8.5+shim4.10.2+xsa282-1+deb9u11),
>> xen-utils-4.8:amd64 (4.8.5+shim4.10.2+xsa282-1+deb9u11)
>>
>> [...]
>> - xenconsoled was not running
>>
>> - searching system logs revealed that xenconsoled seemed to have stopped
>> when 'apt autoremove' removed the obsolete xen 4.8
>> packages after upgrading to xen 4.11.
> 
> Well, there it is again. We tried to make a fix, exactly for this...
> 
> https://salsa.debian.org/xen-team/debian-xen/commit/ef242a700765a971a6afc12d25ee19944dd3a27a
> 
> ...and apparently there's another scenario in which even this doesn't work?
> 
> Can you show the lines from /var/log/dpkg.log from that moment, the
> seconds around 07:38:40? It tells exactly what got removed, in what
> second, just to confirm?
> 
> I'm pretty sure I tried to reproduce this after we added the fix I just
> referenced, and I was unable to. So, I'm very interested in finding out
> what's still going on here.
> 
> Usually being able to reproduce a problem is one of the biggest steps
> towards finding a solution. (since it can be done over and over again,
> finding out what exactly causes it). So, finding the right sequence of
> steps to make it happen again is crucial here.
> 
> Do you think the systemd reload has anything to do with it? Maybe the
> whole systemd init-script-wrapper-trickery is misbehaving in some way?
> 
> Can you reproduce this by manually grabbing the
> xen-hypervisor-4.8-amd64, libxen-4.8 and xen-utils-4.8 from stretch
> again, installing them and removing them again? Do you have any other idea?
> 
> Thanks,
> Hans
> 

Hi Hans,

Thanks for your work with Ian getting xen 4.11 in buster! Very happy
with that.

I seem to remember seeing 'processing triggers for systemd' somewhere,
sometime, but I can't confirm that from the logs so it probably was at
another stage of the upgrade.

This is a production system, so I will not try to reproduce this by
reinstalling the 4.8 packages as you suggested. There is, however an
identical server that I still need to upgrade, so I will be able to look
closely what happens with that.

Here are the relevant lines from dpkg.conf:
2019-07-21 07:38:39 status installed python3.5-minimal:amd64 3.5.3-1+deb9u1
2019-07-21 07:38:39 remove python3.5-minimal:amd64 3.5.3-1+deb9u1 <none>
2019-07-21 07:38:39 status half-configured python3.5-minimal:amd64
3.5.3-1+deb9u1
2019-07-21 07:38:39 status half-installed python3.5-minimal:amd64
3.5.3-1+deb9u1
2019-07-21 07:38:40 status config-files python3.5-minimal:amd64
3.5.3-1+deb9u1
2019-07-21 07:38:40 status installed libpython3.5-minimal:amd64
3.5.3-1+deb9u1
2019-07-21 07:38:40 remove libpython3.5-minimal:amd64 3.5.3-1+deb9u1 <none>
2019-07-21 07:38:40 status half-configured libpython3.5-minimal:amd64
3.5.3-1+deb9u1
2019-07-21 07:38:40 status half-installed libpython3.5-minimal:amd64
3.5.3-1+deb9u1
2019-07-21 07:38:40 status config-files libpython3.5-minimal:amd64
3.5.3-1+deb9u1
2019-07-21 07:38:40 status installed xen-utils-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:40 remove xen-utils-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11 <none>
2019-07-21 07:38:40 status half-configured xen-utils-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:41 status half-installed xen-utils-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:41 status config-files xen-utils-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:41 status not-installed xen-utils-4.8:amd64 <none>
2019-07-21 07:38:41 status installed libxen-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:41 remove libxen-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11 <none>
2019-07-21 07:38:41 status half-configured libxen-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:41 status half-installed libxen-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:41 status config-files libxen-4.8:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:41 status not-installed libxen-4.8:amd64 <none>
2019-07-21 07:38:41 status installed python3-distutils:all 3.7.3-1
2019-07-21 07:38:41 remove python3-distutils:all 3.7.3-1 <none>
2019-07-21 07:38:41 status half-configured python3-distutils:all 3.7.3-1
2019-07-21 07:38:41 status half-installed python3-distutils:all 3.7.3-1
2019-07-21 07:38:41 status config-files python3-distutils:all 3.7.3-1
2019-07-21 07:38:41 status not-installed python3-distutils:all <none>
2019-07-21 07:38:41 status installed python3-lib2to3:all 3.7.3-1
2019-07-21 07:38:41 remove python3-lib2to3:all 3.7.3-1 <none>
2019-07-21 07:38:41 status half-configured python3-lib2to3:all 3.7.3-1
2019-07-21 07:38:41 status half-installed python3-lib2to3:all 3.7.3-1
2019-07-21 07:38:41 status config-files python3-lib2to3:all 3.7.3-1
2019-07-21 07:38:41 status not-installed python3-lib2to3:all <none>
2019-07-21 07:38:41 status installed rename:all 1.10-1
2019-07-21 07:38:41 remove rename:all 1.10-1 <none>
2019-07-21 07:38:41 status half-configured rename:all 1.10-1
2019-07-21 07:38:42 status half-installed rename:all 1.10-1
2019-07-21 07:38:42 status config-files rename:all 1.10-1
2019-07-21 07:38:42 status not-installed rename:all <none>
2019-07-21 07:38:42 status installed xml-core:all 0.18+nmu1
2019-07-21 07:38:42 remove xml-core:all 0.18+nmu1 <none>
2019-07-21 07:38:42 status triggers-pending sgml-base:all 1.29
2019-07-21 07:38:42 status triggers-awaited xml-core:all 0.18+nmu1
2019-07-21 07:38:42 status half-configured xml-core:all 0.18+nmu1
2019-07-21 07:38:42 status half-installed xml-core:all 0.18+nmu1
2019-07-21 07:38:42 status config-files xml-core:all 0.18+nmu1
2019-07-21 07:38:42 remove sgml-base:all 1.29 <none>
2019-07-21 07:38:42 status half-configured sgml-base:all 1.29
2019-07-21 07:38:42 status half-installed sgml-base:all 1.29
2019-07-21 07:38:42 status config-files sgml-base:all 1.29
2019-07-21 07:38:42 status installed tcpd:amd64 7.6.q-28
2019-07-21 07:38:42 remove tcpd:amd64 7.6.q-28 <none>
2019-07-21 07:38:42 status half-configured tcpd:amd64 7.6.q-28
2019-07-21 07:38:42 status half-installed tcpd:amd64 7.6.q-28
2019-07-21 07:38:42 status config-files tcpd:amd64 7.6.q-28
2019-07-21 07:38:42 status not-installed tcpd:amd64 <none>
2019-07-21 07:38:42 status installed xen-hypervisor-4.8-amd64:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:42 remove xen-hypervisor-4.8-amd64:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11 <none>
2019-07-21 07:38:42 status half-configured
xen-hypervisor-4.8-amd64:amd64 4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:38:42 status half-installed xen-hypervisor-4.8-amd64:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:39:41 status config-files xen-hypervisor-4.8-amd64:amd64
4.8.5+shim4.10.2+xsa282-1+deb9u11
2019-07-21 07:39:41 startup packages configure
2019-07-21 07:39:41 trigproc libc-bin:amd64 2.28-10 <none>
2019-07-21 07:39:41 status half-configured libc-bin:amd64 2.28-10
2019-07-21 07:39:41 status installed libc-bin:amd64 2.28-10
2019-07-21 07:39:41 trigproc man-db:amd64 2.8.5-2 <none>
2019-07-21 07:39:41 status half-configured man-db:amd64 2.8.5-2

And here is the relevant portion of /var/log/history.log:
Start-Date: 2019-07-21  07:38:37
Commandline: apt autoremove
Requested-By: [user]
Remove: liblvm2cmd2.02:amd64 (2.02.168-2), libisccfg140:amd64
(1:9.10.3.dfsg.P4-12.3+deb9u5), python3-distutils:amd64 (3.7.3-1),
sgml-base:amd64 (1.29), rename:amd64 (1.10-1), libicu57:amd64
(57.1-6+deb9u2), python3.5:amd64 (3.5.3-1+deb9u1),
python3.5-minimal:amd64 (3.5.3-1+deb9u1), libisc160:amd64
(1:9.10.3.dfsg.P4-12.3+deb9u5), libperl5.24:amd64 (5.24.1-3+deb9u5),
xml-core:amd64 (0.18+nmu1), libapparmor-perl:amd64 (2.13.2-10),
guile-2.0-libs:amd64 (2.0.13+1-5.1), liblvm2app2.2:amd64 (2.02.168-2),
liblwres141:amd64 (1:9.10.3.dfsg.P4-12.3+deb9u5), tcpd:amd64 (7.6.q-28),
python3-lib2to3:amd64 (3.7.3-1), xen-hypervisor-4.8-amd64:amd64
(4.8.5+shim4.10.2+xsa282-1+deb9u11), dh-python:amd64 (3.20190308),
libxen-4.8:amd64 (4.8.5+shim4.10.2+xsa282-1+deb9u11), libdns162:amd64
(1:9.10.3.dfsg.P4-12.3+deb9u5), libisccc140:amd64
(1:9.10.3.dfsg.P4-12.3+deb9u5), libpython3.5-stdlib:amd64
(3.5.3-1+deb9u1), libbind9-140:amd64 (1:9.10.3.dfsg.P4-12.3+deb9u5),
libpython3.5-minimal:amd64 (3.5.3-1+deb9u1), xen-utils-4.8:amd64
(4.8.5+shim4.10.2+xsa282-1+deb9u11)
End-Date: 2019-07-21  07:39:44

niek



More information about the Pkg-xen-devel mailing list