Well, a simple apt upgrade makes the openssh-server fail to install, and
the only thing that can take away the package from that iF situation is
a:
shutdown -r now
apt install --fix-broken
Then a do-release-upgrade again broke the package with the same output
plus:
User sessions running
I'm starting to think that there is something wrong with the horsea
machine indeed: still not able to upgrade to lunar. Starting from jammy
or from kinetic failed.
#Jammy
Deploying again jammy and doing do-release-upgrade again failed with
ssh, with differents things after rebooting and trying
I'm sorry, but I had to reset the machine because it was blocking the
dpdk's MRE process.
I hope the above info serves as a more complete starting point than
before to find out something more. Anyway, after dpdk testing, I will
try to reproduce the upgrade problem on that machine (if I'm lucky).
@Steve
Since the machines original use case is blocked until we know if we can go on.
Is the above enough for your to have a deeper look together with us?
If so please let Miriam know when once she can reset the machine to go
on with the MRE verifications that this was supposed to do :-)
--
You
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2004551
Title:
upgrade to
Crash report
** Attachment added: "openssh-server.0.crash"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2004551/+attachment/5688062/+files/openssh-server.0.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
In horsea's syslog.1, some errors happen at the same time that do-dist-
upgrade is running and fails:
Jul 20 10:20:23 node-horsea fwupd[214065]: 10:20:23:0245 FuEngine
failed to get releases for UEFI dbx: No releases found: Not compatible with
org.freedesktop.fwupd version 1.7.9,
Today I'm trying to reproduce the error in a lxc vm without success: I
logged in via ssh to start the do-release-upgrade there so the system
would initiate sshd on port 1022 as well. The upgrade process went fine
the times I tried it.
Thanks Andreas for spotting the same error in the autopkgtest
Yes, Robie, I didn't touch it for that reason... It's ready for
debugging. It's Christian's machine for dpdk testing on MAAS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
I'm seeing something that looks just like this in a dep8 mantic test
run, where openssh-server is upgraded while preparing the testbed and
postinst fails[1]:
977s Preparing to unpack .../openssh-sftp-server_1%3a9.3p1-1ubuntu1_amd64.deb
...
977s Unpacking openssh-sftp-server (1:9.3p1-1ubuntu1)
Miriam, if you could preserve the state of the system please if you
still have it for debugging, then that would be helpful.
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Hi,
I'm facing the same issue on the same machine (on MAAS), but I didn't
reach lunar yet: first, I did a do-dist-upgrade from jammy to Kinetic
(prompt normal).
I collected the info requested in comment #2:
ubuntu@node-horsea:~$ sudo fuser -n tcp 22
22/tcp: 1133 214495 214551
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Thank you Steve, documenting what kind of debug data you'd expect helps
me or anyone else who might run into this next time.
Once I'm done with my current tasks on this system I'll try to redeploy
and re-upgrade to check if it happens again.
--
You received this bug notification because you are
> rescue-ssh.target is a disabled or a static unit not running, not
starting it.
Not really a complaint, just informational.
> But I think the underlying issue is that ssh is already on, and I'm logged in
> via it.
> And that makes the service restart of the ssh socket which was added break.
I
As expected, on reboot all is fine for the service status
ubuntu@node-horsea:~$ systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
16 matches
Mail list logo
