On Tue, Nov 14, 2017 at 07:19:01PM +0100, Holger Schranz wrote: > Ups ... my fault ... > > libvirtd instead libvirt .... > > > etcsvms5:/var/lib/systemd/coredump # coredumpctl info libvirtd > PID: 10177 (libvirtd) > UID: 0 (root) > GID: 0 (root) > Signal: 11 (SEGV) > Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago) > Command Line: /usr/local/sbin/libvirtd -d > Executable: /usr/local/sbin/libvirtd > Control Group: / > Slice: -.slice > Boot ID: 4d5f74eefb0244c2bc3b2c99986dcee8 > Machine ID: beeb301fe87a14b2eabdb6a75a01cbae > Hostname: etcsvms5 > Coredump: /var/lib/systemd/coredump/core.libvirtd.0.4d5f74eefb0244c2bc3b2c99986dcee8.10177.1510650692000000.xz > Message: Process 10177 (libvirtd) of user 0 dumped core. > etcsvms5:/var/lib/systemd/coredump # coredumpctl dump libvirtd > PID: 10177 (libvirtd) > UID: 0 (root) > GID: 0 (root) > Signal: 11 (SEGV) > Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago) > Command Line: /usr/local/sbin/libvirtd -d > Executable: /usr/local/sbin/libvirtd > Control Group: / > Slice: -.slice > Boot ID: 4d5f74eefb0244c2bc3b2c99986dcee8 > Machine ID: beeb301fe87a14b2eabdb6a75a01cbae > Hostname: etcsvms5 > Coredump: /var/lib/systemd/coredump/core.libvirtd.0.4d5f74eefb0244c2bc3b2c99986dcee8.10177.1510650692000000.xz > Message: Process 10177 (libvirtd) of user 0 dumped core. > Refusing to dump core to tty. > etcsvms5:/var/lib/systemd/coredump # Probably need to try 'coredumpctl gdb libvirtd' to launch the debugger from where you can use 'thread apply all backtrace' to get the stack Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
