"David Highley wrote:" > > "Lennart Poettering wrote:" > > > > On Mon, 04.03.13 07:56, David Highley (dhighley@xxxxxxxxxxxxxxxxxxxxxxx) wrote: > > > > > Twice now we have one Fedora 18 system where systemd seems to get into a > > > non responsive state. We are not able to get the status of any service > > > and we're not able to do an init 6 to restart the system. > > > > > > Did notice today that a full process list showed a message about abrt > > > and something to the effect "nobody cared". We also see a number of > > > defunct processes that seem to never clear. So far the only remedy we > > > have found is a hard power cycle. > > > > Can you get a stack trace of PID1? "sudo pstack 1" should already give a > > hint, but even better would be a a "bt full" via gdb. > > We are offsite right now so will dig deeper later. We had checked the > log files and noticed that it complains about rsyncd not being able to > connect to a port and there was another complaint about Gnome. The > rsync one repeats as there are back ups that are not being serviced > which is is what alerted to something being wrong. We are sending and > receiving email from this system. It also has an internal web, mysql, > and other subsystems which seem to work fine. So when this state occurs > it sometimes takes a while to notice. > Quick check with pstack 1: > #0 0x00007fe7f949d3d0 in __pause_nocancel () from /lib64/libc.so.6 > #1 0x00007fe7fb11fe6d in freeze () > #2 0x00007fe7fb0c6d9c in crash () > #3 <signal handler called> > #4 0x00007fe7f91a8601 in pcre_exec () from /lib64/libpcre.so.1 > #5 0x00007fe7fac7446c in lookup () from /lib64/libselinux.so.1 > #6 0x00007fe7fac6d764 in selabel_lookup_common () from /lib64/libselinux.so.1 > #7 0x00007fe7fac6db9b in selabel_lookup_raw () from /lib64/libselinux.so.1 > #8 0x00007fe7fb10cab7 in label_mkdir () > #9 0x00007fe7fb10cfc4 in makedir_parents () > #10 0x00007fe7fb10c091 in cg_create () > #11 0x00007fe7fb100f38 in cgroup_bonding_realize () > #12 0x00007fe7fb101011 in cgroup_bonding_realize_list () > #13 0x00007fe7fb0f2433 in exec_spawn () > #14 0x00007fe7fb0d74a2 in service_spawn () > #15 0x00007fe7fb0da6f7 in service_enter_start () > #16 0x00007fe7fb0dacf8 in service_start () > #17 0x00007fe7fb131209 in job_run_and_invalidate () > #18 0x00007fe7fb0c9566 in manager_dispatch_run_queue () > #19 0x00007fe7fb0cbd00 in manager_loop () > #20 0x00007fe7fb0c48ae in main () Another piece of information is: Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused This messages comes from any attempt to use systemctl. > > > > > Lennart > > > > -- > > Lennart Poettering - Red Hat, Inc. > > -- > > devel mailing list > > devel@xxxxxxxxxxxxxxxxxxxxxxx > > https://admin.fedoraproject.org/mailman/listinfo/devel > > > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel > -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
