Failing widgets after upgrade to 24.7

[hoondi]

The picture plugin was very handy as there was no other easier way to view what router you were managing when Dashboard glancing.
Either that or a new plugin that simply has "n" simple text fields that can store custom info.

[Monviech (Cedrik)]

The picture plugin was very handy as there was no other easier way to view what router you were managing when Dashboard glancing.
Either that or a new plugin that simply has "n" simple text fields that can store custom info.

Maybe a widget for "os-net-snmp" plugin? These are standardized after all, and can additionally be used via SNMP too.

- sysName
- sysLocation
- sysContact

[mvdheijkant]

Wish I could do even that. Thought I could start with zero widgets, but saving the dashboard settings doesn't even work. Also the traffic graph widget cannot be closed. Furthermore the selection menu runs underneath the "Add Widget" page.

[meyergru]

Until the other themes get fixed, that can be cured by using the standard opnsense theme...

[mtltt]

For me on APU3 the Announcements-Widget is breaking all others. After removing it, the others I need (System Information, Memory, Disk, Thermal Sensors, Gateways, CPU, Interface Statistics) are working fine.

Update: It seems to me that just too many Widgets break all together. I also applied the patch btw.

[xupetas]

For me, i also found that there are widgets that i cant edit or delete, for example the traffic graph one.

[meyergru]

Folks, there are at least 3 separate issues with the new widgets (apart from cosmetic problems with individual widgets):

1. On some themes, the settings cannot be changed. Solution: use the opnsense theme until they get fixed.
2. The number of connections in the web server is limited, so on slow CPUs or if you open the dashboard multiple times, they will fail. Solution: Use the patch or wait until monday's hotfix.
3. The timeout for any widget to show up is fairly small. That means that on slow CPUs, some widgets may fail. IDK if that will be addressed shortly.

[doktornotor]

3. The timeout for any widget to show up is fairly small. That means that on slow CPUs, some widgets may fail. IDK if that will be addressed shortly.

Any idea where's the timeout set? Need to patch it to some sane values and see how it goes; as it is, the dashboard is going to be just unusable on lots of boxes I manage. (#2 does not help there - broken with just default install.)

[meyergru]

I think it is in BaseWidget.js, variable "timeoutPeriod", but cannot test it because my CPU is fast enough.

[spanguel]

I think it is in BaseWidget.js, variable "timeoutPeriod", but cannot test it because my CPU is fast enough.

Hey, i just changed the value from 1000 to 10000 for a quick test. my widgets are all loading now. (just in case i enabled basically everything.

I had the same issue with many widgets. as long as i only had 3-4 active it worked and it did not depend on which widget it was as long as there were few.

CPU used: Intel(R) Celeron(R) CPU N3050 @ 1.60GHz (2 cores, 2 threads)

[doktornotor]

I think it is in BaseWidget.js, variable "timeoutPeriod", but cannot test it because my CPU is fast enough.

Cool, that definitely helped. 

[meyergru]

If it really does help, you could raise an issue on github or even create a pull request. If @franco sees it, it might get included in monday's hotfix...

[doktornotor]

If it really does help, you could raise an issue on github or even create a pull request. If @franco sees it, it might get included in monday's hotfix...

There seems to be already one covering the not loading widgets: https://github.com/opnsense/core/issues/7651

[meyergru]

If it really does help, you could raise an issue on github or even create a pull request. If @franco sees it, it might get included in monday's hotfix...

There seems to be already one covering the not loading widgets: https://github.com/opnsense/core/issues/7651

Yes, but the patch contained in that issue only covers #2 from my list above.

[iorx]

My 2c here.
No widget load even after:
/* Connection timeout params */
        this.timeoutPeriod = 10000;
        this.retryLimit = 3;

Have a test fw running just upgraded it from 24.1.10_8
Using standard theme.
It's a vm in hyper-v with plenty of resources.

Let me know if I can contribute with anything.