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
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?
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?
Quote from: zzup on March 04, 2024, 11:31:32 PM
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.
Quote from: bartjsmit on March 05, 2024, 03:06:46 PM
Quote from: zzup on March 04, 2024, 11:31:32 PM
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.
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.
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.
Quote from: zzup on March 05, 2024, 06:28:17 PM
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.
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.
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...
Quote from: Desolator on March 08, 2024, 05:34:58 PM
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.
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?
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
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.
+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)
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?
I'm just gonna chime in to say I'm having a similar issue. I think with as many people as there are this issue doesn't seem to be hardware specific. I just configured the OPNsense (24.1.19) today, an I'm running it inside a vm with NICs passed through. Couple times during the day I hit the aforementioned issue: `configd.py action rfc2136.reload.wan not found for user root` I got similar entries for my 2 other interfaces. At the same time as the last crash, I saw the following entries in the General log (newest first):
```log
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : wireguard_sync(,wan))
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,wan))
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,wan))
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,wan))
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (,wan)
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : wireguard_configure_do(,wan))
Notice opnsense /usr/local/etc/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,wan))
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,wan))
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure vpn (,wan)
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GW))
Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure monitor (,WAN_GW)
Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: keeping inet default route to www.www.www.www
Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: configuring inet default gateway on wan
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dns (execute task : unbound_configure_do())
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dns (execute task : dnsmasq_configure_do())
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dns (execute task : dnsmasq_configure_do())
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dns ()
Notice opnsense /usr/local/etc/rc.newwanip: ROUTING: entering configure using 'wan'
Notice opnsense /usr/local/etc/rc.newwanip: IP renewal starting (new: xxx.xxx.xxx.xxx, old: xxx.xxx.xxx.xxx, interface: wan, device: igc2, force: yes)
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dhcp (execute task : dhcpd_dhcp_configure())
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dhcp ()
2024-06-19T03:13:58-04:00 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure ipsec (execute task : ipsec_configure_do(,wan))
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure ipsec (,wan)
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_GW))
Notice opnsense /usr/local/etc/rc.linkup: plugins_configure monitor (,WAN_GW)
Notice opnsense /usr/local/etc/rc.linkup: ROUTING: setting inet default route to www.www.www.www
Notice opnsense /usr/local/etc/rc.linkup: ROUTING: configuring inet default gateway on wan
Notice opnsense /usr/local/etc/rc.linkup: ROUTING: entering configure using 'wan'
Notice dhclient dhclient-script: Creating resolv.conf
Notice dhclient dhclient-script: New Routers (igc2): www.www.www.www
Notice dhclient dhclient-script: New Broadcast Address (igc2): zzz.zzz.zzz.zzz
Notice dhclient dhclient-script: New Subnet Mask (igc2): yyy.yyy.yyy.yyy
Notice dhclient dhclient-script: New IP Address (igc2): xxx.xxx.xxx.xxx
Notice dhclient dhclient-script: New Hostname (igc2): hhhhhhhhhh
Notice dhclient dhclient-script: Reason REBOOT on igc2 executing
Notice kernel <6>igc2: link state changed to UP
Notice dhclient dhclient-script: Reason PREINIT on igc2 executing
Notice opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for wan(igc2)
Notice kernel <6>igc2: link state changed to DOWN
Critical dhclient exiting.
Error dhclient connection closed
Notice opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for wan(igc2)
Error opnsense /usr/local/etc/rc.newwanip: The command '/usr/sbin/daemon -f -p '/var/run/updaterrd.pid' '/var/db/rrd/updaterrd.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 14295'
```
Of note is that I don't have any vpn nor dns services enabled at this moment, tho it seems configuring them is just a part of the process.
I don't seem to have leaky memory either, nor any other significant metric during the time of the crash. Any ideas?
Even an update to the latest version 24.1.9_3 did not change the problem. Does anyone have another idea?
For those having this issue, do you happen to have ntopng installed on your OPNsense box?
I was having a similar issue after updating to 24.1.8 where my WAN gateways would drop every hour and I would have to bounce the WAN interface if I caught it soon enough or have to reboot to recover internet access. I was getting the 'configd.py action rfc2136.reload.wan not found for user root' and similar rfc2136.reload errors in the system log files. I was also seeing dhcpd and dchpd6 services stopping and restarting.
Reverting back to 24.1.7 didn't fix anything so I did a clean reinstall of OPNsense (no backup restore) and noticed the issue went away. I slowly turned plugins back on and noticed my issues returned right after I installed ntopng. After deactivating the ntopng plugin the issues went away again.
I also commented on reddit and there was at least one other person who have seen a similar issue with ntopng.
https://www.reddit.com/r/opnsense/comments/1d39a61/comment/l6ca7we/
https://www.reddit.com/r/opnsense/comments/1ddm4sk/comment/l88mrbj/?context=3
I'm now on 24.1.9_3 without issue. I'm not sure what ntopng modifies in the system but it clearly was causing some conflict with my wan gateways and interface.
ntopng is not installed on my system. After a restart, the internet connection can be accessed for a short time, then only e.g. with pkg updates Network is unreachable.
I'm having the same issue with both the "community" and the "business" editions.
Having the same issue, do not have ntopng installed ... any other suggestions?
Quote from: joe26 on June 25, 2024, 12:34:59 AM
Having the same issue, do not have ntopng installed ... any other suggestions?
Imagine a thread with every possible reason for a machine rebooting.
Best to create your own thread with your own settings and we take it from there. It could be hardware problem but each hardware & settings combinations are different.
Quote from: cookiemonster on June 25, 2024, 12:46:08 AM
Quote from: joe26 on June 25, 2024, 12:34:59 AM
Having the same issue, do not have ntopng installed ... any other suggestions?
Imagine a thread with every possible reason for a machine rebooting.
Best to create your own thread with your own settings and we take it from there. It could be hardware problem but each hardware & settings combinations are different.
Thank you, created a new post here: https://forum.opnsense.org/index.php?topic=41237
Hello,
The same error and symptioms is repeating every few weeks since we upgrade to 24.7. Is it a recognized bug by the community? Is there any root cause identified?
Thank you.
getting 3 reboots today just noticed...... latest version..... :'( :'(