[systemd-devel] loginctl hangs when run at boot time

Jeff Solomon jsolomon8080 at gmail.com
Thu Apr 5 06:19:57 UTC 2018


Hi,

On the CentOS7 AWS with the following systemd installed:

    systemd-219-42.el7_4.4.x86_64

Any loginctl command that we try to run at boot time (during the AWS "user
data" section of cloud-init), will hang and then timeout.

The same loginctl command run after you ssh into the box and become root,
works fine.

I can currently get around this problem by running:

    systemd-run loginctl ....

which implies that something about the boot time execution environment
doesn't allow loginctl to run.

When I strace the hanging command, I can see that it's waiting on
/run/dbus/system_bus_socket.

I don't think I have a unit ordering problem because systemd-run is able to
run the command. It must be the environment.

Sorry for what must be a dumb question, but what is different about the
execution environment at boot time that is preventing loginctl from running?

Thanks,

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180404/54a52d7e/attachment.html>


More information about the systemd-devel mailing list