mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: <caglar.kilimci@accenture.com>
To: ejo@pengutronix.de
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Caught an error while installing bundle
Date: Tue, 28 Feb 2017 15:44:34 +0000	[thread overview]
Message-ID: <00cc06db0376417f8f312dbb9e457c4c@BL2PR4205MB0417.048d.mgd.msft.net> (raw)
In-Reply-To: <3f222044-541e-8114-e226-7dd9da12cc3e@pengutronix.de>

Hi Enrico,

> ok, the issue you encounter is that the RAUC service is not running on your system and that the RAUC client, i.e. your command line tool, does not correctly start it via dbus activation.

Thanks a lot. The main reason is this.

> The bug that causes this issue is located in the D-Bus service file `de.pengutronix.rauc.service` and shows that we haven't used non-systemd systems for a long time...
> Am I right in assuming you are using a non-systemd-based system?

Actually no. My system has systemd but neither `service` nor systemctl command is installed on device for now so nobody can start rauc service.

> The reason why activation is not working for the non-systemd case is that the `Exec` argument in the dbus service file lacks the required `service` argument for RAUC in order to be started properly as the background service. Thus the fix is:
>
> --- a/data/de.pengutronix.rauc.service.in
> +++ b/data/de.pengutronix.rauc.service.in
> @@ -1,5 +1,5 @@
>   [D-BUS Service]
>   Name=de.pengutronix.rauc
> -Exec=@bindir@/rauc
> +Exec=@bindir@/rauc service
>   User=root
>   SystemdService=rauc.service
>
>
> Many thanks for revealing this issue! I've created a PullRequest on GitHub for this:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_rauc_rauc_pull_104&d=DwIDaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=upIHLD0Klq6JestBglGOFqnMsu-XuSQmo8ZR72YSuzk&m=v4oRMKmKBbRnJingbFfHqrZCP9xRWoNgl6wzXt1RvCU&s=7cXYEm7-KjhvkFb3cDUseFUViDWGKdkZgNgaFKh_gCs&e=
>

You are welcome. I am happy to help.

> Does this solve your problems?

This patch does not work for me but at least I understand where is the problem. Thank you very much.

Sincerely,
Caglar

________________________________

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.
______________________________________________________________________________________

www.accenture.com
_______________________________________________
RAUC mailing list

      reply	other threads:[~2017-02-28 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 12:27 caglar.kilimci
2017-02-28 13:47 ` Enrico Joerns
2017-02-28 14:24   ` caglar.kilimci
2017-02-28 14:59     ` Enrico Joerns
2017-02-28 15:44       ` caglar.kilimci [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=00cc06db0376417f8f312dbb9e457c4c@BL2PR4205MB0417.048d.mgd.msft.net \
    --to=caglar.kilimci@accenture.com \
    --cc=ejo@pengutronix.de \
    --cc=rauc@pengutronix.de \
    /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