[systemd-devel] Race in post scripts for systemd/systemd-units
Lennart Poettering
lennart at poettering.net
Mon Oct 25 15:18:46 PDT 2010
On Sat, 16.10.10 11:07, Andrey Borzenkov (arvidjaar at gmail.com) wrote:
> (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.
This looks like some mixup in the serialization/deserialization code. If
you can reproduce this with current git, could you report back with an
output of "dmesg" with systemd.log_level=debug and
systemd.log_target=kmsg?
Lennart
--
Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel
mailing list