Cheat sheet for rebooting E@H machines in Hannover
If the E@H machines need to be rebooted (e.g. kernel upgrade) here's the proper ordering:
Isolated machines
The following machines are usually safe to reboot as they are isolated:
- einstein2
- einstein7
- einstein9 (GW post-processing, coordinate w. Bernd,HB)
main (connected) servers
- disable pre-processing (Ben)
- disable WUGs on einstein4 (edit config.xml and commit) (Bernd)
- update/reboot einstein1/3/6 (Carsten)
- pre-processing may be restarted (Ben)
- stop E@H on einstein.uwm and A@H on albert.uwm (Bernd)
- update/reboot einstein4 (Carsten)
- shutdown SQL on einstein-db1/2/3 (Olli)
- update/reboot VPN1/2 (Carsten)
- update einstein-db1/2/3 (Carsten)
- start projects @UWM (Bernd)
- enable WUGs on einstein4 (revert commit) (Bernd)
- back to production
einstein5 depends on current mode of operation: currently it's isolated, when it actually hosts a running project, the project needs to be stopped there instead of at UWM, and the machine needs to be rebooted together with einstein4.
--
CarstenAulbert - 06 May 2014