Error: Cannot retrieve UUID

On nodes where the Message Processor and Router are installed the Apigee script check.sh gives the below errors.

Check Processes: 

---------------- 

router (pid 13610) is running... 

message-processor (pid 14457) is running... 

Check Services: 

--------------- 

Router: Error: Cannot retrieve UUID 

Continue anyhow y/(n) y 

Message Processor: Error: Cannot retrieve UUID 



[root@apigee4-fe bin]# sh ./all-status.sh 
router (pid 13610) is running... 
message-processor (pid 14457) is running... 
[root@apigee4-fe bin]# 

On server with Enterprise UI everything is OK:

Check Processes: 
---------------- 
slapd (pid 15485) is running... 
ZooKeeper (pid 13970) is running... 
Cassandra (pid 14783) is running... 
management-server (pid 16254) is running... 
Apigee UI (pid 17131) is running... 

Check Services: --------------- 
Management Server: 

UUID=7039dc92-4e52-4051-a365-15165d0770a0 
==> 200 

[root@apigee1-be bin]# sh ./all-status.sh 
slapd (pid 15485) is running... 
ZooKeeper (pid 13970) is running... 
Cassandra (pid 14783) is running... 
management-server (pid 16254) is running... 
Apigee UI (pid 17131) is running... 
0 7 1,633
7 REPLIES 7

From the logs I am not able to see any obvious error.

The following curl calls generate valid outputs:

curl -v -u username:pass http://Message_processor_ip:8081/v1/servers/self

curl -v -u username:pass http://Router_ip:8081/v1/servers/self

i ran into this exact same problem yesterday with mgmt server - the error disappeared after some time, 15.04 on RHEL 6.5

Do you see any mgmt server errors at that time ? this uses self/uuid call to get the uuid , probably mgmt was unable to reach the ZK .

Question: does check.sh pull the UUID from zookeeper even?

Thats correct @Benjamin Goldman

@Akash Prabhashankar : Could you check the management server logs ? If feasible, it may be useful to change the log level to -DEBUG on the management server to get extra error information logged.

Alos, we need to have at least 2 of the Zookeeper nodes up before we start other components after OPDK v4.14.04