Haproxy does not update properly on 25.1.1

[astrandb]

Update OPNsense from 25.1 => 25.1.1 fails when updating haproxy.
The update procedure tries to update haproxy from 3.0.7 to 3.0.8 but it fails with an error message in th elog window. The rest of the update is OK and the router reboots as expected. However, haproxy service does not start. When I click update again I am presented with an upgrade of haproxy 3.0.7=>3.0.8. Accepting that and the update succeeds but the service does not start. After starting manually everything seems to work.

I have tried this on two different installations with exactly the same behaviour.

[cookiemonster]

The update procedure tries to update haproxy from 3.0.7 to 3.0.8 but it fails with an error message in th elog window.

It would be useful to add what the error is.

[meyergru]

I have two installations and did not experience this. Worked just fine. I had times when haproxy was not started directly after a reboot in the past, though.

[franco]

Just a guess. You can run this:

# opnsense-update -Fs

And try again....

[astrandb]

I repeated on instance #3 and exatly the same happened again.

Just to clarify. The update completes, but there is an error message about haproxy. See the relevant part of the log below:

Code Select Expand

[42/42] Upgrading haproxy from 3.0.7 to 3.0.8...
[42/42] Extracting haproxy-3.0.8: ........ done
pkg-static: Fail to rename /usr/local/etc/rc.d/.pkgtemp.haproxy.qaAZHiGtVWae -> /usr/local/etc/rc.d/haproxy:No such file or directory
Starting web GUI...done.
When I retry the update only haproxy is upgraded but not restarted. Everything OK after manual start of the service.

Extract from log from second upgrade:

Code Select Expand

***GOT REQUEST TO UPDATE***
Currently running OPNsense 25.1.1 (amd64) at Wed Feb 12 18:04:18 CET 2025
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
haproxy: 3.0.7 -> 3.0.8

Number of packages to be upgraded: 1
[1/1] Upgrading haproxy from 3.0.7 to 3.0.8...
[1/1] Extracting haproxy-3.0.8: ........ done
haproxy-3.0.7: missing file /usr/local/share/licenses/haproxy-3.0.7/GPLv2
haproxy-3.0.7: missing file /usr/local/share/licenses/haproxy-3.0.7/LGPL21
haproxy-3.0.7: missing file /usr/local/share/licenses/haproxy-3.0.7/LICENSE
haproxy-3.0.7: missing file /usr/local/share/licenses/haproxy-3.0.7/catalog.mk
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done


[meyergru]

I also once had problems on upgrade with crowdsec, because it was really slow to shut down. This looks like something to that extent. Do you have "graceful stop" enabled for your HAproxy instances? I found that problematic, since sometime, HAproxy would not stop at all with that enabled. Maybe the update does not succeed when HAproxy is still running.

[JasonJoel]

When I retry the update only haproxy is upgraded but not restarted. Everything OK after manual start of the service.

Exact same on my 25.1.1 upgrade, and same fix - 2nd upgrade then manual service start.