forked from autolab/Tango
-
Notifications
You must be signed in to change notification settings - Fork 13
Restarting Tango
Jesse Hartloff edited this page Oct 13, 2022
·
3 revisions
Do this if Tango is not stable or if you need to change Tango configurations
- Login to armstrong
- Bounce into the tango_deployment container
- Check the status of the running services
supervisorctl status
You should see something like the following output
nginx RUNNING pid 23246, uptime 26 days, 21:48:20
redis_server RUNNING pid 23150, uptime 26 days, 21:49:15
tango:0 RUNNING pid 23217, uptime 26 days, 21:48:20
tango:1 RUNNING pid 23203, uptime 26 days, 21:48:20
tangoJobManager RUNNING pid 23158, uptime 26 days, 21:48:20
wrapdocker RUNNING pid 23159, uptime 26 days, 21:48:20
- Stop all services
supervisorctl stop all
- Ensure all services are stoped
ps aux
The following three processes should not appear
... python /opt/TangoService/Tango/jobManager.py
... python /opt/TangoService/Tango/restful-tango/server.py 8611
... python /opt/TangoService/Tango/restful-tango/server.py 8610
If they are not stopped, kill the pids
kill -9 {pid}
- Start the Redis service
supervisorctl start redis_server
- Blow away the Redis cache to clear the job queue/etc.
redis-cli
> FLUSHALL
> ctrl+C
- Start the services
supervisorctl start all
- Wait. Startup has been known to take 10+ minutes
- Navigate to AutoLab and check the Tango status to verify that it is running
- Send Tango a job and verify that it is successful
- Set up Tango
- Set up Local Docker VMMS
- Set up Dist Docker VMMS
- Set up Amazon EC2 VMMS
- Set up VMs for Jobs
- Updating a Grading Image