Here are the instructions for patching the CAS servers.
Production:
casidp1.cc.binghamton.edu
casidp2.cc.binghamton.edu
casidp3.cc.binghamton.edu
Development:
casidp1-dev.cc.binghamton.edu
The production server can be patched at anytime -- no maintenance period required. The only caveat is that one server must remain untouched while the others are patched and there's a five minute wait period to ensure that the AWS load-balancer recovers the down nodes.
1. Please log onto these servers using the "ec2-user" account.
Lore, I see you use venus a lot, so I configured the servers to allow access from root@venus to ec2-user@casidp{1,2,3}.cc.binghamton.edu
2. Use sudo to access the root account (sudo -i)
3. Stop HTTPD prior to installing patches to disengage the load balancer.
4. Install patches and reboot as needed.
5. Verify that HTTPD is running post boot (service httpd status)
6. Verify that two Tomcat instances are running (ps -ef | grep tomcat | grep -v grep | wc -l)
7. Wait about 5min to allow the load balancer to recognize the host is available and the services to start responding to user requests before moving on to the next server.
tail -f /u01/app/badm/apps/tomcat/apache-tomcat-cas/logs/cas.log
tail -f /u01/app/badm/apps/shibboleth/shibboleth-idp/logs/idp-process.log
The development server is not redundant and therefore, must be patched during the maintenance window or outside of working hours which are generally 8am - 6pm for most folks.