Closed hancush closed 4 years ago
I trigged some deployments and noticed that changes weren't being reflected as I expected. So I took a look at our supervisor processes:
ubuntu@ip-10-0-0-244:~$ sudo supervisorctl status la-metro-dashboard RUNNING pid 13166, uptime 3:31:14 la-metro-dashboard-scheduler RUNNING pid 30648, uptime 11 days, 3:05:47
It would appear the scheduler does not restart on deployment. :-(
I think adding a line like supervisorctl restart la-metro-dashboard la-metro-dashboard-scheduler will do the right thing!
supervisorctl restart la-metro-dashboard la-metro-dashboard-scheduler
I trigged some deployments and noticed that changes weren't being reflected as I expected. So I took a look at our supervisor processes:
It would appear the scheduler does not restart on deployment. :-(