Auc - sysupgrade does not work for me

Installing and Using OpenWrt
21

I just tried and got a Server response: Error: Selected packages exceed device storage after several minutes so it seems the sysupgrade server is not feeling well atm.

22

Unless you added too many packages and pushed the image size over what the device can handle. Remember snapshots with the new kernel 6.6 will probably be larger than 6.1.

Were you using the default packages? Did you add much?

1 Like
23

You can report bug at auc github, that they should show sensible error in that case.

1 Like
24

Default packages for x86/64 + luci-app-attendedsysupgrade and it's dependencies, but I noticed that I also had dockerd pulled in (it's a dev machine so I had that installed to debug a specific GitHub issue), when I removed that it worked, thanks for the guidance. I wonder of there's a documented limit somewhere, cause dockerd is quite big so not surprising, about 14 MB.

EDIT: that should've been a reply to @rygle as well

1 Like
25

docker is dozen megs, like barely fits in 32mb flash...

26

Just sounded like they've actually improved the process to know what size image your device can handle.

I know I've soft bricked devices by going over about 15.5mb

1 Like
27

It can be 4 8 16 for kernel for kernel+bootloader for squashfs or all 3

28

Perfect, thanks!
Saved this tip.

29

Worth reporting at https://github.com/openwrt/asu

30

I have had routers soft brick several times because I went over an image size of about 15.5Mb made using firmware selector or auc. Reflashed with a firmware image with less packages (in my case I think Tailscale was the large package in many cases) and it would work fine with the same base image, just missing a large package or two.

I have never seen that message in the firmware selector or asu before, so perhaps it has been added recently (which would be positive, I think, not a bug), or perhaps it only triggers when you really go over the size and my builds that failed when too large simply weren't large enough to trigger the error.

Edit: sorry about second similar reply. Forgot I actually posted the last, thought I'd just drafted but not posted.

31

What is needed to make this work?
I would donate to get this working reliably.

auc/0.3.2-1
Server:    https://sysupgrade.openwrt.org
Running:   SNAPSHOT r26214-a9781a04a1 on mediatek/filogic (glinet,gl-mt6000)
Requesting package lists...
 base-files: 1590~a9781a04a1 -> 1590~0d74b2a1e5
Are you sure you want to continue the upgrade process? [N/y] Y
Requesting build..........Error: Received inncorrect version r26235-0d74b2a1e5 (requested r26214-a9781a04a1)
Bad message (74)
32

I think service just got some spin and people hit edges more often, "try again later" type of issue

1 Like
33

I have been facing the same problem since Thursday (two days).

auc -b 23.05 -B 23.05-SNAPSHOT -y

auc/0.3.2-1
Server: https://sysupgrade.openwrt.org
Running: 23.05.3 r23809-234f1a2efa on ipq40xx/generic (zte,mf286d)
Available: 23.05-SNAPSHOT r23896-6698e6e76a
Requesting package lists...

Error: Received inncorrect version r23897-3287d82fcf (requested r23896-6698e6e76a)
Bad message (74)

EDIT:
Here are some suggestions: https://github.com/openwrt/openwrt/issues/15619

[brada4] :"Just try again later, you caught sysupgrade server mid-downloading next snapshot."

Looks like I should be more patient.

1 Like
34

Do not add that -y without -n
sysupgrade does not maintain your session between first check and giving actual image, if any repo is rebuilt in few minutes in between it gives you the new version and client rejects it.
The slow version of TOCTOU
You see request did not include build ID
http://sysupgrade.openwrt.org/ui/#/default/asu.api.api_v1_build_post
So server served best it got.
Kind of no problem with stable releases.
I will cross-link with https://github.com/openwrt/asu/issues/848

1 Like
35

OK, the server serves its best, I like it, but I wonder when the offered and the newest version finally matches. It lasts already tens of hours and the server's best will causes the worst case.

36

You can try one of rebuild servers

37

Thank you brada4

Server: http://asu.aparcar.org:8000/
Running: 23.05.3 r23809-234f1a2efa on ipq40xx/generic (zte,mf286d)
No data available (61)

Server: http://asu.hauke-m.de:8000/
Running: 23.05.3 r23809-234f1a2efa on ipq40xx/generic (zte,mf286d)
No data available (61)

EDIT:
I gave up. Since I have a 23.05-snapshot downloaded with Luci GUI I have installed it again. (there was a reason I wanted to prepare a 23.05.3 and skip to snapshot, but if it does not work, then...).
But the situation with auc command is ridiculous:

root@OpenWrt:~# auc
auc/0.3.2-1
Server: https://sysupgrade.openwrt.org
Running: 23.05-SNAPSHOT r23897-3287d82fcf on ipq40xx/generic (zte,mf286d)
Available: 23.05-SNAPSHOT r23896-6698e6e76a
Requesting package lists...
Nothing to be updated. Use '-f' to force.

And we all know that the server forces to send the r23897 even though it offers r23896.

38

You can try pasting output of

opkg list-installed | cut -d ' ' -f 1

into firmware-selector

39

I have done it already for the version 23.05.3. As far as I understand, I can not prepare 23.05-snapshot (e.g. r23897) in the firmware selector, right?

1 Like
40

Issue still valid...
auc - updates not possible with SNAPSHOTS · Issue #848 · openwrt/asu (github.com)