OPNsense Forum

English Forums => 25.1, 25.4 Production Series => Topic started by: vik on April 21, 2025, 12:57:06 AM

Title: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: vik on April 21, 2025, 12:57:06 AM
25.1.4_1 to 25.1.5_5 upgrade fails to properly reboot:

When reboot (tried multiple times)
1) Cannot login via SSH
2) Some services don't restart (Zenarmor, Intrusion Detection, ACME Client, ddclient, DNSCrypty-Proxy, Insight Aggregator)
3) Firmware status screen shows "The upgrade has finished and your device is being rebooted at the moment, please wait..."

Please help
 
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: newsense on April 21, 2025, 03:16:48 AM
Do a healthcheck and post the result here
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: vik on April 21, 2025, 04:29:47 AM
I cannot get to that ... cannot get pass "Your device is rebooting" when I navigate to "System" -> "Firmware"
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: newsense on April 21, 2025, 04:35:49 AM
If you can log in with the console press 12 to check for updates and answer h for healthcheck to the y/n prompt
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: vik on April 21, 2025, 04:49:46 AM
no ssh ... cannot get to the console
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: newsense on April 21, 2025, 05:09:22 AM
Didn't say ssh.

What machine are you running OPNsense on ?
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: vik on April 21, 2025, 05:47:54 AM
got it ... will need to hook up a monitor and keyboard ... thx
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: gillbot on April 21, 2025, 02:07:49 PM
Mine has hung like this before (see similar post https://forum.opnsense.org/index.php?topic=46261.0) and mine "recovers" after a hard reboot. (Pulling Power) That allows me access, but I have recently been keeping a screen and KB nearby as this has happened somewhat often lately.
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: vik on April 21, 2025, 04:41:39 PM
Thx gillbot ... hard reboot looks to have fixed it ... here is the health check:

***GOT REQUEST TO AUDIT HEALTH***
Currently running OPNsense 25.1.5_5 (amd64) at Mon Apr 21 07:34:54 PDT 2025
>>> Root file system: /dev/gpt/rootfs
>>> Check installed kernel version
Version 25.1.5 is correct.
>>> Check for missing or altered kernel files
No problems detected.
>>> Check installed base version
Version 25.1.5 is correct.
>>> Check for missing or altered base files
No problems detected.
>>> Check installed repositories
OPNsense (Priority: 11)
mimugmail (Priority: 5)
SunnyValley (Priority: 7)
>>> Check installed plugins
os-acme-client 4.9
os-adguardhome-maxit 1.15
os-cpu-microcode-intel 1.1
os-ddclient 1.27_1
os-dmidecode 1.2
os-dnscrypt-proxy 1.15_2
os-etpro-telemetry 1.7_5
os-hw-probe 1.0_1
os-intrusion-detection-content-snort-vrt 1.2
os-ipcheck-community 0.3
os-maltrail 1.10_1
os-sensei 1.18.6
os-sensei-updater 1.17
os-speedtest-community 0.9_6
os-sunnyvalley 1.4_3
os-theme-cicada 1.39_1
os-theme-dracula 0.7
os-theme-rebellion 1.9.2_1
os-theme-solarized-community 0.4_1
os-theme-tukan 1.29
os-theme-vicuna 1.49_1
os-tor 1.10
os-unboundcustom-maxit 1.0
>>> Check locked packages
No locks found.
>>> Check for missing package dependencies
Checking all packages: .......... done
>>> Check for missing or altered package files
Checking all packages: ....
os-adguardhome-maxit-1.15: checksum mismatch for /usr/local/AdGuardHome/AdGuardHome
os-adguardhome-maxit-1.15: checksum mismatch for /usr/local/AdGuardHome/AdGuardHome.sig
Checking all packages......... done
>>> Check for core packages consistency
Core package "opnsense" at 25.1.5_5 has 70 dependencies to check.
Checking packages: ....................................................................... done
***DONE***
Title: Re: 25.1.4_1 to 25.1.5_5 fails to properly reboot
Post by: newsense on April 21, 2025, 07:52:28 PM
Conflicting priorities/repos might cause issues in the future.

The AGH error can be ignored, that's expected.

Running ZA in parallel with AGH and Suricata however, might be the root cause of your issue.