Bug 1049668

Summary:	Failed to issue method call: Activation of org.freedesktop.systemd1 timed out
Product:	[Fedora] Fedora	Reporter:	Álvaro Castillo <midgoon>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	abetakehiko, johannbg, lnykryn, msekleta, plautrba, rjones, systemd-maint, vpavlin, zbyszek
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 10:51:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Álvaro Castillo 2014-01-08 01:32:47 UTC

Description of problem: Cannot show plot, time, blame... results.


Version-Release number of selected component (if applicable):
systemd-python-208-9.fc20.x86_64
systemd-libs-208-9.fc20.x86_64
systemd-208-9.fc20.x86_64

Steps to Reproduce:
1. Open terminal
2. Type: systemd-analyze plot > plot.svg (e.g)
3. Show error message:
" Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. "

Comment 1 Álvaro Castillo 2014-01-08 02:53:09 UTC

Reboot, problem fixed.

Comment 2 Zbigniew Jędrzejewski-Szmek 2014-01-08 03:49:01 UTC

(In reply to Álvaro Castillo from comment #1)
> Reboot, problem fixed.
Well, something *was* wrong. Lack of reply usually means that systemd died. You might want to look in the logs (journalctl -b-1 _PID=1) for interesting messages.

Comment 3 Richard W.M. Jones 2014-03-13 11:05:47 UTC

I have a machine where this keeps happening.

Rebooting the machine fixes it for a day or two, then it's back again
like now:

$ sudo systemctl restart libvirtd
Failed to restart libvirtd.service: Activation of org.freedesktop.systemd1 timed out

How can I debug this further?

Comment 4 Richard W.M. Jones 2014-03-13 11:06:08 UTC

systemd-210-3.fc21.x86_64

Comment 5 Richard W.M. Jones 2014-03-13 11:08:37 UTC

Hmm, turns out systemd core dumped.  And I have the core file.

Mar 06 15:49:17 trick.home.annexia.org systemd[1]: Stopping User Manager for UID 1000...
Mar 06 15:49:17 trick.home.annexia.org systemd[1]: Stopped User Manager for UID 1000.
Mar 06 15:49:17 trick.home.annexia.org systemd[1]: Stopping user-1000.slice.
Mar 06 15:49:17 trick.home.annexia.org systemd[1]: Removed slice user-1000.slice.
Mar 06 15:53:03 trick.home.annexia.org systemd[1]: Starting user-1000.slice.
Mar 06 15:53:03 trick.home.annexia.org systemd[1]: Created slice user-1000.slice.
Mar 06 15:53:03 trick.home.annexia.org systemd[1]: Starting User Manager for UID 1000...
Mar 06 15:53:03 trick.home.annexia.org systemd[1]: Starting Session 65 of user rjones.
Mar 06 15:53:03 trick.home.annexia.org systemd[1]: Started Session 65 of user rjones.
Mar 06 15:53:03 trick.home.annexia.org systemd[1]: Started User Manager for UID 1000.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Starting user-0.slice.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Created slice user-0.slice.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Starting User Manager for UID 0...
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Starting Session 66 of user root.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Started Session 66 of user root.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Started User Manager for UID 0.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Stopping User Manager for UID 0...
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Stopped User Manager for UID 0.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Stopping user-0.slice.
Mar 06 16:01:02 trick.home.annexia.org systemd[1]: Removed slice user-0.slice.
Mar 06 16:03:16 trick.home.annexia.org systemd[1]: Starting PackageKit Daemon...
Mar 06 16:03:16 trick.home.annexia.org systemd[1]: Started PackageKit Daemon.
Mar 06 16:09:46 trick.home.annexia.org systemd[1]: Starting dnf makecache...
Mar 06 16:09:46 trick.home.annexia.org systemd[1]: Started dnf makecache.
Mar 06 16:10:21 trick.home.annexia.org systemd[1]: Starting PackageKit Daemon...
Mar 06 16:10:21 trick.home.annexia.org systemd[1]: Started PackageKit Daemon.
Mar 06 16:20:59 trick.home.annexia.org systemd[1]: Caught <SEGV>, dumped core as pid 15342.
Mar 06 16:20:59 trick.home.annexia.org systemd[1]: Freezing execution.

Comment 6 Richard W.M. Jones 2014-03-13 11:14:28 UTC

Core was generated by `/usr/lib/systemd/systemd --system --deserialize 16'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f920d68962b in raise (sig=sig@entry=11)
    at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
37	  return INLINE_SYSCALL (tgkill, 3, pid, THREAD_GETMEM (THREAD_SELF, tid),
Missing separate debuginfos, use: debuginfo-install libattr-2.4.47-3.fc20.x86_64 pcre-8.33-4.fc20.x86_64 zlib-1.2.8-3.fc20.x86_64
(gdb) t a a bt

Thread 1 (Thread 0x7f920ed458c0 (LWP 19031)):
#0  0x00007f920d68962b in raise (sig=sig@entry=11)
    at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
#1  0x00007f920edebc3c in crash.2510 (sig=11) at ../src/core/main.c:151
#2  <signal handler called>
#3  0x00007f920d673b68 in main_arena () from /lib64/libc.so.6
#4  0x00007f920ee24c1b in bucket_hash (h=0x7f920d673b78 <main_arena+1048>, 
    p=0x4a53) at ../src/shared/hashmap.c:168
#5  hashmap_remove_value (h=0x7f920d673b78 <main_arena+1048>, 
    key=key@entry=0x4a53, value=value@entry=0x7f920fe5f4d0)
    at ../src/shared/hashmap.c:646
#6  0x00007f920ee417ca in unit_unwatch_pid (u=u@entry=0x7f920fe5f4d0, 
    pid=19027) at ../src/core/unit.c:1734
#7  0x00007f920ee0711f in invoke_sigchld_event.3785 (m=<optimized out>, 
    u=0x7f920fe5f4d0, si=0x7fff37b81920) at ../src/core/manager.c:1429
#8  0x00007f920ee0f35c in manager_dispatch_sigchld.3790 (
    m=m@entry=0x7f920fc09500) at ../src/core/manager.c:1477
#9  0x00007f920ed996ec in manager_dispatch_signal_fd.3742 (
    source=<optimized out>, fd=<optimized out>, revents=<optimized out>, 
    userdata=0x7f920fc09500) at ../src/core/manager.c:1723
#10 0x00007f920ee33d41 in source_dispatch (s=0x7f920fc13670)
    at ../src/libsystemd/sd-event/sd-event.c:1861
#11 0x00007f920ee35930 in sd_event_run (e=0x7f920fc099b0, 
    timeout=<optimized out>) at ../src/libsystemd/sd-event/sd-event.c:2117
#12 0x00007f920edada84 in manager_loop (m=0x7f920fc09500)
    at ../src/core/manager.c:1844
#13 0x00007f920ed92f86 in main (argc=4, argv=0x7fff37b82758)
    at ../src/core/main.c:1693

Comment 7 Jaroslav Reznik 2015-03-03 15:22:29 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 8 Fedora End Of Life 2016-07-19 10:51:30 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.