My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Last 30 days

  • Dec 15, 2009
    Install (How to install django-cron) Wiki page commented on by sebastien.ramage   -   Hi ! Good project ! I have a question : Is it possible to run a job at an exact time ? for example every day at 04:00 ? Because if I set run_every = 86400, ok the job run every 24H but I don't really know when, it depends of the last run. so it's a problem to me...
    Hi ! Good project ! I have a question : Is it possible to run a job at an exact time ? for example every day at 04:00 ? Because if I set run_every = 86400, ok the job run every 24H but I don't really know when, it depends of the last run. so it's a problem to me...
  • Dec 12, 2009
    Install (How to install django-cron) Wiki page commented on by redarrow...@hotmail.com   -   Great project. A simple question: I want to run a job only once a certain time after a user action. How can I do this? An example: 1. A use triggers an event. 2. Two hours later I want an action to be executed.
    Great project. A simple question: I want to run a job only once a certain time after a user action. How can I do this? An example: 1. A use triggers an event. 2. Two hours later I want an action to be executed.
  • Dec 06, 2009
    Install (How to install django-cron) Wiki page commented on by rviotti   -   The installation instructions above are missing a step: run *manage.py syncdb* to create the *django_cron_job* and *django_cron_cron* database tables. Yes, this will work with the development server.
    The installation instructions above are missing a step: run *manage.py syncdb* to create the *django_cron_job* and *django_cron_cron* database tables. Yes, this will work with the development server.

Older

  • Nov 10, 2009
    Install (How to install django-cron) Wiki page commented on by orest.gaboda   -   >> Comment by zhuxiyuan1, Oct 19, 2009 >>I set up by following the instruction exactly but the cron does not work. The same, it works only once when initialized. So it seems to me we need to use standart linux crontab with django-cron for correctly working.
    >> Comment by zhuxiyuan1, Oct 19, 2009 >>I set up by following the instruction exactly but the cron does not work. The same, it works only once when initialized. So it seems to me we need to use standart linux crontab with django-cron for correctly working.
  • Nov 09, 2009
    Install (How to install django-cron) Wiki page commented on by navyajay06   -   is it possible to install django cron in apache server
    is it possible to install django cron in apache server
  • Oct 28, 2009
    issue 17 (autodiscover blocks syncdb) commented on by Jim.mixt...@gmail.com   -   Is this still a problem? I think I may have fixed it
    Is this still a problem? I think I may have fixed it
  • Oct 28, 2009
    issue 19 (last_run field in django_cron_job table is renewing every ti...) commented on by Jim.mixt...@gmail.com   -   I might be that `last_run` time is correct, and that it's running the job every time a page is loaded let me know if that is the case. If so, we'll need to find a way of being more respectful of the `run_frequency`
    I might be that `last_run` time is correct, and that it's running the job every time a page is loaded let me know if that is the case. If so, we'll need to find a way of being more respectful of the `run_frequency`
  • Oct 28, 2009
    issue 21 (Bug when cron period > 1 day) Status changed by Jim.mixt...@gmail.com   -   Thanks for the fix -> just checked it in
    Status: Fixed
    Thanks for the fix -> just checked it in
    Status: Fixed
  • Oct 28, 2009
    r32 (fixed bug 21 (google code) Cron jobs can now be on a timesca...) committed by Jim.mixt...@gmail.com   -   fixed bug 21 (google code) Cron jobs can now be on a timescale greater than 1 day it seems bespin has a strange idea of tabs... fixed
    fixed bug 21 (google code) Cron jobs can now be on a timescale greater than 1 day it seems bespin has a strange idea of tabs... fixed
  • Oct 28, 2009
    FAQ (A few common questions) Wiki page edited by Jim.mixt...@gmail.com   -   Revision r31 Edited wiki page through web user interface.
    Revision r31 Edited wiki page through web user interface.
  • Oct 28, 2009
    FAQ (A few common questions) Wiki page edited by Jim.mixt...@gmail.com   -   Revision r30 Edited wiki page through web user interface.
    Revision r30 Edited wiki page through web user interface.
  • Oct 28, 2009
    FAQ (A few common questions) Wiki page edited by Jim.mixt...@gmail.com   -   Revision r29 Edited wiki page through web user interface.
    Revision r29 Edited wiki page through web user interface.
  • Oct 28, 2009
    FAQ (A few common questions) Wiki page edited by Jim.mixt...@gmail.com   -   Revision r28 Edited wiki page through web user interface.
    Revision r28 Edited wiki page through web user interface.
  • Oct 28, 2009
    FAQ (A few common questions) Wiki page added by Jim.mixt...@gmail.com   -   Revision r27 Created wiki page through web user interface.
    Revision r27 Created wiki page through web user interface.
  • Oct 28, 2009
    issue 22 (django cron not working) commented on by zhuxiyuan1   -   It seems like that refactoring is not the issue. The cron worked once or twice previously but not any more. Now I've no longer have any errors but the cron just doesn't work. BTW I have a technical question here: Why the cron has to be so sophisticated? I have written a very simple one. Could you please have a quick look and tell me why it is a bad idea? many thanks! from threading import Timer import time t = 10 def cronjob(): def job(): # do something job() Timer(t, cronjob).start() cronjob()
    It seems like that refactoring is not the issue. The cron worked once or twice previously but not any more. Now I've no longer have any errors but the cron just doesn't work. BTW I have a technical question here: Why the cron has to be so sophisticated? I have written a very simple one. Could you please have a quick look and tell me why it is a bad idea? many thanks! from threading import Timer import time t = 10 def cronjob(): def job(): # do something job() Timer(t, cronjob).start() cronjob()
  • Oct 27, 2009
    issue 18 (returned more than one Job ( cronScheduler.register(TimedRot...) commented on by Jim.mixt...@gmail.com   -   ah - good find! did you also find a solution? Obviously you can manually delete the app from the database, but it would be preferrable to do a get_or_create, which does not include the "run_every" and just update the "run_every" attribute when it is changed
    ah - good find! did you also find a solution? Obviously you can manually delete the app from the database, but it would be preferrable to do a get_or_create, which does not include the "run_every" and just update the "run_every" attribute when it is changed
  • Oct 27, 2009
    issue 22 (django cron not working) commented on by Jim.mixt...@gmail.com   -   It looks like you may have renamed the app from django_cron to cronapp. I'm not sure if you can do that
    It looks like you may have renamed the app from django_cron to cronapp. I'm not sure if you can do that
  • Oct 26, 2009
    issue 4 (simple enhancement: run cronjobs from management.py) commented on by andybak   -   A further comment is that I couldn't get django-cron working until I used the patch. I didn't try too hard as I preferred to use the manage.py method (shared hosting so memory is at a premium and I thought the original method of execution might leave an instance of Django hanging around)
    A further comment is that I couldn't get django-cron working until I used the patch. I didn't try too hard as I preferred to use the manage.py method (shared hosting so memory is at a premium and I thought the original method of execution might leave an instance of Django hanging around)
  • Oct 26, 2009
    issue 4 (simple enhancement: run cronjobs from management.py) commented on by andybak   -   I applied the patch manually to r26 and it works perfectly. (by manually I mean by reading the patch and making the individual changes).
    I applied the patch manually to r26 and it works perfectly. (by manually I mean by reading the patch and making the individual changes).
  • Oct 24, 2009
    Install (How to install django-cron) Wiki page commented on by jes...@taxboel.dk   -   Can this work with the development server? eg: running it via "python manage.py runserver"
    Can this work with the development server? eg: running it via "python manage.py runserver"
  • Oct 23, 2009
    issue 4 (simple enhancement: run cronjobs from management.py) commented on by andybak   -   I think this patch is an excellent idea. I'm on the verge of writing my own cron-manager to do exactly that.
    I think this patch is an excellent idea. I'm on the verge of writing my own cron-manager to do exactly that.
  • Oct 21, 2009
    issue 22 (django cron not working) commented on by zhuxiyuan1   -   BTW, the apache error log: [Wed Oct 21 09:22:08 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert(). [Wed Oct 21 09:22:08 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert(). [Wed Oct 21 09:22:14 2009] [error] /var/lib/python-support/python2.6/MySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated [Wed Oct 21 09:22:14 2009] [error] from sets import ImmutableSet [Wed Oct 21 09:22:16 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert(). [Wed Oct 21 09:22:16 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert().
    BTW, the apache error log: [Wed Oct 21 09:22:08 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert(). [Wed Oct 21 09:22:08 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert(). [Wed Oct 21 09:22:14 2009] [error] /var/lib/python-support/python2.6/MySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated [Wed Oct 21 09:22:14 2009] [error] from sets import ImmutableSet [Wed Oct 21 09:22:16 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert(). [Wed Oct 21 09:22:16 2009] [error] [client 127.0.0.1] mod_mime_magic: invalid type 0 in mconvert().
  • Oct 19, 2009
    issue 22 (django cron not working) commented on by zhuxiyuan1   -   I think that I should summarise my problem again: 1. Create a new project and add django_cron.autodiscover() to your urls.py 2. Run manage syncdb 3. I've got an error: /var/lib/python-support/python2.6/MySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated from sets import ImmutableSet Error: No module named cronapp.errors
    I think that I should summarise my problem again: 1. Create a new project and add django_cron.autodiscover() to your urls.py 2. Run manage syncdb 3. I've got an error: /var/lib/python-support/python2.6/MySQLdb/__init__.py:34: DeprecationWarning: the sets module is deprecated from sets import ImmutableSet Error: No module named cronapp.errors
  • Oct 19, 2009
    issue 22 (django cron not working) reported by zhuxiyuan1   -   Hi Jim, Sorry to disturb you. I set up my cron by following the instruction exactly but the it still does not work. What do you think could be the reason? from app.cron import cronScheduler from app.cron import Job # This is a function I wrote to check a feedback email address and add it to our database. Replace with your own imports class Cron_task(Job): """ Cron Job that checks the lgr users mailbox and adds any approved senders' attachments to the db """ # run every 300 seconds (5 minutes) run_every = 5 def job(self): # This will be executed every 5 minutes #print_something() f = open('/tmp/sample.txt', 'a') f.write("Hi Paul\n") f.close() cronScheduler.register(Cron_task) I used "tail -f /tmp/sample.txt" to check the update but nothing happened. Many thanks! BTW, when I tried "python manage.py syncdb" The following error came out: "Error: No module named cronapp.errors" What is "cronapp.errors"?! Kind regards, Joe
    Hi Jim, Sorry to disturb you. I set up my cron by following the instruction exactly but the it still does not work. What do you think could be the reason? from app.cron import cronScheduler from app.cron import Job # This is a function I wrote to check a feedback email address and add it to our database. Replace with your own imports class Cron_task(Job): """ Cron Job that checks the lgr users mailbox and adds any approved senders' attachments to the db """ # run every 300 seconds (5 minutes) run_every = 5 def job(self): # This will be executed every 5 minutes #print_something() f = open('/tmp/sample.txt', 'a') f.write("Hi Paul\n") f.close() cronScheduler.register(Cron_task) I used "tail -f /tmp/sample.txt" to check the update but nothing happened. Many thanks! BTW, when I tried "python manage.py syncdb" The following error came out: "Error: No module named cronapp.errors" What is "cronapp.errors"?! Kind regards, Joe
  • Oct 19, 2009
    Install (How to install django-cron) Wiki page commented on by zhuxiyuan1   -   I set up by following the instruction exactly but the cron does not work.
    I set up by following the instruction exactly but the cron does not work.
  • Oct 05, 2009
    issue 21 (Bug when cron period > 1 day) commented on by joha...@wanadoo.fr   -   Oops, made a mistake, the error occurs in base.py:101
    Oops, made a mistake, the error occurs in base.py:101
  • Sep 30, 2009
    issue 21 (Bug when cron period > 1 day) reported by joha...@wanadoo.fr   -   What steps will reproduce the problem? 1. set a cron to be run once a day for example 2. wait ... 3. Nothing will happen :( The bug is in __init__.py, line 26: if (datetime.now() - job.last_run).seconds > job.run_frequency: timedelta.seconds doesn't convert a timedelta into seconds, bu returns the seconds part of the timedelta, between 0 and 86399 inclusive (http://docs.python.org/library/datetime.html#datetime-timedelta ). The right syntax would be: delta = datetime.now() - job.last_run if delta.seconds + 86400*delta.days > job.run_frequency: Thanks in advance, Johan
    What steps will reproduce the problem? 1. set a cron to be run once a day for example 2. wait ... 3. Nothing will happen :( The bug is in __init__.py, line 26: if (datetime.now() - job.last_run).seconds > job.run_frequency: timedelta.seconds doesn't convert a timedelta into seconds, bu returns the seconds part of the timedelta, between 0 and 86399 inclusive (http://docs.python.org/library/datetime.html#datetime-timedelta ). The right syntax would be: delta = datetime.now() - job.last_run if delta.seconds + 86400*delta.days > job.run_frequency: Thanks in advance, Johan
  • Sep 17, 2009
    r26 (more updates :) ) committed by Jim.mixt...@gmail.com   -   more updates :)
    more updates :)
  • Sep 17, 2009
    r25 (removed the code that deletes old jobs... it's no longer nec...) committed by Jim.mixt...@gmail.com   -   removed the code that deletes old jobs... it's no longer necessary because the "last run time" is stored in the DB. We can just check that for any jobs instead of blindly clearing all the jobs on init
    removed the code that deletes old jobs... it's no longer necessary because the "last run time" is stored in the DB. We can just check that for any jobs instead of blindly clearing all the jobs on init
  • Sep 17, 2009
    r24 (fixed issues with breaking the queue when debugging ) committed by Jim.mixt...@gmail.com   -   fixed issues with breaking the queue when debugging
    fixed issues with breaking the queue when debugging
  • Sep 17, 2009
    issue 16 (syncdb table creation fails using postgresql + psycopg2) Status changed by Jim.mixt...@gmail.com   -   I don't think this is an issue anymore, but I could be wrong. Please let me know if anyone gets it. Marking as fixed (Will re-open if anyone still has the problem)
    Status: Fixed
    I don't think this is an issue anymore, but I could be wrong. Please let me know if anyone gets it. Marking as fixed (Will re-open if anyone still has the problem)
    Status: Fixed
  • Sep 01, 2009
    Install (How to install django-cron) Wiki page commented on by florian....@gmx.at   -   Don't forget to mention the CRON_POLLING_FREQUENCY in settings times how often django_cron will look for jobs to run. (look in base.py)
    Don't forget to mention the CRON_POLLING_FREQUENCY in settings times how often django_cron will look for jobs to run. (look in base.py)
  • Aug 29, 2009
    Install (How to install django-cron) Wiki page commented on by Bell.W.D   -   "django_cron is best used to execute tasks that occur relatively often" Would someone care to comment about why this should be so?
    "django_cron is best used to execute tasks that occur relatively often" Would someone care to comment about why this should be so?
  • Aug 27, 2009
    issue 11 (Syncdb exits on fresh install while executing base.py) commented on by whit537   -   For the record, the change you have to make is to import and use cronScheduler instead of cron.
    For the record, the change you have to make is to import and use cronScheduler instead of cron.
  • Aug 23, 2009
    issue 16 (syncdb table creation fails using postgresql + psycopg2) commented on by nbvFOUR   -   ^^ yeah any news? I really want to use this app, but i'm using psygopg2 so no worky :(
    ^^ yeah any news? I really want to use this app, but i'm using psygopg2 so no worky :(
  • Aug 14, 2009
    issue 20 (Suggestion: When a job errors and is de-qued, an email shoul...) Status changed by Jim.mixt...@gmail.com   -   Good idea...
    Status: Accepted
    Good idea...
    Status: Accepted
  • Aug 12, 2009
    issue 16 (syncdb table creation fails using postgresql + psycopg2) commented on by ninethval   -   Any news on this item?
    Any news on this item?
  • Jul 26, 2009
    issue 20 (Suggestion: When a job errors and is de-qued, an email shoul...) reported by ja...@jarofgreen.co.uk   -   The Problem: Systems failing silently is bad! If your users rely on a cron job running, and suddenly it stops, and the admin's don't realise, your in trouble. Suggestion: In the "except Exception:" bit of CronScheduler.execute that de-ques a job, send a email to settings.ADMINS.
    The Problem: Systems failing silently is bad! If your users rely on a cron job running, and suddenly it stops, and the admin's don't realise, your in trouble. Suggestion: In the "except Exception:" bit of CronScheduler.execute that de-ques a job, send a email to settings.ADMINS.
  • Jul 22, 2009
    issue 19 (last_run field in django_cron_job table is renewing every ti...) reported by dmitry.krivashin   -   What steps will reproduce the problem? 1. Run apache in prefork mode 2. Renew random page from your app for several times 3. Check last_run field in django_cron_job table. The field always contains the time of last request What is the expected output? What do you see instead? This field should be renewed only at server startup and after a job was completed What version of the product are you using? On what operating system? Please provide any additional information below. Everything was OK when I was using apache in worker mode. I used such directives as: PythonAutoReload Off and MaxRequestsPerChild 0 But due to some reasons of compatibility I should run apache only in prefork mode and now I'm getting such type of problem.
    What steps will reproduce the problem? 1. Run apache in prefork mode 2. Renew random page from your app for several times 3. Check last_run field in django_cron_job table. The field always contains the time of last request What is the expected output? What do you see instead? This field should be renewed only at server startup and after a job was completed What version of the product are you using? On what operating system? Please provide any additional information below. Everything was OK when I was using apache in worker mode. I used such directives as: PythonAutoReload Off and MaxRequestsPerChild 0 But due to some reasons of compatibility I should run apache only in prefork mode and now I'm getting such type of problem.
  • Jul 21, 2009
    issue 18 (returned more than one Job ( cronScheduler.register(TimedRot...) commented on by gnugit   -   if change "run_every" value ,get more than one Job
    if change "run_every" value ,get more than one Job
  • Jul 20, 2009
    issue 18 (returned more than one Job ( cronScheduler.register(TimedRot...) reported by gnugit   -   What steps will reproduce the problem? 1. normal 2. May be related to 3. The cache backend to use. [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] ServerName: 'www.template.me', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] DocumentRoot: '/htdocs', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] URI: '/static/skins/090425/images/head_bg.gif', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Location: None, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Directory: None, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Filename: '/htdocs', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] PathInfo: '/static/skins/090425/images/head_bg.gif', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Traceback (most recent call last):, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1537, in HandlerDispatch\n default=default_handler, arg=req, silent=hlist.silent), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1229, in _process_target\n result = _execute_target(config, req, object, arg), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1128, in _execute_target\n result = object(arg), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/handlers/modpython.py", line 228, in handler\n return ModPythonHandler()(req), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/handlers/modpython.py", line 201, in __call__\n response = self.get_response(request), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/handlers/base.py", line 67, in get_response\n response = middleware_method(request), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/middleware/common.py", line 56, in process_request\n if (not _is_valid_path(request.path_info) and, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/middleware/common.py", line 142, in _is_valid_path\n urlresolvers.resolve(path), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/urlresolvers.py", line 246, in resolve\n return get_resolver(urlconf).resolve(path), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/urlresolvers.py", line 179, in resolve\n for pattern in self.urlconf_module.urlpatterns:, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/urlresolvers.py", line 198, in _get_urlconf_module\n self._urlconf_module = __import__(self.urlconf_name, {}, {}, ['']), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/jane/workspace/template.me/www/src/org/../org/urls.py", line 10, in <module>, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/jane/workspace/template.me/www/src/org/lib/mods-enabled/django_cron/__init__.py", line 60, in autodiscover, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/free/workspace/template.me/www/src/org/handler/cron.py", line 45, in <module>\n cronScheduler.register(TimedRotatingFile), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/jane/workspace/template.me/www/src/org/lib/mods-enabled/django_cron/base.py", line 77, in register, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/db/models/manager.py", line 96, in get_or_create\n return self.get_query_set().get_or_create(**kwargs), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/db/models/query.py", line 332, in get_or_create\n return self.get(**kwargs), False, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/db/models/query.py", line 311, in get\n % (self.model._meta.object_name, num, kwargs)), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] MultipleObjectsReturned: get() returned more than one Job -- it returned 3! Lookup parameters were {'name': "<class 'org.handler.cron.TimedRotatingFile'>"}, referer: http://localhost:8005/static/skins/090425/style/style.css What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below.
    What steps will reproduce the problem? 1. normal 2. May be related to 3. The cache backend to use. [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] ServerName: 'www.template.me', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] DocumentRoot: '/htdocs', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] URI: '/static/skins/090425/images/head_bg.gif', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Location: None, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Directory: None, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Filename: '/htdocs', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] PathInfo: '/static/skins/090425/images/head_bg.gif', referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] Traceback (most recent call last):, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1537, in HandlerDispatch\n default=default_handler, arg=req, silent=hlist.silent), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1229, in _process_target\n result = _execute_target(config, req, object, arg), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/usr/lib/python2.5/site-packages/mod_python/importer.py", line 1128, in _execute_target\n result = object(arg), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/handlers/modpython.py", line 228, in handler\n return ModPythonHandler()(req), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/handlers/modpython.py", line 201, in __call__\n response = self.get_response(request), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/handlers/base.py", line 67, in get_response\n response = middleware_method(request), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/middleware/common.py", line 56, in process_request\n if (not _is_valid_path(request.path_info) and, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/middleware/common.py", line 142, in _is_valid_path\n urlresolvers.resolve(path), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/urlresolvers.py", line 246, in resolve\n return get_resolver(urlconf).resolve(path), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/urlresolvers.py", line 179, in resolve\n for pattern in self.urlconf_module.urlpatterns:, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/core/urlresolvers.py", line 198, in _get_urlconf_module\n self._urlconf_module = __import__(self.urlconf_name, {}, {}, ['']), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/jane/workspace/template.me/www/src/org/../org/urls.py", line 10, in <module>, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/jane/workspace/template.me/www/src/org/lib/mods-enabled/django_cron/__init__.py", line 60, in autodiscover, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/free/workspace/template.me/www/src/org/handler/cron.py", line 45, in <module>\n cronScheduler.register(TimedRotatingFile), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/home/jane/workspace/template.me/www/src/org/lib/mods-enabled/django_cron/base.py", line 77, in register, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/db/models/manager.py", line 96, in get_or_create\n return self.get_query_set().get_or_create(**kwargs), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/db/models/query.py", line 332, in get_or_create\n return self.get(**kwargs), False, referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] File "/var/lib/python-support/python2.5/django/db/models/query.py", line 311, in get\n % (self.model._meta.object_name, num, kwargs)), referer: http://localhost:8005/static/skins/090425/style/style.css [Tue Jul 21 10:14:54 2009] [error] [client 127.0.0.1] MultipleObjectsReturned: get() returned more than one Job -- it returned 3! Lookup parameters were {'name': "<class 'org.handler.cron.TimedRotatingFile'>"}, referer: http://localhost:8005/static/skins/090425/style/style.css What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Please provide any additional information below.
  • Jul 20, 2009
    issue 4 (simple enhancement: run cronjobs from management.py) commented on by theMichaek   -   An update: my changes are not compatible with lines 39-47 of base.py, as it'll lead to all jobs being deleted on every cron run. I realize that block makes sense for the thread/timer approach, but it doesn't help in this case. I just deleted those lines from my code, but I'll consider a cleaner solution.
    An update: my changes are not compatible with lines 39-47 of base.py, as it'll lead to all jobs being deleted on every cron run. I realize that block makes sense for the thread/timer approach, but it doesn't help in this case. I just deleted those lines from my code, but I'll consider a cleaner solution.
  • Jul 20, 2009
    issue 4 (simple enhancement: run cronjobs from management.py) commented on by theMichaek   -   Attached is an updated patch. Some changes were needed in __init__.py and base.py, as invoking Timer() makes the script run forever from the command line. I don't think this code is quite acceptable yet (it doesn't return any useful information upon running, for example) but it seems a useful start. (As I noted above, I think this is useful functionality. A cron-enabled hosting environment would simply use a cron script to run "manage.py cronjobs", and the urls.py configuration is not needed.)
    Attached is an updated patch. Some changes were needed in __init__.py and base.py, as invoking Timer() makes the script run forever from the command line. I don't think this code is quite acceptable yet (it doesn't return any useful information upon running, for example) but it seems a useful start. (As I noted above, I think this is useful functionality. A cron-enabled hosting environment would simply use a cron script to run "manage.py cronjobs", and the urls.py configuration is not needed.)
  • Jul 20, 2009
    issue 4 (simple enhancement: run cronjobs from management.py) commented on by theMichaek   -   I agree with the statement in the original issue: "it is preferable to only have one actual cronjob and let django-cron do the rest". Even when cron is available on the system, it would be useful to have a simple way to register jobs with a central cron manager.
    I agree with the statement in the original issue: "it is preferable to only have one actual cronjob and let django-cron do the rest". Even when cron is available on the system, it would be useful to have a simple way to register jobs with a central cron manager.
  • Jul 17, 2009
    issue 17 (autodiscover blocks syncdb) reported by kylemacfarlane   -   What steps will reproduce the problem? 1. Create a new project and add django_cron.autodiscover() to your urls.py 2. Run manage syncdb 3. You get an error saying that the cron table doesn't exist What is the expected output? What do you see instead? Personally I would expect autodiscover to fail silently if the tables don't exist yet.
    What steps will reproduce the problem? 1. Create a new project and add django_cron.autodiscover() to your urls.py 2. Run manage syncdb 3. You get an error saying that the cron table doesn't exist What is the expected output? What do you see instead? Personally I would expect autodiscover to fail silently if the tables don't exist yet.
  • Jul 15, 2009
    issue 16 (syncdb table creation fails using postgresql + psycopg2) Status changed by Jim.mixtake   -   Marking as accepted
    Status: Accepted
    Marking as accepted
    Status: Accepted
  • Jul 15, 2009
    issue 16 (syncdb table creation fails using postgresql + psycopg2) commented on by Jim.mixtake   -   This is very interesting... perhaps a better name to use is CronJob, I'll look into fixing that bug without breaking backwards compatibility
    This is very interesting... perhaps a better name to use is CronJob, I'll look into fixing that bug without breaking backwards compatibility
  • Jul 15, 2009
    issue 14 (Project Home is out of date) Status changed by Jim.mixtake   -   fixed
    Status: Fixed
    fixed
    Status: Fixed
  • Jul 09, 2009
    issue 16 (syncdb table creation fails using postgresql + psycopg2) commented on by rcatherman   -   I got this working by changing the model name to Jobb from Job. Perhaps something in the table name or sequence name boils down to a conflicting name in postgre? Anyway, the hack I'm using is to rename the class, which obviously affects the table name and such, but then add this in the models.py as well: Job = Jobb
    I got this working by changing the model name to Jobb from Job. Perhaps something in the table name or sequence name boils down to a conflicting name in postgre? Anyway, the hack I'm using is to rename the class, which obviously affects the table name and such, but then add this in the models.py as well: Job = Jobb
  • Jun 15, 2009
    issue 4 (simple enhancement: run cronjobs from management.py) commented on by jchamp...@zetacentauri.com   -   Is this also intended to allow you to test whether the cron job code works from a command line? In that case I can see the usefulness when setting up jobs that need to be tested.
    Is this also intended to allow you to test whether the cron job code works from a command line? In that case I can see the usefulness when setting up jobs that need to be tested.
 
Hosted by Google Code