[opensuse-buildservice] Workers building Staging:E are stuck
Hi, all the workers building openSUSE:Factory:Staging:E are stuck with a segfault in systemd, e.g.: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:E... Kind regards, Stefan Log excerpt: [ 11s] copying packages... [ 18s] reordering...cycle: libcrack2 -> cracklib [ 18s] breaking dependency libcrack2 -> cracklib [ 18s] done [ 18s] BFD: /var/cache/obs/worker/root_4/.mount/.build.kernel.xen: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss [ 19s] ### WATCHDOG MARKER START ### [ 19s] booting xen... [ 19s] xl create -c /var/tmp/build.xen.conf-iZjHG2Cab name="build_4" disk=[ "phy:/dev/dm-6,hda1,w", "phy:/dev/dm-7,hda2,w" ] extra="panic=1 quiet init=/.build/build rd.driver.pre=binfmt_misc elevator=noop console=ttyS0" [ 19s] Parsing config from /var/tmp/build.xen.conf-iZjHG2Cab [ 20s] [ 0.154583] PCI: Fatal: No config space access function found [ 20s] [ 0.161736] Unable to read sysrq code in control/sysrq [ 26s] [ 5.474026] i8042: No controller found [ 26s] [ 5.482103] mce: Unable to init device /dev/mcelog (rc: -5) [ 26s] [ 5.556674] systemd[1]: segfault at 8 ip 00007f3e5d6a4793 sp 00007ffe80f3b4f8 error 4 in libc-2.21.so[7f3e5d626000+199000] [ 26s] [ 5.559622] systemd[1]: Caught <SEGV>, dumped core as pid 69. [ 26s] [ 5.559773] systemd[1]: Freezing execution. [ 325s] ### WATCHDOG TRIGGERED, KILLING VM ### -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 21 July 2015, 16:30:27 wrote Brüns, Stefan:
Hi,
all the workers building openSUSE:Factory:Staging:E are stuck with a segfault in systemd, e.g.: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:E...
Kind regards,
Stefan
Log excerpt:
[ 11s] copying packages... [ 18s] reordering...cycle: libcrack2 -> cracklib [ 18s] breaking dependency libcrack2 -> cracklib [ 18s] done [ 18s] BFD: /var/cache/obs/worker/root_4/.mount/.build.kernel.xen: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss [ 19s] ### WATCHDOG MARKER START ### [ 19s] booting xen... [ 19s] xl create -c /var/tmp/build.xen.conf-iZjHG2Cab name="build_4" disk=[ "phy:/dev/dm-6,hda1,w", "phy:/dev/dm-7,hda2,w" ] extra="panic=1 quiet init=/.build/build rd.driver.pre=binfmt_misc elevator=noop console=ttyS0" [ 19s] Parsing config from /var/tmp/build.xen.conf-iZjHG2Cab [ 20s] [ 0.154583] PCI: Fatal: No config space access function found [ 20s] [ 0.161736] Unable to read sysrq code in control/sysrq [ 26s] [ 5.474026] i8042: No controller found [ 26s] [ 5.482103] mce: Unable to init device /dev/mcelog (rc: -5) [ 26s] [ 5.556674] systemd[1]: segfault at 8 ip 00007f3e5d6a4793 sp 00007ffe80f3b4f8 error 4 in libc-2.21.so[7f3e5d626000+199000] [ 26s] [ 5.559622] systemd[1]: Caught <SEGV>, dumped core as pid 69. [ 26s] [ 5.559773] systemd[1]: Freezing execution. [ 325s] ### WATCHDOG TRIGGERED, KILLING VM ###
Hm, you have also an own systemd in your project. So there are good chances that this one is breaking here. You need to debug this using a local "osc build --vm-type=kvm" build IMHO. No idea how to debug systemd though, I suppose starting it via a gdb is not working? -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 2015-07-21 19:08, Adrian Schröter wrote:
[ 26s] [ 5.482103] mce: Unable to init device /dev/mcelog (rc: -5) [ 26s] [ 5.556674] systemd[1]: segfault at 8 ip 00007f3e5d6a4793 sp 00007ffe80f3b4f8 error 4 in libc-2.21.so[7f3e5d626000+199000] [ 26s] [ 5.559622] systemd[1]: Caught <SEGV>, dumped core as pid 69. [ 26s] [ 5.559773] systemd[1]: Freezing execution. [ 325s] ### WATCHDOG TRIGGERED, KILLING VM ###
Hm, you have also an own systemd in your project. So there are good chances that this one is breaking here.
You need to debug this using a local "osc build --vm-type=kvm" build IMHO.
No idea how to debug systemd though, I suppose starting it via a gdb is not working?
Well, you can start systemd via systemd-nspawn, though that is not exactly the same as a domU. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Jul 21, 2015 at 07:30:15PM +0200, Jan Engelhardt wrote:
On Tuesday 2015-07-21 19:08, Adrian Schröter wrote:
[ 26s] [ 5.482103] mce: Unable to init device /dev/mcelog (rc: -5) [ 26s] [ 5.556674] systemd[1]: segfault at 8 ip 00007f3e5d6a4793 sp 00007ffe80f3b4f8 error 4 in libc-2.21.so[7f3e5d626000+199000] [ 26s] [ 5.559622] systemd[1]: Caught <SEGV>, dumped core as pid 69. [ 26s] [ 5.559773] systemd[1]: Freezing execution. [ 325s] ### WATCHDOG TRIGGERED, KILLING VM ###
Hm, you have also an own systemd in your project. So there are good chances that this one is breaking here.
You need to debug this using a local "osc build --vm-type=kvm" build IMHO.
No idea how to debug systemd though, I suppose starting it via a gdb is not working?
Well, you can start systemd via systemd-nspawn, though that is not exactly the same as a domU.
Staging:E is actually the systemd version upgrade. Jan or Cristian need to debug it. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 21 July 2015 23:09:10 Marcus Meissner wrote:
On Tue, Jul 21, 2015 at 07:30:15PM +0200, Jan Engelhardt wrote:
[ 26s] [ 5.482103] mce: Unable to init device /dev/mcelog (rc: -5) [ 26s] [ 5.556674] systemd[1]: segfault at 8 ip 00007f3e5d6a4793 sp 00007ffe80f3b4f8 error 4 in libc-2.21.so[7f3e5d626000+199000] [ 26s] [ 5.559622] systemd[1]: Caught <SEGV>, dumped core as pid 69. [ 26s] [ 5.559773] systemd[1]: Freezing execution. [ 325s] ### WATCHDOG TRIGGERED, KILLING VM ###
Hm, you have also an own systemd in your project. So there are good chances that this one is breaking here.
You need to debug this using a local "osc build --vm-type=kvm" build IMHO.
No idea how to debug systemd though, I suppose starting it via a gdb is not working?> Well, you can start systemd via systemd-nspawn, though that is not exactly
On Tuesday 2015-07-21 19:08, Adrian Schröter wrote: the same as a domU.
Staging:E is actually the systemd version upgrade. Jan or Cristian need to debug it.
Ciao, Marcus
I actually had two concerns here: 1. Broken package, in this case systemd Happens, but will eventually be dealt with by the package maintainers 2. Stuck worker About 20 workers were in a busy state for about 8 hours, without doing anything useful. I would have expected the build process to fail and the worker commencing with the next workload. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (5)
-
Adrian Schröter -
Brüns, Stefan -
Jan Engelhardt -
Marcus Meissner -
Stefan Bruens