[WARNING] [_granian.asgi.io] ASGI transport error: SendError

[MBe-iUS]

Hi,

I'm using Paperless NGX which switched recently to Granian (v2.2) as a webserver instead of Uvicorn.

In my logs I discovered such warnings: [WARNING] [_granian.asgi.io] ASGI transport error: SendError { .. }, unfortunately they do not tell more.

In this issue I addressed this, the maintainers have forwarded me to this repo.

I found related issues #286 and #412 , but couldn't identify similarities between the Paperless issue and the reported issues, except for the warning.

Is there any advice around how to find the cause for the message?

Thanks

[gi0baro]

@MBe-iUS that log line is there just to inform you Granian wasn't able to send data through the underlying connection.
99.9% of the time that just means the client already disconnected, so you shouldn't experience any actual issue.

I have a change planned for 2.2.3 which should lower down the amount of those messages.

[afrank73]

I also use paperless-ngx version 2.15.3 and have exactly the same warnings and errors as here
However, during tests I was able to find out that these warnings and errors only occur when the page is accessed via a domain, e.g. “ht*ps://paperless.domain.tld”. When calling via the internal IP, e.g. “192.168.1.100:8000”, this error is not displayed.

In the meantime, logging nois for ASGI has been reduced with release 2.2.3.

But what does “[ERROR] [_granian.utils] Application callable raised an exception” mean?
What does the statement “99.9% of the time that just means the client already disconnected...” mean in this context?

Many Thanks

[gi0baro]

However, during tests I was able to find out that these warnings and errors only occur when the page is accessed via a domain, e.g. “ht*ps://paperless.domain.tld”. When calling via the internal IP, e.g. “192.168.1.100:8000”, this error is not displayed.

I'm quite confident this is just a casualty.

But what does “[ERROR] [_granian.utils] Application callable raised an exception” mean?

This means the ASGI application (paperless/django in your case) raised an uncatched exception, in fact the rest of the message logs the actual exception.

What does the statement “99.9% of the time that just means the client already disconnected...” mean in this context?

You're mixing 2 different things, the statement is referred to the ASGI transport error: SendError { .. } message, and given the OP, it means the websocket got disconnected and thus following messages cannot being sent over.

[afrank73]

Many thanks for the explanations.
I will completely re-install version 2.15.3 of paperless-ngx in the next few days.

[gregbtm]

Came here due to the same error. Running paperless latest version 2.16.2 and getting the error whilst viewing with ip and domain.

[gi0baro]

Came here due to the same error. Running paperless latest version 2.16.2 and getting the error whilst viewing with ip and domain.

Please ask paperless maintainers to upgrade Granian to latest available version.

[shamoon]

Thanks. Yes there is a PR pending merge, no need for other paperless users to chime in here if it’s just “me too”

[gregbtm]

Thanks. Yes there is a PR pending merge, no need for other paperless users to chime in here if it’s just “me too”

To be fair, mine was more of a 'On testing, issue persists when using IP and domain' due to the comment above, rather than a 'Me too' - just in case that helped negate the condition.

Take care :)

[MBe-iUS]

Indeed, since v2.3.2 I couldn't find any such messages in my logs! Thank you for solving this!