Unfortunately those logs did not tell me anything I didn't already know.
Besides errors that came up while I was developing and testing, there was
nothing new in there. The application is still crashing once a day and
nothing in the console output or the error page of the site have told me
anything useful.
I do have an alternate question, however.
I see this error very frequently in the console log:
ERROR:Rocket.Errors.Port8080:Traceback (most recent call last):
File "/opt/apps/web2py/gluon/rocket.py", line 562, in listen
sock = self.wrap_socket(sock)
File "/opt/apps/web2py/gluon/rocket.py", line 506, in wrap_socket
ssl_version = ssl.PROTOCOL_SSLv23)
File "/usr/lib/python2.7/ssl.py", line 381, in wrap_socket
ciphers=ciphers)
File "/usr/lib/python2.7/ssl.py", line 143, in __init__
self.do_handshake()
File "/usr/lib/python2.7/ssl.py", line 305, in do_handshake
self._sslobj.do_handshake()
error: [Errno 104] Connection reset by peer
And when I say frequently I don't mean a few times a day, I mean constantly
throughout the day. I realize this is caused by a client not waiting for
the site to load before navigating away, however it doesn't make sense that
this would happen that often. Like I explained earlier, this is a
healthcheck application used by our 24x7 support teams to monitor the
health of our servers, they will have the application sitting in a web
browser constantly. They wouldn't be navigating away every few minutes.
Does anyone know any other way this error could be caused so frequently?
Thanks!
On Friday, June 22, 2012 1:34:35 PM UTC-7, msmagoo wrote:
>
> Hi all,
>
> I have a web2py healthcheck monitoring application. Basically the only
> thing the
> application does is make database queries to find healthcheck data and
> make REST
> api calls to a separate web2py application for information on the
> environment.
>
> Recently the application has been "crashing" at least once a day. The
> web2py
> process still exists, but users are unable to connect to the application.
> There
> are no errors in the logs or any useful information in the httpserver.log,
> it's
> like web2py just hangs and I have to restart it. I'm at my wits end trying
> to
> figure out what is happening so I figured I'd see if anyone has
> experienced this
> before or has any tips on log files I'm unaware of to check.
>
> Thanks!
>
>
