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 <neum...@wu.ac.at> wrote: > > 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. at the end of the config file, or via other means such as nsshell), > and it should lead you to the place where the problem occurs. > > Hope, this helps > > -g > > [1] > https://bitbucket.org/naviserver/naviserver/commits/d1c8de59f417b833ff1a8b3b61bf1aea63ac5a94 > > <https://bitbucket.org/naviserver/naviserver/commits/d1c8de59f417b833ff1a8b3b61bf1aea63ac5a94> > On 11.03.20 17:39, THORPE MAYES via naviserver-devel wrote: >> 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 logs thinking that the event was related to something. I >> cannot see any relationship. >> >> I am just serving web pages built using tcl that utilize data generated from >> a database. There is nothing I do that is sophisticated. >> >> For the moment I am monitoring the issue. We will see what happens. >> >> Again, thank you for your response (and your work on the naviserver project). >> >> Thorpe >> >>> On Mar 11, 2020, at 9:18 AM, Gustaf Neumann <neum...@wu.ac.at >>> <mailto:neum...@wu.ac.at>> wrote: >>> >>> 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 proxy to some backend host, >>> but the backend host does not answer. We checked our logs >>> on the busy servers over the last weeks, but could trace the >>> few 503 errors to cases, where the backend server was rebooted. >>> >>> it is possible to intensify the tracing of NaviServer in such cases, >>> but it would certainly be good to learn more about your >>> situation.... Can you check, if there is some unresponsible >>> backend server is involved in your case? >>> >>> all the best >>> >>> -g >>> >>> On 10.03.20 20:12, THORPE MAYES via naviserver-devel wrote: >>>> HI, >>>> >>>> I am getting this error: >>>> >>>> Service Unavailable >>>> The server is temporarily unable to service your request. Please try again >>>> later. >>>> NaviServer/4.99.19 on >>>> >>>> Restarting the server software fixes the issue, but I need a better >>>> solution. >>>> >>>> What causes this? How can I detect when the server is in this state? >>>> >>>> Thank you, >>>> > _______________________________________________ > naviserver-devel mailing list > naviserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/naviserver-devel
_______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
