[RAUC] Update Installation failed

[RAUC] Update Installation failed

[dilip yadav]

[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]

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

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

Where am I making mistake? Please help.



*Thanks & Regards,*

*Dilip Yadav *
* <http://www.apaulinstruments.in>*

[-- Attachment #1.2: Type: text/html, Size: 2574 bytes --]

[-- Attachment #2: Type: text/plain, Size: 65 bytes --]

_______________________________________________
RAUC mailing list

Re: [RAUC] Update Installation failed

[Enrico Joerns]

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

Re: [RAUC] Update Installation failed

[Enrico Joerns]

Hi,

please keep the mailing list in CC so everyone could benefit from our 
discussion :)

On 04/05/2017 01:40 PM, dilip yadav wrote:
> With your kind help, Ihave successfully updated the minimal rootfs with
> rauc.
> I have following concerns:
> 1.How can I automate the "rauc status mark-good", What if installation
> returned with error and it makes the partition good.

To clarify, the `rauc status mark-good` is meant to be executed during 
the start of your system, not after an installation. Selecting the 
appropriate slot for the next boot is done by RAUC automatically after a 
successful installation.

What the mark-good command does is preventing you from starting a 
non-booting system over and over. The bootloader should decrease a 
counter or set a flag that indicates that this slot might be bad.

Then from your system, at the point where your are really sure all your 
components came up as intended, you invoke the `status mark-good` that 
resets the bootloaders flag/counter.

If your system reboots before this good-marking is performed, this 
mechanism allows you to assure that the bootloader will not forever 
attempt to select the same (non-working) slot.

> 2.Is there any provision of delta updates only?

We definitely have plans for this on paper, but they are not realized, 
yet. Because currently development is mainly driven from what customers 
require and the need for this was not high enough, yet, this item is 
still on our wish list.

> 3.How to integrate it with remote updating server like hawkbit?

Well, you typically need a custom application for this that talks to 
RAUC vi D-Bus on one side and talks with hawkBit via the DDI REST API on 
the other side. This is not part of RAUC as we focus on being an update 
client and update bundle generator. Integration into a system is very 
individual and many users already have an application component.

What we did for a Demo is creating a small python service that acts as a 
bridge between RAUC and hawkBit. But despite it is planned to provide 
some of its components as Open Source software, we did not find the time 
to refactor it.

> 4.What if I want to update only the app? Should I create new partition
> for that?

Yes, that would be an option, RAUC supports this. Also grouping them 
together with giving the appfs slot a `parent` attribute (see [1]). But 
let me point out two things about this:

1. Also if you have a separate application, you always want to assure 
that you only install you application along the exact base system it was 
tested to work with.

2. On the bright side: On *this* level, we support some kind of 
Delta-Updates. If you provide an update bundle with a rootfs and an 
appfs image, and you already have the exact appfs image installed on the 
targets slot you intend to update, only the appfs image will be written.

Well, this still requires you to have both images in the bundle, but it 
will decrease the time required to perform the update while still 
assuring you only install well tested software states. It depends on 
what your critical factor is (storage capacity vs. space) if that helps you.


Hope I could point out our current state of the art about the points you 
mentioned.


Best regards

Enrico


[1] 
http://rauc.readthedocs.io/en/latest/reference.html#system-configuration-file


-- 
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