-
Notifications
You must be signed in to change notification settings - Fork 0
Staging Debugging Guide
Jorge Silva edited this page Mar 30, 2016
·
11 revisions
So you yell and you yell and no one is fixing staging. Well, now you can debug yourself :)
- Go to runnable.io.
- Ensure rabbitMQ, redis, and mongo are up. If any of these are down, simply click
start container(DO NOT REBUILD THESE CONTAINERS). But if you did .... - mongo flushed
- redis flushed
- Ensure supporting services are up:
- api
-
api-worker WORKER-do-not-delete branch (updated to latest code
git fetch && git merge origin/master) and restart container - runnable-angular
-
mavis
** hit
http://mavis-staging-codenow.runnableapp.com/docksto ensure docks are available - optimus
- to get navi to work you have to do something special using navi on staging To ensure things are up do the following:
- Go to terminal of the service
-
curlthe respective port, example:curl localhost:80for api: 1. If you do not see any output of curl (or it hangs) then start/stop or click latest commit. - Run
ip addr | grep ethweand ensure the output contains ethwe. If not, rebuild container. - Inspect the logs by opening a terminal and running:
1.
npm install bunyan -g2.LOG_LEVEL_STDOUT=trace npm start | bunyan