HaProxy fails to start after updating from v22 to v23.1

[tz-mbc]

I went through all the updates from v22 to 23.1 last night and at first glance things looked fine. However this morning we noticed that the haproxy service isn't running.
Unfortunately the log isn't at all telling. All it says is the below:
   2023-02-22T10:06:00   Error   configd.py   [eacd69f9-4ff4-433b-90ed-bd00cb64b4a7] returned exit status 1

The ID seems to be random as it changes with every start attempt.
After searching for similar cases here, I also tried to manually start the service from the cli, unfortunately I am not any wiser:

root@opn2:~ # service haproxy start
Starting haproxy.
/usr/local/etc/rc.d/haproxy: WARNING: failed to start haproxy

Is there any way to get more information on why it won't start?
I think I noticed there were some Python3 (?) warnings when the update ran, but the messages went by too quickly to read them. Are the upgrade logs still available somewhere by any chance?

Any help is highly appreciated
Thanks

[kurthw]

Here with me AdGuardHome, cron, ntpd also no longer start automatically since the upgrade 

Must always trigger these by hand. After that, the acme service also starts but again with a long delay.

OPNsense 23.1.1_2-amd64

----------------------

Could just solve my startup problems myself. The cause was the DynDNS (legacy) plugin. Deactivated all updates and restarted, everything is good again.

[Fright]

@tz-mbc

service haproxy start

should be "configctl haproxy start" imho