LuCI Attended Sysupgrade support thread

Hi,

ah ok, understood.
I was not sure if the functionality of this package is still needed after the upgrade.
Normally you're very careful if you see dependencies like that :slight_smile:

I'll try the upgrade later this day, leaving out this package.

Thanks for the clarification.

Regards,
MagicMight

what about 25.12-rc4? I can update my device Rostelecom s1010

It has not yet been released, so will not be available in LuCI ASU until all the metadata has been produced. It should be available in 24-48 hours.

1 Like

ok.. thanks

By the way, will there be a stable release of 25.12 openwrt or only in mid-2026?

Hello, first time trying an upgrade using either attended-sysupgrade from LuCI or owut from the command line.

I don't know what to expect so maybe this is normal but is the number of builds "ahead of you" supposed to update and go down? It says Status: queued - 3193 ahead of you and it's been 20 minutes in queue now and it hasn't changed.

Perhaps something is blocking on the server? I see that according to the stats on https://sysupgrade.openwrt.org/ there has been an uptick of requests per day in the last 3 days, so it's fine if because of the number of requests mine takes a long time, I just want to make sure it's going to be done at some point.

Thanks in advance

The OpenWrt ASU server is currently not working. It has internal limits for 200 queued jobs, so I'm not sure how it's queuing up so many... Best to wait a while and try again.

Normally there are 0-3 jobs in the queue, even when there's heavy load, and you only wait a couple minutes to get your job accepted and built.

You can easily check the queue length and see if it's still broken:

$ curl -s https://sysupgrade.openwrt.org/api/v1/stats
{"queue_length":3275}    << Yup, it's still broken.
1 Like

Thanks for the info! I will look at the status and see later.

Suggestion: https://sysupgrade.openwrt.org/ should show the current number of pending requests, it would be easier to see the status than having to issue a curl request through the API.

Will it resolve by itself or does someone need to do something? I mean, if builds are just accumulating and no one does anything, they will just keep accumulating and waiting won't change anything, right?

Edit: for now I used the mirror https://sysupgrade.guerra24.net/

1 Like

Turns out that storage was full, being fixed as I type...

2 Likes

Hi, ASU is not able to determine board_name/profile for my device and doesn't include them in the requiest:

{
    "system_board": {
        "kernel": "6.6.86",
        "hostname": "OpenWrt",
        "system": "Geode(TM) Integrated Processor by AMD PCS",
        "rootfs_type": "ext4",
        "release": {
            "distribution": "OpenWrt",
            "version": "24.10.1",
            "revision": "r28597-0425664679",
            "target": "x86/geode",
            "description": "OpenWrt 24.10.1 r28597-0425664679",
            "builddate": "1744562312"
        }
    },
    "advanced_mode": "0",
    "url": "https://sysupgrade.openwrt.org",
    "branch": "24.10",
    "revision": "r28597-0425664679",
    "efi": null,
    "sha256_unsigned": "",
    "client": "luci/26.029.67023~a0d5c47",
    "packages": {
      // skipped
    },
    "target": "x86/geode",
    "version": "24.10.1",
    "diff_packages": true,
    "filesystem": "ext4",
    "rootfs_size_mb": null
}

so request fails with 422:

{"detail":[{"type":"missing","loc":["body","profile"],"msg":"Field required","input": {...

This is my device https://wikidevi.wi-cat.ru/PC-Engines_Alix_alix2d13
Was installed using image openwrt-24.10.1-x86-geode-generic-ext4-combined.img.gz
I see I can provide the profile value if I enable advanced mode. Any ideas where I can find the value for my board?

Soooo.... I guess you guys must be busy...

Server response: server overload, queue contains too many build requests: 201

How to install zapret in router (rostelecom s1010) firmware 25.12-rc4

There should be two files in /tmp/sysinfo that provide that info. Here's an example from my APU2E4:

$ grep '' /tmp/sysinfo/*
/tmp/sysinfo/board_name:pc-engines-apu2
/tmp/sysinfo/model:PC Engines apu2

It appears that you are missing the board_name file for some reason. Since the actual value for the board name is ignored for this generic-ish target/subtarget, you can just do something like below and it should work fine for ASU purposes.

echo 'pc-engines-alix' > /tmp/sysinfo/board_name

Then proceed with your upgrade...

Is that a package? I don't see it in any of the OpenWrt feeds...

It's custom package

Custom means not available to the online imagebuilder, which can only use official packages. Anything else would pose a command injection attack vector into the server running the online imagebuilder.

You will have to install custom packages at runtime or build your own images on your own computer.

Not just a ban, it's a VPN that I need to set up, but there's an error.

There's no such folder on my system :slight_smile:
Do you think I have to create the file for the upgrade to succeed or can just provide any random value in ASU UI after enabling advanced mode?
Also the server response complained about absence of profile rather than board_name, so it either doesn't check board_name or checks profile first and reports the first error.

OOPS, yes, that's the way to go. I had forgotten that profile is exposed there.

Creating the file seems easiest, but if you want to get into the browser debugger and inject it into the JSON packet, that probably will work, too.

They are synonyms: profile, device, board name, platform, device profile, device name are all used to refer to the same thing.

Very nice, I've had a device added to Openwrt of my own, which is still not supported yet, AX80 EU U-boot layout. I tried to attended sysupgrade, it thrown me back error. Just reporting a normal behaviour. System works as expected.

{
    "system_board": {
        "kernel": "6.12.66",
        "hostname": "Archer-AX80",
        "system": "ARMv8 Processor rev 4",
        "model": "TP-Link Archer AX80 v1 (EU, UBI)",
        "board_name": "tplink,archer-ax80-v1-eu-ubi",
        "rootfs_type": "squashfs",
        "release": {
            "distribution": "OpenWrt",
            "version": "SNAPSHOT",
            "firmware_url": "https://downloads.openwrt.org/",
            "revision": "r32731-21e2d6c738a",
            "target": "mediatek/filogic",
            "description": "OpenWrt SNAPSHOT r32731-21e2d6c738a",
            "builddate": "1769118201"
        }
    },
    "advanced_mode": "0",
    "url": "https://sysupgrade.openwrt.org",
    "branch": "SNAPSHOT",
    "revision": "r32731-21e2d6c738a",
    "efi": null,
    "sha256_unsigned": "",
    "client": "luci/26.006.47974~6ebcfe6",
    "packages": {
        "adblock": "4.5.0-r1",
        "apk-mbedtls": "3.0.2-r2",
        "attendedsysupgrade-common": "9",
  ...A LOT OF PACKAGES....
        "zlib": "1.3.1-r1"
    },
    "profile": "tplink,archer-ax80-v1-eu-ubi",
    "target": "mediatek/filogic",
    "version": "SNAPSHOT",
    "diff_packages": true,
    "filesystem": "squashfs",
    "rootfs_size_mb": null
}
1 Like