Hmm, this is unfortunate - in order to develop a fix we need to have some way
of understanding the error reproduction.
to improve the setup in the future, I've opened bug #2136303.
Btw your copilot explanation from comment #9 unfortunately misses the
fact that haproxy is chrooted and is only able to access rsyslog's
socket in there.
In any case, thank you for reporting this bug! I'll set it to incomplete
now, and we can continue investigating until we have a clear picture to
fix this on Ubuntu noble.
** Also affects: haproxy (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: haproxy (Ubuntu Noble)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2133460
Title:
haproxy for noble may start before systemd-journald
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/2133460/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
