<Server xsi:type="serverDeploymentStatus">
<ErrorCode>messaging.runtime.UnknownEventReceived</ErrorCode>
<Error>Received an unknown event with description SYNC Application /organizations/test/apiproxies/Check/revisions/1/</Error>
<UUID>$UUID</UUID>
<Status>error</Status>
<Type>message-processor</Type>
</Server>
The above is the output of deployment status (management API) of an apiproxy 'Check' showing some issues with the deployments and we see that mainly in the below cases .
#1 . Failed Registrations - Mps with the environment / region - pod association .
#2 . Right environment not loaded on Mp startup.
#3. ManagementAPI
curl -v http://mgmt:port/v1/servers/{UUID}/bindings -u xxxxx:xxxx if bindings doesn’t show the right environment , there is a problem with the MP registration and we may need to associate it properly .
You can check that from Zk too
[zk: localhost:2181(CONNECTED) 4] ls /regions/cal/pods/gateway
[types,bindings,servers]
#4 Mp internal runtime API
curl -v http://localhost:mgmtportonMP/v1/runtime/organizations/test/environments
If runtime API doesn’t show the expected environment , chances that MP has problems during startup and system log can provide more information on the actual reason.
#5 There could be many reasons for #4
I saw this when we had an expired cert in one of the target keystores . // This is still a bug (APIRT-1393) on latest 15.04 too.
To avoid this make sure you don’t have any expired certs.
If you know of any other reasons , pls add to the list .
LinkedIn
Twitter