23.05.5 crash after updates from luci

Error
Unhandled exception during request dispatching
module 'luci.ucodebridge' not found:
no field package.preload['luci.ucodebridge']
no file './luci/ucodebridge.lua'
no file '/usr/share/lua/luci/ucodebridge.lua'
no file '/usr/share/lua/luci/ucodebridge/init.lua'
no file '/usr/lib/lua/luci/ucodebridge.lua'
no file '/usr/lib/lua/luci/ucodebridge/init.lua'
no file './luci/ucodebridge.so'
no file '/usr/lib/lua/luci/ucodebridge.so'
no file '/usr/lib/lua/loadall.so'
no file './luci.so'
no file '/usr/lib/lua/luci.so'
no file '/usr/lib/lua/loadall.so'

In [anonymous function](), file [C]
In [anonymous function](), file /usr/share/ucode/luci/runtime.uc, line 133, byte 10:
  called from function [arrow function] (/usr/share/ucode/luci/runtime.uc:141:63)
  called from function render ([C])
  called from function [anonymous function] (/usr/share/ucode/luci/runtime.uc:141:64)
  called from function run_action (/usr/share/ucode/luci/dispatcher.uc:778:34)
  called from function [anonymous function] (/usr/share/ucode/luci/dispatcher.uc:1003:48)
  called from anonymous function (/www/cgi-bin/luci:39:13)

 `            die(ex);`
  Near here --------^

what now?


i have been using raw 23.05.5 but i was thinking maybe i get luck and nothing will fuk up if i use renew buttons (especially banip) is most important for me, and that s how it ended

From what version did you upgrade? Did you keep settings?

What device are we talking about here:

ubus call system board
root@OpenWrt:~# ubus call system board
{
        "kernel": "5.15.167",
        "hostname": "OpenWrt",
        "system": "MediaTek MT7621 ver:1 eco:3",
        "model": "ASUS RT-AX53U",
        "board_name": "asus,rt-ax53u",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05.5",
                "revision": "r24106-10cc5fcd00",
                "target": "ramips/mt7621",
                "description": "OpenWrt 23.05.5 r24106-10cc5fcd00"
        }
}
root@OpenWrt:~# 
root@OpenWrt:~# 

i just used update packages, one by one in luci, propably some config file has some new part somewhere but old doesnt and is saved as -opkg (i just assume)

Upgrading packages (via the CLI opkg upgrade command or the LuCI Upgrade... button) can result in major problems. It is generally highly discouraged, unless you know what you are doing or if there is specific instruction to do so.

To resolve your issue, make a backup using the command line, then reset the router to defaults. You can then restore your backup. If the problem was caused by your package upgrades, restoring the backup should be safe.

ok then, i thought if they are in same tree (not snapshot) is safe to go, not sure what to do now, remove all config files?

root@OpenWrt:/etc/config# #!/bin/sh
root@OpenWrt:/etc/config# FLASH_TIME="$(awk '
> $1 == "Installed-Time:" && ($2 < OLDEST || OLDEST=="") {
>   OLDEST=$2
> }
> END {
>   print OLDEST
> }
> ' /usr/lib/opkg/status)"
root@OpenWrt:/etc/config# 
root@OpenWrt:/etc/config# awk -v FT="$FLASH_TIME" '
> $1 == "Package:" {
>   PKG=$2
>   USR=""
> }
> $1 == "Status:" && $3 ~ "user" {
>   USR=1
> }
> $1 == "Installed-Time:" && USR && $2 != FT {
>   print PKG
> }
> ' /usr/lib/opkg/status | sort
banip
luci
luci-app-banip
luci-app-ddns
luci-app-firewall
luci-app-opkg
luci-base
luci-i18n-banip-pl
luci-i18n-base-pl
luci-i18n-ddns-pl
luci-i18n-firewall-pl
luci-i18n-opkg-pl
luci-i18n-statistics-pl
luci-lib-base
luci-lib-ip
luci-lib-jsonc
luci-lib-nixio
luci-light
luci-mod-admin-full
luci-mod-network
luci-mod-status
luci-mod-system
luci-proto-ipv6
luci-proto-ppp
luci-theme-bootstrap
nano-full
root@OpenWrt:/etc/config# 

i will try create new image from https://firmware-selector.openwrt.org/ and newest packages should be included?

The package upgrade process was almost certainly the cause of the problem. This can happen in general for a number of reasons, but is essentially guaranteed to happen if you start installing packages from the snapshot repo (or really any repo that is linked against a different OpenWrt/kernel version).

Yes, you can create a custom image with the firmware selector that has all of your packages pre-installed. Or you can reset to defaults and then install those packages post-reset. The result will be largely the same, although the firmware selector method will actually consume less space because the images are squashfs compressed.

In general user installed packages like banip can be upgraded (I upgrade that regularly as well) but system apps like busybox will soft brick.

Some others can be updated as well but if you aren't familiar then as mentioned in general it is not recommended.

post the output of
opkg list-installed

and see if it changes after
opkg install ucode

This message is typical when you install and uninstall luci-compat, either sysupgrade or use auc forcing upgrade to same version to clean up.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.