Closed
Bug 571283
Opened 14 years ago
Closed 14 years ago
Restart and cron SIGHUP for support-stage-new celeryd process
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jsocol, Assigned: oremj)
References
Details
The celeryd instance running for support-stage-new (Jeremy knows _where_ it's running) needs to be kicked periodically to pick up any changes. The easiest way to do that is to SIGHUP it on a cron. I'm sure you know more about the details of doing that than I do: I use ps to get the pid and kill -s SIGHUP to do it. This is blocking testing of our release this afternoon, so => blocker.
Reporter | ||
Updated•14 years ago
|
Assignee | ||
Updated•14 years ago
|
Assignee: thardcastle → jeremy.orem+bugs
Assignee | ||
Comment 1•14 years ago
|
||
Added /sbin/service celeryd-kitsune-stage reload to update cron job.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > Added /sbin/service celeryd-kitsune-stage reload to update cron job. Great, thanks!
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•