pfSense Plus will automatically reboot in -1 seconds. ??

skogs

So upgrade went in ok. Took long enough that I went and fished out a monitor, but it did fire up before I got the monitor hooked up all the way.

Upon first boot it confirms 24.03, and has a lovenote at the top about how it will automatcially reboot in -1 seconds. Click verify button to confirm temporary boot environment as permanent.

I clicked the verify button. Then the box went away, but no reboot happened.

Gave it another reboot about 15 minutes later, and the box popped up again.
Boot environment reports default is 24.03 correctly.

On at least the first try, the 'verify' environment button didn't seem to do anything. It certainly didn't reboot on its own. Just a little confused by the messaging.

SwissSteph

In my case, the "-1" message was displayed for 2-3 seconds and then simply disappeared (without doing anything).

On the other hand, "unbound" hadn't started and it was impossible to launch it manually.

After a moment of total panic ... I had the idea of restarting my Netgate and on this second start-up, "unbound" started up (automatically) ... phew!

pfsjap

Need to reboot manually after update was reported on BETA and RC, wished it would have been corrected up to now, but no:

Apr 24 12:01:18	php-fpm	683	/status_services.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1713949278] unbound[12091:0] error: Error for server-cert-file: /var/unbound/unbound_server.pem [1713949278] unbound[12091:0] error: Error in SSL_CTX use_certificate_chain_file crypto error:80000002:system library::No such file or directory [1713949278] unbound[12091:0] error: and additionally crypto error:10080002:BIO routines::system lib [1713949278] unbound[12091:0] error: and additionally crypto error:0A080002:SSL routines::system lib [1713949278] unbound[12091:0] fatal error: could not set up remote-control'

jimp

The "-1" seconds thing is harmless (just cosmetic). You logged into the GUI quite fast during boot before the automatic boot verification finished. Usually that dialog is suppressed in that case but we've seen a couple instances where it still shows up.

dem

I just got this message after my system had been up for a couple of days. I think I figured out what happened:

Before logging in to the Web UI I was logged in via SSH and poking around to try and figure out how automatic boot verification worked. This lead me to run the command more /etc/rc.bootonce_verify.

While this command was still running I logged in to the Web UI and the "-1 seconds" message appeared. Quitting the more command caused the message to go away.

So the pkill command in rc.bootonce_verify was matching on the argument to more.

This is repeatable, though pretty harmless.

stephenw10

Huh so it matched the more process and thought it was already running?

dem

@stephenw10 Yes, it apparently matched the argument to more.

The fix might be something like:

--- rc.bootonce_verify.orig     2024-05-31 14:44:31.630017000 -0400
+++ rc.bootonce_verify  2024-05-31 14:45:18.778140000 -0400
@@ -115,7 +115,7 @@
 #
 is_running()
 {
-       pkill_quiet -0 -f "${ME}"
+       pkill_quiet -0 -f "^${ME}"
 }

But I haven't tested this.

stephenw10

Opened a bug to track it: https://redmine.pfsense.org/issues/15533

Feel free to add comments.