Huh? “Another instance of pfSense-upgrade is running”

[DominikHoffmann]

I am managing several Netgate 1100 boxes and am updating them to pfSense+ 24.11. I have seen this on the three of those on which I have attempted the update:

The System update page says, “Another instance of pfSense-upgrade is running.” I don’t see that there is. A reboot and installing the update right afterwards works, however.

[Bob.Dig]

@DominikHoffmann Have seen this too with beta and RC. Upgrading those to Release where without that problem though.

[DominikHoffmann]

I have yet to encounter a system, where I did not have that problem. Just now, however, I found that a simple page reload also fixed it.

[michmoor]

Yep already happened on two of my systems.
Just wait a few minutes and try it again. Clears itself up.

[DominikHoffmann]

I am not too concerned. Just wanted to give the developers a datapoint for future consideration.

[dennypage]

@DominikHoffmann FWIW, I encountered this as well.

[marcg]

Saw the same thing when attempting to update from 24.03 on third-party hardware via the GUI.

Connected to the console, confirmed that no other pfsense-upgrade instances were running, then upgraded via the console (Option 13). That upgrade went smoothly with no complaints about other pfsense-upgrade instances.

[stephenw10]

Yes, you're more likely to see that on an 1100 because the relatively low powered CPU takes longer to complete the check that was previously running. But refreshing the page there should show the update once it is able to run as you found.

[pepino]

I'm getting this on a Netgate 2100 as well.

On another 2100 I get:

"A temporary boot environment is enabled for the next system reboot.
Netgate pfSense Plus will boot into default during the next system reboot."

This error is persistent across several reboots.

Seems the 24.11 is very buggy - I have over 60 Netgate pfSense boxes so I think I will wait with the upgrades.

[stephenw10]

The temporary boot environment is part of the upgrade process in ZFS. It should be removed after booting into the new BE successfully. If the upgrade process was interrupted somehow it can remain tagged.

You can always roll back and run the upgrade again.

[tgl]

@DominikHoffmann I too saw this, on a 4200 during update from 24.03 to 24.11. Presumably it's the fault of 24.03 not 24.11. Navigating away from the Update page and back fixed it.