Closed
Bug 1440349
Opened 7 years ago
Closed 7 years ago
bugzilla-push and phabbugz feed daemon fail to start automatically on bugzilla-dev.allizom.org
Categories
(bugzilla.mozilla.org :: Infrastructure, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: dkl, Unassigned)
Details
Currently the bugzilla-push daemon and phabicator feed daemon are running manually using two screen sessions. It would be ideal if they could be configured as proper initd process similar to how it is done with the production systems.
Bonus points if they could be restarted when ever a new code push is done on bugzilla-dev.allizom.org as they will use the old code until restarted.
Thanks
dkl
Comment 1•7 years ago
|
||
I would say that automatic restart is not a bonus but a required part of this bug. If we don't do that, we are guaranteed to be running an older version at some point and likely end up very confused when trying to debug a problem.
Comment 2•7 years ago
|
||
Updated manifests to add the push and phab daemons to dev (web5.stage.bugs), and updated the deploy scripts for dev and prod to restart 'em. Waiting on :dkl to verify and hopefull a dev push to ensure things restart.
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to Kendall Libby [:fubar] from comment #2)
> Updated manifests to add the push and phab daemons to dev (web5.stage.bugs),
> and updated the deploy scripts for dev and prod to restart 'em. Waiting on
> :dkl to verify and hopefull a dev push to ensure things restart.
Everything seems to be in order even after a test push to developmnent branch.
dkl
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•