2010/10/16 Andrey Borzenkov <[email protected]>: > (Working on Mandriva cooker), systemd v11. > > {pts/0}% sudo rpm -Fvh RPMS/x86_64/* > Подготовка... ########################################### [100%] > 1:systemd-units ########################################### [ 50%] > 2:systemd ########################################### [100%] > 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. > > Well, systemd post re-executes systemd and systemd-units reloads it. > Is it possible that systemd is busy with reloading so it does not > respond to request for re-execution? > > Somehow I am not really fond of simply increasing timeout in > daemon_reload() but may be this is the simplest solution. >
May be not. This just happened with only daemon-reexec call. Here is /var/log/messages for installation: Oct 16 19:40:16 cooker urpmi: transaction on / (remove=0, install=0, upgrade=4) Oct 16 19:40:23 cooker perl: [RPM] systemd-debug-11-2mdv2011.0 installed Oct 16 19:40:24 cooker perl: [RPM] lib64cairomm1.0_1-1.9.2-1mdv2011.0 installed Oct 16 19:40:25 cooker perl: [RPM] systemd-units-11-2mdv2011.0 installed Oct 16 19:40:25 cooker dbus-daemon: [system] Reloaded configuration Oct 16 19:40:25 cooker dbus-daemon: [system] Reloaded configuration Oct 16 19:40:25 cooker dbus-daemon: [system] Reloaded configuration Oct 16 19:40:27 cooker perl: [RPM] systemd-11-2mdv2011.0 installed Oct 16 19:40:27 cooker systemd[1]: Reexecuting. Oct 16 19:40:27 cooker systemd[1]: systemd 11 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX +SYSVINIT; fedora) Oct 16 19:40:27 cooker systemd[1]: [/etc/rc.d/init.d/networker:13] Failed to add LSB Provides name nsrexecd.service, ignoring: File exists Oct 16 19:40:27 cooker systemd[1]: [/etc/rc.d/init.d/iptables:18] Failed to add LSB Provides name firewall.service, ignoring: File exists Oct 16 19:40:27 cooker systemd[1]: Unit vmware.service entered failed state. Oct 16 19:40:27 cooker systemd[1]: Startup finished in 3s 671ms 10us (kernel) + 1h 18min 8s 806ms 88us (userspace) = 1h 18min 12s 477ms 98us. Oct 16 19:40:28 cooker perl: [RPM] systemd-11-1mdv2011.0 removed Oct 16 19:40:30 cooker perl: [RPM] systemd-units-11-1mdv2011.0 removed Oct 16 19:40:31 cooker perl: [RPM] lib64cairomm1.0_1-1.9.1-1mdv2011.0 removed Oct 16 19:40:31 cooker perl: [RPM] systemd-debug-11-1mdv2011.0 removed So systemd was actually re-executed just fine; but for some reasons systemctl failed to get reply? _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
