|
|
Sep 3 23:59:38 controller1 systemd: Started HAProxy Load Balancer.. U( q& s: d: E
Sep 3 23:59:38 controller1 systemd: Starting HAProxy Load Balancer...
; {- w" E! i3 |! h+ B3 A0 B2 \* fSep 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'.0 `. L5 a6 a) \# x; w3 O$ Z
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.) j* \* f7 t& o. e9 |$ X! I. K
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]: k. V" P# ~5 x* u% Q9 @2 i
Sep 3 23:59:38 controller1 haproxy-systemd-wrapper: haproxy-systemd-wrapper: exit, haproxy RC=15 f5 a2 H; F% P- q
Sep 3 23:59:38 controller1 systemd: haproxy.service: main process exited, code=exited, status=1/FAILURE
+ c2 A$ l2 P0 W; @+ N+ dSep 3 23:59:38 controller1 systemd: Unit haproxy.service entered failed state.
* T! R- l5 |6 B8 K6 bSep 3 23:59:38 controller1 systemd: haproxy.service failed.* x$ L( e" ^* F6 j% u0 ~2 e1 V/ `# Y. i
" i$ j) m/ I! S5 D& N$ C6 s& [这个问题呢,解决办法就是:1 W0 B( J# s+ V4 n
netstat -ntlp
7 H; u( V: C+ E" U- g/ P查看端口是否启动正常了,尤其是haproxy中配置的端口号,如果看到0.0.0.0:100$ b! c8 b# g; S1 I
在haproxy文件中配置有
: w( E8 h; l4 q& v8 D6 Tx.x.x.x:100
! l) V* q& \ d
) a3 m9 j# h" J8 K7 ~' B( U- R7 C会导致haproxy的服务启动失败。7 r+ Y5 C7 R: ^: I* T5 Z) d- i+ k$ H
修改服务的启动端口方式,确定为当前主机IP地址 ip:100! m' K9 v& m4 L
与haproxy的不是同一个IP地址,就不会冲突,haproxy自然就能启动了。 |
|