Pfsense on Futro S900 random restart



  • Hello,

    I'm running a pfsense on Futro S450 and I would like replace with Futro S900;
    I have install the last version of pfsense on Futro S900 hardware using an addition PCIe Intel Pro 1000 NIC and restore the backup (just the config no packages) I have continuosly random restart, I have try with 2 different S900 machine with same result.

    Thinking was a PCIe problem (the only difference from S450) I have try to use the standard PCI bus as secondary NIC with the same result, anyone have use this kind of hardware ?

    Looking the logs I can't see any particular problem, just and error on NTP :

    02-01-2019 08:10:19 Auth.Info 10.1.0.252 Feb 1 07:08:49 login: login on ttyv0 as root
    02-01-2019 08:10:17 Daemon.Error 10.1.0.252 Feb 1 07:08:48 php-fpm[337]: /rc.start_packages: Restarting/Starting all packages.
    02-01-2019 08:10:17 Daemon.Error 10.1.0.252 Feb 1 07:08:48 php-fpm[338]: /rc.dyndns.update: phpDynDNS (xxxxxxx.ddns.net): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
    02-01-2019 08:10:16 Kernel.Info 10.1.0.252 Feb 1 07:08:47 syslogd: kernel boot file is /boot/kernel/kernel
    02-01-2019 08:10:16 Syslog.Error 10.1.0.252 Feb 1 07:08:46 syslogd: exiting on signal 15
    02-01-2019 08:10:15 Kernel.Critical 10.1.0.252 Feb 1 07:08:46 kernel: done.
    02-01-2019 08:10:15 User.Error 10.1.0.252 Feb 1 07:08:46 php-cgi: rc.bootup: Creating rrd update script
    02-01-2019 08:10:13 Daemon.Info 10.1.0.252 Feb 1 07:08:44 unbound: [16658:0] info: generate keytag query _ta-4f66. NULL IN
    02-01-2019 08:10:11 Kernel.Critical 10.1.0.252 Feb 1 07:08:42 kernel: .done.
    02-01-2019 08:10:11 User.Notice 10.1.0.252 Feb 1 07:08:41 check_reload_status: Updating all dyndns
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listening on routing socket on fd #35 for interface updates
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 14 ovpns3 10.111.113.1:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 13 ovpns3 [fe80::921b:eff:fe1a:821d%9]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 12 ovpns2 10.111.112.1:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 11 ovpns2 [fe80::921b:eff:fe1a:821d%8]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 10 ovpns1 10.111.111.1:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 9 ovpns1 [fe80::921b:eff:fe1a:821d%7]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 8 lo0 127.0.0.1:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 7 lo0 [fe80::1%4]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 6 lo0 [::1]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 5 re1 192.168.10.51:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 4 re1 [fe80::2e0:4cff:fe69:25d8%2]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 3 re0 10.1.0.252:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen normally on 2 re0 [fe80::921b:eff:fe1a:821d%1]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen and drop on 1 v4wildcard 0.0.0.0:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: Listen and drop on 0 v6wildcard [::]:123
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25352]: proto: precision = 0.977 usec (-20)
    02-01-2019 08:10:10 User.Error 10.1.0.252 Feb 1 07:08:41 php-cgi: rc.bootup: NTPD is starting up.
    02-01-2019 08:10:10 System2.Info 10.1.0.252 Feb 1 07:08:41 ntpd[25295]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
    02-01-2019 08:10:10 Kernel.Critical 10.1.0.252 Feb 1 07:08:41 kernel: done.
    02-01-2019 08:10:10 System2.Notice 10.1.0.252 Feb 1 07:08:41 ntpd[25295]: ntpd 4.2.8p12@1.3728-o Wed Oct 3 14:21:49 UTC 2018 (1): Starting
    02-01-2019 08:10:09 Kernel.Notice 10.1.0.252 Feb 1 07:08:39 kernel: re0: link state changed to UP
    02-01-2019 08:10:09 Kernel.Critical 10.1.0.252 Feb 1 07:08:39 kernel:


  • Netgate Administrator

    Does it reboot completely or halt and require intervention?

    Do you see a crash report after rebooting?

    Do you see anything on the console when it reboots? It looks like it has serial ports so I would set the serial console as default and log the output there if you can.

    Steve



  • Completely reboot
    No crash report, I have to connect serial port and check the output.
    thanks