Sep 3rd, 2010, 04:16 AM
False alerts on status 302 - instance not reporting in
Hi, since Wednesday I've been getting constant false alerts for my production app:
"An alert has been triggered - Deployment XYZ - instance ... not reporting in"
I've tried redeploying and rebooting and it still happens. The problem started on an app that had originally been running fine, I updated to a new version which now always performs a redirect to the .com address and it continues.
After checking the httpd access log I see that there are a number of requests for an Apache Commons HTTP client which I assume may be the monitor and they all give a 302, since I'm redirecting all requests to the "proper" url -
127.0.0.1 - - [03/Sep/2010:05:03:52 -0400] "GET / HTTP/1.1" 302 - "-" "Jakarta Commons-HttpClient/3.1"
but I don't see any 4xx or 5xx errors.
Does anyone have any idea why this might be happening?
Sep 26th, 2010, 10:59 AM
Worked out it was my redirect - it eventually took the site down - I've blogged the solution: http://manbuildswebsite.com/2010/09/...-cloudfoundry/
Last edited by dgjbower; Sep 29th, 2010 at 02:55 PM.