Haproxy boot failure: Starting Proxy:cannot bind Socke

Haproxy prompt failed at startup:

[ALERT] 146/132210 (3443): Starting frontend redis:cannot bind socket [0.0.0.0:6379]

This problem, in fact, because your haproxy did not get VIP, and your profile is bound to the VIP address, so will prompt the above error.

Of course, you also want to make sure that your Haproxy server does hearbeat or keepalived, binds the VIP, or it cannot be highly available.

Workaround:

vi/etc/sysctl.conf        # Modify kernel parameter  = 1  # No, add this record  -P        # Save results to make the results effective

Description

Net.ipv4.ip_nonlocal_bind = 1 means that the presence of the VIP is allowed to be ignored when starting Haproxy

In addition to the above reasons, it is possible to cause starting proxy linuxyw.com:cannot bind socket

Determine if your Haproxy server has Web services such as Apache or Nginx turned on, and if so, please stop these services

Otherwise, the above failure occurs.

By the way, Haproxy Proxy Server also to open the core forwarding function, the following parameters:

Net.ipv4.ip_forward = 1

--Solemn statement: This article is only for the author's personal notes, please do not reprint! ——

Haproxy boot failure: Starting Proxy:cannot bind Socke