云中漫步 发表于 2019-1-1 08:03:48

缺少/run/haproxy目录,haproxy服务启动失败

  问题描述:
搭建haproxy的机器,因出现故障重启了,然后发现haproxy服务出现异常。重新启动haproxy服务的时候出现下面的错误:

# service haproxy start
Starting haproxy (via systemctl):Job for haproxy.service failed because the control process exited with error code. See "systemctl status haproxy.service" and "journalctl -xe" for details.
[失败]
  使用ps -ef查看进程,服务进程没起来:

#
# ps -ef|grep haproxy
106      12735 126690 09:29 ?      00:00:00 haproxy -p /var/run/haproxy.pid -f /etc/haproxy/haproxy.cfg -sf 26
root   13002 124750 09:32 pts/0    00:00:00 grep --color=auto haproxy
#
  执行 systemctl status haproxy.service,出现下面的结果:

# systemctl status haproxy.service
● haproxy.service - SYSV: HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP andHTTP-based applications
Loaded: loaded (/etc/rc.d/init.d/haproxy; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since 四 2018-05-10 10:33:24 CST; 9s ago
Docs: man:systemd-sysv-generator(8)
Process: 17614 ExecStart=/etc/rc.d/init.d/haproxy start (code=exited, status=1/FAILURE)
5月 10 10:33:24 dev115 systemd: Starting SYSV: HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP andHTTP-based applications...
5月 10 10:33:24 dev115** haproxy: Starting haproxy: 129/103324 (17622) : Starting frontend GLOBAL: cannot bind UNIX socket **
5月 10 10:33:24 dev115 systemd: haproxy.service: control process exited, code=exited status=1
5月 10 10:33:24 dev115 haproxy: [失败]
5月 10 10:33:24 dev115 systemd: Failed to start SYSV: HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP andHTTP-based applications.
5月 10 10:33:24 dev115 systemd: Unit haproxy.service entered failed state.
5月 10 10:33:24 dev115 systemd: haproxy.service failed.
#
  根据报错中的“5月 10 10:33:24 dev115haproxy: Starting haproxy: 129/103324 (17622) : Starting frontend GLOBAL: cannot bind UNIX socket ”这一句,经过链接https://stackoverflow.com/questions/30101075/haproxy-doesnt-start-can-not-bind-unix-socket-run-haproxy-admin-sock   的解答:

  Haproxy needs to write to /run/haproxy/admin.sock but it wont create the directory for you. Create the directory /run/haproxy/ first or set stats socket to a different path.

  原来是/run下面的haproxy目录丢失了,所以手动在/run目录下面创建了一个haproxy目录,并且改权限为haproxy:haproxy

# mkdir haproxy
# chown haproxy:haproxy -P haproxy/
  然后重新启动haproxy,成功:

# cd /etc/init.d
# ./haproxy start
Starting haproxy:                                          [确定]
#
  检查服务进程,进程已经起来了:

# ps -ef|grep haproxy
106      17574 175090 10:33 ?      00:00:05 haproxy -p /var/run/haproxy.pid -f /etc/haproxy/haproxy.cfg -sf 26
haproxy17858   10 10:36 ?      00:00:00 /usr/local/haproxy/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid
root   20764 124750 11:20 pts/0    00:00:00 grep --color=auto haproxy
#


页: [1]
查看完整版本: 缺少/run/haproxy目录,haproxy服务启动失败