search

mytardis / mytardis-app-atom

MyTardis app for Atom consumption.
4 stars 10 forks source link

Celery Issues #1

Closed steveandroulakis closed 12 years ago

steveandroulakis commented 12 years ago

Hey Tim,

Here's a screenie (for coloured syntax!) of the error I'm encountering trying to run django celery --beat. Looks like something isn't being wired up.

http://i.imgur.com/ZvLP7.png

(I think imgur hates OS X screenies.. renders large)

I'm running a fresh buildout install, all tests pass, preliminary clicking around of the site has worked, and the celery tables etc have been created fine.

Cheers, Steve

tjdett commented 12 years ago

Did you add tardis.apps.atom to your INSTALLED_APPS? Tasks are only detected for installed applications.

tjdett commented 12 years ago

Ah hah! I just saw the issue:

Schema matching query does not exist.

Have you run bin/django syncdb with the installed app? There's a initial_data.json fixtures file that needs to load.

steveandroulakis commented 12 years ago

I have, and I have a bunch of djcelery tables as a result..

Any other extra models I should be getting?

Also just to try and eliminate a possibility, I've tried this with sqlite and now mysql to no avail (thought it could have been concurrent db session handling issues).

Meetings this afternoon.. would love to pick this up again tomorrow and can answer email during day though.

Thanks for the help!

S

On Thu, Feb 2, 2012 at 11:46 AM, Tim Dettrick < reply@reply.github.com

wrote:

Ah hah! I just saw the issue:

"Schema matching query does not exist."

Have you run bin/django syncdb with the installed app? There's a initial_data.json fixtures file that needs to load.

Reply to this email directly or view it on GitHub: https://github.com/tjdett/mytardis-app-atom/issues/1#issuecomment-3770470

steveandroulakis commented 12 years ago

More info:

Seeing "Periodic tasks won't be dispatched unless you set the CELERYBEAT_SCHEDULER setting to djcelery.schedulers.DatabaseScheduler, or specify it using the -S option to celerybeat" in admin for that table.. perhaps that's telling.

Also 0 rows in each of the djcelery tables. Perhaps initial data hasn't loaded in the syncdb?

Gotta go. Cheers, Steve

On Thu, Feb 2, 2012 at 11:49 AM, Steve Androulakis < steve.androulakis@gmail.com> wrote:

I have, and I have a bunch of djcelery tables as a result..

Any other extra models I should be getting?

Also just to try and eliminate a possibility, I've tried this with sqlite and now mysql to no avail (thought it could have been concurrent db session handling issues).

Meetings this afternoon.. would love to pick this up again tomorrow and can answer email during day though.

Thanks for the help!

S

On Thu, Feb 2, 2012 at 11:46 AM, Tim Dettrick < reply@reply.github.com

wrote:

Ah hah! I just saw the issue:

"Schema matching query does not exist."

Have you run bin/django syncdb with the installed app? There's a initial_data.json fixtures file that needs to load.

Reply to this email directly or view it on GitHub: https://github.com/tjdett/mytardis-app-atom/issues/1#issuecomment-3770470

tjdett commented 12 years ago

Steve, I don't think the issue is with Celery. Your error message shows the job being created and dispatched, but it's failing because the parameter schema the atom app needs is absent.

I think I might take another look at it and see if I can load the fixtures on demand some other way.

steveandroulakis commented 12 years ago

I'll try and manually load the fixture when I get a chance. Thanks, that makes a lot of sense.

Steve

Sent from my iPhone

On 02/02/2012, at 2:21 PM, Tim Dettrick reply@reply.github.com wrote:

Steve, I don't think the issue is with Celery. Your error message shows the job being created and dispatched, but it's failing because the parameter schema the atom app needs is absent.

I think I might take another look at it and see if I can load the fixtures on demand some other way.

Reply to this email directly or view it on GitHub: https://github.com/tjdett/mytardis-app-atom/issues/1#issuecomment-3772000

steveandroulakis commented 12 years ago

Fixed! One must manually load the app's fixture:

bin/django loaddata tardis/apps/atom/fixtures/initial_data.json

Impending dev list email about this. It's awesome and this kind of mechanism is the future of MyTardis..

Steve

On Thu, Feb 2, 2012 at 2:22 PM, Steve Androulakis < steve.androulakis@gmail.com> wrote:

I'll try and manually load the fixture when I get a chance. Thanks, that makes a lot of sense.

Steve

Sent from my iPhone

On 02/02/2012, at 2:21 PM, Tim Dettrick < reply@reply.github.com

wrote:

Steve, I don't think the issue is with Celery. Your error message shows the job being created and dispatched, but it's failing because the parameter schema the atom app needs is absent.

I think I might take another look at it and see if I can load the fixtures on demand some other way.

Reply to this email directly or view it on GitHub:

https://github.com/tjdett/mytardis-app-atom/issues/1#issuecomment-3772000