On Tue, 08.09.15 07:56, Yeela Kaplan (ykap...@redhat.com) wrote: > > > Thank you for your response. > > > I have tried running: strace -f systemctl --no-ask-password start > > > supervdsmd.service > > > and it still reproduces. > > > but now intead of: > > > bash(3448)─┬─pstree(3625) > > > └─strace(3618)───systemctl(3623)───systemd-tty-ask(3624) > > > > > > I get: > > > bash(3448)─┬─pstree(3586) > > > └─strace(3564)───systemctl(3569) > > > > > > Do you know what systemctl is waiting for then? > > > > Most likely that supervdsmd.service finishes start-up. Maybe there's a > > bug in the unit file regarding notification when it finished start-up? > > > > (You can also tell systemctl to just enqueue a start job, but not wait > > for it to complete. Use --no-block for that). > > This is the unit file: > [Unit] > Description="Auxiliary vdsm service for running helper functions as root" > Requires=libvirtd.service > > [Service] > Type=simple > LimitCORE=infinity > EnvironmentFile=-/etc/sysconfig/supervdsmd > ExecStart=/usr/share/vdsm/daemonAdapter "/usr/share/vdsm/supervdsmServer" > --sockfile "/var/run/vdsm/svdsm.sock" > Restart=always > > > The service works fine on other machines... this is the first time we see it.. > and the service is able to start without systemd.. by just running: > /usr/share/vdsm/daemonAdapter "/usr/share/vdsm/supervdsmServer" --sockfile > "/var/run/vdsm/svdsm.sock" > but hangs for a long time without starting even when using --no-block..
Ah, you are saying that even with --no-block it will block? If so, that indicates a D-Bus problem of some kind. Could you paste the strace output of "systemctl --no-block --no-ask-password start ..." somewhere please? What distro is this? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel