[08:47] <Moha> There's an error that does not allow to update/upgrade the system: `Aborted (core dumped)... 99%` <---- https://paste.ubuntu.com/p/dTbKtyBy28/
[08:50] <Moha> I also can't install or remove anything! the same problem: `Aborted (core dumped)`
[08:51] <Moha> Version: 22.04.2
[08:52] <tomreyn> Moha: hmm, that's pretty bad. i assume you get the same when youssing apt-get instead?
[08:53] <tomreyn> are you using third party software? how was this system installed?
[08:54] <tomreyn> what is this first repository listed, "http://ubuntu-cloud.repos.abramad.com/ubuntu jammy-updates/zed"?
[08:55] <Moha> `apt-get` returns same error. It's part of an ELK cluster that the other two machines are ok. 
[08:56] <Moha> That is a local repository for openstack stuff. It's a mirror.
[08:57] <tomreyn> ah that's openstack zed, i see
[08:58] <Moha> Nothing has been installed from this repo yet.
[08:59] <tomreyn> do you have any errors in     journalctl -b -p3
[08:59] <tomreyn> i'm wondering whether maybe there can be a hardware or file system error,
[08:59] <Moha> yes:
[09:00] <tomreyn> !paste
[09:00] <Moha> tomreyn: it's just one line (:
[09:00] <Moha> `Mar 10 01:48:49 logging01-elastic-logstash sshd[3254]: pam_systemd(sshd:session): Failed to release session: Interrupted system call`
[09:01] <Moha> !pastebinit
[09:02] <tomreyn> so.. it's rather unusual that apt (and apt-get) would just segfault
[09:03] <Moha> can I reinstall apt by `dpkg` somehow?
[09:03] <tomreyn> you can try analyzing the core file, but that's a bit advanced
[09:04] <tomreyn> you can download and reinstall the apt packages, but if this is a deployed system i would just deploy it again
[09:05] <tomreyn> did you make changes to the default python release on this system by chance?
[09:08] <tomreyn> you can use    dpkg -l <packagename>    to see which package version is installed, and compare that to the other systems
[09:09] <tomreyn> if you have different package versions for apt or its libraries, this may hint on a problem
[09:13] <tomreyn> sometimes it helps to delete the package cache: sudo rm /var/cache/apt/*pkgcache.bin
[09:15] <tomreyn> but this segfault situation should not occur in the first place, hints at some deeper problem (if this is a VM / container and you have access to the host system, it may be good to check the systemd jounral / dmesg there, too)
[17:00] <athos> paride4: I just filed https://salsa.debian.org/debian/isc-kea/-/merge_requests/26
[17:00] -ubottu:#ubuntu-server- Merge 26 in debian/isc-kea "d/rules: add strict shlibs control file" [Opened]
[17:02] <athos> do you think this would be sth we could land before the next Debian freeze on the 12th? I know it is a last minute thing, and if this is not OK I will also add a delta in ubuntu for this one
[17:03] <athos> AFAIU https://release.debian.org/bullseye/freeze_policy.html#hard, we can still upload it after the 12th, but it will take 20 days to migrate
[17:04] <athos> in this latter case, I will still add a delta in ubuntu since we will not be able to sync it before ubuntu's beta freeze
[17:10] <paride> athos, hmm I'm unable to review it right now (eow). does it fix a specific bug?
[17:24] <athos> paride: not really. And it should not have little to no impact now that there are no reverse dependencies using those libraries other than packages within kea itself. In Debian, this is definitely something that could wait for the next release. In Ubuntu, this is part of the work for the MIR process
[17:25] <athos> there is no rush. I just pinged in case you were still around since the freeze is on sunday. I will move forward to include it as a delta in ubuntu :)
[17:26] <athos> have a great weekend, paride!!!