are you running sqlite ? if so, AT LEAST run the scheduler on a different sqlite database, as sqlite doesn't really withstand lots of concurrent writes (that the scheduler does). if your web app shares the same sqlite db as the scheduler, it gets blocked whenever the scheduler writes something to the db (which happens a LOT!)
On Thursday, November 17, 2016 at 1:25:50 AM UTC+1, Pengfei Yu wrote: > > Hi, > > I am using web2py as framework for my web application and using the > built-in scheduler for the user tasks. They are working fine for more than > one years. > During the recent several days, I found that whenever I start a task to > scheduler, the apache web server is not working, it is stuck in somewhere > and give 500 internal server error. If I kill the task process or wait > until the task completed, then the apache server goes back to normal. I > checked the error log file of apache server, and the error message is > "Script timed out before returning headers: wsgihandler.py". > I think the scheduler task run is independent of the apache web server and > just run in background in parallel. I don't know what could be the reason > for this problem. The only thing I changed for the scheduler is the change > of migrate from True to False when I initiate the scheduler: > scheduler = Scheduler(db,dict(run=run),migrate=False) > > Did anyone encounter similar problem before? I will be very appreciated if > someone can provide me a hint to solve this problem. > > Thanks very much! > > -- 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.
