[systemd-devel] v33 - crashes on 'systemctl enable'?

Frederic Crozat fcrozat at suse.com
Tue Aug 16 01:25:06 PDT 2011


Le lundi 15 août 2011 à 19:12 +0300, Mantas M. a écrit :
> So I just had systemd (v33 Arch Linux) crash while running "systemctl enable nscd.service" -- twice (after reboot).
> 
> Syslog:
> | sudo:  grawity : TTY=pts/2 ; PWD=/home/grawity ; USER=root ; COMMAND=/bin/systemctl start nscd.service
> | sudo:  grawity : TTY=pts/2 ; PWD=/home/grawity ; USER=root ; COMMAND=/bin/systemctl enable nscd.service
> | systemd[1]: Caught <ABRT>, dumped core as pid 3238.
> | systemd[1]: Executing crash shell in 10s...
> | systemd[1]: Successfully spawned crash shell as pid 3242.
> | systemd[1]: Freezing execution.
> 
> "gdb -p 1":
> | (gdb) bt
> | #0  0x00007fc9e97260e0 in __pause_nocancel () from /lib/libpthread.so.0
> | #1  0x000000000046a69d in ?? ()
> | #2  0x000000000040a638 in ?? ()
> | #3  <signal handler called>
> | #4  0x00007fc9e8bc4725 in raise () from /lib/libc.so.6
> | #5  0x00007fc9e8bc5b9b in abort () from /lib/libc.so.6
> | #6  0x00007fc9e9963955 in ?? () from /usr/lib/libdbus-1.so.3
> | #7  0x00007fc9e995abe7 in ?? () from /usr/lib/libdbus-1.so.3
> | #8  0x00007fc9e994da2b in dbus_message_iter_append_basic () from /usr/lib/libdbus-1.so.3
> | #9  0x000000000043aaa5 in ?? ()
> | #10 0x000000000043d81e in ?? ()
> | #11 0x00007fc9e99518a1 in ?? () from /usr/lib/libdbus-1.so.3
> | #12 0x00007fc9e99437c0 in dbus_connection_dispatch () from /usr/lib/libdbus-1.so.3
> | #13 0x000000000043968a in ?? ()
> | #14 0x0000000000410b9c in ?? ()
> | #15 0x000000000040885d in ?? ()
> | #16 0x00007fc9e8bb113d in __libc_start_main () from /lib/libc.so.6
> | #17 0x00000000004098bd in ?? ()
> | #18 0x00007fff2f102c98 in ?? ()
> | #19 0x00000000ffffffff in ?? ()
> | #20 0x0000000000000001 in ?? ()
> | #21 0x00007fff2f103fd3 in ?? ()
> | #22 0x0000000000000000 in ?? ()
> 
> I have no clue what else to include in a crash report... The system is still up and running, though.

I'm also seeing similar crashes on openSUSE Factory :


#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb754ae5f in raise () from /lib/libc.so.6
#2  0x08051be3 in crash (sig=6) at src/main.c:121
#3  <signal handler called>
#4  0xffffe430 in __kernel_vsyscall ()
#5  0xb754ae5f in raise () from /lib/libc.so.6
#6  0xb754c7f5 in abort () from /lib/libc.so.6
#7  0xb7722305 in _dbus_abort () at dbus-sysdeps.c:94
#8  0xb771830b in _dbus_warn_check_failed (
    format=0xb77281e8 "arguments to %s() were incorrect, assertion \"%s
\" failed in file %s line %d.\nThis is normally a bug in some
application using the D-Bus library.\n") at dbus-internals.c:289
#9  0xb7708ffc in dbus_message_iter_append_basic (iter=0xbf891d3c,
type=98,
    value=0xbf891de4) at dbus-message.c:2514
#10 0x08088b84 in message_from_file_changes (m=<optimized out>,
    changes=0x8189a48, n_changes=1, carries_install_info=2)
    at src/dbus-manager.c:448
#11 0x0808bec1 in bus_manager_message_handler (connection=0x818a1d8,
    message=0x8199e28, data=0x811e5c8) at src/dbus-manager.c:1365
#12 0xb770d9db in _dbus_object_tree_dispatch_and_unlock (tree=0x818ab38,
    message=0x8199e28, found_object=0xbf892368) at
dbus-object-tree.c:862
#13 0xb76fd599 in dbus_connection_dispatch (connection=0x818a1d8)
    at dbus-connection.c:4644
#14 0x0808748c in bus_dispatch (m=0x811e5c8) at src/dbus.c:521
#15 0x08059353 in manager_loop (m=0x811e5c8) at src/manager.c:2426
#16 0x0804f6d2 in main (argc=1, argv=0xbf892834) at src/main.c:1317



-- 
Frederic Crozat <fcrozat at suse.com>
SUSE



More information about the systemd-devel mailing list