I'm upgrading right now! Yay!!!
I followed my own advice and started doing straces on upgrade related programs.
My breakthrough came when less'ing through the output of:
strace -f -s 200 update-manager > /tmp/um.strace 2>&1 &
I saw these lines in the dump just before it starts closing dozens of files and
munmapping dozens of memory areas:
----------
[pid 25685] connect(5, {sa_family=AF_UNIX, sun_path="/run/snapd.socket"}, 20) =
-1 ENOENT (No such file or directory)
pid 25685] write(2, "error: cannot communicate with server: Get
http://localhost/v2/debug?aspect=connectivity: dial unix /run/snapd.socket:
connect: no such file or directory\n", 154 <unfinished ...>
----------
Snapd? I remember snapd. I turned it off many months ago, when I was
cleaning up my boot process (which used to take 10 minutes, with all the
rubbish I was running). It seemed (at the time) that snapd was yet
another jeOS installer for games, like lutris and steam-installer. So I
turned it off and nothing bad happened - 'till trying to upgrade.
I can't remember how I turned it off, but I woke it up a bit brute-force-ishly
with:
systemctl --system enable snapd.autoimport.service snapd.core-fixup.service
snapd.seeded.service snapd.service snapd.system-shutdown.service snapd.socket
snapd.snap-repair.timer
systemctl --system start snapd.autoimport.service snapd.core-fixup.service
snapd.seeded.service snapd.service snapd.system-shutdown.service snapd.socket
snapd.snap-repair.timer
So, with an early python test for /run/snapd.socket plus an error
message that mentions SNAPD, I think we can close this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849669
Title:
do-release-upgrade (19.04 -> 19.10) aborts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849669/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
