You can translate the question and the replies:

HAProxy Load balancer error

root@denodo-01-sm:/etc/haproxy# sudo systemctl restart haproxy root@denodo-01-sm:/etc/haproxy# systemctl status haproxy ● haproxy.service - HAProxy Load Balancer Loaded: loaded (/lib/systemd/system/haproxy.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-08-02 04:26:14 UTC; 6s ago Docs: man:haproxy(1) file:/usr/share/doc/haproxy/configuration.txt.gz Process: 2997858 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS) Main PID: 2997859 (haproxy) Tasks: 3 (limit: 9528) Memory: 7.4M CGroup: /system.slice/haproxy.service ├─2997859 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock └─2997861 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock Aug 02 04:26:14 denodo-01-sm systemd[1]: Starting HAProxy Load Balancer... Aug 02 04:26:14 denodo-01-sm haproxy[2997859]: [NOTICE] 213/042614 (2997859) : New worker #1 (2997861) forked Aug 02 04:26:14 denodo-01-sm systemd[1]: Started HAProxy Load Balancer. Aug 02 04:26:14 denodo-01-sm haproxy[2997861]: [WARNING] 213/042614 (2997861) : Server backend_servers_tomcat_http/node01 is DOWN, reason: Layer4 connection problem, in fo: "Connection refused", check duration: 2ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Aug 02 04:26:14 denodo-01-sm haproxy[2997861]: [WARNING] 213/042614 (2997861) : Server backend_servers_tomcat_http/node02 is DOWN, reason: Layer4 connection problem, in fo: "Connection refused", check duration: 2ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Aug 02 04:26:14 denodo-01-sm haproxy[2997861]: [ALERT] 213/042614 (2997861) : backend 'backend_servers_tomcat_http' has no server available! Aug 02 04:26:16 denodo-01-sm haproxy[2997861]: [WARNING] 213/042616 (2997861) : Server backend_servers_tomcat_https/node01 is DOWN, reason: Layer4 timeout, check durati on: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Aug 02 04:26:16 denodo-01-sm haproxy[2997861]: [WARNING] 213/042616 (2997861) : Server backend_servers_tomcat_https/node02 is DOWN, reason: Layer4 timeout, check durati on: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Aug 02 04:26:16 denodo-01-sm haproxy[2997861]: [ALERT] 213/042616 (2997861) : backend 'backend_servers_tomcat_https' has no server available!
load balancer haproxy
user
02-08-2022 00:28:12 -0400
code

1 Answer

Hi, The error is related to the service not being able to connect to the server. If I face a similar error then, I would check whether I have used correct IP address under the backend_servers_tomcat_http in the configuration. Also, I would check whether the port is listening and not blocked by a firewall. In order to check this I would use telnet from the proxy server machine to the webcontainer on the vdp instance to validate the connectivity. The error can be caused by the HAProxy itself. Additionally, if you need further assistance and if you are a user with valid support access, create a support case in [Denodo Support Site](https://support.denodo.com/) so that our support team will assist you. Hope this helps!
Denodo Team
02-08-2022 09:05:34 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here