No, I did not remove it, this is a Contabo VPS ubuntu 24.04 factory setup
(as provided by Contabo):
systemctl status rsyslog
● rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled;
preset: enabled)
Active: active (running) since Sun 2025-11-30 12:02:18 -04; 24h ago
TriggeredBy: ● syslog.socket
Docs: man:rsyslogd(8)
man:rsyslog.conf(5)
https://www.rsyslog.com/doc/
Main PID: 850 (rsyslogd)
Tasks: 4 (limit: 14306)
Memory: 3.0M (peak: 5.1M)
CPU: 19.541s
CGroup: /system.slice/rsyslog.service
└─850 /usr/sbin/rsyslogd -n -iNONE
Nov 30 12:02:18 vmi2905065 systemd[1]: Starting rsyslog.service - System
Logging Service...
Nov 30 12:02:18 vmi2905065 systemd[1]: Started rsyslog.service - System
Logging Service.
Nov 30 12:02:18 vmi2905065 rsyslogd[850]: imuxsock: Acquired UNIX socket
'/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2312.0]
Nov 30 12:02:18 vmi2905065 rsyslogd[850]: rsyslogd's groupid changed to 102
Nov 30 12:02:18 vmi2905065 rsyslogd[850]: rsyslogd's userid changed to 102
Nov 30 12:02:18 vmi2905065 rsyslogd[850]: [origin software="rsyslogd"
swVersion="8.2312.0" x-pid="850" x-info="https://www.rsyslog.com";] start
Dec 01 00:00:01 vmi2905065 systemd[1]: rsyslog.service: Sent signal SIGHUP
to main process 850 (rsyslogd) on client request.
Dec 01 00:00:01 vmi2905065 rsyslogd[850]: [origin software="rsyslogd"
swVersion="8.2312.0" x-pid="850" x-info="https://www.rsyslog.com";] rsyslogd
was HUPed
On Mon, Dec 1, 2025 at 11:55 AM Andreas Hasenack <[email protected]>
wrote:
> > No, I did not modify the haproxy service configuration
>
> I meant if you removed the rsyslog package
>
> --
> 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
>
> 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
