Upgrade to 24.7.5 does not automatically reboot

[meyergru]

I just upgraded 3 machines from 24.7.4_1 to 24.7.5. All of them completed the upgrade, showed a popup that they now reboot, but did not. After 2 minutes, the popup clears and the dashboard shows with 24.7.5, but a reboot has not occurred as the uptime shown by "w" still was a few days.

[Vexz]

Others have reported this too. Could be something about the installed plugins. CrowdSec maybe?

[Patrick M. Hausen]

Same here. Rebooted manually, ran all available audits, looks good.

Yes, CrowdSec is installed - see full list:

[DEC670airp414user]

No plugins installed
Mine rebooted just fine

[franco]

It's likely crowdsec again.

https://www.reddit.com/r/opnsense/comments/1fpt7xn/comment/lp06tfk/


Cheers,
Franco

[Bob.Dig]

No plugins installed
Mine rebooted just fine

Here too.

[MoonbeamFrame]

I've done a couple of firewalls.

They did both reboot, but not before showing the dashboard with 24.7.5.

I watched the second one via it's iLO console an could see a delay between the dashboard refresh and it starting to stop services for the reboot.

[meyergru]

I have crowdsec on all my machines, too. But I can see that it upgrades and even updates geoip data during the upgrade and how can it keep the reboot from happening?

[MCMLIX]

Hello. So I just upgraded to 24.7.5 on a Proxmox VM with crowdsec and all went well. Reboot VM at end of upgrade. Its a little N5105 box.

[pyrodex]

My bare metal didn't reboot either after update and I have crowds installed.

I also saw a few segfaults from a few daemons on boot up:

Code: [Select]

pid 32801 (squid), jid 0, uid 100: exited on signal 11 (no core dump - bad address)
pid 28907 (ntpd), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
pid 29870 (ntpd), jid 0, uid 0: exited on signal 11 (no core dump - bad address)


[LOTRouter]

I upgraded 5 systems from 24.7.4_1 to 24.7.5.  The first three with Crowdsec installed.  All three with Crowdsec returned to the Lobby without rebooting.  On all three, I then initiated a reboot, two of which rebooted fine, the third hung up hard and had to be power cycled to recover it.

For the next two, I uninstalled the Crowdsec plugin, then initiated the upgrade.  On both of these systems, the upgrade went exactly as expected.  One of them did return to the Lobby briefly before rebooting, but both did reboot on their own withour issue.  I then re-installed the Crowdsec plugin withour issue.

This is certainly a Crowdsec issue.

I have five more system to upgrade, but I'll wait for a hotfix to test on them.

[RES217AIII]

bare metal: I only stopped crowdsec before the update. The update was as expected.
I did this on two other servers via VPN without any problems.

[flushell]

Same. No reboot with crowdsec installed. Had to reboot manually.

[flushell]

To add: Manually rebooting does only work the second time in 24.7.5
Crowdsec seems to be the issue here. Disabling it and rebooting works as normal.