'Impossible package selection' for luci-app-statistics?

Never had this happen before with attendedsysupgrade, is there anything to do but wait for collectd or luci-app-statistics to be updated?

Collected errors:
 * opkg_install_cmd: Cannot install package collectd-mod-thermal.
 * pkg_hash_check_unresolved: cannot find dependency collectd for luci-app-statistics
 * pkg_hash_check_unresolved: cannot find dependency collectd-mod-rrdtool for luci-app-statistics
 * pkg_hash_check_unresolved: cannot find dependency collectd-mod-iwinfo for luci-app-statistics
 * pkg_hash_check_unresolved: cannot find dependency collectd-mod-cpu for luci-app-statistics
 * pkg_hash_check_unresolved: cannot find dependency collectd-mod-memory for luci-app-statistics
 * pkg_hash_check_unresolved: cannot find dependency collectd-mod-interface for luci-app-statistics
 * pkg_hash_check_unresolved: cannot find dependency collectd-mod-load for luci-app-statistics
 * pkg_hash_check_unresolved: cannot find dependency collectd-mod-network for luci-app-statistics
 * pkg_hash_fetch_best_installation_candidate: Packages for luci-app-statistics found, but incompatible with the architectures configured
 * opkg_install_cmd: Cannot install package luci-app-statistics.

Thank you.

1 Like

Getting the same issue here as well.

This is happening a lot.

Until I hear otherwise I'm calling it a server congestion issue.
Try your builds late at night.

To clarify, I've done attendedsysupgrade in Luci about every two weeks for the last few years, and this is the first time I've seen this error.

My position in queue for building the image was 0 so I doubt congestion was a concern.

I am ascribing this to an incompatibility in collectd or luci-app-statistics that must be fixed, or else whatever broke it in SNAPSHOT itself needs to be fixed.

1 Like

I'm getting this issue installing the package luci-app-statistics directly from LUCI.

so it has nothing to do with server congestion.

Its been going on for 2 days for me. I have tried many times of the day and night.

1 Like

I were wrong (and I've been giving this 'answer' for weeks now) be assured someone beyond my Trust Level would have shot it down.

1 Like

@hnyman I am wondering if this is something you can help with since I believe you helped with this issue in the past here: Collectd and luci-app-statistics packages not installing - #6 by neheb

thank you!

looks like a build failure for collectd.

configure: error: "Some plugins are missing dependencies - see the summary above for details"
make[3]: *** [Makefile:462: /builder/shared-workdir/build/sdk/build_dir/target-aarch64_cortex-a53_musl/collectd-5.12.0/.configured_6234745924b9d8230a970ee36a38fe57] Error 1
time: package/feeds/packages/collectd/compile#89.74#17.81#125.81
1 Like

Yeah, or actually, the failure is in one of the dependencies ( the packages needed for collected plugins). Currently the problem is postgresql...

    ping  . . . . . . . . yes
    postgresql  . . . . . no (libpq-fe.h not found) (dependency error)
    powerdns  . . . . . . yes
    processes . . . . . . yes
    procevent . . . . . . no (disabled on command line)
    protocols . . . . . . yes
    python  . . . . . . . no (disabled on command line)

And postgresql fail for some vague reason.

Collectd is vulnerable as it's various optional plugins are tied to so many underlying packages.


Done, you are wrong this time.

It pays off to look at the actual build failure logs of the buildbot to see it there is something.
Currently several dozen packages are failing for a reason or other.
Nothing to do with server congestion.


Fair enough:

Provide a solution.

:spiral_notepad: Not for all the failures that look the same; just for this one.

I just, sucessfully, built firmware for a Pi4 with luci-app-statistics

Try it now.

0301 EDT.

1 Like

try with the latest snapshot, and see if that changes anything. I just refreshed package list and it looks like a lot of luci-app-**** aren't being found.

But that is outside my packages and using the server; I already have statistics installed.

This is likely due to the version upgrade of postgresql to 16.3 three days ago by @dangowrt.
Postgresql fails to build in buildbot, and that then breaks a few dozen other packages including collectd (and thus LuCI statistics).


You may be right about congestion on the firmware-selector.openwrt.org mirror at times, but as @hnyman notes, this issue lies with a recent commit by @dangowrt and not congestion.

The firmware-selector relies on pre-built buildbot images and that All Release Images will reflect Static builds based on the latest commit at the time.

You can see this in the GUI for any Release listed by the firmware-selector in the Revision Number and the Release Date. Since only SNAPSHOT builds are dynamic, they will be affected until the Postgresql version update gets resolved while you will be able to run 23.05.3 Release builds without issue.


I appreciate you taking the time to explaine.

I appreciate the "this time" caveat @hnyman used.

Thank you both.

To those I was wrong: I apologize for my Sheer Fracking Hubris.

1 Like

Were these packages discontinued?
For the last 4 or so days, building an image for this target couldn't succeed because of the following packages - shown in the screenshot:

Due to postgresql that fails since 4-5 days since the version upgrade to new major version 16.3

Nothing to do with dl-wrx36 specifically (that this thread is about).

The problem only concerns those who do not build from sources, (and use imagebuilder or buildbot binaries based auc/owut/attendedsysupgrade). You can quite normally build from sources as long as you avoid the postgresql related packages (or submodules like collectd-mod-postgresql).


Thank you very much for the prompt and very clear explanation. I will keep checking back to see if the issue gets resolved.