glad you worked it out but IMHO a request in appadmin should have created
.table AND the underlying structure on the db (in other words, there
shouldn't be a place on the universe where .table files are created but the
underlying tables on the backend are not created.)
On Monday, December 21, 2
Done!
Here is the solution:
Delete scheduler.py file
Delete scheduler table files
Delete scheduler tables in db
Create again the scheduler
At this point running the admin just create the table files but not the
tables in the db
Restarting the server db tables are created
AND! Now scheduler works
there's no way .table files are created but tables aren't ... please triple
check your settings
On Sunday, December 20, 2015 at 9:28:39 PM UTC+1, Gael Princivalle wrote:
>
> Now tables files are created in the database folder, but tables are not
> created in the postgress DB.
> Error in alw
Now tables files are created in the database folder, but tables are not
created in the postgress DB.
Error in always the same when I try to open a table from the administration
interface.
ProgrammingError: relation "scheduler_worker" does not exist
LINE 1: SELECT count(*) FROM "scheduler_worker"
you just had to delete corresponding .table files. scheduler tables are
created as soon as the scheduler is istantiated, unless migrations are
turned off.
On Friday, December 18, 2015 at 4:17:48 PM UTC+1, Gael Princivalle wrote:
>
> No I don't.
>
> But now I have:
> Dropped all tables in the dat
No I don't.
But now I have:
Dropped all tables in the database folder
Delete all scheduler tables in the postgress database.
Delete the scheduler
Create the scheduler.
I still have the same db error, for example for workers:
SELECT count(*) FROM "scheduler_worker" WHERE ("scheduler_wo...
table f
when you dropped tables, did you remember to delete the corresponding
*.table files from the databases/ folder ?
On Friday, December 18, 2015 at 12:47:38 PM UTC+1, Gael Princivalle wrote:
>
> >scheduler tables can be dropped manually
> Done
>
> >deleting scheduler.py also.
> Done
>
> >But I still
>scheduler tables can be dropped manually
Done
>deleting scheduler.py also.
Done
>But I still don't think that it's the way to fix the issue you're facing.
Well I'm not able to understand which is this problem, as when I create a
scheduler in a new app tasks are running.
For the moment creating
scheduler tables can be dropped manually
deleting scheduler.py also.
But I still don't think that it's the way to fix the issue you're facing.
On Friday, December 18, 2015 at 11:22:57 AM UTC+1, Gael Princivalle wrote:
>
> >delete what ? the istantiation ?
>
> Delete the scheduler.py file from mod
>delete what ? the istantiation ?
Delete the scheduler.py file from models and all scheduler tables.
How can I do it?
Il giorno venerdì 18 dicembre 2015 10:48:23 UTC+1, Niphlod ha scritto:
>
>
>
> On Friday, December 18, 2015 at 10:45:22 AM UTC+1, Gael Princivalle wrote:
>>
>> I've set a schedul
On Friday, December 18, 2015 at 10:45:22 AM UTC+1, Gael Princivalle wrote:
>
> I've set a scheduler in a new application and tasks are running.
>
> So probably there's a problem when a app comes from a previous web2py
> version.
>
as long as you let migration happen, no issues whatsoever.
>
I've set a scheduler in a new application and tasks are running.
So probably there's a problem when a app comes from a previous web2py
version.
Anyway I think it can be resolved deleting the scheduler and create it
again, but I've tried to:
Killing the worker - Ok
Delete Scheduler Ko
When I del
Thanks Niphlod.
>So, here it is the breakdown of the possible issues:
>- are tasks QUEUED or ASSIGNED ?
QUEUED. But if I set the net run time to now + 2 minutes I can check that
task don't run.
Status options don't have ASSIGNED.
>If they are QUEUED, either they can't be executed yet (i.e. start
I thought more people liked to see the code : I find myself explaining
scheduler internals more often than I'd like to :P
soo. worker names worker names are used to identify a worker
process (it's enforced as unique in the model)...
I'll reply to some ideal "FAQ" questions
- Why
14 matches
Mail list logo
