Bug #15638
closed
BE verification fails after logging in before the boot process finishes
Added by Marcos M 5 months ago.
Updated about 2 months ago.
Affected Plus Version:
24.11
Description
On the first boot of a BE snapshot (e.g. after an upgrade), logging in too quickly causes BE verification to fail. Looking at the boot log over serial, this seems to happen because pfSense-upgrade exits with an error code:
Configuring filter for dynamic IPsec VPN hosts... done
Starting CRON... done.
Another instance is already running... Aborting!
*** SYSTEM BOOT FAILURE ***
System will reboot in 60 seconds...
Failed Boot Environment: quick-20240722161228
Next Boot Environment: default
R/r: Enter a recovery shell
Any: Reboot immediately
Enter an option:
The reason pfSense-upgrade errors out is because logging into the dashboard triggers an update check (enabled by default), hence the Another instance is already running message.
Enabling verbose output with touch /verbose_rc shows the following:
Starting CRON... + cd /tmp
+ /usr/sbin/cron -s
+ echo done.
done.
+ errexit_on
+ zfs_on_root
+ /bin/kenv -q vfs.root.mountfrom
+ local '_mountfrom=zfs:pfSense/ROOT/quick-20240723104543'
+ [ zfs '=' zfs ]
+ set -e
+ /bin/rm -rf /usr/local/pkg/pf/CVS
+ /usr/local/bin/minicron 240 /var/run/ping_hosts.pid /usr/local/bin/ping_hosts.sh
+ /usr/local/bin/minicron 300 /var/run/ipsec_keepalive.pid /usr/local/bin/ipsec_keepalive.php
+ /usr/local/bin/minicron 3600 /var/run/expire_accounts.pid '/usr/local/sbin/fcgicli -f /etc/rc.expireaccounts'
+ /usr/local/bin/minicron 86400 /var/run/update_alias_url_data.pid '/usr/local/sbin/fcgicli -f /etc/rc.update_alias_url_data'
+ /bin/chmod a+rw /tmp/.
+ /sbin/gmirror status
+ GMIRROR_STATUS=''
+ [ '' '!=' '' ]
+ [ -z '' ]
+ /usr/local/sbin/pfSense-upgrade -y -U -b 3
Another instance is already running... Aborting!
+ _boot_failure
+ errexit_off
- Status changed from New to Feedback
- Assignee set to Marcos M
- % Done changed from 0 to 100
- Affected Plus Version set to 24.08
Fixed in commit:ac195834436a29d9dd54781cc4e50246caccdce9
- Subject changed from BE verification fails after logging in too quickly to BE verification fails after logging in before the boot process finishes
triggered it once on 24.03 -> 24.08.a.20240607, can't reproduce now when updating to latest dev
tested on:
24.08-DEVELOPMENT (amd64)
built on Thu Aug 1 8:00:00 CEST 2024
FreeBSD 15.0-CURRENT
- Affected Plus Version changed from 24.08 to 24.11
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by