proxy not found after stop/start AIO scripts

Google Cloud Apigee
1

Hi,

After installing All-In-One, I built a proxy (no target). It worked fine.

Then I ran the stop/start scripts:

/opt/apigee/apigee-service/bin/apigee-all stop

/opt/apigee/apigee-service/bin/apigee-all start

Seemed like it started up Ok. The UI came up and I could see that the proxy was there. But I could not get a response from the proxy.

Below is what I see when I try to call the proxy using curl, on the same machine that AIO is running on.

What does “messaging.adaptors.http.flow.ApplicationNotFound”? and how do I fix it?

[root@server1 ~]# curl -v [http://192.168.40.134:9001/proxy-loopback](http://192.168.40.134:9001/proxy-loopback)
* About to connect() to 192.168.40.134 port 9001 (#0)
*   Trying 192.168.40.134...
* Connected to 192.168.40.134 (192.168.40.134) port 9001 (#0)
> GET /proxy-loopback HTTP/1.1
> User-Agent: curl/7.29.0
> Host: 192.168.40.134:9001
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Thu, 14 Dec 2017 10:38:31 GMT
< Content-Type: application/json
< Content-Length: 182
< Connection: keep-alive
<
* Connection #0 to host 192.168.40.134 left intact
{"fault":{"faultstring":"Unable to identify proxy for host: 192.168.40.134:9001 and url: \/proxy-loopback","detail":{"errorcode":"messaging.adaptors.http.flow.ApplicationNotFound"}}}[root@server1 ~]#

 /opt/apigee/apigee-service/bin/apigee-all status
+ apigee-service apigee-cassandra status
apigee-service: apigee-cassandra: OK
+ apigee-service apigee-openldap status
apigee-service: apigee-openldap: OK
+ apigee-service apigee-postgresql status
apigee-service: apigee-postgresql: OK
+ apigee-service apigee-qpidd status
apigee-service: apigee-qpidd: OK
+ apigee-service apigee-zookeeper status
apigee-service: apigee-zookeeper: OK
+ apigee-service edge-management-server status
apigee-service: edge-management-server: OK
+ apigee-service edge-message-processor status
apigee-service: edge-message-processor: OK
+ apigee-service edge-postgres-server status
apigee-service: edge-postgres-server: OK
+ apigee-service edge-qpid-server status
apigee-service: edge-qpid-server: OK
+ apigee-service edge-router status
apigee-service: edge-router: OK
+ apigee-service edge-ui status
apigee-service: edge-ui: OK
[root@server1 ~]#
2

Hi,

Well I never got to the bottom of this, but I found that if I un-deploy then re-deploy the proxy, I get the expected response.

I think what is happening is that the startup script is trying to deploy the proxy before it’s ready to be deployed…so I think the deployment needs to be push back in the sequence of processes that are coming up, or maybe put in a delay before deployment?

Thanks, Sam

3

Please try checking API deployment status using below command, in the response if you notice its deployment status as not deployed on MP.

curl --v -u sysadmin:pwd -H ‘Content-Type:application/json’ https://{MgServ}/v1/organizations/{Org_Name}/environments/{Env}/apis/{ApiName}/deployments

Then you need to re-deploy API.