什么是用121分的状态HTTP 500错误意味着什么？ [英] What does an HTTP 500 error with a 121 sub-status signify?

问题描述

我在Azure中的Web应用程序运行，我也曾有过一些故障所在服务器没有响应。当我看到在IIS日志中，我看到HTTP 500错误与121 SC-子状态和 SC-win32的状态 0

I have a Web Application running in Azure and I've had a few outages where the server is unresponsive. When I look in the IIS log, I see HTTP 500 errors with a sc-substatus of 121 and a sc-win32-status of 0.

省略所有其他领域，日志是这样的，顺序是：

Omitting all other fields, the logs look like this, in this order:

sc-status sc-substatus sc-win32-status
500 121 0

我找不到参照500.121错误具竞争力的超低。

I can't find reference to a 500.121 error anywhere online.

推荐答案

我刚刚得到这个从Azure的软件工程师之一：

I just got this from one of the Azure Software Engineers:

121是超时事件这基本上意味着该请求花
  在工人VM230秒没有进行任何读/写IO上
  连接。极有可能为这是一个应用程序
  的问题，但并不一定要这样。

121 is a timeout event which basically means that the request spent 230 seconds on the worker VM without initiating any read/write IO on the connection. It is highly likely for this to be an application issue, but doesn’t necessarily have to be so.

IIS日志都有一个时间值取徘徊约230秒。解开了谜底。

The IIS logs all have a time-taken value hovering around 230 seconds. Mystery solved.

这篇关于什么是用121分的状态HTTP 500错误意味着什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！