From: Enrico Joerns <ejo@pengutronix.de>
To: dilip yadav <yadav.dilip582@gmail.com>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Update Installation failed
Date: Wed, 5 Apr 2017 12:40:54 +0200 [thread overview]
Message-ID: <a255d589-62d5-ede5-866c-39889d006bc0@pengutronix.de> (raw)
In-Reply-To: <CALC1k0BgzmKuB2NqHOQaTpzTzxO-X+1ua_Nrw+7RqOAwS8WQHA@mail.gmail.com>
Hi Dilip.
On 04/05/2017 12:29 PM, dilip yadav wrote:
> Hi Team,
>
> I am following your example in the docs for grub bootloader on x86_64
> debian machine.
> i have created the rootfs image and trying to update the system via:
>
>> rauc -d install update-2015.04-1.raucb
>
> It throws an error :
>
> Domains: 'rauc'
> (rauc:2879): rauc-DEBUG: install started
> (rauc:2879): rauc-DEBUG: input bundle:
> /home/apaul/rauc/examples/update-2015.04-1.raucb
> trying to contact rauc service
> rauc-Message: installing
> /home/apaul/rauc/examples/update-2015.04-1.raucb: installing
> installing `/home/apaul/rauc/examples/update-2015.04-1.raucb` failed
well, from this log I am not able to get what went wrong. I would need
the log of the RAUC service in order to give a hint about what went wrong.
Unfortunately, currently there is no way to access the service log from
the command line client.
Thus, what you can do, if you have set up your system with systemd is
executing
journalctl -u rauc.service --no-pager
to get the services log. Alternatively, try to grab the log file from
your init processes log location or start the service manually on a
shell where you can get the output from:
rauc service
Then start the command line interface (i.e. the rauc install ..) from
another one and you will get the verbose output on the first shell.
Paste your results here and lets see if we can figure out what went wrong.
> I have tested the image using:
>
>>rauc -d info update-2015.04-1.raucb
>
> Output looks fine:
> Domains: 'rauc'
> (rauc:2905): rauc-DEBUG: No grubenv path provided, using
> /boot/grub/grubenv as default
> rauc-Message: Reading bundle: update-2015.04-1.raucb
> rauc-Message: Verifying bundle...
> Compatible: 'rauc-demo-x86'
> Version: '2015.04-1'
> Description: '(null)'
> Build: '(null)'
> Hooks: ''
> 1 Image:
> (1) mydisk.img
> Slotclass: rootfs
> Checksum:
> 4b0f8e37bfaa79fcec616aa3e7f139aea50aa5d8830db07147c1903b4b5729f2
> Size: 11214848
> Hooks:
> 0 Files
Yes, this looks right to me, too.
> Where am I making mistake? Please help.
We will try to figured this out when having the logs available
Best regards, Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2017-04-05 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 10:29 dilip yadav
2017-04-05 10:40 ` Enrico Joerns [this message]
[not found] ` <CALC1k0CxfGXAEAf4WKJfm6PjahfLyf5W3quwbyn7dfHZ+VeZnQ@mail.gmail.com>
[not found] ` <CALC1k0BVs1iB9XwdWwftxdZzWxLXguix2S9pFZCJasTS2PoTkg@mail.gmail.com>
2017-04-05 13:57 ` Enrico Joerns
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=a255d589-62d5-ede5-866c-39889d006bc0@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=rauc@pengutronix.de \
--cc=yadav.dilip582@gmail.com \
/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