NP. perfectly kosher. For all matter and purposes, unless you need "transactional consistency" a separate db makes perfect sense. Those messages though indicate that the scheduler isn't finding the tables, or the tables have an incorrect structure.
On Tuesday, June 7, 2016 at 7:08:41 PM UTC+2, Andre Kozaczka wrote: > > Ah bummer! Thank you for looking into this for me. > > Through PythonAnywhere, I've added a Postgres database. I'm not sure if I > will migrate everything from MySQL to Postgres but I was thinking of just > starting off with the scheduler. I created a second DAL for the Postgres > and initialized the scheduler with it. All the tables are generated however > I'm getting error messages on the console and the task sits in QUEUED > status. > > I know I'm veering off from the original question, but is it kosher to > have a second database just for the scheduler? > > Here are the error messages: > 2016-06-07 14:54:57,026 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - Error retrieving status > 2016-06-07 14:54:57,335 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (0) > 2016-06-07 14:54:57,843 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (1) > 2016-06-07 14:54:58,353 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (2) > 2016-06-07 14:54:58,862 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (3) > 2016-06-07 14:54:59,370 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (4) > 2016-06-07 14:54:59,878 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (5) > 016-06-07 14:55:00,048 - web2py.scheduler.giles-liveconsole2#12039 - ERROR > - Error retrieving status > 2016-06-07 14:55:00,398 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (6) > 2016-06-07 14:55:00,908 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (7) > 2016-06-07 14:55:01,417 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (8) > 2016-06-07 14:55:01,972 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - TICKER: error assigning tasks (9) > 2016-06-07 14:55:03,066 - web2py.scheduler.giles-liveconsole2#12039 - > ERROR - Error retrieving status > > On Tuesday, June 7, 2016 at 8:07:32 AM UTC-4, Niphlod wrote: >> >> uhm, then it'll be quite impossible to fix it given the timeout is >> seemingly random. >> >> On Tuesday, June 7, 2016 at 1:19:07 PM UTC+2, Andre Kozaczka wrote: >>> >>> Yes, same lines. >>> >>> On Tuesday, June 7, 2016 at 5:54:37 AM UTC-4, Niphlod wrote: >>>> >>>> is the exception raised in the same lines ? >>>> >>>> On Tuesday, June 7, 2016 at 4:32:45 AM UTC+2, Andre Kozaczka wrote: >>>>> >>>>> >>>>> Well..... adding "sync_output=200" ended up working for tasks that >>>>> were just over the 300 second mark (where previously I was failing). I >>>>> changed the task length to 600 seconds and I'm back to failing. Ah... so >>>>> close!!! >>>>> >>>>> I tried changing sync_output to 100 but still failed. Unless you have >>>>> another trick up your sleeve, I may have to wave the white flag and ditch >>>>> MySQL.... and maybe give Postgres a try? >>>>> >>>>> -Andre >>>>> >>>> -- 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.
