Strange new reboot couple times a day

[zzup]

Since i updated to 24.1.2_1 from 23.X I have been having random reboots of my opensense system.  Before this update my system was up for months at a time. It is now rebooting 2 - 3 times per day.  The only error i see in the logs is below.  I do have ZenArmor installed and running but that was also in before.  I have a simple 1 wan 1 lan connections, no vlans.  Any ideas where i should start looking to track down the random reboots.


Error   configd.py   action rfc2136.reload.lan not found for user root

[zzup]

After reading another post i checked my logs and found that my dhcp on my wan after the upgrade is now renewing every 1 - 2 hours vs before upgrade.  The crash seems to happen  during one of these frequent renews.  It seems like the new version is requesting a shorter dhcp than the default of the pervious version.  But i am guessing.  How would i tell the dhcp on the wan to ask for a longer lease in the gui and what would be recommended to have it set to for cable internet?

[CJ]

You would have to specify a custom config file under your WAN interface in order to adjust the asked for lease time.  However, it's unlikely the the lease frequency is the cause of your issues as it's likely the same as before and you just never noticed.

What else are you seeing in your logs?  What symptoms are you seeing?  Is OPNsense actually rebooting with the system down and up noises or something else?

[bartjsmit]

It seems like the new version is requesting a shorter dhcp than the default of the pervious version.

DHCP clients don't determine the lease time. The server dictates it to the client as part of the offer and clients request renewal at the half way point.

[CJ]

It seems like the new version is requesting a shorter dhcp than the default of the pervious version.

DHCP clients don't determine the lease time. The server dictates it to the client as part of the offer and clients request renewal at the half way point.

Not true.  The client can ask for a specific lease time.

Code: [Select]

option dhcp-lease-time uint32;

This option is used in a client request (DHCPDISCOVER or DHCPREQUEST) to allow the client to request a lease time for the IP address. In a server reply (DHCPOFFER), a DHCP server uses this option to specify the lease time it is willing to offer.

This option is not directly user configurable in the server; refer to the max-lease-time and default-lease-time server options in dhcpd.conf(5).
https://kb.isc.org/docs/isc-dhcp-44-manual-pages-dhcp-options#standard-dhcpv4-options

You'll also note that the OPNsense UI has a default lease time field for clients that don't specify a lease time as well as a max lease time field for clients that do.

[zzup]

I see in the GUI there is options to set for the DHCP options that i can just add the option dhcp-lease-time uint32
I will give that a go and see how it does.

[CJ]

I see in the GUI there is options to set for the DHCP options that i can just add the option dhcp-lease-time uint32
I will give that a go and see how it does.

Ah, I missed the lease section under advanced.  So you won't need a custom config.  However, be aware that dhcp-options aren't necessarily straightforward and can require some tweaking of option 55.

I still think you're avoiding addressing the actual cause of your problem.  Look in System: Log Files: General for IP renewal starting at the Notice level.  That should show you the frequency going all the way back as far as you have logs.  Then you can compare the timing from then until now.

[zzup]

  I rolled back to 23.7 and am having no reboots or issues now.  I am wondering if it was something new in 24.  I am not seeing the frequency of dhcp renews on 23 vs 24 for the WAN interface.

[Desolator]

Google brought me here...

I'm in the same boat, random reboots since the 24.1.2 & 24.1.3 update. I see strange memory behaviour in the graphs, maybe there is some kind of memory leak? There were reboots around the spikes...

The log files tell me nothing...

[CJ]

Google brought me here...

I'm in the same boat, random reboots since the 24.1.2 & 24.1.3 update. I see strange memory behaviour in the graphs, maybe there is some kind of memory leak? There were reboots around the spikes...

The log files tell me nothing...

Start a new thread and post your hardware and other info.

[gilspina]

I'm having the same problem

2024-04-18T02:28:38-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-17T02:28:44-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-16T02:28:50-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-15T02:28:57-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-14T02:29:03-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-13T02:29:09-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-12T02:29:15-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-11T02:29:18-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-10T02:29:25-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-09T02:29:31-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-08T02:29:38-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-07T02:29:43-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-06T02:29:48-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-05T02:29:55-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-04T02:30:01-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-03T02:30:07-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root   
2024-04-02T02:30:13-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root

Any update about this?

[gilspina]

Tried to reinstall opnsense, but not solved the problem.

2024-04-25T02:27:57-03:00   Error   configd.py   action rfc2136.reload.opt1 not found for user root

[Kenji776]

I am also having what I think is the same issue. A few times a day requests will just start failing. The UI reports that the WAN connection is up, but no requests either by IP or DNS resolution can be resolved. It does seem to happen more often when downloading large files (1gb+) but I'm not 100% convinced yet that is the issue. The only things that look like errors in any of the logs are numerous entries of

2024-05-09T21:12:32   Error   configd.py   action rfc2136.reload.wan not found for user root

I have a fairly basic setup, I only just got it running yesterday and have done minimal additional config. I setup DHCP, and was running unbound DNS but I've disabled that temporarily for testing as some other posts indicated it could help. Same with AdGuard, I did have it running, but I've since disabled it to see if it makes any difference though this issue was occurring before I installed that so I doubt it.

[qu37zal]

+1, I lose internet and find that opnsense is no longer accepting logins via the lan port, but is still printing occasional log on the attached monitor.  This def looks like a soft problem.

```
2024-05-17T08:41:16-05:00   Error   configd.py   action rfc2136.reload.lan not found for user root   
2024-05-17T08:40:51-05:00   Error   configd.py   action rfc2136.reload.lan not found for user root
2024-05-17T08:40:11-05:00   Error   configd.py   action rfc2136.reload.lan not found for user root   
2024-05-17T08:39:51-05:00   Error   configd.py   action rfc2136.reload.lan not found for user root   
2024-05-17T08:39:11-05:00   Error   configd.py   action rfc2136.reload.lan not found for user root   
```

OPNsense 24.1.7-amd64
FreeBSD 13.2-RELEASE-p11
OpenSSL 3.0.13

Intel(R) Celeron(R) N5095 @ 2.00GHz (4 cores, 4 threads)

[tsense]

I have had a similar problem since version 24.1.7. The WAN interface can only access the Internet shortly after a restart, after which it no longer works, neither via ping trace etc. I can also find the following entry in my logs. Error configd.py action rfc2136.reload.wan not found for user root. Is this a fundamental error?