CASIDP1 -- /root-casidp-1.login -- 172.31.60.12
AWS CASIDP-1
######## hostname: ip-172-31-60-12.ec2.internal
CASIDP2 -- /root-casidp-2.login -- 172.31.48.221
AWS CASIDP-2
######## hostname: ip-172-31-48-221.ec2.internal
CASIDP-DEV -- /root-casidp-dev.login -- 172.31.56.111
AWS CASIDP-DEV
######## hostname: casidp1-dev.cc.binghamton.edu
BingDev -- /root-dev-aws.login -- 172.31.17.113
AWS BINGDEV
######## hostname: ip-172-31-17-113.ec2.internal
Bingwww -- /root-www-aws.login -- 172.31.16.208
AWS BINGWWW
######## hostname: ip-172-31-16-208.ec2.internal
Bingwww - Test -- /bingwww-test-aws.login -- 172.31.5.182
/root-east-www.login
AWS TESTWWW
######## hostname: ip-172-31-5-182.ec2.internal
BUBind -- /BUBind.login -- 172.31.12.220
Here are the instructions for patching the CAS servers.
Production:
casidp1.cc.binghamton.edu/casidp1.login
casidp2.cc.binghamton.edu
casidp3.cc.binghamton.edu
Development:
casidp1-dev.cc.binghamton.edu
CASIDP Server yum update; sync; sync; sync; date
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
From CENTOSONE.
/casidp1.login
/casidp2.login
/casidp3.login
2. Use sudo to access the root account (sudo -i)
sudo -i
3. Stop HTTPD prior to installing patches to disengage the load balancer.
systemctl stop httpd
systemctl status httpd
4. Install patches and reboot as needed.
Connect to console: https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Instances:
yum update; sync; sync; sync; reboot
5. 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.
AFTER sync;sync;sync;reboot DO tomcat CHECK ...
6. Verify that HTTPD is running post boot (service httpd status) systemctl status httpd 7. Verify that two Tomcat instances are running ps -ef | grep tomcat | grep -v grep | wc -l ps -ef |egrep tomcat | egrep cas |grep -v grep |wc -l ps -ef |egrep tomcat | egrep shib |grep -v grep |wc -l /etc/init.d/tomcat-cas /etc/init.d/tomcat-shib tail -f /u01/app/badm/apps/shibboleth/shibboleth-idp/logs/idp-process.log tail -f /u01/app/badm/apps/tomcat/apache-tomcat-cas/logs/cas.log