haproxy.service failed.

admin

Sep  3 23:59:38 controller1 systemd: Started HAProxy Load Balancer.
& w& p* u, c# eSep  3 23:59:38 controller1 systemd: Starting HAProxy Load Balancer...
* H9 o( ?* H' e5 R5 `& K% f: i( LSep  3 23:59:38 controller1 haproxy-systemd-wrapper: [WARNING] 245/235938 (1862) : parsing [/etc/haproxy/haproxy.cfg:12] : 'option httplog' not usable with proxy 'mariadb_cluster' (needs 'mode http'). Falling back to 'option tcplog'.
Sep  3 23:59:38 controller1 haproxy-systemd-wrapper: [WARNING] 245/235938 (1862) : config : 'option forwardfor' ignored for proxy 'mariadb_cluster' as it requires HTTP mode.
Sep  3 23:59:38 controller1 haproxy-systemd-wrapper: [ALERT] 245/235938 (1862) : Starting proxy mariadb_cluster: cannot bind socket [192.168.90.70:3306]
/ Z- M+ {4 y+ ?3 M) n2 fSep  3 23:59:38 controller1 haproxy-systemd-wrapper: haproxy-systemd-wrapper: exit, haproxy RC=1
% b. k) {/ P" S8 y3 aSep  3 23:59:38 controller1 systemd: haproxy.service: main process exited, code=exited, status=1/FAILURE
Sep  3 23:59:38 controller1 systemd: Unit haproxy.service entered failed state.
- p2 e# I% b7 w+ r+ L" L3 xSep  3 23:59:38 controller1 systemd: haproxy.service failed.
% }$ d" u, k5 A6 H0 U; Q* a1 F, V6 [
( o* Q. X% V5 s2 {! K' d9 k+ b这个问题呢，解决办法就是：
netstat -ntlp  
; }, p- Y" N& {5 D查看端口是否启动正常了，尤其是haproxy中配置的端口号，如果看到0.0.0.0:100
在haproxy文件中配置有
x.x.x.x:100
8 `% `' `) T) }! o+ w
' \# q! c$ j& o/ F会导致haproxy的服务启动失败。
修改服务的启动端口方式，确定为当前主机IP地址   ip:100
7 _/ K1 t* e# i0 P) v! p与haproxy的不是同一个IP地址，就不会冲突，haproxy自然就能启动了。

admin

很多haproxy不能启动多是因为端口原因导致的