Crash report begins. Anonymous machine information
-
Dears
I'm New here using Pfsense actually from 8 months ago.
from 1 month message appear and I afraid if it big issue so I rolled back 2 days and the message disappeared, so now it appeared again and i dunno what it means ...
the message:
Crash report begins. Anonymous machine information:
amd64
11.2-RELEASE-p4
FreeBSD 11.2-RELEASE-p4 #2 b00c407ba5d(RELENG_2_4_4): Mon Nov 26 11:41:48 EST 2018 root@buildbot2.nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSenseCrash report details:
PHP Errors:
[13-Oct-2019 12:33:40 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'intl.so' (tried: /usr/local/lib/php/20170718/intl.so (/usr/local/lib/php/20170718/intl.so: invalid file format), /usr/local/lib/php/20170718/intl.so.so (/usr/local/lib/php/20170718/intl.so.so: invalid file format)) in Unknown on line 0
[13-Oct-2019 12:33:51 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'intl.so' (tried: /usr/local/lib/php/20170718/intl.so (/usr/local/lib/php/20170718/intl.so: invalid file format), /usr/local/lib/php/20170718/intl.so.so (/usr/local/lib/php/20170718/intl.so.so: invalid file format)) in Unknown on line 0No FreeBSD crash data found.
Thank you
-
Library errors like that are usually the result of filesystem damage. If that system has not been upgraded recently I would first run a filesystem check on it:
https://docs.netgate.com/pfsense/en/latest/hardware/troubleshooting-disk-check-errors-fsck.htmlSteve
-
thank you stephenw10 for your fast response
I will try to move the machine to another disk, actually it works on Hyper-V environment.
is the virtualization can make this error appear OR this is pure Hard Disk issue
Thank you
-
It can be either. It's subjectively more common on physical installs but that could just be because VMs are less likely to reset without unmounting the filesystem.
Steve
-
Yea the power cut off 5 times a week and the batteries was empty :(
-
Ah, then that's almost certainly the cause!
In environments where it's not possible to guaranty the power you can set /var and /tmp as ram drives. That minimises drive writes and hence the chances of filesystem issues. That's a setting in Sys > Adv > Misc. It does require rebooting to set that.
Steve