[systemd-devel] Cannot start service due to 'systemd-tty-ask-password-agent --watch' not answering

[Lennart Poettering]

On Tue, 08.09.15 10:47, Yeela Kaplan (ykaplan at redhat.com) wrote:

> 
> 
> ----- Original Message -----
> > From: "Lennart Poettering" <lennart at poettering.net>
> > To: "Yeela Kaplan" <ykaplan at redhat.com>
> > Cc: systemd-devel at lists.freedesktop.org, "Oved Ourfali" <ovedo at redhat.com>, "Dan Kenigsberg" <danken at redhat.com>
> > Sent: Tuesday, September 8, 2015 4:48:31 PM
> > Subject: Re: [systemd-devel] Cannot start service due to 'systemd-tty-ask-password-agent --watch' not answering
> > 
> > On Tue, 08.09.15 07:56, Yeela Kaplan (ykaplan at 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?
> 
> It's not blocking, but it also does not start the service so it is
> not a notification issue.. 

Hmm? You wrote earlier that systemctl was hanging. Is it hanging or
isn't it hanging?

> That's the strace:
> https://paste.fedoraproject.org/264808/72290914/

That shows that systemctl exits cleanly with exit code 0...

What precisely is the problem? You now say that systemctl wasn't
hanging and show me that it exits with exit code 0, so there's nothing
wrong from what I can see. Not sure what you are trying to say at all?

Lennart

-- 
Lennart Poettering, Red Hat