Dear OPNsense team,
I got issues [OPNSense Community Edition 24.7.8] which may look like an old topic for you // seen in https://github.com/opnsense/core/issues/5516 (https://github.com/opnsense/core/issues/5516)
Every time I change anything in one of my INTERFACES (no matter what changes and which INTERFACE) the WEBGUI becomes inaccessible for nearly 3-4 minutes after pushing "APPLY". After drinking 1 more coffee I can log in again a new websession and go on with configuration.
Please have a look over this topic (again?).
If anybody has any kind of solution I'll highly appreciate let knowing me.
Thanks everybody in community and especially the MASTERS of the System - your product is GREAT!!!
cheers,
Udo
2024-11-13T18:14:44 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T18:10:37 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T18:10:37 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 5504
2024-11-13T18:10:37 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-13T18:07:11 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T18:00:06 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T18:00:06 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 40240
2024-11-13T18:00:06 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-13T17:56:56 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T14:27:26 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T14:27:26 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 85278
2024-11-13T14:27:26 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-13T14:23:58 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-13T14:19:20 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-13T14:19:20 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 33189
2024-11-13T14:19:20 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
Are you using a LAGG as interface?
There is no LAGG Interface.
LAN (em0)
WAN (em1)
LAN2 (em2)
WireGuard (wg1)
Hmm okay no lagg or vlan means probably no switch issues. Just wanted to check. I sadly cannot help with lighttpd issues. Did you try reverting the webgui to HTTP and see if you have the same issue over HTTP? Just for reference.
It doesn't matter if I'm using http only or https with acme certificate.
I just re-installed my system "fresh".
And after uploading my config file OPNsense is working fine - including the "not accesible WebGUI Problem" which came back too.
Hello Franco and team,
the following phenomenon:
OPNSENSE 24.7 freshly installed --> run an "update from console" to 24.7.8 via root login --> rebooted --> login to WebGUI from LAN --> run initial settings === Everything fine so far.
Then I go to INTERFACE / WAN and just click on "Prevent Interface Removal" --> save (good so far) and then on "APPLY"
Now the problem starts - the WEBGUI makes a "graceful shutdown" - but then does not start as expected directly afterwards.
2024-11-16T13:19:24 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-16T13:19:24 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 86795
2024-11-16T13:19:24 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-16T13:15:22 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-16T13:14:50 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-16T12:14:50 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 55307
2024-11-16T12:14:49 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-16T12:12:19 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
While the struggling 3-4 minutes between automatic restart i tried via shell to "restart all services" - when showing "Web GUI" it shows status "locked".
This behaviour I got on 2 pieces of hardware which have served me well for years.
- HUNSN FW6A (Intel 3865 + 6 x Intel NIC 211)
- Fujitsu Futro 720 (AMD GX 222 + INTEL NIC)
The click on "prevent interface removal" is more or less an example - I could click anything on any Interface - after "APPLY" the WEBGUI struggles like shown above.
Should I be the only person on this planet which this problem? I don't think so.
Please give any kind of solution a try.
Did you change the interface for the web UI to anything but "All (recommended)"?
No - its exactly as i said.
Fresh install - update to 24.7.8 - initial setup - and on first interaction in wan / lan interface it is struggling as mentioned before.
I didn't change anything in "administration" panel.
Confirmation: Similar under [ BE 24.10_7-amd64 ] .
Example:
-> Interface -> select LAN interface -> enable IPv6 :
. . . "IPv6 Configuration Type" = "Track Interface"
. . . "Assign prefix ID" = 0x11
-> Save -> Apply
-> WEB GUI unresponsible for 3'..4'
-> WEB GUI becomes responsible by itself afterwards; no need to reboot et al.
Strange:
During this time, access to other websites works as expected - not being blocked
In the 3-4 min period of WebGui being unaccessible everything beside works as it should.
But this behaviour is very annoying.
If developers wants, I can send my Fujitsu in for further testings.
I rolled back to a new installation of 24.1.10_8 and everything is working fine - even the WebGui.
Until further notice I avoid the 24.7 series.
@Team: Please have a look on my posted (and from 3rd site confirmed) issue.
Can you try your exact same configuration in a VM and replicate it there?
I have like 10 OPNsense VMs and 4 real hardwares I use for testing stuff and I don't have this issue. It must mean for you it's either something related to your hardware, or a general configuration issue which you do with each OPNsense you deploy.
If you can replicate it in a VM with a minimal configuration, e.g. in proxmox, hyper-v, kvm, esxi..., please provide the config.xml file (of course be careful with passwords etc...)
There is no need for special config file - as I said two times before - FULLY FRESH INSTALLATION - and on first switch action in WAN it struggles (on my well-trusted piece of hardware)
But - I tried in a VM (Virtualbox) and 24.7.8 - even GUI - is working fine there.
But that's not my intention - it should run on industry standard "bare metal" as previous versions - and there is something broken in 24.7x. As one former guy confirmed - even in actual Business Edition [BE 24.10_7-amd64] when using bare metal installation.
24.1.x is working great on my bare metal hardware.
Can the scope of that issue be reduced to IPv6 configuration on these interfaces?
Does the issue happen if IPv6 Configuration Type is set to "None"?
Gimme some time - i just install 24.7 new on my 2nd bare metal - the Fujitsu Futro.
I'll report later.
Quote from: AES777GCM on November 18, 2024, 09:26:10 AM
As one former guy confirmed - even in actual Business Edition [BE 24.10_7-amd64] when using bare metal installation.
Processor: Intel Haswell I3-4360T
Memory: 32 GiB
Network:
. Intel I218-V
. Intel I350-T2 v2
. Intel I350-T4 v2
https://github.com/opnsense/core/issues/8064 (https://github.com/opnsense/core/issues/8064)
QuoteCan the scope of that issue be reduced to IPv6 configuration on these interfaces?
Does the issue happen if IPv6 Configuration Type is set to "None"?
When 24.7 (0) is fresh installed, the Issue is there - but away, when disabling IPv6 on WAN. Afterwards it behaves as it should when changing anything on LAN/WAN Port.
But - after patching to 24.7.8 ist won't work this way any longer. Here is - with disabled IPv6 on WAN - the same 3-4 min "time for coffee" reality.
By the way - my new "most loved picture"...
On the "not so fast" Fujitsu Futro the "time out" with unaccessible WebGui stays for nearly 5 min 10sec
Date
Severity
Process
Line
2024-11-18T12:06:48 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-18T12:06:48 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 83587
2024-11-18T12:06:48 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-18T12:01:40 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-18T11:55:47 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-18T11:55:47 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 906
2024-11-18T11:55:47 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-18T11:50:37 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-18T11:49:23 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-18T11:49:23 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 87441
2024-11-18T11:49:23 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-18T11:43:55 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-18T11:43:12 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-18T11:41:06 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-18T11:41:06 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 41340
2024-11-18T11:41:05 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
2024-11-18T11:02:03 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1939) server started (lighttpd/1.4.76)
2024-11-18T10:02:02 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.2350) server stopped by UID = 0 PID = 22138
2024-11-18T10:02:02 Error lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/mod_openssl.c.3674) SSL (error): 5 -1: Operation timed out
2024-11-18T09:57:46 Notice lighttpd (/usr/obj/usr/ports/www/lighttpd/work/lighttpd-1.4.76/src/server.c.1230) [note] graceful shutdown started
On the HUNSN FW6A somethin about 3-4 min.
Quote from: Monviech (Cedrik) on November 18, 2024, 09:39:47 AM
Does the issue happen if IPv6 Configuration Type is set to "None"?
Please, also note https://github.com/opnsense/core/issues/8064#issuecomment-2482676644 .
I've had the same delay or page come up that says page can't be displayed on the latest business release
I just refresh the page and it all comes back
QuoteI've had the same delay or page come up that says page can't be displayed on the latest business release
I just refresh the page and it all comes back
Good idea, but let me say one truth: Without having an appropriate Web Server running, you won't see anything - even when you refresh a hundred times. And pls guess - I tried to refresh the page at first several times.
When this works for you - great. But as you can see in the logfiles, the lighttpd task is "locked" for several minutes and so no Web GUI can be brought up. Even the "reload all services" task is not able to break the spell when lighttpd is "Locked".
When I apply any interface change globally, I get one failed connection to the UI in the browser, but an immediate refresh always works. I guess that's expected and acceptable.
Your problem is ... weird :)
But "this weird thing" is reality.
Have you install 24.7.8 on bare metal and tried it?
I run 24.7.8 on all my community edition installs and they are all bare metal. Single loss of connection, refresh fixes it immediately.
I'm wondering what is actually hanging -- the GUI process itself or the state for the connection to the GUI in the firewall?
Cheers,
Franco
Hi Franco,
thx for leaning in. How can I find out to answer your question?
This is you what you see in 4-5 minutes of WebGui outage when trying to "Reload All Services" via Shell
Enter an option: 11
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring CRON...done.
Setting timezone: Europe/Berlin
Setting hostname: OPNsense.localdomain
Generating /etc/resolv.conf...done.
Generating /etc/hosts...done.
Configuring loopback interface...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring LAN interface...done.
Configuring WAN interface...done.
Setting up routes...done.
Setting up gateway monitor...done.
Configuring firewall.......done.
Starting DHCPv4 service...done.
Starting NTP service...done.
Configuring OpenSSH...done.
Starting Unbound DNS...done.
Starting web GUI...locked.
Syncing OpenVPN settings...done.
What I found out...
1) Opened Shell via SSH
2) Did a change on "Interface / WAN" - Applied --> System in "struggling mode"
3) via "ps -aux | grep lighttpd" I wanted to see the PID
4) As soon as I killed this PID the WebGui comes up again instantly - and lighttpd got another PID
root@OPNsense:/home/udo # ps -aux | grep lighttpd
root 41003 0.0 0.3 22756 9740 - S 15:25 0:00.21 /usr/local/sbin/lighttpd -f /usr/local/etc/lighttpd_web
root 20369 0.0 0.1 12716 2280 0 S+ 15:32 0:00.00 grep lighttpd
#former state - system "hangs now"
root@OPNsense:/home/udo # kill 41003
#WebGui comes up instantly
root@OPNsense:/home/udo # ps -aux | grep lighttpd
root 31146 0.4 0.3 22756 9712 - S 15:32 0:00.06 /usr/local/sbin/lighttpd -f /usr/local/etc/lighttpd_web
root 89160 0.0 0.1 12716 2284 0 S+ 15:32 0:00.00 grep lighttpd
root@OPNsense:/home/udo #
Here is a full extract of "dmidecode" - for whom it may concern (or help?)
root@OPNsense:/home/udo # dmidecode
# dmidecode 3.6
Scanning /dev/mem for entry point.
SMBIOS 2.8 present.
55 structures occupying 2363 bytes.
Table at 0xACEC8018.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: FUJITSU // American Megatrends Inc.
Version: V4.6.5.4 R1.14.0 for D3313-G1x
Release Date: 09/21/2017
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.14
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: FUJITSU
Product Name: FUTRO S920
Version:
Serial Number: YLUE126808
UUID: f22e28e4-69b8-11e8-b1e0-4c52620cf994
Wake-up Type: Power Switch
SKU Number: S26361-Kxxx-Vyyy
Family: FUTRO-FTS
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: FUJITSU
Product Name: D3313-G1
Version: S26361-D3313-G1
Serial Number: 56511213
Asset Tag:
Features:
Board is a hosting board
Board is replaceable
Location In Chassis:
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 25 bytes
Chassis Information
Manufacturer: FUJITSU
Type: Desktop
Lock: Not Present
Version:
Serial Number: YLUE126808
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 1
<OUT OF SPEC> (0)
SKU Number: To be filled by O.E.M.
Handle 0x0004, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Nuvoton
Internal Connector Type: None
External Reference Designator: PS/2 Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0005, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Nuvoton
Internal Connector Type: None
External Reference Designator: PS/2 Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x0006, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SMsC
Internal Connector Type: None
External Reference Designator: Serial-1
External Connector Type: DB-9 male
Port Type: Serial Port 16550 Compatible
Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SMsC
Internal Connector Type: None
External Reference Designator: Serial-2
External Connector Type: DB-9 male
Port Type: Serial Port 16550 Compatible
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SMsC
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator: Serial-3
External Connector Type: None
Port Type: Serial Port 16550 Compatible
Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SMsC
Internal Connector Type: 25 Pin Dual Inline (pin 26 cut)
External Reference Designator: Parallel
External Connector Type: None
Port Type: Parallel Port ECP/EPP
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Realtek
Internal Connector Type: None
External Reference Designator: LAN
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HD8330E
Internal Connector Type: None
External Reference Designator: DVI-I
External Connector Type: Other
Port Type: Video Port
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HD8330E
Internal Connector Type: None
External Reference Designator: Display Port
External Connector Type: Other
Port Type: Video Port
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ALC671
Internal Connector Type: None
External Reference Designator: Rear: Line-Out
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ALC671
Internal Connector Type: None
External Reference Designator: Rear: Line-In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ALC671
Internal Connector Type: None
External Reference Designator: Front: Line-Out
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ALC671
Internal Connector Type: None
External Reference Designator: Front: Mic-In
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: None
External Reference Designator: Rear: USB-1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: None
External Reference Designator: Rear: USB-2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: None
External Reference Designator: Rear: USB-3
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: None
External Reference Designator: Rear: USB-4
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: None
External Reference Designator: Front: USB-1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: None
External Reference Designator: Front: USB-2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator: Intern: USB-1
External Connector Type: None
Port Type: USB
Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: SATA-0
External Connector Type: None
Port Type: None
Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: Other
External Reference Designator: mSATA
External Connector Type: None
Port Type: None
Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: Other
External Reference Designator: mPCIe
External Connector Type: None
Port Type: None
Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: GX-415GA
Internal Connector Type: Other
External Reference Designator: TPM HDR
External Connector Type: None
Port Type: None
Handle 0x001C, DMI type 9, 17 bytes
System Slot Information
Designation: PCIe
Type: PCI Express 2 x16
Data Bus Width: 4x or x4
Current Usage: Unknown
Length: Short
ID: 0
Characteristics:
3.3 V is provided
PME signal is supported
Bus Address: 0000:00:00.0
Handle 0x001D, DMI type 10, 16 bytes
On Board Device 1 Information
Type: Other
Status: Enabled
Description: SMsC SCH5627 Super I/O
On Board Device 2 Information
Type: Other
Status: Enabled
Description: Nuvoton NCT5571D Super I/O
On Board Device 3 Information
Type: Sound
Status: Enabled
Description: Realtek ALC671
On Board Device 4 Information
Type: Video
Status: Enabled
Description: HD8330E
On Board Device 5 Information
Type: Other
Status: Enabled
Description: Antiope
On Board Device 6 Information
Type: Ethernet
Status: Enabled
Description: Realtek RTL8111G
Handle 0x001E, DMI type 11, 5 bytes
OEM Strings
String 1: FUJITSU
String 2: FUJITSU
String 3: FUJITSU TECHNOLOGY SOLUTIONS
Handle 0x001F, DMI type 12, 5 bytes
System Configuration Options
Option 1: J3-5: Default position
Option 2: J1-2: Reserved
Option 3: J5-6: Recovery BIOS active
Handle 0x0026, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Disabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Disabled
Front Panel Reset Status: Not Implemented
Handle 0x0027, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x0028, DMI type 41, 11 bytes
Onboard Device
Reference Designation: SMsC SCH5627 Super I/O
Type: Other
Status: Enabled
Type Instance: 1
Bus Address: 00ff:ff:1f.7
Handle 0x0029, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Nuvoton NCT5571D Super I/O
Type: Other
Status: Enabled
Type Instance: 1
Bus Address: 00ff:ff:1f.7
Handle 0x002A, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Realtek ALC671
Type: Sound
Status: Enabled
Type Instance: 1
Bus Address: 00ff:ff:1f.7
Handle 0x002B, DMI type 41, 11 bytes
Onboard Device
Reference Designation: HD8330E
Type: Video
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:00.0
Handle 0x002C, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Antiope
Type: Other
Status: Enabled
Type Instance: 1
Bus Address: 00ff:ff:1f.7
Handle 0x002D, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Realtek RTL8111G
Type: Ethernet
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:00.0
Handle 0x002E, DMI type 15, 77 bytes
System Event Log
Area Length: 16383 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFC46000
Status: Valid, Not Full
Change Token: 0x00000001
Header Format: Type 1
Supported Log Type Descriptors: 27
Descriptor 1: Single-bit ECC memory error
Data Format 1: Multiple-event handle
Descriptor 2: Multi-bit ECC memory error
Data Format 2: Multiple-event handle
Descriptor 3: Parity memory error
Data Format 3: None
Descriptor 4: Bus timeout
Data Format 4: None
Descriptor 5: I/O channel block
Data Format 5: None
Descriptor 6: Software NMI
Data Format 6: None
Descriptor 7: POST memory resize
Data Format 7: None
Descriptor 8: POST error
Data Format 8: POST results bitmap
Descriptor 9: PCI parity error
Data Format 9: Multiple-event handle
Descriptor 10: PCI system error
Data Format 10: Multiple-event handle
Descriptor 11: CPU failure
Data Format 11: None
Descriptor 12: EISA failsafe timer timeout
Data Format 12: None
Descriptor 13: Correctable memory log disabled
Data Format 13: None
Descriptor 14: Logging disabled
Data Format 14: None
Descriptor 15: System limit exceeded
Data Format 15: None
Descriptor 16: Asynchronous hardware timer expired
Data Format 16: None
Descriptor 17: System configuration information
Data Format 17: None
Descriptor 18: Hard disk information
Data Format 18: None
Descriptor 19: System reconfigured
Data Format 19: None
Descriptor 20: Uncorrectable CPU-complex error
Data Format 20: None
Descriptor 21: Log area reset/cleared
Data Format 21: None
Descriptor 22: System boot
Data Format 22: None
Descriptor 23: End of log
Data Format 23: None
Descriptor 24: OEM-specific
Data Format 24: OEM-specific
Descriptor 25: OEM-specific
Data Format 25: OEM-specific
Descriptor 26: OEM-specific
Data Format 26: OEM-specific
Descriptor 27: OEM-specific
Data Format 27: OEM-specific
Handle 0x0031, DMI type 176, 36 bytes
OEM-specific Type
Header and Data:
B0 24 31 00 00 00 13 33 00 39 03 00 03 31 FF FF
F9 83 15 E3 68 FA 2D 4C A4 80 C2 04 A0 7F 70 C4
02 00 02 00
Handle 0x0032, DMI type 177, 42 bytes
OEM-specific Type
Header and Data:
B1 2A 32 00 12 00 00 00 12 00 00 00 12 04 06 05
04 01 0E 00 00 00 00 00 00 00 00 12 00 00 00 00
00 00 00 00 00 00 00 00 00 00
Handle 0x0033, DMI type 188, 8 bytes
OEM-specific Type
Header and Data:
BC 08 33 00 30 39 31 24
Handle 0x003C, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 4 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x003D, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Array Handle: 0x003C
Partition Width: 255
Handle 0x003E, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x003C
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: No Module Installed
Form Factor: SODIMM
Set: None
Locator: DIMM 2
Bank Locator: CHANNEL A
Type: DDR3
Type Detail: None
Handle 0x003F, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x003C
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 4 GB
Form Factor: SODIMM
Set: None
Locator: DIMM 1
Bank Locator: CHANNEL A
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 1600 MT/s
Manufacturer: Hynix/Hyundai
Serial Number: 0356C745
Asset Tag: A1_AssetTagNum1
Part Number: HMT451S6BFR8A-PB
Rank: 1
Configured Memory Speed: 1600 MT/s
Minimum Voltage: 1.35 V
Maximum Voltage: 1.5 V
Configured Voltage: 1.5 V
Handle 0x0040, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000000003FF
Range Size: 1 kB
Physical Device Handle: 0x0000
Memory Array Mapped Address Handle: 0x0000
Partition Row Position: <OUT OF SPEC>
Handle 0x0041, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x003F
Memory Array Mapped Address Handle: 0x003D
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x0043, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 CACHE
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 kB
Maximum Size: 128 kB
Supported SRAM Types:
Pipeline Burst
Installed SRAM Type: Pipeline Burst
Speed: 1 ns
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 2-way Set-associative
Handle 0x0044, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 CACHE
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 1 MB
Maximum Size: 1 MB
Supported SRAM Types:
Pipeline Burst
Installed SRAM Type: Pipeline Burst
Speed: 1 ns
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 16-way Set-associative
Handle 0x0045, DMI type 4, 42 bytes
Processor Information
Socket Designation: P0
Type: Central Processor
Family: G-Series
Manufacturer: AuthenticAMD
ID: FF FB 8B 17 01 0F 73 00
Signature: Family 11, Model 15, Stepping 15
Flags:
FPU (Floating-point unit on-chip)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
DS (Debug store)
ACPI (ACPI supported)
Version: AMD GX-222GC SOC with Radeon(TM) R5E Graphics
Voltage: 1.4 V
External Clock: 100 MHz
Max Speed: 2200 MHz
Current Speed: 2200 MHz
Status: Populated, Enabled
Upgrade: None
L1 Cache Handle: 0x0043
L2 Cache Handle: 0x0044
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0046, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 2
en|US|iso8859-1
ja|JP|unicode
Currently Installed Language: en|US|iso8859-1
Handle 0x0049, DMI type 127, 4 bytes
End Of Table
Regarding bug-hunting: Isn't it helpful when developers know now that "killing" the lighttpd task manually (while system is in status "locked") brings the Web Gui instantly back to live ?
Pls have a look @ my posting from 18th Nov 03:28pm.
Is this problem taken seriously?
I hope so.
However - thank's in advance @Franco and Team!!!
Can you tell me the minimal configuration and environment which can reproduce this?
Minimal configuration would be any configuration changes after a clean install.
Environment would be if it can also be reproduced without any external infrastructure involved. Direct connection of client to Opnsense hardware
If there are switches, ISP routers or whatever involved it makes it harder to reproduce since it can be many specific factors in your personal environment I do not know.
Does it have to be random hardware? I still have an old intel core2duo pc around if thats needed for reproduction. I ran opnsense on it before like 4 years ago I think.
Hello Cedrik,
at first thanks for your reply and intention to look this up.
My setup is really simple basic: WAN put in em1; LAN in em0. LAN connected to a layer 2 switch - pc directly connected to this switch.
Installation of fresh 24.7 --> then update via console to 24.7.8.
After reboot login as root (WEB GUI)--> run initial setup.
Then act as you want to do anything on WAN interface - like OPT IN "Prevent Interface Removal" --> Save --> APPLY
This "Apply" leads on my 2 Systems (HUNSN / FUJITSU) to the above mentioned system stall.
Its very interesting how your system react and if it the same, what might be the problem.
Cheers,
Udo
Does your system react the same if WAN is disconnected, the Layer 2 switch does not exist, and your client is plugged into LAN directly?
Please deconstruct your setup a bit more for a common baseline.
I hardly can use a Firewall with WAN disconnected and an unbroken, unmanaged Layer 2 Switch can't be a factor.
As I said - when the lighttpd task is killed manually the WebGui pop ups directly again of the former struggled system.
But I can find out on thursday what you proposed.
Do you have a "special idea" by asking this for?
How does your System behaves?
My systems (mostly DEC740 and 750) as well as my developement and general use VMs all work without issues. Thats why right now I want to rule out outside factors in your environment. Asking you to disconnect all outside factors is not to make your system unusable, but to see if the issue still happens.
Thats common troubleshooting practice, deconstructing a setup until the issue is not present, and then slowly introducing more complexity until it happens again.
Digging around on the box itself would be far more productive but thats commercial support scope.
EDIT:
Looking at the lighttpd error logs you provided makes it look like the graceful shutdown of the process fails. It seems to wait for something, e.g., all connections to close. Thats why killing it fixes it for you, the graceful process shutdown fails.
Okay - got the point.
I'll give report on thursday. Thx in advance for your support.
cheers,
udo
Hello Cedrik,
I tried already and - bad news - When disconnect WAN - nothing happens regarding this issse.
Second - directly plugin of LAN had no impact, too.
It keeps on being "weird".
Btw: Patched up to today's latest version (24.7.9_1) and (as expected) nothing changes - issue is same.
Hey thanks for trying and confirming that it must be an isolated hardware/software related issue. I'll install the latest version on some old and new hardware and see if I can reproduce the steps you outlined.
I just tested a fresh installation on a DEC740, couldn't reproduce the issue.
Also had IPv6 on WAN with DHCPv6 just to ensure parity.
Next I dusted off some pretty ancient hardware.
Tarox Digital Machine
Intel Core Duo T6600 2.2ghz
2GB DDR2 RAM
64GB SSD
Realtek Nic
I could only install 24.7 on it, updates would fail since its too bad. But clicking aroun, saving and applying the interface settings in 24.7 did not make the web GUI freeze like in your case.
EDIT:
It didnt update cause my time was wrong lol
root@OPNsense:~ # date
Thu Aug 21 00:11:50 UTC 2008
root@OPNsense:~ # date
Wed Nov 20 20:25:18 UTC 2024
Now it is on 24.7.9 on that ancient but trusty piece of industry standard hardware.
root@OPNsense:~ # dmidecode
# dmidecode 3.6
Scanning /dev/mem for entry point.
SMBIOS 2.4 present.
39 structures occupying 1058 bytes.
Table at 0x000F0000.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Phoenix Technologies, LTD
Version: 6.00 PG
Release Date: 08/21/2008
Address: 0xE0000
Runtime Size: 128 kB
ROM Size: 1 MB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/360 kB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: AOpen
Product Name: i965GMx-HG
Version: OEM
Serial Number: OEM
UUID: 00000000-0000-0000-0000-000000000001
Wake-up Type: Power Switch
SKU Number:
Family:
Handle 0x0002, DMI type 2, 10 bytes
Base Board Information
Manufacturer: AOpen
Product Name: i965GMx-HG
Version: 55ADE01I650
Serial Number: 90200487JEA7
Asset Tag:
Features:
Board is a hosting board
Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
Manufacturer: AOpen
Type: Desktop
Lock: Not Present
Version: i965GMx-HG
Serial Number:
Asset Tag:
Boot-up State: Unknown
Power Supply State: Unknown
Thermal State: Unknown
Security Status: Unknown
OEM Information: 0x00000000
Handle 0x0004, DMI type 4, 35 bytes
Processor Information
Socket Designation: Socket 479
Type: Central Processor
Family: Core 2 Duo
Manufacturer: Intel
ID: 7A 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 10
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM)2
Voltage: 1.1 V
External Clock: 200 MHz
Max Speed: 4000 MHz
Current Speed: 2200 MHz
Status: Populated, Enabled
Upgrade: ZIF Socket
L1 Cache Handle: 0x0008
L2 Cache Handle: 0x0009
L3 Cache Handle: Not Provided
Serial Number:
Asset Tag:
Part Number: <BAD INDEX>
Handle 0x0005, DMI type 5, 20 bytes
Memory Controller Information
Error Detecting Method: 8-bit Parity
Error Correcting Capabilities:
None
Supported Interleave: One-way Interleave
Current Interleave: One-way Interleave
Maximum Memory Module Size: 2048 MB
Maximum Total Memory Size: 4096 MB
Supported Speeds:
Other
Supported Memory Types:
DIMM
Memory Module Voltage: 5.0 V
Associated Memory Slots: 2
0x0006
0x0007
Enabled Error Correcting Capabilities:
None
Handle 0x0006, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A0
Bank Connections: None
Current Speed: Unknown
Type: Unknown
Installed Size: Not Installed
Enabled Size: Not Installed
Error Status: OK
Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: A1
Bank Connections: 2 3
Current Speed: Unknown
Type: DIMM
Installed Size: 1024 MB (Double-bank Connection)
Enabled Size: 1024 MB (Double-bank Connection)
Error Status: OK
Handle 0x0008, DMI type 7, 19 bytes
Cache Information
Socket Designation: Internal Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0009, DMI type 7, 19 bytes
Cache Information
Socket Designation: External Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: External
Installed Size: 1 MB
Maximum Size: 1 MB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PRIMARY IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SECONDARY IDE
Internal Connector Type: On Board IDE
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: FDD
Internal Connector Type: On Board Floppy
External Reference Designator: Not Specified
External Connector Type: None
Port Type: 8251 FIFO Compatible
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: COM1
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator:
External Connector Type: DB-9 male
Port Type: Serial Port 16450 Compatible
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: COM2
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator:
External Connector Type: DB-9 male
Port Type: Serial Port 16450 Compatible
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LPT1
Internal Connector Type: DB-25 female
External Reference Designator:
External Connector Type: DB-25 female
Port Type: Parallel Port ECP/EPP
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Keyboard
Internal Connector Type: PS/2
External Reference Designator:
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PS/2 Mouse
Internal Connector Type: PS/2
External Reference Designator:
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB0
External Connector Type: Other
Port Type: USB
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Other
Port Type: USB
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Other
Port Type: USB
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB3
External Connector Type: Other
Port Type: USB
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB4
External Connector Type: Other
Port Type: USB
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB5
External Connector Type: Other
Port Type: USB
Handle 0x0018, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB6
External Connector Type: Other
Port Type: USB
Handle 0x0019, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB7
External Connector Type: Other
Port Type: USB
Handle 0x001A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB8
External Connector Type: Other
Port Type: USB
Handle 0x001B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Not Specified
Internal Connector Type: None
External Reference Designator: USB9
External Connector Type: Other
Port Type: USB
Handle 0x001C, DMI type 9, 13 bytes
System Slot Information
Designation: PCI0
Type: PCI
Data Bus Width: 32 bit
Current Usage: Available
Length: Long
ID: 1
Characteristics:
5.0 V is provided
PME signal is supported
Handle 0x001D, DMI type 9, 13 bytes
System Slot Information
Designation: PCI1
Type: PCI Express
Data Bus Width: 32 bit
Current Usage: In Use
Length: Long
ID: 2
Characteristics:
5.0 V is provided
PME signal is supported
Handle 0x001E, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 3
n|US|iso8859-1
n|US|iso8859-1
r|CA|iso8859-1
Currently Installed Language: n|US|iso8859-1
Handle 0x001F, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 2 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x0020, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x001F
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: A0
Bank Locator: Bank0/1
Type: Unknown
Type Detail: Unknown
Handle 0x0021, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x001F
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1 GB
Form Factor: DIMM
Set: None
Locator: A1
Bank Locator: Bank2/3
Type: Unknown
Type Detail: Synchronous
Speed: 55438 MT/s
Manufacturer: None
Serial Number: None
Asset Tag: None
Part Number: None
Handle 0x0022, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Array Handle: 0x001F
Partition Width: 1
Handle 0x0023, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000000003FF
Range Size: 1 kB
Physical Device Handle: 0x0020
Memory Array Mapped Address Handle: 0x0022
Partition Row Position: 1
Handle 0x0024, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x0021
Memory Array Mapped Address Handle: 0x0022
Partition Row Position: 1
Handle 0x0025, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x0026, DMI type 127, 4 bytes
End Of Table
root@OPNsense:~ # opnsense-version
OPNsense 24.7.9_1 (amd64)
root@OPNsense:~ # ifconfig
re0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
description: LAN (lan)
options=82088<VLAN_MTU,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
ether 00:01:80:77:8d:4d
inet 172.16.0.94 netmask 0xffffff00 broadcast 172.16.0.255
inet6 fe80::201:80ff:fe77:8d4d%re0 prefixlen 64 scopeid 0x1
inet6 2003:XXXX:XXXX:XXaa:201:80ff:fe77:8d4d prefixlen 64 autoconf pltime 14400 vltime 86400
inet6 fd70:248c:966f:de48:201:80ff:fe77:8d4d prefixlen 64 detached autoconf pltime 1800 vltime 1800
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
Still no dice though, all interface editing works for me without any lighttpd crashes.
So I give up here, sorry.
Okay... I see.
Thx for your try.
cheers,
Udo
Last post from me on this topic, cause it seems that only very few hardware items got this "weird" behaviour.
So I have to live with it, that after "Applying" on any INTERFACE made GUI action the System's GUI hang up for a several time.
This leads to my question: Is it okay, when I make x-Switch Actions on several Interfaces and click only ONE TIME the "APPLY" Button at the end?
Or is it better to klick on APPLY each time before leaving any Interface?
I can live with one time waiting 4 minutes before re-entering GUI; but x-time Waiting for 4 minutes is really not good for my heart due too much coffee pauses ::)
as posted previously. I am running a DEC 670 running the latest business release.
if I open a interface > choose 1400 as MTU. click save then APPLY>. this immediately happens each time.
I'm running the router to a Unifi 8 port switch with 2 vans.
static IP for wan
edit. when I removed 1400 under MTU. and hit save > apply. it happens again. I refresh Safari
I just tried this in Firefox ESR and it acts differently. if I make the change and click save then Apply. nothing happens.. I have to click Apply Twice for it to save.
so easily replicated in Safari. different issues in Firefox ESR
is the OP using Safari?
Quoteas posted previously. I am running a DEC 670 running the latest business release.
if I open a interface > choose 1400 as MTU. click save then APPLY>. this immediately happens each time.
What happens immediately each time?
A System "Stall" for 3-4 minutes describes as in this thread?
QuoteI just tried this in Firefox ESR and it acts differently. if I make the change and click save then Apply. nothing happens.. I have to click Apply Twice for it to save.
What means "nothing happens"?
The system saves not? The system hangs? The system react like it should?
Could you give an information which describes your experiences clearly?
Quote from: AES777GCM on November 24, 2024, 05:39:36 PM
Quoteas posted previously. I am running a DEC 670 running the latest business release.
if I open a interface > choose 1400 as MTU. click save then APPLY>. this immediately happens each time.
What happens immediately each time?
A System "Stall" for 3-4 minutes describes as in this thread?
the hardware does not stall. just the browser goes to page can not be displayed message in Safari. in firefox. you click apply and nothing happens... if i wait and click apply again, it then saves
QuoteI just tried this in Firefox ESR and it acts differently. if I make the change and click save then Apply. nothing happens.. I have to click Apply Twice for it to save.
What means "nothing happens"?
The system saves not? The system hangs? The system react like it should?
all tunnels still work, traffic flows. you just lose access to the page you are on currently until you fresh
Could you give an information which describes your experiences clearly?
Okay - so in your case - the browser has an impact and everything else worked fine for you. That's weird but okay.
As I mentioned in the thread, my both Systems! I gave a try [with 24.7.x] behave the same: After Applying any switch action in INTERFACE SECTION you can see that save is done, but instead of "coming back after doing his things" the WebGui Server hangs up for 3-4 minutes.
In this state of lighttpd task being "locked" you can't even reset this task. I have two choices then: Wait for 3-4 minutes; somehow the task is then being killed automatically and comes back or killing the "stalled" lighttpd manually.
The Browser could not be an impact for me in this time.
"locked" means your lighttpd is in the process of already being reconfigured. No idea why it's taking so long. You could add
log_msg("my message here");
commands to https://github.com/opnsense/core/blob/master/src/etc/inc/plugins.inc.d/webgui.inc#L137-L174
My guess is lighttpd doesn't stop or start and hangs the PHP script which keeps the lock over the lifetime of the PHP script. I will not speculate over where it may hang. You'll find it if you want to and can report back.
Cheers,
Franco
Hi Franco,
I have no clue how to insert this code line cause I don't see any /src directory when using shell.
I help myself right now by killing lighttpd and reloading all services again.
For other who may have same issue and needs a step by step manual:
1. Open a ssh session
2. Insert "su" as first line and authorize with ROOT Password
3. Change to menu item 8) SHELL
0) Logout 7) Ping host
1) Assign interfaces 8) Shell
2) Set interface IP address 9) pfTop
3) Reset the root password 10) Firewall log
4) Reset to factory defaults 11) Reload all services
5) Power off system 12) Update from console
6) Reboot system 13) Restore a backup
Enter an option: 8
root@obelix:/home/udo #
Now find out how many lighttpd tasks your system has
root@obelix:/home/udo # ps aux | grep lighttpd
root 17036 0.0 0.1 22784 10068 - S 18:05 0:00.35 /usr/local/sbin/lighttpd -f /usr/local/etc/lighttpd_w
root 31424 0.0 0.0 14448 4084 - S 18:04 0:00.02 /usr/local/sbin/lighttpd -f /var/etc/lighttpd-acme-ch
root 48669 0.0 0.0 12716 2396 0 S+ 18:18 0:00.00 grep lighttpd
root@obelix:/home/udo #
In this example I got 2 running services. When System stalls, it is is NOT the acme service, so have a look at the PID of the other one --> 17036
So - when system stalls after "Applying", just kill this "locked" task and everything is fine again.
root@obelix:/home/udo # kill 17036
Th variant for lazy Guys is more like a HAMMER Method, but same effective.
I know via PS-AUX that I have 2 lighttpd tasks. So what, if we kill all lighttpd tasks and reload all services again?
root@obelix:/home/udo # ps aux | grep lighttpd
root 95866 2.8 0.1 20220 9564 - S 18:24 0:00.02 /usr/local/sbin/lighttpd -f /usr/local/etc/lighttpd_w
root 26470 1.3 0.0 14448 4088 - S 18:24 0:00.00 /usr/local/sbin/lighttpd -f /var/etc/lighttpd-acme-ch
root 12748 0.0 0.0 12716 2392 0 S+ 18:24 0:00.00 grep lighttpd
root@obelix:/home/udo # pkill lighttpd -f
root@obelix:/home/udo # pkill lighttpd -f
root@obelix:/home/udo # configctl service reload all
OK
root@obelix:/home/udo #
Sorry, but I am not a professional coder and getting the things work "somehow" is my intention.
But nevertheless - thanks tho all Folks working directly and indirectly on codebase and keeps IT a little safer for all of us.
cheers,
Udo
I've been experiencing weird issues, particularly when setting up interfaces. I thought my whole setup was being bricked as I was not waiting long enough. I wonder if this bug is what I'm experiencing. I made a separate thread already but just thought I'd post to say I may also be experiencing this. Next time it happens I will give it time to see if it fixes itself. I will have a continuous ping, then do a change to interfaces, then lose everything and the ping also fails. Can't access web interface from any interfaces.
At one point I also did a reload service within the local console, and during that process I got one ping in then it failed again. So that did something, sort of.
I had one issue where one interface was handing out the wrong DHCP range, but then it fixed itself overnight. So it seems to me there may be some issues where things don't happen instantly when you make changes and there's something happening in the background.
I don't want to hijack this thread though and I already made my own, but starting to wonder if it's related and just thought I'd mention it.
This thread reminds me of race conditions in the PHP and shell scripts that I pointed out in https://github.com/opnsense/core/issues/6351 (make sure to show comments which might be hidden by github due to the long conversation thread)
I am a professional programmer (lighttpd developer) and made suggestions how to eliminate the race conditions I identified, and some -- but not all -- changes were implemented. It might be useful if some one else with scripting and process management experience would review that code again and provide feedback to Franco, as my posts in https://github.com/opnsense/core/issues/6351 were not enough.
Glenn, with all due respect your preachy behaviour is betting a bit old on the subject like lighttpd start race or OCSP.
I did address your concerns in the meantime and more regarding it but now it's gotten worse and your attitude needs a shift now that a proper lock is in place. We're still running into lockups... not that I am overly surprised to hear, but I also cannot reproduce. Can you?
Cheers,
Franco
The locking code. To be frank I cannot see anything other than lighttpd locking up as witnessed by the user having to kill it. :)
https://github.com/opnsense/core/commit/4182f1993
Thx for Glenn and Franco talking about the problem. Only by accepting a problem hope to fix it can be assumed.
@Franco:: If you wanna reproduce it - I'd like to send you my Fujitsu (you can keep it afterwards) so you can see I'm not telling a fairy tale. The fact I got this issue on 2 pieces of hardware (and being not alone in the world) tells one simple truth: There must be a problem somewhere in Code.
If Glenn is able to help - pls let him help.
Ok, I'll send you a PM.
Thanks,
Franco
People affected can try this patch:
# opnsense-patch https://github.com/opnsense/core/commit/988dbae92
But this is just speculation from not being able to reproduce it here. The client environment seems to affect the current behaviour and I don't understand the trigger condition.
Cheers,
Franco
Seems to help in my case. Haven't tested it extensively though.
In my case the patch is a big step forward.
Just to tell everybody what this patch actually is:
In usr/local/www/interfaces.php ...
--> line 586 should be commented out
/*plugins_configure('early');*/
--> line 587 should be inserted
configd_run('webgui restart 3', true);
After a reboot I got no issues after switching anything in Menu Section "INTERFACES" and "APPLY" anymore - WebGUI came back as expected.
I just had one time the issue that "Widgets failed to load" in dashboard came up; but after rebooting and trying again some weird things in GUI everything looked okay.
I recommend to have this changed "patched" Version in further Versions of OPNSENSE.
I want to say biggest "thank you" to Franco for his engagement. And I will have a look if my used "ESET INTERNET SECURITY" might have an impact due to "false driven" HTTP/HTTPS traffic inspection.
I'll test next days and keep you informed.
Cheers,
Udo
Quote from: AES777GCM on December 10, 2024, 07:11:27 PM
In usr/local/www/interfaces.php ...
--> line 586 should be commented out
/*plugins_configure('early');*/
--> line 587 should be inserted
configd_run('webgui restart 3'),true);
Just to be sure this isn't missed... running the command line as below will actually patch the file, no need for commenting out or typo-related mishaps :)
# opnsense-patch https://github.com/opnsense/core/commit/988dbae92
Let's see if this holds up... in any case this is 24.7.11 material so we don't need to wait too long for it.
Cheers,
Franco
Yesterday I kicked "UBlock Origin" out of my Firefox Extension after reading about an issue another user had with UBlock Origin lite.
Today I updated to latest Version - 24.7.11 and everything is working fine now - at least it seems after some minutes of extensive testing.
Thx to Franco and Team - you did a great job and for me you delivered an early x-mas surprise.
@all: Pls try new Version and post your experience under this.
Greetings,
Udo
Hi Udo,
Thanks for the feedback. Happy to hear it's better now.
Cheers,
Franco