You can translate the question and the replies:

how to set up an active-active Denodo Cluster with 2 nodes behind the Nginx load balancer

how to set up an active-active Denodo Cluster with 2 nodes behind the Nginx load balancer for Denodo 8
Load Balancer Nginx Denodo 8
user
30-06-2022 03:34:27 -0400
code

9 Answers

Hello, When using Nginx, after accessing the load balancer url, I would create a cluster following the steps below: * In the Solution Manager Administration Tool, I would select New Cluster on an environment that I created. Then a dialog will open to create a new cluster. * In the Configuration of the My Applications Panel, I would provide the load balancer url instead of the default url so that it can access the nodes via the load balancer url. I would like to note that only global administrators and Solution Manager administrators can create clusters. After the cluster is created, I can add servers to it. The document [Creating Standard Clusters](https://community.denodo.com/docs/html/browse/8.0/en/solution_manager/administration/standard/creating_clusters/creating_clusters) shows the Configuration of the My Applications Panel section where Load Balancer URL should be inputted. The document [Denodo Platform Cluster Architecture](https://community.denodo.com/kb/en/view/document/Denodo%20Platform%20Cluster%20Architecture?category=Best+Practices#:~:text=Load%20Balancer%20%E2%80%93%20The%20load%20balancer,servers%20belonging%20to%20the%20cluster.) describes how the load balancer works and important considerations for optimal performance. I would use these documents as a useful reference. If you have a valid support user account and need any further assistance, please open a new support case at [Denodo Support Site](https://support.denodo.com) so that the support team can review this in detail. Hope this helps!
Denodo Team
30-06-2022 19:55:22 -0400
code
https://community.denodo.com/kb/en/view/document/Configuring%20a%20Denodo%20Cluster%20with%20HAProxy%20Load%20Balancer I am following above document for HAProxy Load Balancer configuration, Do you have any updated document for the same ? We have a jks file, we converted into pem file using following steps. Is it correct way or can we point it to jks file itself, because we cannot restart haproxy service after changing the configuration. The error code is below ./keytool -importkeystore -srckeystore /opt/denodo/solution-manager/denodo_prod_server_key_store.jks \ -destkeystore /opt/denodo/solution-manager/keystore.p12 \ -srcstoretype jks \ -deststoretype pkcs12 openssl pkcs12 -in /opt/denodo/solution-manager/keystore.p12 -out /opt/denodo/solution-manager/denodo_server_key_store.pem Jul 01 07:44:01 denodo-01-sm haproxy[2055434]: Enter PEM pass phrase: Jul 01 07:44:01 denodo-01-sm haproxy[2055434]: [ALERT] 181/074401 (2055434) : parsing [/etc/haproxy/haproxy.cfg:80] : 'bind *:9443' : unable to load SSL private key fro m PEM file '/etc/haproxy/denodo_server_key_store.pem'. Jul 01 07:44:01 denodo-01-sm haproxy[2055434]: [ALERT] 181/074401 (2055434) : Error(s) found in configuration file : /etc/haproxy/haproxy.cfg Jul 01 07:44:01 denodo-01-sm haproxy[2055434]: [ALERT] 181/074401 (2055434) : Fatal errors found in configuration. Jul 01 07:44:01 denodo-01-sm systemd[1]: haproxy.service: Control process exited, code=exited, status=1/FAILURE
user
01-07-2022 04:17:40 -0400
Hello, The document [Configuring a Denodo Cluster with HAProxy Load Balancer](https://community.denodo.com/kb/en/view/document/Configuring%20a%20Denodo%20Cluster%20with%20HAProxy%20Load%20Balancer) is for the latest Denodo update. Also, a pem file is a requirement of the HAProxy load balancer, therefore you would need to convert the jks to pem. You are getting the “Enter PEM pass phrase" because openssl doesn't want to output private key in clear text. The password is used to output encrypted private key. Below command can be used to output private key in clear text. No password is then asked. `openssl pkcs12 -nodes -in /opt/denodo/solution-manager/keystore.p12 -out /opt/denodo/solution-manager/denodo_server_key_store.pem` As you have a valid support user account, if you need any further assistance, please open a new support case at Denodo Support Site so that the support team can review the issue in detail. Hope this helps!
Denodo Team
01-07-2022 18:14:52 -0400
code
Getting the following error: root@denodo-01-sm:/etc/haproxy# haproxy -f /etc/haproxy/haproxy.cfg -c [WARNING] 184/064709 (2140931) : parsing [/etc/haproxy/haproxy.cfg:80] : 'bind *:9443' : unable to load default 1024 bits DH parameter for certificate '/etc/haproxy/denodo_server_key_store.pem'. , SSL library will use an automatically generated DH parameter. [WARNING] 184/064709 (2140931) : Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear. Configuration file is valid root@denodo-01-sm:/etc/haproxy# sudo systemctl restart haproxy Job for haproxy.service failed because the control process exited with error code. See "systemctl status haproxy.service" and "journalctl -xe" for details. 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: failed (Result: exit-code) since Mon 2022-07-04 06:47:54 UTC; 14s ago Docs: man:haproxy(1) file:/usr/share/doc/haproxy/configuration.txt.gz Process: 2140952 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS) Process: 2140953 ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -p $PIDFILE $EXTRAOPTS (code=exited, status=1/FAILURE) Main PID: 2140953 (code=exited, status=1/FAILURE) Jul 04 06:47:54 denodo-01-sm systemd[1]: haproxy.service: Scheduled restart job, restart counter is at 5. Jul 04 06:47:54 denodo-01-sm systemd[1]: Stopped HAProxy Load Balancer. Jul 04 06:47:54 denodo-01-sm systemd[1]: haproxy.service: Start request repeated too quickly. Jul 04 06:47:54 denodo-01-sm systemd[1]: haproxy.service: Failed with result 'exit-code'. Jul 04 06:47:54 denodo-01-sm systemd[1]: Failed to start HAProxy Load Balancer.
user
04-07-2022 02:53:09 -0400
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 Mon 2022-07-04 13:48:20 UTC; 4s ago Docs: man:haproxy(1) file:/usr/share/doc/haproxy/configuration.txt.gz Process: 2150622 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS) Main PID: 2150623 (haproxy) Tasks: 3 (limit: 9528) Memory: 7.2M CGroup: /system.slice/haproxy.service +-2150623 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock +-2150624 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock Jul 04 13:48:20 denodo-01-sm systemd[1]: Starting HAProxy Load Balancer... Jul 04 13:48:20 denodo-01-sm haproxy[2150623]: [NOTICE] 184/134820 (2150623) : New worker #1 (2150624) forked Jul 04 13:48:20 denodo-01-sm systemd[1]: Started HAProxy Load Balancer. Jul 04 13:48:20 denodo-01-sm haproxy[2150624]: [WARNING] 184/134820 (2150624) : Server backend_servers_tomcat_http/vdp-preprod is DOWN, reason: Layer4 connection proble m, info: "Connection refused", check duration: 2ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jul 04 13:48:21 denodo-01-sm haproxy[2150624]: [WARNING] 184/134821 (2150624) : Server backend_servers_tomcat_http/vdp-prod is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 2ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jul 04 13:48:21 denodo-01-sm haproxy[2150624]: [ALERT] 184/134821 (2150624) : backend 'backend_servers_tomcat_http' has no server available!
user
05-07-2022 11:18:31 -0400
Getting above error while restarting haproxy and checking status Jul 04 13:48:20 denodo-01-sm haproxy[2150624]: [WARNING] 184/134820 (2150624) : Server backend_servers_tomcat_http/vdp-preprod is DOWN, reason: Layer4 connection proble m, info: “Connection refused”, check duration: 2ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jul 04 13:48:21 denodo-01-sm haproxy[2150624]: [WARNING] 184/134821 (2150624) : Server backend_servers_tomcat_http/vdp-prod is DOWN, reason: Layer4 connection problem, info: “Connection refused”, check duration: 2ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Jul 04 13:48:21 denodo-01-sm haproxy[2150624]: [ALERT] 184/134821 (2150624) : backend ‘backend_servers_tomcat_http’ has no server available!
user
05-07-2022 11:19:50 -0400
Hello, I understand you used a modified version of the templated configuration in the document linked above and modified it to have a node that should be connecting to the tomcat on vdp. The errors show that the service can’t connect to the server. If I have these errors, I would check if I used the appropriate IP address under backend backend_servers_tomcat_http in the configuration by looking at the below part . `server vdp-prod <ip>:9090 cookie ck_vdp-prod check` I would also verify the port is listening and not blocked by a firewall or used by another application. 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 your HAProxy itself. If you would like assistance in troubleshooting this further, a support ticket is the appropriate place to address your issue, as we would require the configuration file in order to assist in the troubleshooting. Hope this helps!
Denodo Team
05-07-2022 13:25:06 -0400
code
Bad Request This combination of host and port requires TLS. while testing https url for haproxy load balancer https://denodo-01-sm.iqzsystems.io:9443/denodo-design-studio/#/ and same for all other https components scheduler, data catalog, dmt and restfulws below error still exists while checking for status of 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)haproxlAProxy Load Balancer... Jul 08 10:39:11 denodo-01-sm haproxy[2269959]: [NOTICE] 188/103911 (2269959) : New worker #1 (2269960) forked Jul 08 10:39:11 denodo-01-sm systemd[1]: Started HAProxy Load Balancer. Jul 08 10:39:11 denodo-01-sm haproxy[2269960]: [WARNING] 188/103911 (2269960) : 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. Jul 08 10:39:12 denodo-01-sm haproxy[2269960]: [WARNING] 188/103912 (2269960) : 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. Jul 08 10:39:12 denodo-01-sm haproxy[2269960]: [ALERT] 188/103912 (2269960) : backend 'backend_servers_tomcat_http' has no server available!
user
08-07-2022 06:45:27 -0400
Hello, There are some limits to support for this issue in the Community Q&A. If you would like assistance in troubleshooting this further, please open a support ticket at [Denodo Support Site](https://support.denodo.com/) so that the support team can review the issue in detail to assist you. Hope this helps!
Denodo Team
08-07-2022 14:10:43 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here