[SOLVED] pfSense 2.7.2 not responding - restarted from power to revive
-
Hello everyone,
my pfSense was not responding, all the services were down. no vpn, no LAN response.
i had to reboot with power cycle.
The only strange thing in logs was this ISC DHCP (Deprecated) watchdog restarting the service, but in settings i have selected Kea DHCP many months ago. I don't know if this has to do with the freezing of the device.
After power cycle all is ok. what might be the problem ?? what else i should check ?
any comments appreciated !!Mar 27 10:48:55 kernel FreeBSD 14.0-CURRENT amd64 1400094 #1 RELENG_2_7_2-n255948-8d2b56da39c: Wed Dec 6 20:45:47 UTC 2023
Mar 27 10:48:55 kernel FreeBSD is a registered trademark of The FreeBSD Foundation.
Mar 27 10:48:55 kernel The Regents of the University of California. All rights reserved.
Mar 27 10:48:55 kernel Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Mar 27 10:48:55 kernel Copyright (c) 1992-2023 The FreeBSD Project.
Mar 27 10:48:55 kernel ---<<BOOT>>---
Mar 27 10:48:55 syslogd kernel boot file is /boot/kernel/kernel
Mar 27 09:33:00 php-cgi 77699 servicewatchdog_cron.php: Service Watchdog detected service dhcpd stopped. Restarting dhcpd (ISC DHCP Server)
Mar 27 09:32:23 php-fpm 35093 /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed IP addresses. Reloading endpoints that may use plant79.
Mar 27 09:32:23 php-fpm 35093 /rc.openvpn: The command '/sbin/route -n6 get 'default' 2>/dev/null | /usr/bin/egrep 'flags: <.PROTO.>'' returned exit code '1', the output was ''
Mar 27 09:32:21 check_reload_status 439 Reloading filter
Mar 27 09:32:21 check_reload_status 439 Restarting OpenVPN tunnels/interfaces
Mar 27 09:32:21 check_reload_status 439 Restarting IPsec tunnels -
Anything shown at the console when that happened? Was it responsive in any way?
Any reason you have the service watchdog enabled for dhcpd?
If a device stops responding entirely with no crash report and no errors logged I'd usually suspect hardware.
-
@stephenw10 thank you for your suggestion.
no response , tried all possible ways. vpn, LAN interface, screen.i'm adding the services in watchdog as a habit, because on pfsense 2.4.5 and 2.5.0 i had site to site open vpn connections that were not restoring the tunnel when a disconnection happened in between the two pfSense. So i always add all my services to watchdog.
but why is restarting the ISC dhcp when Kea is selected, i still didn't figure out.
i will check the hardware though, or maybe the power supply. -
The service watchdog is really only there for troubleshooting. It should not be used if you're not seeing a problem with services. It can definitely cause problems for some services, especially if it's applied to several services where timing can become critical.
Perhaps you enabled the watchdog on ISC before switching to Kea?
-
@stephenw10 something like that can be true, since ISC was active, with watchdog enabled and then i switched to Kea when i got the notification without removing the old ISC watchdog entry.
Can this be a reason for this total freeze ?
-
No. Even if it triggered some incorrect process that shouldn't affect the console. It should always respond there.
Privacy Policy · Cookie Policy