automatic reboot right after boot finished?
-
pfSense seems to reboot automatically (using rc.initial.reboot script) shortly after it finishes booting up. Per my Github search, this script is only used by the Reboot system console menu option. Anyone has any idea what is going on? There was nobody at the console at the time so nobody pressed the menu option manually. Thanks.
Aug 4 22:53:25 root 23873 Bootup complete Aug 4 22:53:26 php 21921 [pfBlockerNG] filterlog daemon started Aug 4 22:53:26 php 23323 [pfBlockerNG] DNSBL parser daemon started Aug 4 22:53:27 login 28471 login on ttyv0 as root Aug 4 22:53:27 sshguard 31051 Now monitoring attacks. Aug 4 22:55:08 php 32198 rc.initial.reboot: Stopping all packages. Aug 4 22:55:08 upsmon 17901 Signal 15: exiting Aug 4 22:55:08 lighttpd_pfb 40586 [pfBlockerNG] DNSBL Webserver stopped Aug 4 22:55:09 tail_pfb 42573 [pfBlockerNG] Firewall Filter Service stopped Aug 4 22:55:09 php_pfb 42640 [pfBlockerNG] filterlog daemon stopped Aug 4 22:55:11 reboot 47706 rebooted by root Aug 4 22:55:11 syslogd exiting on signal 15 Aug 4 22:56:01 syslogd kernel boot file is /boot/kernel/kernel Aug 4 22:56:01 kernel pflog0: promiscuous mode disabled Aug 4 22:56:01 kernel Waiting (max 60 seconds) for system process `vnlru' to stop... done Aug 4 22:56:01 kernel Waiting (max 60 seconds) for system process `syncer' to stop... Aug 4 22:56:01 kernel Syncing disks, vnodes remaining... 2 1 0 0 done Aug 4 22:56:01 kernel Waiting (max 60 seconds) for system thread `bufdaemon' to stop... done Aug 4 22:56:01 kernel Waiting (max 60 seconds) for system thread `bufspacedaemon-0' to stop... done Aug 4 22:56:01 kernel Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done Aug 4 22:56:01 kernel All buffers synced. Aug 4 22:56:01 kernel Uptime: 3m34s Aug 4 22:56:01 kernel ---<<BOOT>>--- Aug 4 22:56:01 kernel Copyright (c) 1992-2021 The FreeBSD Project. Aug 4 22:56:01 kernel Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 4 22:56:01 kernel The Regents of the University of California. All rights reserved. -
It could also be triggered from the gui. Was there anyone logged in anywhere?
-
@stephenw10 Nothing manual was involved. I am thinking something (package?) may be waiting for something to come up after boot and if it doesn't, it reboots automatically using this script.
-
Of the things I can see there upsmon looks most likely. So NUT or apcupsd.
That also seems to tie in with your other thread.
-
@stephenw10 right, so not sure if nut would do such a thing, something like if it can't communicate with UPS after booting up, it would trigger a reboot?
-
I would not expect it to. Disabling NUT as a test is pretty easy though.
