An infinite loop causes this behavior. Don't Ask Me How I Know This :). Also, with Postgres, I *think* this has happened because certain migrations cause existing data in a field to fail a new constraint. This would happen if you make notnull=True on a field that already contains null. However, if your all your models execute on every request you will see this happen right away. It won't be intermittent.
On Friday, June 22, 2012 4:34:35 PM UTC-4, Maggs 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! > >
