I tried yesterday 3 times with my Contabo VPS, via reboot command,  but I
was unable to reproduce it. Tthis VPS is where I got this socket permission
problem a few days ago after a restart because of a kernel update.
In case I manage to see this problem again, can you tell me what logs do
you need? it seems to be an erratic occurrence, but I would like to collect
some useful information If I find this problem again. Thank you.


On Tue, Dec 16, 2025 at 6:50 AM Jonas Jelten <[email protected]>
wrote:

> 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 subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2133460
>
> Title:
>   haproxy for noble may start before systemd-journald
>
> Status in haproxy package in Ubuntu:
>   Incomplete
> Status in haproxy source package in Noble:
>   Incomplete
>
> Bug description:
>   This applies to the HAProxy 2.8 package installed from the Noble 24.04
>   repos:
>
>   Distributor ID: Ubuntu
>   Description:    Ubuntu 24.04.3 LTS
>   Release:        24.04
>   Codename:       noble
>
>   HAProxy version 2.8.15-0ubuntu0.24.04.1 2025/10/08 -
>   https://haproxy.org/
>
>   When rebooting the OS, HAProxy may start before systemd-journald
>   because its service configuration does not have a dependency under the
>   [Unit] section on journald. This will cause a socket permission error
>   when writing the HTTP access log:
>
>   haproxy[44612]: [ALERT] (44612) : sendmsg()/writev() failed in logger
>   #1: Permission denied (errno=13)
>
>   As a workaround, a restart of journald and haproxy will solve the
>   problem, but if journald is the default logger service in Ubuntu
>   24.04, I think this could be avoided by adding the proper dependencies
>   under the Unit service configuration.
>
>   [Unit]
>   After=systemd-journald.service
>   Requires=systemd-journald.service
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/2133460/+subscriptions
>
>

-- 
API-Server++ - C++ low-code REST engine
https://github.com/cppservergit/apiserver-odbc
Martín Córdova y Asociados, C.A.
WhatsApp: +58-2686639
www.linkedin.com/in/martincordova

-- 
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

Reply via email to