Files
2012-02-21 01:15:00 -05:00

1 line
2.1 KiB
JSON

[{"user_id": 7129, "stars": [], "topic_id": 16709, "date_created": 1301670682.6476049, "message": "(And whilst we're at it, it shouldn't use --background and --make-pidfile; see start-stop-daemon(8) pidfile)", "group_id": 81, "id": 502471}, {"user_id": 7129, "stars": [], "topic_id": 16709, "date_created": 1301670645.187628, "message": "There should be rm -f $CELERY_PIDFILE_WHATEVER in the stop action too.", "group_id": 81, "id": 502465}, {"user_id": 1102, "stars": [], "topic_id": 16709, "date_created": 1301668596.809792, "message": "I'm having issues getting Celery to run as a daemon. I had it working at one point, but now it fails, so I'm looking for ideas about what could be causing it! To cross-post my serverfault question: http://serverfault.com/questions/254260/trouble-running-python-celery-as-a-daemon", "group_id": 81, "id": 501908}, {"user_id": 7129, "stars": [], "topic_id": 16709, "date_created": 1301670612.996115, "message": "From a reading of the initscript, I think think you have stale pidfile - delete /var/run/celeryd.pid and start it again?", "group_id": 81, "id": 502459}, {"user_id": 1102, "stars": [], "topic_id": 16709, "date_created": 1301677072.0302031, "message": "if I remove --background, it throws a Python import error. Even though I'm using start-stop-dameon's --chdir option, it's not finding the files in that directory. So I'm going to try to add them to the path elsewhere for the moment... see if that takes.", "group_id": 81, "id": 503391}, {"user_id": 1102, "stars": [], "topic_id": 16709, "date_created": 1301677016.927511, "message": "I *think* this has something to do with paths", "group_id": 81, "id": 503386}, {"user_id": 1102, "stars": [], "topic_id": 16709, "date_created": 1301677009.282207, "message": "yeah, no luck with removing .pid before hand ... although I did notice it wasn't getting removed.", "group_id": 81, "id": 503385}, {"user_id": 1102, "stars": [], "topic_id": 16709, "date_created": 1301684102.561444, "message": "Turns out it was just permissions issues. The tasks/config files were not readable by celery. Only found it out by removing the --background bit, so thank you!", "group_id": 81, "id": 504431}]