|
|
Sep 3 23:59:38 controller1 systemd: Started HAProxy Load Balancer.) b% B: S) ^& y8 k+ ?3 B, b4 l# u
Sep 3 23:59:38 controller1 systemd: Starting HAProxy Load Balancer...
5 U9 f. v p- @) Z- U9 b& |) l) jSep 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'.
' K8 Z4 |4 B( k- H$ g pSep 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.
' b. o. N% G1 } mSep 3 23:59:38 controller1 haproxy-systemd-wrapper: [ALERT] 245/235938 (1862) : Starting proxy mariadb_cluster: cannot bind socket [192.168.90.70:3306]& ?0 R) F- ~0 l) j
Sep 3 23:59:38 controller1 haproxy-systemd-wrapper: haproxy-systemd-wrapper: exit, haproxy RC=1$ w$ N- }/ e1 y2 s- ?# {5 H3 w& Z7 I
Sep 3 23:59:38 controller1 systemd: haproxy.service: main process exited, code=exited, status=1/FAILURE& E3 M- j8 G% \+ T
Sep 3 23:59:38 controller1 systemd: Unit haproxy.service entered failed state.
+ m5 s5 s, }% X; s' BSep 3 23:59:38 controller1 systemd: haproxy.service failed.
$ A9 {# ]5 ]7 n# u! Z# S
U- a4 a$ w. t5 T4 B6 B' Z这个问题呢，解决办法就是：: }: c, p% I; s6 |, F! Y( Y" B
netstat -ntlp h4 Q. h7 H. [+ T* L9 v8 K1 }
查看端口是否启动正常了，尤其是haproxy中配置的端口号，如果看到0.0.0.0:100, _3 k$ ~/ ?# ~2 G5 x q. }! d1 I6 A
在haproxy文件中配置有4 K- Z) ]8 J L! M: v) d
x.x.x.x:100 7 ?% _* U8 H. ~4 {# G* Z6 ]7 t
6 T) X! t: ^* a# \1 P会导致haproxy的服务启动失败。
0 h- V' v6 O Z, n, A修改服务的启动端口方式，确定为当前主机IP地址 ip:100. m' e4 u( _( D
与haproxy的不是同一个IP地址，就不会冲突，haproxy自然就能启动了。 |
|
发表于 2018-9-4 00:34:35