Re: App running even after delete. Pointers on finding it and debugging?

Amit Kumar Gupta

Ok, I would use veritas to look at the Diego BBS, and confirm that it still
thinks the app is there. You can also go onto the router and query its
HTTP endpoint to confirm that the route you're seeing is also still there: Lastly I would
connect to the CCDB and confirm that the app and route are *not* there.
This will reduce the problem to figuring out why Diego isn't being updated
to know that the non-existing app is no longer desired.

On Mon, Apr 4, 2016 at 3:47 PM, Tom Sherrod <tom.sherrod(a)> wrote:

The route still exists. I was reluctant to delete it and have the "app"
still running. I wanted some way to track it down, not that it has helped,
other than let me know it is still running.

Pushed the app, with a different name/host, with no problems and it runs
as it should.

On Mon, Apr 4, 2016 at 6:17 PM, Amit Gupta <agupta(a)> wrote:


So you're saying that none of the org/spaces shows the app or the route,
but the app continues to run and be routeable?

I could imagine this happen if some CC Bridge components are not able to
talk to either CC or Diego BBS, leaving the data in the Diego BBS stale.
In the case of stale info, Diego may not know that the LRP is no longer
desired, and it will do the safe thing of keeping it around, and emitting
its route to the gorouter, which just does what it's told (it doesn't check
whether CC knows about the route or not).

Are you able to push new apps or delete other apps with the Diego backend?


On Fri, Apr 1, 2016 at 1:00 PM, Tom Sherrod <tom.sherrod(a)>


Thanks for responding.

This is a test runtime and small. I checked all orgs and spaces. No
routes matching the app.

Found the route information and the result:


"total_results": 0,

"total_pages": 1,

"prev_url": null,

"next_url": null,

"resources": []


To learn what the output may look like, I check existing routes with
apps and without. The output appears to be the same as if the app has been

Even now, the app url still returns a page from the app, even though it
is deleted.



On Fri, Apr 1, 2016 at 1:52 PM, JT Archie <jarchie(a)> wrote:


Are you sure the route isn't bound to another application in another

When you do `cf routes` it only show routes for the current space. You
can hit specific API endpoints though to get all the apps for a route.

For example, `cf
curl /v2/routes/89fc2a5e-3a9b-4a88-a360-e405cdbd6f87/apps` will show all
the apps for a particular route. Obviously replacing the route ID with the
correct ID. To find that, I recommend going through `CF_TRACE=true cf
routes` and grabbing the ID.

Let see if you can hunt it down that way.

Kind Regards,


On Fri, Apr 1, 2016 at 8:51 AM, Tom Sherrod <tom.sherrod(a)>

cf 230, diego 0.1450.0, etcd 27, garden-linux 0.330.0
Default to diego true.

Developer deployed a java application. Deleted the application: cf
delete <app> No errors.
The app still responds. The only thing left is the route.
I've not encountered this before. Delete has been delete and even if
route remains, 404 Not Found: Requested route ('<hostname.domain>') does
not exist. is returned.

Pointers on tracking this down appreciated.


Join { to automatically receive all group messages.