Closed
Bug 891791
Opened 11 years ago
Closed 11 years ago
[snippets] Apache needs restart after chief push
Categories
(Infrastructure & Operations Graveyard :: WebOps: Engagement, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: giorgos, Assigned: dmaher)
References
Details
I used chief to push to dev and stage. For both we needed to manually restart httpd for the changes to take effect, although the chief logs say that wsgi file was touched. We waited more than a couple of minutes. For prod we waited couple of minutes and httpd was restarted successfully. The restart wasn't immediate.
Reporter | ||
Comment 1•11 years ago
|
||
Update on prod: We had to manually restart prod as well because I was getting either an outdated version or the current version or a 'Page not found' error. After restarting both instances everything works as expected.
Assignee | ||
Updated•11 years ago
|
Assignee: server-ops-webops → dmaher
Status: NEW → ASSIGNED
Component: Server Operations: Web Operations → WebOps: Engagement
Priority: -- → P3
Product: mozilla.org → Infrastructure & Operations
Summary: [snippets] Apache needs restart after chief push (sometimes) → [snippets] Apache needs restart after chief push
Assignee | ||
Comment 2•11 years ago
|
||
This was due to the fact that the app was not running as a daemon, and thus, did not respond to the "touch" method of restarting the app. The app is now running as a daemon in dev, stage, and prod, therefore it can be "touch-restarted" in the usual fashion.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•