Pfsense stops. Please help.

[emammadov]

Thanks. Did you have a look at logs? Did you see any strange things there? I don't know much more about logs.

For example:
1.
Oct 29 19:38:05 php-cgi rc.bootup: The command '/usr/sbin/arp -s '192.168.4.245' '00:50:56:8a:94:a4'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'
Oct 29 19:38:04 php-cgi rc.bootup: The command '/usr/sbin/arp -s '192.168.4.244' 'f0:76:1c:37:62:35'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'

---

Oct 29 19:38:04 kernel ppc0: cannot reserve I/O port range
Oct 29 19:38:04 kernel atkbd0: [GIANT-LOCKED]

---

Oct 29 19:38:05 sshd 93222 Server listening on 0.0.0.0 port 33426.
Oct 29 19:38:05 sshd 93222 Server listening on :: port 33426.

---

Oct 29 19:38:04 kernel pci0: <base peripheral, interrupt controller> at device 20.2 (no driver attached)
Oct 29 19:38:04 kernel pci0: <base peripheral, interrupt controller> at device 20.1 (no driver attached)
Oct 29 19:38:04 kernel pci0: <base peripheral, interrupt controller> at device 20.0 (no driver attached)

---

Oct 29 19:38:04 kernel uhub3: 2 ports with 2 removable, self powered
Oct 29 19:38:04 kernel uhub1: 2 ports with 2 removable, self powered

[stephenw10]

Only that first log is a real error. It could be a number of things but potentially it could be bad RAM.

You need to check the server logs if you can reach them.

Steve

[viragomann]

The flashing LED is the system health indicator.
Blinking red means: Critical system failure detected (processor, memory, regulator, thermal event, fan, NMI)

In iLO you may find detailed information to the failure.

[emammadov]

@stephenw10 This error can be because of bad RAM?

Oct 29 19:38:05 php-cgi rc.bootup: The command '/usr/sbin/arp -s '192.168.4.245' '00:50:56:8a:94:a4'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'

This server is old and I don't know how to setup its management port and see server logs.

[viragomann]

You will also find system failure events in the BIOS.

[emammadov]

I will have a look at that events at work tomorrow. Could you please let me know the meanings of logs with numbers above?

[stephenw10]

pfSense tried to create an ARP entry for that IP/MAC and failed because it couldn't write to the routing socket due to a memory allocations failure. Hard to say more than that. I imagine those are fixed DHCP leases you have set static ARP on.

Really I wouldn't even look at that until your hardware issue is addressed. Which resolve it anyway.

Steve

[emammadov]

This memory allocations failure is due to hardware problem, right? After fixing that, these error will not occur again? Until today, I have never seen these errors before.

[stephenw10]

Then they are probably related.

Steve

[emammadov]

I changed all rams with new ones, but still get this errors in system logs.

Oct 31 09:06:05 php-fpm 336 /rc.linkup: The command '/usr/sbin/arp -s '192.168.2.240' '00:1a:81:00:1a:f4'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'
Oct 31 09:06:05 php-fpm 336 /rc.linkup: The command '/usr/sbin/arp -s '192.168.2.235' '00:0c:29:a8:72:2b'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'
Oct 31 09:06:05 php-fpm 336 /rc.linkup: The command '/usr/sbin/arp -s '192.168.2.234' '00:0c:29:23:82:78'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'
Oct 31 09:06:05 php-fpm 336 /rc.linkup: The command '/usr/sbin/arp -s '192.168.2.230' '00:0c:29:d0:17:c5'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'

[stephenw10]

Is that a static DHCP lease defined on the firewall? If not what is that device, where is it defined?

Did you see those errors logged prior to the hardware event?

Steve

[emammadov]

Clients are getting ip address via dhcp with static mappings. I began to see these errors after restarting pfsense. Actually I have noticed pfsense after restart in the past and haven't see these error logs.

[Gertjan]

@emammadov said in Pfsense stops. Please help.:

Cannot allocate memory'

Time for a trip to the console. Here are several useful commands.

[emammadov]

It has been 2 days that pfsense doesn't stop. But I want to understand why I see these errors in system logs.

[stephenw10]

So you're seeing that for all the static ARP entries then?

Do you actually see them in the ARP table?

Steve

[emammadov]

Yes, I see all the static arp entries and they are also located in the arp table. I changed all RAMs with new ones. Network cards are new.

I am attaching logs in .txt file.
0_1541015861024_logs.txt

[stephenw10]

Hmm, odd. Do you need those to be static ARP entries?

Did you find any logging in the bios or iLO indicating what the hardware issue was?

Steve

[almost__retarded]

@stephenw10 said in Pfsense stops. Please help.:

Hmm, odd. Do you need those to be static ARP entries?

Did you find any logging in the bios or iLO indicating what the hardware issue was?

Steve

Bumping this as I am experiencing the same issue as discussed although my pfsense box seems to be operating normally.

Here is a copy of my syslog.

I have created a thread on the pfSense subreddit as well. That thread is located here.

[stephenw10]

Usually that means it can't add entries for those IPs as it doesn't have an interface in that subnet. What interfaces/IPs do you have?

What are those IPs though? They all have the same, obviously spoofed, MAC.

Steve

[almost__retarded]

@stephenw10 should have mentioned that the logs were scrubbed. The MAC addresses are all unique and valid.

I have a two port chelsio t520 with both ports bonded in a LAGG interface. I am using that LAGG as the parent for all of the VLANs. The IP addresses are static DHCP/ARP reservations created for each of the subsequent virtual interfaces.