Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - wide

#1
Most likely this was not related to 25.7.11_1 update but changes in IDS configuration I had done right after the update. Finally today I restored the Opnsense VM from the backup taken before 25.7.11_1 update and updated the VM then to latest 25.7.11_2 and now all good so far.
#2
I was able to isolate this issue to WebGUI Dashboard. When I have shell open at the same time when I login to WebGUI and tens of php processes starts to spawn I then run killall php from the shell and then go to some other part of the WebGUI without any issues. So there is something in the Dashboard itself or in my particular Dashboard view which gets Opnsense to go haywire.
#3
I managed to update to version 25.7.11_2 by using opnsense-shell and then run restart all the services from shell also.
System remains stable. No exessive disk writes, normal memory consuption and regular CPU load.

But still immediately after I open the WebGUI the systems goes haywire. Tens and then hundreds of PHP processes spawn and system runs out of memory.

#4
Hi,

System is fully functional and stable after reboot if I don't open the WebGUI. So clean start and staying away from management keeps the load and memory consumption in similar levels what were before the 25.7.11_1 update. Is it sure that my case is connected to this Neighbors: Automatic Discovery feature?
#5
I've updated from 25.7.10 to 25.7.11_1 yesterday. It's now impossible to access WebGUI because after the login screen when dashboard starts loading the UI spawns hundreds of PHP processes which causes system load to raise above 100 and after few minutes sytem runs out of memory and also consumes all the allocated swap space finally killing the network traffic completely.

System recovers from the situation after closing the WebGUI browser tab but it might take 30-60 minutes when all the PHP processes are finished and memory consumption and system load returns back to normal values.
#6
I'm having this exactly same issue as Shoresy described.

Immediately when I switch the gateway to WAN Gateway Group it console is flooded with these
arpresolve: can't allocate llinfo for <WAN IPv4> on igc1 / igc2 messages.

For me it looks that <WAN IPv4> it mentions in interface igc1 llinfo message is the default WAN gateway for igc2 and similarly <WAN IPv4> it mentions in interface igc2 llinfo is the default WAN gateway for igc1.

In my case both WAN interfaces igc1 and igc2 get the IP configurations from two different ISPs DHCP servers.