Crash report
-
@stephenw10 It is in production, so a bit scary to upgrade since it seems to work for most usage (except one LAN-network, but not sure if related). I have a 2nd machine with same config offline standing ready for years now, so in theory I can just fire it up and load the backup when I'm onsite, but...
In the log, there is weird stuff like the below - many hundred. It is correct it is not a host, it is an alias for hosts and ports that are valid. Maybe this causes overload? I haven't change the aliases for months, started appearing just now. It doesn't seem to cause any problems, but strange that it suggest that the alias names are host.
-
It shouldn't ever cause a crash but you should remove unresolvable entries from aliases and rules.
It can cause delays in updating the ruleset that can cause other issues if there are enough.Steve
-
@stephenw10 There was 6-7 aliases that was no longer in use. Meaning that I have earlier deleted one more more host behind the alias (from the GUI), but the alias it was part of had been left behind or had other valid entries. Now there is only one left in the logs and I can't find it..
-
I usually search the config file directly in that situation.
-
I have the same problem since i move to pfsense 2.5. actually i use pfsense 2.6 and i have one crash by day.
i have in report : fault code = supervisor read instruction, page not present
what are differences in configuration files between pfsense 2.4 and 2.5 ?
best regards
-
Depends which specific version but there are a lot:
https://docs.netgate.com/pfsense/en/latest/releases/versions.htmlIt shouldn't matter though, you can import an older config into the current pfSense version.
Steve
-
Changing hardware didn't help, not removing aliases or IPSec tunnels either.
What finally solved it for me after a year of trouble, was removing the LAN LAG against two switches. Had redundancy in case of one switch failed. All the switches shown the correct properties against the other end (short/long etc), so had no reason to suspect any issues. It all started after a pfSense upgrade.
I assume it must have been some kind of network confusion that caused the crash to happen every month. After this change, no problems has appeared.
-
Hmm, that's weird. You never saw any errors relating the the LAGG?
It was LACP I assume. Was the LAN just directly assigned to it? Or VLANs over it?
Steve
-
@stephenw10 LACP, correct. No VLANS at all, LAN directly assigned to it.
Maybe stupid, but only reason why I started suspecting it, was this message on one of the servers on the network (from the dump/crash-log):
<6>arp: moved from ac:1f:6b:6f:f2:8a to ac:1f:6b:6f:f2:8b on lagg0
I was suspecting that something wasn't working correctly, as there was no reason for a always-on file server to switch port. Maybe it is routine, who knows.. And not a single crash after.
-
Hmm, that's the server's MAC address(es)?
That looks like a log message on pfSense showing that the server moved to a different MAC. I assume you omitted the IP address there.
That wouldn't normally be an issue. It might happen if the server itself was connected with a lagg to the switch stack for example.
-
@stephenw10 Yes, the servers mac-address. The server (all servers, not only this) was connected through LAGG-setup against switch in the same way. Didn't really think it should be a big problem, just tiny bit weird that only one had the "problem" (qnap server).
-
Yeah, it shouldn't be a problem. The servers IP can change MAC and it's usually only an inconvenience in the logging. It's sufficiently common that you can disable those log messages if you know the cause:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/logs-arp-moved.htmlSo I'd say those log messages are unrelated to whatever was causing that crash.
Steve
-
I never had a crash with version 2.4.4. Crash appears with 2.4.5
-
2.4.5? Any reason you're not running 2.52 or 2.6?
What crash are you actually seeing?
supervisor read instruction, page not present could be any number of things.Steve
