[systemd-devel] How to debug blocking service start?

[Lennart Poettering]

On Fri, 27.03.15 10:32, Kai Hendry (hendry at webconverger.com) wrote:

> First, thanks for trying to help me Kai. Awesome name btw.
> 
> On Fri, 27 Mar 2015, at 03:26 AM, Kai Krakow wrote:
> > Try Type=simple to not let it wait. That is telling systemd, that the
> > binary 
> > will not daemonize - athough it should be default according to [1].
> 
> It's still getting stuck with Type=simple.
> 
> http://s.natalian.org/2015-03-27/simple.png
> 
> Isn't there a better way to debug than running journalctl -u <service>
> -f in parallel?
> 
> The frustrating thing is that the SAME service file works fine on
> another rpi2.

With the unit file in the screenshot above (and the implied
Type=simple) systemd will fork off the process, and immediately
return. If the "systemctl start" operation hangs this means that
something else that runs before it is hanging hence. What does
"systemctl list-jobs" say before you run this and it hangs?

Lennart

-- 
Lennart Poettering, Red Hat