Hi Stour, thank you very much for helping improve Ubuntu with this bug
report!
I tried placing your modified /etc/haproxy/haproxy.cfg config file in a
Noble container, but do not really understand how to observe the issue.
FWIW the haproxy package in Ubuntu is built using "USE_SYSTEMD=1" by
default, enabling the systemd-notify mechanism.
Can you please update your bug description to be a bit more specific?
- How/where do you set that WATCHDOG_USEC environment variable?
- What would be the expected behavior (i.e. where to observer the periodic
WATCHDOG=1 notifications)?
- What is the actual/broken behavior (i.e. which logs can be observed to see
the issue)?
Also, do you know if the issue is still happening on newer versions of
Ubuntu/HAproxy, like 3.0.8/3.0.10 in Plucky/Questing/Resolute? – Once we
have a detailed step-by-step reproducer, we should be able to verify
that inside corresponding containers easily.
FTR "systemctl cat haproxy" (on Noble) prints:
# /usr/lib/systemd/system/haproxy.service
[Unit]
Description=HAProxy Load Balancer
Documentation=man:haproxy(1)
Documentation=file:/usr/share/doc/haproxy/configuration.txt.gz
After=network-online.target rsyslog.service
Wants=network-online.target
[Service]
EnvironmentFile=-/etc/default/haproxy
EnvironmentFile=-/etc/sysconfig/haproxy
BindReadOnlyPaths=/dev/log:/var/lib/haproxy/dev/log
Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid"
"EXTRAOPTS=-S /run/haproxy-master.sock"
ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -p $PIDFILE $EXTRAOPTS
ExecReload=/usr/sbin/haproxy -Ws -f $CONFIG -c -q $EXTRAOPTS
ExecReload=/bin/kill -USR2 $MAINPID
KillMode=mixed
Restart=always
SuccessExitStatus=143
Type=notify
# The following lines leverage SystemD's sandboxing options to provide
# defense in depth protection at the expense of restricting some flexibility
# in your setup (e.g. placement of your configuration files) or possibly
# reduced performance. See systemd.service(5) and systemd.exec(5) for further
# information.
# NoNewPrivileges=true
# ProtectHome=true
# If you want to use 'ProtectSystem=strict' you should whitelist the PIDFILE,
# any state files and any other files written using 'ReadWritePaths' or
# 'RuntimeDirectory'.
# ProtectSystem=true
# ProtectKernelTunables=true
# ProtectKernelModules=true
# ProtectControlGroups=true
# If your SystemD version supports them, you can add: @reboot, @swap, @sync
# SystemCallFilter=~@cpu-emulation @keyring @module @obsolete @raw-io
[Install]
WantedBy=multi-user.target
** Changed in: haproxy (Ubuntu)
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/2131789
Title:
Doesn't send periodic WATCHDOG=1 notifications when using systemd-
notify (compiled with USE_SYSTEMD=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/2131789/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
