Starting frontend GLOBAL: cannot bind socket [127.0.0.1:14567]

Elastic Stack Beats
1

I'm trying to follow HAProxy module | Metricbeat Reference [6.1] | Elastic, specifically part:

place this statement under the global or default section of the haproxy config:
stats socket 127.0.0.1:14567

I've tried placing above statement into global or default, followed by restart of haproxy.service, however I haproxy.service fails to run with following message:

Jan 23 11:50:17 X.X.X haproxy-systemd-wrapper[12212]: [ALERT] 022/115017 (12213) : Starting frontend GLOBAL: cannot bind socket [127.0.0.1:14567]

software stack:

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.4 (Maipo)
# rpm -q metricbeat
metricbeat-6.1.2-1.x86_64
# rpm -q haproxy
haproxy-1.5.18-6.el7.x86_64
#

Please advise.

2

It sounds like netstat cannot bind on that port. Perhaps the port is used by another process? You can check with netstat -apn.

3

@tudor, haha, I should have include that to begin with, however since error did not say port is already in use, I thought this would not come up, I was wrong...

# netstat -apn | grep 14567
#

let me also include my interface as well, just in case if someone will think it's missing:

# ip addr show lo 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
#
4

Hmm, not sure what is wrong. What version of HAproxy do you have?

5

@tudor

# haproxy -v
HA-Proxy version 1.5.18 2016/05/10
Copyright 2000-2016 Willy Tarreau <willy@haproxy.org>

#
6

We've tested the module with haproxy 1.6, and the haproxy changelog seems to indicate that the stats socket command is new in 1.6, see the line - MINOR: cli: new stats socket command: show servers state.

It might be that 1.5 just needs a different configuration in haproxy, but I'm not sure.

7

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.