We experienced another outtage today with Cherokee in production environment.
Was wondering if someone could explain why Cherokee would deliver a 503 Service Unavailable message in reverse proxy mode. Assuming Cherokee is labeling something failed with the backend information sources - but I can't figure out where any failure is occurring. Additionally Cherokee seems to keep the servers unavailable. I watched for 5 minutes hoping Cherokee would reestablish the backend information sources gracefully - but it did not. All during this time, the backend servers were functioning perfectly. So, unsure if there is a bug in Cherokee or something else. Any ideas on debugging this issue? _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
