X86_64 build of 21.02 doesn't boot because ubus exits with error code 32512

For Developers
1

Tried upgrading my custom build APU2 image to 21.02.1, but even though it builds fine, booting it stops just after init with ubus repeatedly exiting

Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
2
[    3.739994] mount_root: mounting /dev/root
[    3.749915] EXT4-fs (sda2): re-mounted. Opts: (null)
[    3.785596] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[    5.778857] urandom-seed: Seed file not found (/etc/urandom.seed)
[    5.790515] procd: - early -
[    6.308583] procd: - ubus -
[    6.311267] procd: Create service ubus
[    6.313763] procd: Start instance ubus::instance1
[    6.316912] procd: Started instance ubus::instance1[1278]
[    6.320246] procd: running /etc/init.d/ubus running
[    6.323413] procd: glob failed on /etc/init.d/ubus
[    6.324848] procd: Instance ubus::instance1 exit with error code 32512 after 0 seconds
[    7.328331] procd: Started instance ubus::instance1[1279]
[    7.331744] procd: Instance ubus::instance1 exit with error code 32512 after 0 seconds
[    8.338135] procd: Started instance ubus::instance1[1280]
[    8.341543] procd: Instance ubus::instance1 exit with error code 32512 after 0 seconds
[    9.347963] procd: Started instance ubus::instance1[1281]
[    9.351382] procd: Instance ubus::instance1 exit with error code 32512 after 0 seconds
error repeats ...

Tried it on QEMU instead of the APU2 , same issue.
Tried to build a default x86 config, after a make distclean, same issue.
Tried building on Arch linux instead of Ubuntu 20.04 LTS, same issue.
Tried the 21.02 branch instead of 21.02.1 tag in a competently new and clean build dir, same issue.

19.07.8 still builds and runs fine on my systems

2

Made a VM with a clean Debian 11 install - no issues there. I guess there's an issue with both my Ubuntu 20.04 LTS build host as well as Arch linux ... strange

3

FWIW I'm having the same issue on my ramips build from v21.02.1 tag:

[   15.029769] procd: - ubus -
[   15.037060] procd: Create service ubus
[   15.046059] procd: Start instance ubus::instance1
[   15.058463] procd: Started instance ubus::instance1[416]
[   15.629358] procd: running /etc/init.d/ubus running
[   15.640580] procd: glob failed on /etc/init.d/ubus
[   15.652124] procd: Connection to ubus failed
[   15.664080] procd: Instance ubus::instance1 exit with error code 32512 after 0 seconds
[   15.761983] procd: Connection to ubus failed
[   15.971281] procd: Connection to ubus failed
[   16.381491] procd: Connection to ubus failed
[   16.683000] procd: Started instance ubus::instance1[417]
[   16.701164] procd: Instance ubus::instance1 exit with error code 32512 after 0 seconds
[   17.192732] procd: Connection to ubus failed
...
4

I had the very same issue back in August: Init routine goes into loop when trying to execute ubus with custom image for Deco M4R

I too used Ubuntu in a VM as build host.

Happend with the master branch and 21.02-rc4 as well.

Never figured out why and thus my devices are still running on 19.07.8.

But that sounds like I should just set up a Debian VM and install the same stuff as on the Ubuntu VM? Can it be that simple?

6

That's what worked for me. I haven't hey found time to dig why this is happening. I'm surprised so few people are having this issue.

7

Maybe some quirk in some of the tools needed to compile images provided by the ubuntu repositories that isn't present in the debian repositories.

After all the quick setup guide for openwrt tells you to download a debian VM and maybe that's what's used by the dev(s) who do all the fun ubus coding.

8

Same issue here on Suse tumbleweed. I already have a debian vm so I guess I'll give it a shot :person_shrugging:

9

i reported: https://github.com/openwrt/openwrt/issues/9511

11

root cause found: see #9545

1 Like