|
|
Sep 3 23:59:38 controller1 systemd: Started HAProxy Load Balancer.% Y8 ?; M h( {7 l" t: \4 Q) u
Sep 3 23:59:38 controller1 systemd: Starting HAProxy Load Balancer...( ~8 e) c( z8 W. q- w8 \: f& t1 V5 S
Sep 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'.
& f/ O9 \2 E' \3 L5 mSep 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.; N+ @; ]3 \. |2 c$ k- y8 f" G
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], j3 s3 } f" U5 Z
Sep 3 23:59:38 controller1 haproxy-systemd-wrapper: haproxy-systemd-wrapper: exit, haproxy RC=1
' |# S/ a% _; bSep 3 23:59:38 controller1 systemd: haproxy.service: main process exited, code=exited, status=1/FAILURE
2 n6 E+ ?; d/ q& xSep 3 23:59:38 controller1 systemd: Unit haproxy.service entered failed state.
6 Q1 r' A* j( T% y! G5 s/ |8 d) oSep 3 23:59:38 controller1 systemd: haproxy.service failed.& Q% g( b6 R( e
: w! A/ L* w0 e# e
这个问题呢，解决办法就是：' @6 ^7 _: f, t2 e" q Q& {/ i
netstat -ntlp , t1 r8 \" Z: N' L; P: h
查看端口是否启动正常了，尤其是haproxy中配置的端口号，如果看到0.0.0.0:100& n; }) z+ ^. ?3 Y: u
在haproxy文件中配置有( O* y& q b. Z7 n# l
x.x.x.x:100 " R X9 k5 E) B' _ a
$ m% D/ P2 j; ]; z
会导致haproxy的服务启动失败。0 w X3 Y4 N7 q" k5 G# I; o. l; S
修改服务的启动端口方式，确定为当前主机IP地址 ip:1002 }0 ?$ E: _! g. ~: \' `
与haproxy的不是同一个IP地址，就不会冲突，haproxy自然就能启动了。 |
|
发表于 2018-9-4 00:34:35