[00:54] <ruben23> hi guys any idea my key in data on crontab -e, after some tiem suddenly dissapear and its empty, any idea what might be the issue
[06:05] <cpaelzer> coreycb: interesting - that should only be a problem for the UCA backport since Bionic has python3.6 and not an issue for the 3.8 in focal right?
[07:09] <lordievader> Good morning
[09:38] <albech> My apache webserver crashes randomly during graceful restarts: https://paste.ubuntu.com/p/dQsr6mgzvD/
[09:50] <kiokoman> albech: you are not alone https://stackoverflow.com/questions/54213685/apache-seg-fault-krb5int-key-delete-assertion-destructors-setkeynum-1-fail https://krbdev.mit.edu/rt/Ticket/Display.html?id=8863
[09:51] <albech> kiokoman: yeah i saw that one, but no solution :/
[09:52] <kiokoman> we need to wait i suppose -_(O_O)_-
[09:52] <albech> guess so.. thanks anyway
[09:53] <albech> meanwhile.. i may write a script that checks if its down and do a hard restart
[09:58] <tomreyn> geez using RT as a bug tracker is a really bad idea
[10:00] <tomreyn> albech: please make sure you file a bug agains tthe relevant package in ubuntu if this hasn't been reported against ubuntu on launchpad, yet
[10:01] <albech> tomreyn: working on just that right now
[10:01] <tomreyn> is this backed by a "snap" (snapcraft.io) package? "mod_fastcgi/mod_fastcgi-SNAP-0910052141"
[10:01] <tomreyn> albech: great, make sure you use the "ubuntu-bug" command so log files are added, too
[10:02] <tomreyn> alternatively use "apport-collect BUGID" on the affected system after filing the report.
[11:26] <CrummyGummy>  Hi! Have any of you seen a problem where an IP address gets changed on a container with dhcp and the old routes remain?
[11:27] <CrummyGummy> Maybe some netplan wierdness but the containers now have old source addresses attached to the routes and it's messing up my networking.
[11:27] <CrummyGummy> I'm not really even sure why the ip addresses are changing anyway tbh.
[11:37] <CrummyGummy> how does Netplan control dhcp anyway?
[11:37] <CrummyGummy> does it run dhcp-client?
[11:41] <rbasak> It configured systemd-networkd or Network Manager.
[11:41] <rbasak> They take care of DHCP as necessary.
[11:41] <rbasak> configures*
[11:56] <friendlyguy> hi there! i am struggeling with a ubuntu vm where /boot has 0 free space left
[11:56] <friendlyguy> its 18.04, but it has been release upgraded several times
[11:57] <lordievader> friendlyguy: How large is your `/boot` and how many kernels/initramfs-es are on there?
[11:57] <friendlyguy> boot is 236mb
[11:58] <friendlyguy> about 9 of them
[11:58] <lordievader> Yeah, that is rather small.
[11:58] <friendlyguy> autoremove doesnt work
[11:58] <lordievader> Especially for that number of kernels.
[11:58] <friendlyguy> yup, its default from the setup
[11:58] <friendlyguy> never changed it
[11:58] <lordievader> Manually remove the kernels except for the last and in use ones.
[11:58] <friendlyguy> i just assumed that the size would make sense back then
[11:59] <lordievader> For a couple of kernels (<=3) it is fine.
[11:59] <friendlyguy> okay, i check with uname -a which kernel version i run and delete all others in boot?
[11:59] <friendlyguy> where can i specify the number of kernels to hold there?
[11:59] <lordievader> Remove the packages.
[12:00] <friendlyguy> is this usually done with "autoremove"?
[12:00] <ducasse> friendlyguy: use dpkg -P to remove them
[12:00] <lordievader> If only `linux-image-generic` (or however Ubuntu calls the package) is installed this should happen automatically.
[12:00] <friendlyguy> i have a couple of vmlinuz files, a couple of initrd files, a couple of config files
[12:01] <lordievader> friendlyguy: Only if the versions are not explicitly installed.
[12:02] <friendlyguy> i never installed a version "manually", only ever ran upgrades
[12:03] <friendlyguy> so... do i delete the files that do not match with the kernel version, or do i uninstall them with dpkg -P?
[12:03] <lordievader> friendlyguy: What is the output of `dpkg -l|grep linux-image`?
[12:05] <friendlyguy> https://paste.ubuntu.com/p/HHQrsMxkvw/
[12:08] <lordievader> friendlyguy: `sudo apt purge linux-image-4.{15.0-5{5,8},4.0-154}-generic`
[12:08] <lordievader> Whatever is left of those other 9 minus 4.15.0-60 need to be removed manually.
[12:19] <ducasse> friendlyguy: use dpkg
[12:22] <friendlyguy> back again
[12:22] <friendlyguy> okay, lets try that
[12:22] <friendlyguy> argh, cant copy paste any more... brb
[12:24] <friendlyguy> okay, that failed because of unmatched dependencies
[12:25] <friendlyguy> https://paste.ubuntu.com/p/3F4yKPRDCv/
[12:28] <friendlyguy> when i do the --fix-broken i get this: https://paste.ubuntu.com/p/WgsM7tbQFg/
[12:28] <friendlyguy> back in half an hour... need to eat somethign
[12:37] <lordievader> friendlyguy: Are you mixing repos?
[13:22] <coreycb> cpaelzer: yes that just affects bionic with python 3.6
[13:40] <friendlyguy> lordievader: erm... not intentionally
[13:40] <friendlyguy> how can i verify that? check the sources.list?
[13:42] <lordievader> Yes, and the contents of `/etc/apt/sources.list.d/*.list`
[13:42] <friendlyguy> https://paste.ubuntu.com/p/PXcX8vc7CB/
[13:42] <friendlyguy> thats what i have in the sources.list
[13:42] <friendlyguy> i dont remember editing it though
[13:43] <friendlyguy> oh, there are a bunch of config in the sources.list.d folder
[13:47] <friendlyguy> deb http://ppa.launchpad.net/ondrej/php/ubuntu xenial main
[13:47] <friendlyguy> thats the only one in the sources.list.d that isnt commented out
[13:49] <friendlyguy> ah, xenial looks old... shall i get rid of it?
[13:50] <friendlyguy> ah, i just noticed thats a repo for php versions
[13:57] <friendlyguy> all others were disabled during migration to trusty/xenial/bionic
[13:57] <lordievader> Your sources look sane.
[13:57] <lordievader> Are there updates available?
[14:01] <friendlyguy> yup, but cant install: 0 space left on boot
[14:06] <lordievader> Hrmm
[14:06] <lordievader> Well, guess (re)moving old kernels is the easiest way around this.
[14:11] <friendlyguy> removing as in delete it from the filesystem without using a package manager, right?
[14:18] <lordievader> Yes
[14:25] <friendlyguy> okay, let me try that
[14:25] <coreycb> jamespage: sahid: all the current backport failures will get fixed up once pandas gets to bionic-updates. I'll push on that monday.
[14:28] <friendlyguy> okay, cleaned all that stuff... (there even was a 3.3 kernel around)
[14:29] <friendlyguy> so... shall i update now, or try to "autoremove" or... whats the best way to continue?
[14:29] <friendlyguy> the --fix-broken?
[14:41] <lordievader> Yes, update. And then remove/purge the old kernel packages.
[14:42] <friendlyguy> my guess is that this will fill up boot right away again
[14:43] <friendlyguy> (i guess we both meant update == upgrade
[14:43] <friendlyguy> )
[14:43] <sahid> coreycb: ack thanks
[14:54] <lordievader> friendlyguy: Install the available updates, yes. (I know apt calls this upgrade)
[15:03] <friendlyguy> lordievader: wont let me... i need to run the fix-broken first: https://paste.ubuntu.com/p/VRpnzZfqp6/
[15:04] <lordievader> Hrmm, do that first then 😉
[15:05] <friendlyguy> lets c if that works or if i run out of space again
[15:05] <friendlyguy> ~200mb free space on boot
[15:08] <friendlyguy>  APT had planned for dpkg to do more than it reported back (78 vs 82).
[15:08] <friendlyguy>    Affected packages: initramfs-tools:amd64
[15:08] <friendlyguy> but apart from that it went through nicely
[15:09] <friendlyguy> 60 mb space left
[15:09] <friendlyguy> running a autoremove now to get rid of old entries
[15:10] <friendlyguy> okay, so far so good. rebooting to switch to the new kernel now...
[15:14] <friendlyguy> yay, that did work :)
[15:14] <friendlyguy> running a upgrade now
[15:15] <friendlyguy> btw, kernel now is 4.15.0-76-generic
[15:23] <friendlyguy> oh boy... now it looks like things go south
[15:26] <friendlyguy> https://paste.ubuntu.com/p/6QwFrZyDnD/
[15:26] <friendlyguy> tried to install the old kernels again and fille boot up again
[15:27] <friendlyguy> i cant figure out why
[15:28] <friendlyguy> everything looked good after the autoremove... until i ran the "apt upgrade"
[15:28] <friendlyguy> i guess there is a old package somewhere with dependencies to a very very old kernel
[15:29] <friendlyguy> but still, why would it pull multiple old kernels?
[15:29] <friendlyguy> frustrating
[15:29] <friendlyguy> lordievader: got an idea for me?
[15:40] <itsame> "gzip: stdout: No space left on device" ?
[15:43] <itsame> always a bit situation to be in =X if you have a bood cd you could move things around a bit after a backup (making boot a bit bigger)
[15:46] <sdeziel> friendlyguy (if you come back), I sometimes resort to truncating a vmlinuz and initrd when I'm *sure* they are not needed anymore. To truncate: "> /boot/vmlinuz-$FOO"
[15:47] <itsame> aptitude why <packagename> <- helps to figure what causes a package to be installed
[15:47] <sdeziel> by nuking a bunch of unused initrd, you should reclaim a good chunk of space
[15:54] <itsame> interesting, one of the older version kernels is installed because it provides aufs-dkms on my machine, which is also provided by the newer version, but i guess the way the dependecies resolves causes it to still be flagged as required
[15:55] <itsame> ((vaguely described xD))
[15:57] <itsame> sdeziel: you think that can be seen as bug? i wonder somehow
[15:59] <sdeziel> itsame: dunno, I was just trying to give some cues to friendlyguy on how to deal with his out of space problem on the rootfs
[16:02] <itsame> i think about it some more later and when i get around to it file a bugreport i guess
[17:38] <rbasak> bryce: CI passed on https://code.launchpad.net/~racb/usd-importer/+git/usd-importer/+merge/378744, ready to go. No major rush. Monday would be fine - I've got other bits to get on with.
[17:38] <bryce> ok