Crash nearly every day with 2.4.4
-
Hi all, I've been getting crashes almost daily for the last 2 versions. Haven't reported them since the button is gone. Below is the crash dump, I've only removed the binary (diamond with ? in it) from the output.
EDIT: ... can't seem to post it here as it's very quickly too large, I take it we're meant to upload these? Trying that next.0_1547634622331_crashdump.tar.gz
-
And another crash:
-
Is anyone looking at this? Am I posting it to the right place? I'm getting multiple crashes per day now and I don't know what I'm supposed to be looking for in these crash dumps.
-
I would remove your squid package first and see if that helps. You have had a crash running FSCK won't hurt, boot into single user mode; fun
fsck /a few times to fix any file corruption you have.I could only read the second Crash, first one was not able to be opened...
-
Getting into single user mode will be non-trivial. I only have a network connection and it's an embedded device so I would have to bring a laptop with a serial cable to my server room. Is there any way to get the device to boot and run cleanup itself?
-
single boot requires human interaction, if you can use an external device (say a raspi), to run as a console server you can do it over the network.
-
Ok, I brought the router upstairs and ran fsck /. Took about 3 times before all the errors went away so maybe that was indeed the issue. Will keep you posted.
-
Well, after running fsck I've got uptime almost 3 days with no issues so I think that was the fix. Thanks for your help.
-
The router lasted about 3 days, now it has crashed again:
-
2 crashes with different causes.... It's looking like hardware failure.
Would do a memtest; perhaps replace the hard drive. At some point and time you will need to make the call, what's worth more, your time or purchasing a new device.
Please let me know how this works out for you.
-
This device is pretty new. :( It's an embedded PC Machines, basically a NIC with a CPU on it and an SSD drive.
-
What you see is the result after the crash.
Put an UPS up front to exclude any power issues. Set up a clean shut down - add a mail notification if a power.Also : start mall when using new hardware. No packages, nothing fancy.
After some days / weeks, throlle up the load, and add a package, and retest.
Finally, install : Squid.If you have hardware issues, problems will popup as soon as you start using the device for some time.
If it concerns resource errors : when the load goes up : more errors.
A faulty setup : as soon as you activate the pack -
@jasonarlouser Make and model please? I am running several PC Engines APU boxes. For some versions it is required to upgrade the firmware (otherwise these will crash often).
-
PC Engines APU2
BIOS Vendor: corebootNot sure where to see more. Does that help? Running the disk clean up reduced reboots a lot. Now it's every couple of weeks instead of daily.
-
Try running
kenvat the command line or Diag > Command Prompt. If it reports the BIOS version at all it will show there.Steve
-
@jasonarlouser said in Crash nearly every day with 2.4.4:
PC Engines APU2
BIOS Vendor: corebootNot sure where to see more. Does that help? Running the disk clean up reduced reboots a lot. Now it's every couple of weeks instead of daily.
I am running quite a lot APU2/3/4 boxes. The APU4 (with 4 NICs) requires a BIOS upgrade for sure.
I recommend to check the current BIOS version. And you have to know which board you are using. Some identify an APU3 as an APU2...
-
Please find the BIOS update here: https://pcengines.github.io/
Tip: when you login to your pfSense webUI, the BIOS version should be displayed.
For further testing you could enable SSH and SSH into your firewall.
Next start a shell and install Flashrom: pkg install flashromOnce installed close the shell (by typing 'exit' and pressing <ENTER>). Next open the shell again.
Determine the board with this command: flashrom -p internal -V | grep DMINext download the matching ROM from pcengines.github.io. You could use curl. If curl isn't present, then install it "pkg install curl".
Next untar the file (tar xvfz apu?_v?.?.?.rom.tar.gz).
Next flash the BIOS: flashrom -w apu?_v?.?.?.rom -p internal:boardmismatch=force
Take note fo the detected mainboard. Mostly it doesn't match exactly - but that's a known issue. Just carry on when you are sure it is the correct ROM for your board.
After successfully flashing your BIOS you have to reboot (use the "reboot" command).
I am hoping this is helpful. Please only flash your board after a fresh reboot. You just don't want to brick your board. If you brick your board, you will need an unbricking tool (flash recovery board): https://www.pcengines.ch/spi1a.htm (I have one - but never had to use it).
-
kenv | grep smbios
