Gustaf,
Thank you for the follow up and the direction.
I will implement you suggestion.
So far the problem has not reoccurred.
Best regards,
Thorpe
> On Mar 14, 2020, at 3:22 PM, Gustaf Neumann wrote:
>
> Dear Thorpe,
>
> the commit [1] introduces more more log severity named "Debug(timeo
Dear Thorpe,
the commit [1] introduces more more log severity named "Debug(timeout)",
which causes - when switched on - the server to write timeout related
entries to the system log, such this can be used as well on busy servers.
Just turn it on with
ns_logctl severity Debug(timeout) on
(e.g
Gustaf,
Thank you very much for your response.
The server stands alone.
This has happened twice in the past 10 days. Never before for the last 20 years
(unless I induced it).
I looked at the cpu usage, which tells me if we are in a never-ending loop. All
was well there.
I looked at the log
Dear Thorpe,
i just checked the source code, and found two situations, when the server
returns a 503 HTTP status:
a) The Tcl code issues a "ns_returnunavailable"
b) The Tcl-/ADP-request ends in a NS_TIMEOUT
I would exclude (a) for now. (b) can happen e.g. when
one uses NaviServer as a reverse p
