Failing widgets after upgrade to 24.7

Started by mvdheijkant, July 25, 2024, 05:50:53 PM

Previous topic - Next topic
Quote from: iorx on July 28, 2024, 06:49:27 PM
My 2c here.
No widget load even after:
/* Connection timeout params */
        this.timeoutPeriod = 10000;
        this.retryLimit = 3;

Did you apply the lighttpd configuration patch as well and restarted the GUI? Patching the timeout alone will probably make things even worse.


https://github.com/opnsense/core/issues/7651#issuecomment-2252096655

Of course I didn't :o because I didn't read everything. Sorry for that noise :-[

Now, I've applied it. But still all widgets are broken.
Did a Dashboard Restore Default. No widgets.
And a reboot. No widgets.

root@fw:~ # opnsense-patch 724f8494d
Fetched 724f8494d via https://github.com/opnsense/core
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|From 724f8494d64074e0384b9f593e699daf2d84d604 Mon Sep 17 00:00:00 2001
|From: Ad Schellevis <ad@opnsense.org>
|Date: Fri, 26 Jul 2024 08:49:38 +0200
|Subject: [PATCH] webgui: long lasting calls and locking the request pipeline.
| work-around for https://github.com/opnsense/core/issues/7651
|
|The number of php processes we offer to lighttpd is quite low (2 x 3), which results in a global lock when 2 dashboards are open at the same time.
|Although we should increase the limit, we also should figure out a way to limit the number of long running processes as well.
|---
| src/etc/inc/plugins.inc.d/webgui.inc | 2 +-
| 1 file changed, 1 insertion(+), 1 deletion(-)
|
|diff --git a/src/etc/inc/plugins.inc.d/webgui.inc b/src/etc/inc/plugins.inc.d/webgui.inc
|index 88cf886d100..6aaef8cd882 100644
|--- a/src/etc/inc/plugins.inc.d/webgui.inc
|+++ b/src/etc/inc/plugins.inc.d/webgui.inc
--------------------------
Patching file etc/inc/plugins.inc.d/webgui.inc using Plan A...
Hunk #1 succeeded at 239.
done
All patches have been applied successfully.  Have a nice day.
root@fw:~ # configctl webgui restart
OK
root@fw:~ # reboot



No idea. Look at the developer console output (F12 in Chrome-based browsers, no idea about FF).

And... it's working!

Went away for a while and came back check on replies. Reloaded the page (ctrl+r) with the dev console open and they showed up.
Strange: Tried the reload page thingy right after the reboot too with "no go" on the widgets.
So, I got no clue what's going on here, some timeout/cache maybe.

(F12 in FF too.) Checked the console output, and before reload there was a bunch of errors, didn't grab that sadly.

Also juggled around with them and saved the layout. It stuck, so guess everything is dandy now! :)

Thank you for the extremely fast response and assistance here, KUDOS!

Latest update 24.7_9 seems to have resolved all my known GUI and timeout issues.
Thanks guys.

Hi @Franco.

Just updated to 24.7_9 and the problem for me at least is getting worst. Now i lost also some widgets regarding vpn (openvpn and ipsec).
Also, the widget that will not die (traffic report), still refuses to close with the following error:

Uncaught TypeError: this.charts.trafficIn is null
    onWidgetClose https://pfsense01.net.xpto/ui/js/widgets/Traffic.js?t=1722259354715:243
    _onWidgetClose https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:693
    _onMarkupRendered https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:412
    jQuery 2


Thanks for your help!

@xupetas

In your case I would try to remove the traffic widget and reload the page.


Cheers,
Franco

July 29, 2024, 04:47:09 PM #52 Last Edit: July 29, 2024, 04:51:52 PM by xupetas
@Franco

That error i pasted... is what i get when i try to remove the widget. It will not allow me to remove it. I press the X on the top right corner of the widget and it throws that error i pasted and it will not delete the widget.

Uncaught TypeError: this.charts.trafficIn is null
    onWidgetClose https://pfsense01.net.xpto/ui/js/widgets/Traffic.js?t=1722259354715:243
    _onWidgetClose https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:693
    _onMarkupRendered https://pfsense01.net.xpto/ui/js/opnsense_widget_manager.js?v=1aa4420ce0d0b23e:412
    jQuery 2


Is there a configuration file that i can delete/truncate on the server so all the widgets are reset and i have an empty and clear homepage and go from there?

Thanks for your help.
Cheers.

Hi @Franco. Do you have any idea on how i can reset the entire widget configuration so i dont have any widgets loaded?
See what happens on my previous reply to this thread when i try to delete the ones that are hanged.

@xupetas

Can you try this patch? https://github.com/opnsense/core/commit/4501c593ecd

# opnsense-patch 4501c593ecd


Cheers,
Franco

July 31, 2024, 11:01:24 AM #55 Last Edit: July 31, 2024, 11:28:52 AM by xupetas
@Franco

Thanks. I can delete the widget now. Thanks so much.
I added again the ones that would not work, and some are still dead, for example the CPU and OpenVPN connections.

But at least i can have a clean screen. 

Thanks for your help! I will wait for the others when the team has time to address them.

Kindly,
Nuno

@Franco

Hi Franco,
the patch work for me also. After the patch saving widgets also work... before I tried to add Thermal Sensor Widget withou sucess. After the patch it works.

The Traffic Widget also didn't display any kind of information. It's complete empty (white)

BR Andreas, thanks for the patch :)

Thanks for confirming. There are more patches in the pipeline. We will get there step by step.


Cheers,
Franco

August 01, 2024, 05:31:49 PM #58 Last Edit: August 01, 2024, 05:54:49 PM by NonGough
My LANNER PFW600 (at OPNsense 24.7_9) starts the Lobby: Dashboard OK, but eventually stops working on my Linux laptop dedicated to being a OPNsense management laptop connected to a local network access only port on the LANNER (Browser is the current Linux Firefox ESR variant running on a System 76 EduBook Starling 2; EduBook's OS is Debian 12.5 with updates).  A 2nd browser just activated for 24.7 dashboard testing is an Iridium (Chrome fork) running on a Windows 10 system on a Toshiba Portege laptop.

The Linux machine, even when the only program that is active is the browser running the OPNsense dashboard and a Firewall: Log Files: Live View eventually ends up with the OPNsense dashboard no longer working when the dashboard no longer has focus and always if the screen saver kicks in.  The Firefox ESR complains about the drag on browser performance due to the dashboard javascript.  The CPU widget appears to stop working first, then every other widget quickly comes to a halt.

There may be a problem with the widgets re-initializing after being suspended by the OS due to not having focus (swapping and laptop/browser memory constraints are not a factor).     The dashboard responsiveness slowly degrades even if focus is kept on the dashboard web page -- there may be a problem with flags not being cleared, memory leakage, memory not being freed.

Testing of the Windows 10/dashboard is ongoing, will update this post with a reply if insights occur . . . . . (the Windows 10/Iridium machine's dashboard display is still working after 30 minutes . . . . .).

Having an option to run the old dashboard on my Linux laptop would be a workaround.

August 01, 2024, 07:17:12 PM #59 Last Edit: August 01, 2024, 08:24:30 PM by NonGough
The Windows 10/Iridium's OPNsense dashboard is still working fine after two hours have passed -- even after a forced screen saver (i.e., a Lock).   This is on an old Windows 10 laptop (16 GB RAM) that is missing more than a few OS updates; the Iridium browser is the latest version.  Other activity in addition to the Iridium browser are not affecting the dashboard's widget displays (when focus returns to Iridium's dashboard page, the widgets restart correctly and as expected).

The Linux/Firefox ESR laptop's OPNsense dashboard stops working sometimes only after a few seconds even though there is no other keyboard/mouse activity after an OS restart and only the Firefox ESR is started up.   Whether or not the public Internet access is enabled or not does not appear to affect OPNsense dashboard widgets behavior.