I came in to a message from UptimeRobot that my server was down (4:20 am mytime). So I check the logs ...
The httpserver.log file ends at 4:02, with the last successful UptimeRobot check. The logs/web2py.log has 3 entries beyond that, at 4:05 Rocket is throwing an exception because self.sslobj.do_handshake() got "Connection reset by peer". Unfortunately, the traceback report doesn't indicate who the peer is .... is this something left over from the UR check, or a different client trying to access the service? ps -ef indicated that all my python processes were still running, but my browser timed out looking for the index page. I killed all the processes, restarted everything, and server is now responding normally to me and to UptimeRobot. Even though I'm preparing to switch to nginx, I'd like to better understand the Rocket "crash". The process had been started from the command line, and put in the background (and the parent shell eventually quitted). As an orphan process, no console messages are on the screen, and there is no more detail in the logs than the 3 tracebacks (all the same). The top level is rocket.py, line 590 (2.14.6), in listen(), which calls self.wrap_socket(), etc. Is there any place besides the log to look for artifacts that would give me more information? Oh, /var/log/messages has a "Possible SYN flooding pn port 443" entry at 4:05. Thanks for any pointers. Dave /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
