23.7.8 crashes periodically and unbound reporting becomes inactive. Need assist.

Started by enpassant, November 22, 2023, 06:07:34 PM

Previous topic - Next topic
Notice   kernel   <6>igb2: link state changed to DOWN
This is the most relevant entry (entries) on this log snippet. It tells that the interface for some reason, became "detached" from the system. Entries for services going down and up following the interface what we would expect.
As to why the interface is going down is the next step in the diagnostic.
It can be a physical problem like a loose connection but doesn't have to be.

Quote from: cookiemonster on December 25, 2023, 10:32:57 PM
Notice   kernel   <6>igb2: link state changed to DOWN
This is the most relevant entry (entries) on this log snippet. It tells that the interface for some reason, became "detached" from the system. Entries for services going down and up following the interface what we would expect.
As to why the interface is going down is the next step in the diagnostic.
It can be a physical problem like a loose connection but doesn't have to be.
Thank you for the reply. I will check with the vendor and do hardware tests.

I am returning to this to let folks know I found a solution. The combination of these has my network back to normal and no crashes or errors in the system logs lately.

1. I am now using Suricata on the LAN and WAN interfaces.
2. I am now using AdGuard Home to do filtering with Unbound as the upstream resolver.
3. I was getting some interface flapping on igb2, my management NIC. I deleted that interface and moved my management network to a VLAN.
4. I was getting a wireguard interface loop, so I set up a restart instance in Monit using these instructions: https://forum.opnsense.org/index.php?topic=35919.0

Since making these changes, Unbound has been working smoothly - no issues, no crashes, and reporting is working. I also enjoy the AdGuard interface for filtering. Problems solved.