Failing widgets after upgrade to 24.7

[mcsedude]

Doesn't matter what browser the Firewall widget and traffic in & out widget not working correctly after grading to 24.7

[NonGough]

The upgrade from 24.7.1 to 24.7.2:
* A Linux Debian 12.5 laptop (dedicated to being a firewall management device) with Firefox ESR is unable to run:
  - /ui/diagnostics/firewall/log#Lobby
  - /?url=ui/core/dashboard
  An error message is eventually displayed:  The Connection has timed out
  Linux is no longer usable as a firewall management device for OPNsense.
* My OPNsense firewall appliance has a USB port for keyboard and a VGA port for a monitor.
* The swap file in OPNsense (console displayed error message onto the VGA display running pfTop) shows that the FreeBSD swap file for OPNsense kept expanding in one execution until the swap space filled up.
* A Windows 10 laptop executing the Pale Moon browser is able to run as expected the  Lobby  and  Firewall:Log Files:Live View  displays.  Missing is a display of the swap file size.  The graphics now work smoothly in 24.7.2. 

The pre-24.7 lobby displayed memory status (disk,ram,swap) in text - please return this display capability as an option.

[NonGough]

With 24.7.2, there apparently is a memory leak.  Eventually, OPNsense reboots itself automatically.  The VGA console display presents a Login prompt (and a corresponding login needs to be done for the GUI OPNsense management interface).

I noticed that in System: Settings: Miscellaneous, the Swap File setting to "add a 2GB swap file to the system" was unchecked.  It is unclear whether a 24.7.x update disabled my swap file settings, I remember having an 8GB swap file for my OPNsense appliance.

When the swap file fills up (or is not established by a setting), it would be nice to have a more elegant way to add more swap space dynamically as well as a FYI message as part of the login messages displayed why an automatic restart was done by OPNsense (such as the swap file filing up).

It is possible that when the blocklists are being processed that invariably the swap file space will fill up (my configuration is 4GB Ram, 8GB swap space).   It seems that blocklist processing under 24.7.2 (Hagezi specifically) has never successfully completed since I applied the 24.7.2 changes.  OPNsense is also creating multiple history backups (every 2-3 minutes!) while processing the blocklists - so I have lost my original configuration backups (my generous backup of count of 2048 means that OPNsense has trashed all of my pre 24.7 history backups and has used up 30% of my disk space for useless history backups).   While processing blocklists, there is no need for interim history backups!!!

It would be very helpful to add a 14th option to the console selection menu:
14)  Display status of settings for RAM, Swap Space, Disk Space

I am disabling my usage of Hagezi block lists until the 24.7.x problems are sorted out.

[doktornotor]

I am disabling my usage of Hagezi block lists until the 24.7.x problems are sorted out.

Hello. If you mean these https://github.com/hagezi/dns-blocklists which are anywhere from many MBs to tens of MBs, then your solution is not swap but adequate hardware or not using such lists.

That said, you are absolutely off-topic here.

[NonGough]

Grep memory /var/run/dnesg.boot   displays:
agp0: aperture size is 256M, detected 8188k stolen memory
pid 69794 (pftop), jid 0, uid 0, was killed: failed to reclaim memory

These messages started appearing with an upgrade to 24.7 and first noticed with an upgrade to 24.7.2 (even with the cessation of Hagezi blocklist processing).  Note that Hagezi blocklist processing (as a background task) pre-24.7 took less than an hour to always complete.

[doktornotor]

Not feeling like wasting more time arguing the obvious (as you can see, you are getting things on your box killed by OOM). Insist on using those lists? Use them with BIND. No python parsing nonsense needed.

https://github.com/hagezi/dns-blocklists/tree/main/rpz

Now, kindly stop hijacking this thread for absolutely unrelated issues.

[franco]

Let's all take a break please. Failing widgets topics only here now. :)


Cheers,
Franco

[wajatmaka]

For your information I got crash for widget after upgrade 24.7.2 commit 8ffbc6387.


Here the log console js :

Code Select Expand


opnsense_widget_manager.js?v=f55a118244ec13ff:148 Failed to load one or more widgets: (23) [TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base". Relative references must start with ei..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base". Relative references must start with ei..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-gauge". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base". Relative references must start with ei..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w..., TypeError: Failed to resolve module specifier "widget-base-table". Relative references must start w...]
(anonymous) @ opnsense_widget_manager.js?v=f55a118244ec13ff:148
await in (anonymous)
e @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
t @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
setTimeout
(anonymous) @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fire @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
l @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
(anonymous) @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
load
send @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
ajax @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
_loadWidgets @ opnsense_widget_manager.js?v=f55a118244ec13ff:122
initialize @ opnsense_widget_manager.js?v=f55a118244ec13ff:109
(anonymous) @ dashboard:1362
e @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
t @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
setTimeout
(anonymous) @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fire @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
c @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
fireWith @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
ready @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2
B @ jquery-3.5.1.min.js?v=f55a118244ec13ff:2Understand this error
opnsense_widget_manager.js?v=f55a118244ec13ff:117 Failed initializing Widgets Error: No widgets loaded
    at WidgetManager._initializeWidgets (opnsense_widget_manager.js?v=f55a118244ec13ff:154:19)
    at WidgetManager.initialize (opnsense_widget_manager.js?v=f55a118244ec13ff:111:18)


I used VM with speficiation

4 vcpu
8 GB RAM


Thank you Team

[franco]

Yes it's your browser and it should be fixed in 24.7.3 anyway.


Cheers,
Franco