From: Andreas Oberritter <obi@opendreambox.org>
To: Mark Asselstine <mark.asselstine@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] systemd.bbclass: don't block on service restart
Date: Sat, 26 Nov 2016 21:59:17 +0100 [thread overview]
Message-ID: <b0072da0-ee70-0b57-7cf8-e1e800a591bc@opendreambox.org> (raw)
In-Reply-To: <1480047434-20600-1-git-send-email-mark.asselstine@windriver.com>
On 25.11.2016 05:17, Mark Asselstine wrote:
> The current class works fine when a recipe uses SYSTEMD_AUTO_ENABLE
> 'enable' and has no on device pkg_postinst(), ie when the postinst is
> run as part of rootfs creation. However, when there is a component of
> pkg_postinst() that is run on device the 'systemctl restart' is run as
> part of the run_postinsts.service at boot. This results in the boot
> spinning indefinitely with:
>
> [ *** ] A start job is running for Run pending postinsts (7s / no limit)
>
> The issue could potentially be that the packages service has an
> 'After' clause which comes later in the boot, beyond
> run_postinsts.service, creating a chicken before the egg
> scenario. Even service files without an 'After' clause cause this
> situation however. Despite this not being the cause of the issue this
> fix will prevent this scenario from happenning.
>
> Using strace we are able to find that during boot, when
> run_postinsts.service is running attempting to start or restart any
> service will result in the call get stuck on poll(). Since the
> run_postinsts.service does not monitor the outcome of the call to
> restart we can work around this by using '--no-block'.
>
> Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
I was going to submit the exact same patch soon. It also helps to
complete system updates if a service fails to restart properly.
Acked-by: Andreas Oberritter <obi@opendreambox.org>
> ---
> meta/classes/systemd.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/systemd.bbclass b/meta/classes/systemd.bbclass
> index 7e51ed6..99a08a0 100644
> --- a/meta/classes/systemd.bbclass
> +++ b/meta/classes/systemd.bbclass
> @@ -36,7 +36,7 @@ if type systemctl >/dev/null 2>/dev/null; then
> systemctl $OPTS ${SYSTEMD_AUTO_ENABLE} ${SYSTEMD_SERVICE}
>
> if [ -z "$D" -a "${SYSTEMD_AUTO_ENABLE}" = "enable" ]; then
> - systemctl restart ${SYSTEMD_SERVICE}
> + systemctl --no-block restart ${SYSTEMD_SERVICE}
> fi
> fi
> }
>
next prev parent reply other threads:[~2016-11-26 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 4:17 [PATCH] systemd.bbclass: don't block on service restart Mark Asselstine
2016-11-26 20:59 ` Andreas Oberritter [this message]
2016-11-29 17:33 ` Khem Raj
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=b0072da0-ee70-0b57-7cf8-e1e800a591bc@opendreambox.org \
--to=obi@opendreambox.org \
--cc=mark.asselstine@windriver.com \
--cc=openembedded-core@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