Luci status page fails and hangs "TypeError" "pkg is undefined

Hi,

I have just built the latest release of openwrt "OpenWrt 23.05-SNAPSHOT r24045-5773538c90 / LuCI openwrt-23.05 branch git-24.212.79335-cdbe903"

I have several routers of different make models, all but 2 models based on ipq806 work fine.
Both Netgear RT7800 and Linksys EA8500 now give an error on the main status page. The error is (in a red rectangle with a "Dismiss" button):

TypeError
pkg is undefined
Status
Loading View....

and it hangs.


Some package must be missing from the new version or something must have changed for this chipset that causes this issue.
The problem is that the error does not help understand what is missing. Nothing is logged either, so I have no clue.

How can I find out what is going on?

Why are you running a 23.05 snapshot ?

Iirc, luci isn't included in snapshots - search for opkg install luci to get the actual command to load basic luci. The luci extras you'll need to install manually as well.

I do not understand the question. I prefer to build my own images from source for my routers as I do some development too.

Going back to my question, is there any way I can get more information from luci about the error so that I can identify what is missing?

I build my own image using make menuconfig and I pick the packages I need from there. The configuration for my 2 ipq806 based routers has not changed in several months, only this last build is giving me this error (after deployment, on the Status splash page).

I was only trying to understand how can I get more information from luci so that I can identify what is missing.

23.05-SNAPSHOT is eqal to 23.05.x releases with luci.

If you build the image yourself (with some dev work) you already know what you have removed.

How are we going to guess what you have removed?

1 Like

Show the picture with URL visible, should be obvious error is not there for everybody.

Below is a screenshot

Selecting drop down Status menu:

Overview: as above
Routing, Firewall, System Log, Processes, Channel Analysis, Realtime Graphs, Mobile Service, Wireguard ... all good.

Unless I find the issue tomorrow I will try to start from scratch a new software configuration by deleting the .config file used to build the image ("make menuconfig"). Perhaps something has been changed/added/removed that the saved .config does not include or fix automatically. Although if possible I would like to avoid this because it is a lengthy manual process with many packages to select (one has to remember all the necessary packages and their configuration).

That is one way to do it, the other way as described in the wiki for building firmware is to have them configured in a text file and copy that to the config file.

That is what I do, but I found out that occasionally the saved configuration becomes incompatible with new updates. When this happens, normally the build fails because of some missing dependencies. This time it succeeded, so I am not even sure whether this could be the problem.

pkg rhymes with luci-app-opkg ? Try in incognito mode, maybe something cached is in the way.

I reconfigured the source manually, built, deployed, same error.
I have now reverted back to:

OpenWrt 23.05-SNAPSHOT r24025-c241885687 / LuCI openwrt-23.05 branch git-24.212.79335-cdbe903

And the error goes away.

Unfortunately I cannot use a standard build because I have to turn on openssl and turn off mbedtls, I use openvpn with openssl and wpad-openssl other than dhcp-full and several other kernel and packages tweaks.

I have to go back to my original question: is there any way to get a more detailed error report from luci so that I can understand what goes wrong?

Last working is on jul31, can you try to backtrack if you use any modules changed? Or either of overall patches break it?

You ain’t supposed to define the dependables or any version of anything in that file. You only define the basic packages you want to include, nothing more.

Rest is taken care of pretty much automatically!

Thank you for sharing the latest commits' history. I will see what I can do as I do not have a spare router with an ipq806 chipset that I can use for troubleshooting. 2 of them are deployed in unattended remote sites (therefore I cannot risk crashing either), one is local, but constantly in use too in a key role.

You just need to reinstall luci packages.

There should be a stacktrace in the console in your browser when you hit the error which could give a hint of what's going on.