Message processor and zookeeper out of sync?

[#1]

We have on-prem and cannot start message processor. It can't register the uuid:

[root@ip-10-96-2-224 logs]# /apigee/apigee4/bin/apigee-service message-processor start Starting apigee-message-processor Checking if apigee-message-processor is up. .Connection to 10.96.2.224 8082 port [tcp/*] succeeded!

Success apigee-message-processor is up.

Checking if we can get the message-processor uuid: 94a01c1f-64b2-42df-b75c-8dcf932dd555 ................... Last chance. Waiting 2 minutes longer. message-processor may have failed to start. Check /apigee/apigee4/var/log/apigee/message-processor/logs/system.log for errors.

Looking in zookeeper it appears that it thinks the message processor is already up. Could this out-of-sync situation be causing this behavior? If so, how can we resolve?

[#2]

Hi @Jeff Nadeau , I don't think thats the case.

AFAIK at least from what I have seen earlier , you will see Success apigee-message-processor is up when Mp starts (it listens on 8998 and 8082 at that point) but immediately after that during the Checking if we can get the message-processor uuid: 94a01c1f-64b2-42df-b75c-8dcf932dd555 , it deploys some server applications and if there are any issues during that you will see that problem and MP stops .

You should check your Mp logs to find out the exact issue as there could be many reasons .