From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: systemd service failing at start
Date: Fri, 11 Jul 2014 10:47:32 +0200 [thread overview]
Message-ID: <lpo8b4$3hd$1@ger.gmane.org> (raw)
In-Reply-To: <CAEaCVQiEEX45zS0PLGrExLxqLofDNht5c7MD9uBDbh4MpbskDA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eduardo Silva schreef op 11-07-14 04:43:
> Hi,
>
> For some reason the systemd service that i plan to use for Monkey HTTP
> Server in Yocto is not starting up when booting the core-image-sato
> image. Once is booting it hangs saying:
>
> [ OK ] Stopped Monkey HTTP Server [ *** ] A Start job is running for
> Run pending postinsts (20min 12s...)
>
> My service file looks like this:
>
> --- start of monkey.service---
>
> [Unit] Description=Monkey HTTP Server Requires=network.target
> remote-fs.target After=network.target remote-fs.target
>
> [Service] Type=forking ExecStart=/usr/bin/monkey --daemon
> PIDFile=/var/run/monkey.pid.2001 TimeoutSec=10
>
> [Install] WantedBy=multi-user.target
>
> -- end--
>
> If i deploy Monkey RPM (cooked by bitbake) on the Sato image and i add
> this service once the system is up, systemd can start the service
> without problems, everything works: start, stop, status, etc. Do i am
> missing something that can be generating some problems on the first boot
> ?
The postinst startup script is blocking boot, you;d have to check which
postinst is causing the holdup.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFTv6SkMkyGM64RGpERAko3AJ9aJCgDtQqTNaDRFx0x0/J0JbE3agCgrYxP
cfEuXH8Qg/Z+jdh6yeCS96U=
=t4rZ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-07-11 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 2:43 systemd service failing at start Eduardo Silva
2014-07-11 6:01 ` Li Zhijian
2014-07-11 7:37 ` Sébastien Mennetrier
2014-07-11 7:31 ` Henning Heinold
2014-07-11 8:47 ` Koen Kooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lpo8b4$3hd$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox