[03:48] I often have issues with log files: https://bpa.st/UWPA -> anyone see anything wrong with that? the live.log file doesn't get written sometimes I have to delete it [03:48] oh, likely perms - looks like that file is owned by root [03:52] err, why isn't this showing [03:55] Ok, if I run home/dev/app/live/venv3.9/bin/gunicorn --timeout 900 --workers 1 --log-level=debug --bind unix:live.sock wsgi:web_app by itself in a terminal I can see the error... so it's not getting written to the log file. I've been tolerating this for a while, really curious why this is happening [06:00] good morning [10:06] good morning! [10:09] good morning [10:09] athos! so early for you! === pvdp40 is now known as pvdp4 [12:09] mirespace: well... it is raining here, so there were no early morning outside exercises for me :| [12:18] here is raining too :( [12:21] hi ahasenack and athos [12:23] hrm, I need to check if this might be just my odd setup - anyone running jammy already that could run this for me "qemu-system-x86_64 -cpu host -machine q35,accel=kvm -m 512M -vga qxl -display none -spice port=5903,addr=127.0.0.1" ? [12:23] let me know if it returns "qxl_send_events: spice-server bug: guest stopped, ignoring" for you [12:24] hi cpaelzer [12:24] morning [12:24] I can try that on my old t420, it's on jammy [12:26] cpaelzer: I got exactly that error message [12:26] hrm, thanks [12:26] and it's stalled [12:26] so it is not just me [12:26] it is stalled because we told it nothing useful to do [12:26] I have 1:6.2+dfsg-2u5 [12:26] that stall is fine [12:26] the message disturbs me [12:26] I already have all kind of debug on it [12:26] queue the song [12:26] disturbed [12:26] time to file a bug ... [12:27] what I know so far is "it is jammy" not qemu [12:27] actually, band, not song [12:27] older/newer packaged qemu all work fine in F,H,I but in J all of them expose this - git behaves the same [12:27] and does spice work? [12:28] cpaelzer: Yes, I get "qxl_send_events: spice-server bug: guest stopped, ignoring" here [12:29] thanks athos [12:29] I have 1:6.2+dfsg-2ubuntu5 [12:29] ahasenack: yes spice does work [12:29] ahasenack: there might be a few interrupts not sent though, which sounds like nasty late detect issues [12:30] so I'm glad I started fighting it [12:30] thanks athos [12:36] how can i get kexec working on ubuntu (20.04)? i've tried kexec -l /boot/vmlinuz --initrd=/boot/initrd.im --reuse-cmdline, then systemctl kexec, but it still goes through the full reboot cycle. [12:36] the same commands work on debian 11. [12:41] athos: ahasenack: it seems to be a race at the start resolved later which explains why not fatal issue happen later [12:41] nevertheless I would like to have it gone ... [12:41] there was one thing bothering me in impish, let me check [12:42] a continuous log in dmesg [12:43] [seg mar 14 09:42:58 2022] Lockdown: rpc-worker: debugfs access is restricted; see man kernel_lockdown.7 [12:43] as soon as I start bms [12:43] every 3s [12:43] that comes from libvirt iirc [12:43] one line per running vm it seems, every 3s [12:46] gnuoy: some feedback and questions on https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1883112 [12:46] Launchpad bug 1883112 in ceph-iscsi (Ubuntu Focal) "rbd-target-api crashes with python TypeError" [High, Triaged] [12:46] I'll take a look later [12:47] thanks [13:00] athos: ahasenack: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1964777 [13:00] Launchpad bug 1964777 in qemu (Ubuntu) "qxl_send_events: spice-server bug: guest stopped, ignoring" [Undecided, New] === almostdvs1 is now known as almostdvs [15:10] ahasenack: PM incoming! === GWM-Deus is now known as GWM === sarnold_ is now known as sarnold === smoser1 is now known as smoser