Tags: unredacted/unifi-on-boot
Tags
fix: wait for network connectivity before starting on_boot.d scripts After firmware upgrade, network-online.target may be reached before actual internet connectivity is available. install.sh now pings 1.1.1.1 and 8.8.8.8 for up to 60 seconds before starting the main service. Only affects firmware-upgrade restores, not normal boots. Bumped to v1.0.8.
fix: start main service after restore for single-boot recovery install.sh now explicitly starts unifi-on-boot.service after dpkg -i so on_boot.d scripts run on the same boot as the restore, not requiring a second reboot. Removed Before=network-online.target from the install service to prevent a deadlock (main service needs After=network-online.target). Bumped to v1.0.7.
fix: rm old symlink before cp to prevent cp from following it cp follows destination symlinks by default, so when an old symlink to /data/ existed at /etc/systemd/system/unifi-on-boot-install.service, the cp wrote the file back to /data/ instead of creating a regular file on the overlay. Fix: rm -f first, then cp. Bumped to v1.0.6.
fix: copy service file to overlay instead of symlinking to /data/ Root cause: /data/ is on an SSD that isn't mounted when systemd scans for units at boot. Symlinks to /data/ result in 'No such file' and the self-restore service never starts. Fix: copy the install service file directly into /etc/systemd/system/ (overlay upper dir, always available at boot). Also added RequiresMountsFor=/data to the service file so ExecStart waits for the SSD to be mounted. Bumped to v1.0.5.
fix(ansible): detect and recover from stale dpkg state after firmware… … upgrades After firmware upgrades, dpkg's database (on persistent storage) still reports the package as installed, but the actual files are gone because the root filesystem was rebuilt. The role now checks if the service file exists and purges the stale dpkg record before reinstalling.
PreviousNext