User Tools
Writing /app/www/public/data/meta/support/dig_portal/restarting_dig_portal.meta failed
support:dig_portal:restarting_dig_portal
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| support:dig_portal:restarting_dig_portal [2016/09/19 17:53] – mmcc | support:dig_portal:restarting_dig_portal [2021/06/25 10:09] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Restarting the Dig Portal ====== | ||
| + | |||
| + | Author: Colm Carew | ||
| + | |||
| + | **Please Edit this if you see any errors** | ||
| + | |||
| + | * Email the Noc - Check what Anna sends previously (ReleaseManagement@crowncastle.com, | ||
| + | |||
| + | * Connect to 1a and 1b vis ssh | ||
| + | * Make sure to change your name here where appropriate: | ||
| + | |||
| + | ssh -i '/ | ||
| + | ssh -i '/ | ||
| + | |||
| + | * aws.amazon.com/ | ||
| + | * Top right -> Northern California Region -> EC2 Section -> Load Balancers -> Dig Portal Balancer | ||
| + | * Check 1a and 1b links directly in browser | ||
| + | * Remove them from load balancer | ||
| + | |||
| + | * Verify both tickets not parsing tail -f / | ||
| + | * Check Ticketer/ | ||
| + | * cd / | ||
| + | * ./ | ||
| + | * ps -edf | grep Ticketer | ||
| + | * #check no Ticketer processes are running | ||
| + | |||
| + | * cd / | ||
| + | * | ||
| + | * ps -edf | grep NocPortal | ||
| + | * Start NOC | ||
| + | * tail -f ../ | ||
| + | * cd / | ||
| + | * ./ | ||
| + | * Exception for saved sessions is fine | ||
| + | * tail -f / | ||
| + | |||
| + | * Hit dig portal 1a and 1b directly and do not log in | ||
| + | * Start 1 ticketer at a time to prevent double email parsing | ||
| + | * cd / | ||
| + | * ./ | ||
| + | * tail -f / | ||
| + | * tail -f / | ||
| + | * Hit digportal1a: | ||
| + | * Ticketer/ | ||
| + | |||
| + | * aws.amazon.com/ | ||
| + | * northern california region load balancer dig portal instances | ||
| + | * edit instances | ||
| + | * Pick the 2 running dig portal instance and wait | ||
| + | * Go to load balancer link (http:// | ||
| + | |||
| + | **If anything goes wrong:** | ||
| + | |||
| + | * Chrome developer tools -> resources cookies worker 1 or 2 | ||
| + | * Keeping logging in verifying - At this point we are done and can email them back saying restart completed | ||
| + | * If having to log in twice | ||
| + | * cd / | ||
| + | * vi server.xml | ||
Page Tools
