Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings about __version__, tz and utc_enabled #1923

Closed
yuvadm opened this issue Mar 17, 2014 · 6 comments
Closed

Warnings about __version__, tz and utc_enabled #1923

yuvadm opened this issue Mar 17, 2014 · 6 comments

Comments

@yuvadm
Copy link

yuvadm commented Mar 17, 2014

Every default celery worker running with -B prints the following warnings:

[2014-03-17 09:37:00,741: WARNING/Beat] Reset: Account for new __version__ field
[2014-03-17 09:37:00,742: WARNING/Beat] Reset: Account for new tz field
[2014-03-17 09:37:00,742: WARNING/Beat] Reset: Account for new utc_enabled field

It is not clear why they are printed, what their meaning is, or how to fix them if they actually indicate of a problematic configuration.

Can anyone shed some light on this?

@yuvadm yuvadm changed the title Warnings abous __version__, tz and utc_enabled Warnings about __version__, tz and utc_enabled Mar 17, 2014
@ask
Copy link
Contributor

ask commented Mar 17, 2014

The log messages specifically means that it's upgrading a celerybeat-schedule file, but in your case I guess it's there because it had to create one (no existing db) or the db was broken.

@yuvadm
Copy link
Author

yuvadm commented Mar 17, 2014

@ask for a first run it makes sense, but this happens on subsequent start of the worker+beat process. Is my schedule not persistent? Did I perhaps forget to set Redis as the schedule backend? (Checking...)

@ask ask closed this as completed in 9d026fa Mar 17, 2014
@ask ask reopened this Mar 17, 2014
@ask
Copy link
Contributor

ask commented Mar 17, 2014

@yuvadm I'm not sure but it does seem like the celerybeat-schedule file is removed maybe?

@yuvadm
Copy link
Author

yuvadm commented Mar 17, 2014

@ask these are tasks running on Heroku. Do I need to explicitly tell celery to use Redis somehow? I can't find a config for this, and Redis is properly configured otherwise.

@ask
Copy link
Contributor

ask commented Mar 17, 2014

@yuvadm This is not a regular db, it's a DBM file named celerybeat-schedule, it may end up with a suffix at the end (often .db, but this depends on the underlying dbm implementation). It will be created in the same directory as the worker, but you can specify a custom path using the --schedule argument.

@yuvadm
Copy link
Author

yuvadm commented Mar 17, 2014

@ask yeah I'm familiar with the file, I just thought there's a way to set the scheduler to use Redis as the backend for that purpose. But I don't really care about it. Just wanted to make sure these warning aren't hiding something sneaky. Thanks!

@yuvadm yuvadm closed this as completed Mar 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants