OPNsense Forum

English Forums => 24.7, 24.10 Legacy Series => Topic started by: iorx on January 26, 2025, 10:01:49 PM

Title: Low prio on this. dhclient send_packet: Cannot allocate memory
Post by: iorx on January 26, 2025, 10:01:49 PM
Hi Ladies & Germs!

This is low priority and only if anyone has the time to help me out.

I have a summer house, and while it's not a big deal when it loses internet connection, it's quite inconvenient this time of year. Without the connection, I can't adjust the heat pump remotely before we arrive. It's a minor issue, but my wife and kids would be much happier if the house wasn't 10°C when we get there 😉.

We lost connection on January 20th, and visited a very cold house this weekend. The system has been unreachable since then.

2025-01-20T15:15:40 Error dhclient send_packet: Cannot allocate memory
2025-01-20T15:15:29 Error dhclient send_packet: Cannot allocate memory
2025-01-20T15:15:25 Error dhclient send_packet: Cannot allocate memory
2025-01-20T15:15:23 Error dhclient send_packet: No route to host
2025-01-20T15:15:21 Error dhclient send_packet: No route to host
2025-01-16T09:15:26 Warning opnsense /usr/local/etc/rc.newwanip: Interface '' (ovpns1) is disabled or empty, nothing to do.
2025-01-16T09:15:24 Error ntopng 16/Jan/2025 09:15:24 [NetworkInterface.cpp:144] ERROR: Failure initializing Network Discovery
2025-01-16T09:15:23 Warning ntopng 16/Jan/2025 09:15:23 [Ntop.cpp:4072] WARNING: Unable to find timezone: using UTC
2025-01-16T04:35:32 Warning opnsense /usr/local/etc/rc.newwanip: Interface '' (ovpns1) is disabled or empty, nothing to do.
2025-01-16T04:35:29 Error ntopng 16/Jan/2025 04:35:29 [NetworkInterface.cpp:144] ERROR: Failure initializing Network Discovery
2025-01-16T04:35:29 Warning ntopng 16/Jan/2025 04:35:29 [Ntop.cpp:4052] WARNING: Unable to find timezone: using UTC
  DELETE FROM `flow_alerts` WHERE tstamp < 1704855720
2025-01-09T04:02:00 Error ntopng 09/Jan/2025 04:02:00 [SQLiteAlertStore.cpp:162] ERROR: SQL Error: database disk image is malformed

The priority was to get the internet up and running, so I didn't troubleshoot much upon arrival. However, I noticed one peculiar thing: I had to hard reboot OPNsense as it was unresponsive both through the console and over the network.

I'm running it virtually on Hyper-V with 4GB RAM and 4 CPUs. I had to kill the VM and restart it to get things going again. The services normally active are: ntopng - redis, AdGuard Home, netflow, opn-arp, net-snmp, LLDP daemon, and WireGuard. I turned off ntopng - redis, opn-arp, and LLDP to reduce memory usage, suspecting ntopng might be the culprit.

So, Am I totally off the rails here trying to run above "normal" on 4GB of RAM?
And can make a alert for when memory is about to run out?
Can I find out, now afterwards, what caused it into this grinding halt?

Best, iorx.