opt/hp/propel/sx/WEB-INF/classes/config/infrastructure.jsonĢ5672 is used by rabbit to manage clustering:īOOT FAILED - Timeout contacting cluster nodes: -This cluster node was shut down while other nodes were still running. The following section provides some useful commands for RabbitMQ. If PostgreSQL runs out of space and does not respond: var/lib/pgsql/9.5/data/pg_log DB restart: # service postgresql-9.5 restart DB not responding:
#504 gateway time out my pet cert how to
How to change postgreSQL to listen to all interfacesĮdit the pg_hba.conf file: # su – postgresĮdit the nf file: # vi /var/lib/pgsql/9.5/data/nf The following section contains information about a DB node. Nginx conf : /etc/nginx/conf.d/nfĬommand to restart nginx: service nginx restart Database node information To fix the issue, follow the same steps in Pgpool not attaching to nodes. Node_id | hostname | port | status | lb_weight | role When one or both databases are up and pgpool is running, this error should not occur: # sudo -u postgres psql -h -p 9999 -c "show pool_nodes" This probably means the server terminated Psql: server closed the connection unexpectedly
When one or both databases are up and pgpool is running, this error should not occur: # sudo -u postgres psql -h -p 9999 -c 'SELECT now()' Wait 60 seconds and then check the result: # sudo -u postgres psql -h -p 9999 -c "show pool_nodes" Password: # /usr/pgpool-9.4/bin/pcp_detach_node -U pgpool -h localhost -p 9898 -W -n # /usr/pgpool-9.4/bin/pcp_attach_node -U pgpool -h localhost -p 9898 -W -n On the primary server, run these commands using the node_id that reports a status of “3”: # /usr/pgpool-9.4/bin/pcp_detach_node -U pgpool -h localhost -p 9898 -W -n If these are incorrect, the issue is more likely with the configuration of PostgreSQL. The result should be “t”: # sudo -u postgres psql -h -p 5432 -c 'select pg_is_in_recovery()' pg_is_in_recovery - t The result should be “f”: # sudo -u postgres psql -h -p 5432 -c 'select pg_is_in_recovery()' pg_is_in_recovery - fĬonfirm the status of the standby server. If the status is “2” for both nodes, restart pgpool on the standby server: # service pgpool startĬonfirm the status of primary server. On the primary server, restart pgpool: # service pgpool start # rm –i /var/run/postgresql/.s.PGSQL.9999 On the primary server, verify that pgpool exited gracefully: On the primary server, confirm eth0:0 is down: # ifdown eth0:0 On the primary server, stop pgpool: # service pgpool stop On the standby server, stop pgpool: # service pgpool stop If the status is still incorrect, perform the following steps: On the standby server, restart pgpool: # service pgpool restartĬheck the result: # sudo -u postgres psql -h -p 9999 -c "show pool_nodes" On the primary server, restart pgpool: # service pgpool restart To obtain the expected result, try the following: When both databases are running, the “show pool_nodes” query should show a status of “2” for both nodes. Ignore_errors: yes Pgpool not attaching to nodes
#504 gateway time out my pet cert install
You can update the propel-distributed/roles/pgpool/tasks/main.yml for the pgpool role to force to install a specific version: name: roles:pgpool Install older pgPool This is the version that HPE validated with in the Distributed Service Manager Service Portal configuration. Make sure that version 3.4.7 is installed (see the following figure for an example).
If that works, restart all other services on al Service Manager Service Portal nodes. If they can connect to the DB, try the LB connection again. When this error occurs, do the following:Ĭheck if pgpool is running and listening: # systemctl status pgpoolĬheck if IdM on node1/2 can connect to the DB (see logs in /var/log/propel/idm). This section provides troubleshooting hints and tips that can help you set up a Distributed Service Manager Service Portal Cluster. Install > Install and set up Service Manager Service Portal > Deploy a distributed Service Manager Service Portal cluster > Troubleshoot distributed Service Manager Service Portal clustering Troubleshoot distributed Service Manager Service Portal clustering
0 kommentar(er)
