Sorry for the late reply, I was on unplanned leave.
What I observed in my investigation, when I commented below line it's
working as expected. Means even after reboot the machine the haproxy
service get started automatically.
#stats socket /etc/haproxy/haproxysock level admin
I'm not sure what
I've not personally had any issues with systemd which I know doesn't mean
there isn't any... However, on closer inspection, it gets started through a
wrapper "haproxy-systemd-wrapper" for me :
[Unit]
Description=HAProxy Load Balancer
After=network.target
[Service]
Might be a systemd dependency issue, where the socket is not created before
the process is started.
Baptiste
On Mon, Jan 16, 2017 at 4:46 PM, Aaron West wrote:
> Hi Praveen,
>
> Am I right in assuming it's a socket for the stats page? Also what user is
> starting
Hi Praveen,
Am I right in assuming it's a socket for the stats page? Also what user is
starting HAproxy because maybe it doesn't have permissions to create the
socket?
We might need your whole config or at least the GLOBAL section...
Aaron West
Loadbalancer.org Limited
+44 (0)330 380 1064
There are some very knowledgeable people on this list so I'm sure someone
can help, however, what might the problem actually be?
Aaron West
Loadbalancer.org Limited
+44 (0)330 380 1064
www.loadbalancer.org
On 16 January 2017 at 15:32, Praveen Koppula
wrote:
>
Some content was missing. Adding again.
When we reboot our machine (Where haproxy installed) teh haproxy going to
be down and it's not starting after machine boot.
When we force to start haproxy service getting below error.
Error: Starting haproxy [ALERT] 047/083514 : Starting frontend GLOBAL:
Can you please help me on this.
Haproxy version is : 1.5.4-2.1
Thanks in advance
7 matches
Mail list logo