Can anyone please advise me on how to check the deployment status on Apigee Edge for Private Cloud and fix it as needed?
When we call to check the deployment status by;
curl -u <admin user>:<admin passwd> http://localhost:8080/v1/organizations/orgname/deployments
it sometimes gives the response with including "error" like;
{ "error" : "Call timed out; either server is down or server is not reachable", "status" : "error", "type" : [ "router" ], "uUID" : "6185be60-ff6d-401f-ba5c-026e42695a1d" },...
And we found that the it's caused by the configuration of the Routers or Message Processors which actually don't exist in the system, where the configurations could remain there possibly by some issues at the setup conducted before. Now we want to fix it by deleting unnecessary configurations.
According to the 'Apigee Edge Operations Guide' we see that we can delete the above nonexistent servers by following the steps in the section of 'Removing a Server (Management Server/Message Processor/Router)';
I'll appreciate your help on this.
Solved! Go to Solution.
We have faced similar issues with some orphan UUIDs recently, we have used below steps to clean up them.
/opt/apigee4/contrib/registration-overview.sh [-p <admin-password>] <region> <pod>
This will list all registered nodes with its UUIDs.
curl -v -u admin userid:password http://localhost:<<ms server port, default
8080>>/v1/servers/<UUID>
curl -v -X POST http://localhost:<<MS server port, default
8080>>/v1/o/<ORG_NAME>/environments/<ENV_NAME>/servers -d "uuid=<UUID>®ion=
<DC_NAME>&pod=<GATEWAY_NAME>&action=remove" -u admin uid:password
curl http://localhost:<<MS port>>/v1/servers -v -X POST -d "type=<TYPE_NAME>®ion=<DC_NAME>&pod=<GATEWAY_NAME>&uuid=<UUID>&action=remove" -u admin uid:password
curl -v -X DELETE "http://localhost:<<MS Port>>/v1/servers/<UUID>" -u admin uid:password
You can also remove old snapshot files from zookeeper please check OPDK Apigee Edge On-Premises Operations Guide and search "Removing Old Snapshot Files" .
It is also good to remove(using rmr command) these UUID associated tree paths from Zookeeper. Hope this helps.
Regards,
Remeesh
We have faced similar issues with some orphan UUIDs recently, we have used below steps to clean up them.
/opt/apigee4/contrib/registration-overview.sh [-p <admin-password>] <region> <pod>
This will list all registered nodes with its UUIDs.
curl -v -u admin userid:password http://localhost:<<ms server port, default
8080>>/v1/servers/<UUID>
curl -v -X POST http://localhost:<<MS server port, default
8080>>/v1/o/<ORG_NAME>/environments/<ENV_NAME>/servers -d "uuid=<UUID>®ion=
<DC_NAME>&pod=<GATEWAY_NAME>&action=remove" -u admin uid:password
curl http://localhost:<<MS port>>/v1/servers -v -X POST -d "type=<TYPE_NAME>®ion=<DC_NAME>&pod=<GATEWAY_NAME>&uuid=<UUID>&action=remove" -u admin uid:password
curl -v -X DELETE "http://localhost:<<MS Port>>/v1/servers/<UUID>" -u admin uid:password
You can also remove old snapshot files from zookeeper please check OPDK Apigee Edge On-Premises Operations Guide and search "Removing Old Snapshot Files" .
It is also good to remove(using rmr command) these UUID associated tree paths from Zookeeper. Hope this helps.
Regards,
Remeesh
® replace with & reg (no space) and ∾ with & ac(no space)
Thank you so much for the details of the useful information that must help us also. We will check the steps you explained here and will come back if there are any further questions.
Customer wants to know whether we need to restart Routers/Message Processors and Management Servers after removing the server information as described above. Could you please answer to the question?
Yes, I think it's safe to do a rolling restart.
Thank you for the confirmation. I also got info from GSC that older versions have issue on ZK bindings and we to need to restart to avoid it.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |