Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Recurring HTTP 500/502 Errors with a Shared Windows Azure Website

DZone's Guide to

Recurring HTTP 500/502 Errors with a Shared Windows Azure Website

· Cloud Zone ·
Free Resource

Discover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.

On 4/25/2013 I created a new, free Windows Azure Website with WebMatrix and WordPress: Android MiniPCs and TVBoxes. While adding about 50 MB of content to it from the OakLeaf Systems blog, I exceeded the free Website quota so I changed the deployment from Free to Shared. I then enabled Pingdom’s free Website monitoring service for the site, which duplicates that for my Live OakLeaf Systems Windows Azure Table Services Sample Project.

Two days later, Pingdom was reporting periodic HTTP 500 Internal Server and 502 Bad Gateway errors:

image

Following are Root Cause Analyses for the two errors shown in the above screen capture:

image

image

Here’s the Root Cause Analysis for an earlier HTTP 502 error:

imageimage

Fortunately, the errors subsided on 2/29/2012, but I’m curious if others have encountered this problem.

Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}