App Service python app: logging flooded with "LogStreamManager: Request is aborted + context is null"

Question

App Service python app: logging flooded with "LogStreamManager: Request is aborted + context is null"

Heyns Emiliano 31

I've uploaded a python Flask app to App Service, and it generally works, but my logs are flooded with

2021-09-30T12:38:55 Error occurred, type: error, text: LogStreamManager: Request is aborted + context is null, ignoring exception

I think this must be part of the App Service release pipeline, but I don't know what I should configure to get rid of this message.

Brendan Murphy 1 Reputation point

2021-10-01T02:45:51.133+00:00

I'm receiving the same error with a Node app as of a half hour ago.

I redeployed a working version of my app and I'm still getting the same error.
Tanmay Lad 1 Reputation point

2021-10-02T00:31:22.603+00:00

Yes, I have been getting the same message with a python app and setup that produced no errors in the past (last week or so).

Actual app performance is unaffected. I don't see anything in the portal that could be to do with log configuration.
SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2021-10-04T09:20:16.307+00:00

Thanks for reaching here! Could you please share document you are referring to help you better on this.

In case you want to Create a Python app using Azure App Service?
you may refer to steps on this official document link: https://learn.microsoft.com/en-us/azure/app-service/quickstart-python?tabs=bash&pivots=python-framework-flask

Let us know.
Heyns Emiliano 31 Reputation points

2021-10-04T13:34:56.993+00:00

I followed that tutorial, that's how I got my web app up.
Jakob Gaardsted 1 Reputation point

2021-10-05T09:07:13.363+00:00

The message seems to come from Kudu.Services.Performance.LogStreamManager.
However, the current version of LogStreamManager does not seem to contain any of the parts "request is aborted", "context is null" or "ignoring exception".
We experience the same issue with our production system, where the log will spam a lot of these messages instead of showing the actual log we need, with no indication of what is actually wrong.

I would expect parts of this error message in https://github.com/projectkudu/kudu/blob/master/Kudu.Services/Resources.resx.
Does anyone know if the error message was there, in an earlier version?
Jakob Gaardsted 1 Reputation point

2021-10-05T09:21:50.997+00:00

JakobGaardsted-2278 avatar image
0 Votes" 0
JakobGaardsted-2278 answered • 17 hours ago

I get this same error message. I'm assuming it's kudu, and related to
Kudu.Services.Performance.LogStreamManager.

However, I am unable to find any part of this string in
kudu\Kudu.Services\Diagnostics\LogStreamManager.cs ?
possibly, azure is running on a different version.
I see it has a member
..
private void OnError(object sender, ErrorEventArgs e)
..

it has an exception-handler, that calls
..
OnCriticalError(ex)
..
which again calls
TerminateClient().
with this string:
Resources.LogStream_Error
which is unfortunately
<data name="LogStream_Error" xml:space="preserve">
<value>{0}{1} Error has occurred and stream is terminated. {2}{0}</value>
</data>

But again, that resources-file Resources.resx does not seem to contain
any text resembling
"Error occurred, type: error, text: LogStreamManager: Request is aborted + context is null, ignoring exception"

I cannot find a source of
"context is null",
"ignoring exception"
or "request is aborted".

But I care about this, because currently our production servers are
logging plenty of this annoying message many times per minute,
so we would really like to know about those possible exceptions :-/.
Jakob Gaardsted 1 Reputation point

2021-10-05T09:22:21.683+00:00

I also have some suspicions about what it may concern.

My suspicion is, that some task or work has been started, in a separate task or thread, which is left running AFTER the original http request has finished or been aborted.
As I understand it, aspnet is not very happy about 'running background threads' that carry on outside of http request.

My suspicion for our own system, is that it accumulates an ever-growing list of 'some zombie thing(s) unsuccessfully trying to do something', in the background.

Unfortunately, this unhelpfully spammed log message is my main indication of this happening.

Some context: I inherited a greenfield dotnet core application, which had some optimistic but wrong attempts at doing e.g. db transactions with method annotations.
(this is of course broken, because the annotations will only execute AFTER the http response has been sent or initiated, and it's mighty hard to change a http 200 ok into a 401-forbidden, once your http response has already been sent.)
Worse, trying to do it after the http request has finished, causes problems with exceptions and error handling for that database code, out of context.

I may have fixed the immediate issues, but have no idea what other surprises await me still.
Heyns Emiliano 31 Reputation points

2021-10-12T12:13:58.927+00:00

You reached out to me by email, but I don't have sufficient rights to claim the issue ticket, so I can not proceed.
SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2021-10-12T12:49:57.927+00:00

Sure, reached out to you with description.
VIAL INGENIEROS 86 Reputation points

2022-02-02T04:25:24.54+00:00

Did anyone solve this issue?

Im getting the same error: Error occurred, type: error, text: LogStreamManager: Request is aborted + context is null, ignoring exception

I just created a flask application and deployed the Web App via Visual Studio Code to Azure App Service

1 answer

Your answer

Brendan Murphy 1 Reputation point

2021-10-01T02:45:51.133+00:00

I'm receiving the same error with a Node app as of a half hour ago.

I redeployed a working version of my app and I'm still getting the same error.
Tanmay Lad 1 Reputation point

2021-10-02T00:31:22.603+00:00

Yes, I have been getting the same message with a python app and setup that produced no errors in the past (last week or so).

Actual app performance is unaffected. I don't see anything in the portal that could be to do with log configuration.
SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2021-10-04T09:20:16.307+00:00

Thanks for reaching here! Could you please share document you are referring to help you better on this.

In case you want to Create a Python app using Azure App Service?
you may refer to steps on this official document link: https://learn.microsoft.com/en-us/azure/app-service/quickstart-python?tabs=bash&pivots=python-framework-flask

Let us know.
Heyns Emiliano 31 Reputation points

2021-10-04T13:34:56.993+00:00

I followed that tutorial, that's how I got my web app up.
Jakob Gaardsted 1 Reputation point

2021-10-05T09:07:13.363+00:00

The message seems to come from Kudu.Services.Performance.LogStreamManager.
However, the current version of LogStreamManager does not seem to contain any of the parts "request is aborted", "context is null" or "ignoring exception".
We experience the same issue with our production system, where the log will spam a lot of these messages instead of showing the actual log we need, with no indication of what is actually wrong.

I would expect parts of this error message in https://github.com/projectkudu/kudu/blob/master/Kudu.Services/Resources.resx.
Does anyone know if the error message was there, in an earlier version?
Jakob Gaardsted 1 Reputation point

2021-10-05T09:21:50.997+00:00

JakobGaardsted-2278 avatar image
0 Votes" 0
JakobGaardsted-2278 answered • 17 hours ago

I get this same error message. I'm assuming it's kudu, and related to
Kudu.Services.Performance.LogStreamManager.

However, I am unable to find any part of this string in
kudu\Kudu.Services\Diagnostics\LogStreamManager.cs ?
possibly, azure is running on a different version.
I see it has a member
..
private void OnError(object sender, ErrorEventArgs e)
..

it has an exception-handler, that calls
..
OnCriticalError(ex)
..
which again calls
TerminateClient().
with this string:
Resources.LogStream_Error
which is unfortunately
<data name="LogStream_Error" xml:space="preserve">
<value>{0}{1} Error has occurred and stream is terminated. {2}{0}</value>
</data>

But again, that resources-file Resources.resx does not seem to contain
any text resembling
"Error occurred, type: error, text: LogStreamManager: Request is aborted + context is null, ignoring exception"

I cannot find a source of
"context is null",
"ignoring exception"
or "request is aborted".

But I care about this, because currently our production servers are
logging plenty of this annoying message many times per minute,
so we would really like to know about those possible exceptions :-/.
Jakob Gaardsted 1 Reputation point

2021-10-05T09:22:21.683+00:00

I also have some suspicions about what it may concern.

My suspicion is, that some task or work has been started, in a separate task or thread, which is left running AFTER the original http request has finished or been aborted.
As I understand it, aspnet is not very happy about 'running background threads' that carry on outside of http request.

My suspicion for our own system, is that it accumulates an ever-growing list of 'some zombie thing(s) unsuccessfully trying to do something', in the background.

Unfortunately, this unhelpfully spammed log message is my main indication of this happening.

Some context: I inherited a greenfield dotnet core application, which had some optimistic but wrong attempts at doing e.g. db transactions with method annotations.
(this is of course broken, because the annotations will only execute AFTER the http response has been sent or initiated, and it's mighty hard to change a http 200 ok into a 401-forbidden, once your http response has already been sent.)
Worse, trying to do it after the http request has finished, causes problems with exceptions and error handling for that database code, out of context.

I may have fixed the immediate issues, but have no idea what other surprises await me still.
Heyns Emiliano 31 Reputation points

2021-10-12T12:13:58.927+00:00

You reached out to me by email, but I don't have sufficient rights to claim the issue ticket, so I can not proceed.
SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2021-10-12T12:49:57.927+00:00

Sure, reached out to you with description.
VIAL INGENIEROS 86 Reputation points

2022-02-02T04:25:24.54+00:00

Did anyone solve this issue?

Im getting the same error: Error occurred, type: error, text: LogStreamManager: Request is aborted + context is null, ignoring exception

I just created a flask application and deployed the Web App via Visual Studio Code to Azure App Service

Answer 1

Steven R 1

Why is this still an issue 5 months after it was report?

Share via

App Service python app: logging flooded with "LogStreamManager: Request is aborted + context is null"

1 answer

Your answer