Public bug reported:
This is similar to #689734 I believe.
When starting haproxy using a DNS name on the 'server' line haproxy
fails to start, giving the message:
```
May 05 19:09:40 hyrule systemd[1]: Starting HAProxy Load Balancer...
May 05 19:09:40 hyrule haproxy[1146]: [ALERT] 124/190940 (1146) : parsing
[/etc/haproxy/haproxy.cfg:157] : 'server scanmon' :
May 05 19:09:40 hyrule haproxy[1146]: [ALERT] 124/190940 (1146) : Failed to
initialize server(s) addr.
May 05 19:09:40 hyrule systemd[1]: haproxy.service: Control process exited,
code=exited status=1
May 05 19:09:40 hyrule systemd[1]: haproxy.service: Failed with result
'exit-code'.
May 05 19:09:40 hyrule systemd[1]: Failed to start HAProxy Load Balancer.
```
In this case the server statement was:
` server scanmon myservername.mydomain.org:8000`
Changing it to use the IP address corrected the problem.
I believe there is a missing dependency for DNS in the unit file.
--Info:
Description: Ubuntu 18.04 LTS
Release: 18.04
haproxy:
Installed: 1.8.8-1
Candidate: 1.8.8-1
Version table:
*** 1.8.8-1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771335
Title:
haproxy fails at startup when using server name instead of IP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1771335/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
