haproxy.service failed.

admin

Sep  3 23:59:38 controller1 systemd: Started HAProxy Load Balancer.
Sep  3 23:59:38 controller1 systemd: Starting HAProxy Load Balancer...
# r% Z4 T6 c6 \% E/ N' ?: ZSep  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]
( ^% W" V4 @" l$ U4 w- tSep  3 23:59:38 controller1 haproxy-systemd-wrapper: haproxy-systemd-wrapper: exit, haproxy RC=1
Sep  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.
Sep  3 23:59:38 controller1 systemd: haproxy.service failed.
6 s- n# x/ o  B: r# g2 |# C5 Y
这个问题呢，解决办法就是：
netstat -ntlp  
# P/ q  T7 I$ k: e查看端口是否启动正常了，尤其是haproxy中配置的端口号，如果看到0.0.0.0:100
, o0 ~% `# ^( k& i2 _在haproxy文件中配置有
4 @+ T' O  E* `3 Nx.x.x.x:100
- h  |7 b/ b, P% s+ p! k8 @; ?4 r
会导致haproxy的服务启动失败。
修改服务的启动端口方式，确定为当前主机IP地址   ip:100
与haproxy的不是同一个IP地址，就不会冲突，haproxy自然就能启动了。

admin

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