Letting the scheduler recreate the tables did the trick; thanks! On Monday, May 30, 2016 at 8:48:11 AM UTC-4, Niphlod wrote: > > that error comes only on two codepaths: tables that are missing columns > (and/or have different column types) and database locks. > try dropping tables, letting scheduler recreate them and see what happens. > > On Monday, May 30, 2016 at 1:53:04 PM UTC+2, Scott Hunter wrote: >> >> I have an appliance hosted on pythonanywhere which uses the Scheduler >> (invoked using a separate web2py process with the -K switch). >> >> This setup in my test environment (OS X at home) works fine, but on >> pythonanywhere, the scheduler process generates a stream of errors like: >> >> ERROR:web2py.scheduler.giles-livetask2#30970:Error coordinating TICKER >> ERROR:web2py.scheduler.giles-livetask2#30970: error popping tasks >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970: error popping tasks >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970: error popping tasks >> ERROR:web2py.scheduler.giles-livetask2#30970:Error coordinating TICKER >> ERROR:web2py.scheduler.giles-livetask2#30970: error popping tasks >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970: error popping tasks >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> ERROR:web2py.scheduler.giles-livetask2#30970: error popping tasks >> ERROR:web2py.scheduler.giles-livetask2#30970:Error retrieving status >> >> >> Attempts to schedule a task fail to even have a new task record inserted, >> much less executing that task. >> >> It was working a week ago. I thought it might be due to upgrading to >> 2.14.6, but the last successful tasks show >> "web2py.scheduler.giles-livetask", so maybe the problem came after that >> upgrade. >> >> I thought maybe the scheduler database was corrupted, but I can view the >> records via the admin appliance. >> >> Any suggestions as to what I should investigate next would be appreciated. >> >> - Scott >> >
-- 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.
