Skip to main content

error zookeeper

  • 19 June 2024
  • 5 replies
  • 221 views

El prisma no realiza su inicio al dar cluster status genera lo siguiente 

 
2024-06-19 04:08:33,408Z INFO MainThread zookeeper_session.py:191 cluster is attempting to connect to Zookeeper
2024-06-19 04:08:43,519Z ERROR MainThread configuration.py:158 Could not get Zookeeper connection with host_port_list: zk1:9876,zk2:9876,zk3:9876
2024-06-19 04:08:43,521Z INFO MainThread cluster:2943 Executing action status on SVMs 172.20.1.158,172.20.1.159,172.20.1.161,172.20.1.162,172.20.1.163
2024-06-19 04:08:58,534Z INFO MainThread cluster:1976 Waiting for response from 172.20.1.159, 172.20.1.163, 172.20.1.158, 172.20.1.161, 172.20.1.162
2024-06-19 04:09:13,534Z INFO MainThread cluster:1976 Waiting for response from 172.20.1.159, 172.20.1.163, 172.20.1.158, 172.20.1.161, 172.20.1.162
The state of the cluster: Zookeeper is down. Is the cluster configured?
Lockdown mode: Disabled
2024-06-19 04:09:24,235Z INFO MainThread cluster:3104 Success!
 

This topic has been closed for comments

5 replies

Userlevel 6
Badge +8

When does this happen? Where the nodes already in a cluster? 

If there was no cluster first create one with: 

cluster -s 172.20.1.158,172.20.1.159,172.20.1.161,172.20.1.162,172.20.1.163 create

(please add all cvm ips in the list ;)) 

 

El prisma central no responde ni por web y ssh, cual seria una opción de iniciar la maquina 172.20.1.83 que es la ip correspondiente al prism. se ejecuto el comando el resultado 

nutanix@NTNX-5L2N1S2-A-CVM:172.20.1.158:~$  cluster -s 172.20.1.158,172.20.1.159,172.20.1.161,172.20.1.162,172.20.1.163 create           2024-06-19 13:36:14,009Z INFO MainThread cluster:2943 Executing action create on SVMs 172.20.1.158,172.20.1.159,172.20.1.161,172.20.1.162,172.20.1.163
2024-06-19 13:36:20,247Z CRITICAL MainThread cluster:1001 Could not discover all nodes specified. Please make sure that the SVMs from which you wish to create the cluster are not already part of another cluster. Undiscovered ips : 172.20.1.159,172.20.1.158,172.20.1.162,172.20.1.163,172.20.1.161
 

Userlevel 6
Badge +8

Can you please describe the environment? 

 

Are these newly build ce nodes? Or where there nodes already running in a cluster?

Is this nested (in vmware or something else) or is this bare metal deployment? 

es una implementación sobre dell, estaba funcional pero hace unos días dejo de funcionar al dar cluster status genera esto. 

 

nutanix@NTNX-5L2N1S2-A-CVM:172.20.1.158:~$ cluster status
2024-06-19 14:19:07,880Z INFO MainThread zookeeper_session.py:191 cluster is attempting to connect to Zookeeper
2024-06-19 14:19:17,988Z ERROR MainThread configuration.py:158 Could not get Zookeeper connection with host_port_list: zk1:9876,zk2:9876,zk3:9876
2024-06-19 14:19:17,990Z INFO MainThread cluster:2943 Executing action status on SVMs 172.20.1.158,172.20.1.159,172.20.1.161,172.20.1.162,172.20.1.163
2024-06-19 14:19:33,000Z INFO MainThread cluster:1976 Waiting for response from 172.20.1.161, 172.20.1.163, 172.20.1.159, 172.20.1.162, 172.20.1.158
2024-06-19 14:19:48,000Z INFO MainThread cluster:1976 Waiting for response from 172.20.1.161, 172.20.1.163, 172.20.1.159, 172.20.1.162, 172.20.1.158
The state of the cluster: Zookeeper is down. Is the cluster configured?
Lockdown mode: Disabled
2024-06-19 14:19:58,604Z INFO MainThread cluster:3104 Success!

Userlevel 6
Badge +8

Ahh oke. Looks like there is something changed at the netwerk level.

Is this CE or commercial version? If commercial, involve nutanix support. If CE then look at the network. Make sure the hosts and cvms can talk to each other.