pf 2.5 Crash report details
-
Crash report begins. Anonymous machine information:
amd64
12.0-RELEASE-p10
FreeBSD 12.0-RELEASE-p10 90ecb6e4e66(RELENG_2_5) pfSenseCrash report details:
PHP Errors:
[14-Sep-2019 04:26:55 Asia/Shanghai] PHP Warning: file_get_contents(/tmp/ovpnc7_routerv6): failed to open stream: No such file or directory in /etc/inc/gwlb.inc on line 1513No FreeBSD crash data found.
-
pfSense-upgrade -4
Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg-static: https://beta.pfsense.org/packages/pfSense__amd64-core/meta.txz: Not Found
repository pfSense-core has no meta file, using default settings
pkg-static: https://beta.pfsense.org/packages/pfSense__amd64-core/packagesite.txz: Not Found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: https://beta.pfsense.org/packages/pfSense__amd64-pfSense_devel/meta.txz: Not Found
repository pfSense has no meta file, using default settings
pkg-static: https://beta.pfsense.org/packages/pfSense__amd64-pfSense_devel/packagesite.txz: Not Found
Unable to update repository pfSense
Error updating repositories! -
https://forum.netgate.com/topic/146707/temporary-problem/
-
when i start FRR 7.0 service, then pfsense all down.
other install log show
FRR's OSPF daemons tries to allocate big socket buffer, so generate warning
messages like:
"setsockopt_so_sendbuf: fd 6: SO_SNDBUF set to 1048576 (requested 8388608)"
To prevent such message kern.ipc.maxsockbuf can be increased:
sysctl kern.ipc.maxsockbuf=16777216Error message "ifam_read() doesn't read all socket data" is under investigation
Cleaning up cache... done.
Success -
/etc/inc/config.lib.inc line 383 this wrong
$config['version'] = sprintf('%.1f', $next / 10); -
That line is fine, and working on every other box around. It hasn't changed in over 10 years.
What is broken is your system (probably your config.xml), or something on the filesystem.
You have some other problem that isn't a bug, probably need to reinstall and start from scratch, or try different hardware.
-
i am always work 2019.09.22 before version, now i can't use frr, if start the frr service will system down.
i think the frr what's your have changed. i have been try reinstall system and restore old config, but if install and start frr will system down.
-
The systems I have with FRR on current snapshots are all working OK. Again, it's something specific to your setup or environment. You need to figure out what that is. Since it's not happening to anyone else, nobody else can tell you what is happening in your system.
-
report
-
I think should lastest new version for FRR. why not use frr7.1 ?
https://github.com/FRRouting/frr/issues/1899
FRR's OSPF daemons tries to allocate big socket buffer, so generate warning
messages like:
"setsockopt_so_sendbuf: fd 6: SO_SNDBUF set to 1048576 (requested 8388608)"
To prevent such message kern.ipc.maxsockbuf can be increased:
sysctl kern.ipc.maxsockbuf=16777216Error message "ifam_read() doesn't read all socket data" is under investigation
Cleaning up cache... done.
-
I found that the problem recurred,If I add two ipv6 BGP Neighbors, the Remote AS is the same ASN number. like 39751. Then the system will crash or it will automatically revert to a bgp neighbor configuration.
I have installed a new version of the pf system, but the frr installation package is the same. I am also a new configuration frr, so there is no problem with my configuration is incorrect. So I am sure there is a problem with the frr installation package.
i try this is pfSense-CE-memstick-2.5.0-DEVELOPMENT-amd64-20190922-1902.img and get crash report also.
-
remote Neighbors is via openvpn connect. still can't fix it.
-
i want to try change back to frr 0.6.3 config , how i do it?
-
msgbuf.txt06000027767013552366215 7664 ustarrootwheele: writing to routing socket: Network is unreachable
<118>route: route has not been found
<118>route: writing to routing socket: Network is unreachable -
when i try add two ipv6 address Neighbor Name/Addr happen wrong, but add ipv4 Neighbor address not happen wrong.
So i think the ipv6 has issuse.
-
<118>savecore 77 - - reboot after panic: ffs_valloc: dup alloc
<118>savecore 77 - - writing core to /var/crash/textdump.tar.1
<118>...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.30/mach/CORE
<118>32-bit compatibility ldconfig path:
<118>done.
<118>2019-11-07T15:27:20.567567+08:00 php-fpm 330 - - /ecl.php: No config.xml found, attempting last known config restore.
<118>2019-11-07T15:27:20.569295+08:00 php-fpm 330 - - /ecl.php: New alert found: No config.xml found, attempting last known config restore.
<118>2019-11-07T15:27:20.572194+08:00 php-fpm 330 - - /ecl.php: pfSense is restoring the configuration /conf/backup/config-0.xml
<118>2019-11-07T15:27:20.572399+08:00 php-fpm 330 - - /ecl.php: New alert found: pfSense is restoring the configuration /conf/backup/config-0.xml
<118>2019-11-07T15:27:20.574478+08:00 php-fpm 330 - - /ecl.php: XML error: no pfsense or pfsense object found!
<118>2019-11-07T15:27:20.574588+08:00 php-fpm 330 - -
<118>2019-11-07T15:27:20.575118+08:00 php-fpm 330 - - /ecl.php: pfSense is restoring the configuration /cf/conf/backup/config-0.xml
<118>2019-11-07T15:27:20.575318+08:00 php-fpm 330 - - /ecl.php: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-0.xml
mode = 0100666, inum = 8988751, fs = /
panic: ffs_valloc: dup alloc
cpuid = 1
time = 1573111640
KDB: enter: panic
panic.txt0600002513560743530 7143 ustarrootwheelffs_valloc: dup allocversion.txt0600007113560743530 7537 ustarrootwheelFreeBSD 12.0-RELEASE-p10 fe839027797(RELENG_2_5) pfSense -
That's a filesystem crash, you need to run fsck or reinstall. Possible that the other panics caused it (or made it worse).
