User Tools
resolution_area:openstack
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| resolution_area:openstack [2022/02/17 21:44] – 10.91.120.28 | resolution_area:openstack [2022/02/18 17:20] (current) – 10.91.120.28 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| The purpose of this page is to gather a list of resolutions which can be used by anyone to recover an OpenStack environment to keep the system up. | The purpose of this page is to gather a list of resolutions which can be used by anyone to recover an OpenStack environment to keep the system up. | ||
| Line 40: | Line 40: | ||
| Find the largest folder store, and delete all files present | Find the largest folder store, and delete all files present | ||
| - | |||
| ====== CAS / You do not have permission to access this. ====== | ====== CAS / You do not have permission to access this. ====== | ||
| Line 51: | Line 50: | ||
| Verify the URL is resolving by a simple '' | Verify the URL is resolving by a simple '' | ||
| - | if this fails to render, then the CAS authentication cannot succeed, and points to a DNS issue. | + | if this fails to render, then the CAS authentication cannot succeed, and points to a DNS issue. |
| + | |||
| + | **Configurations** | ||
| + | Check CAS services and make sure they contain the correct urls. You'll find these on the handlers at /// | ||
| + | |||
| + | |||
| + | If you're seeing in the CAS logs, that the service url isn't matching the supplied service urls, like in the example below, it might be a configuration issue in HTTPD on the loadbalancer | ||
| + | |||
| + | < | ||
| + | ERROR [org.jasig.cas.CentralAuthenticationServiceImpl] - Service ticket [ST-62-LcMoIN7pmxTjPxI9eNkb-qascoapps1] with service [https:// | ||
| + | </ | ||
| + | |||
| + | As you can see, the supplied service is using **qascoapps1.err** but the existing service is for **sco.errigal.com**. | ||
| + | |||
| + | So, ssh into the loadbalancer and navigate to /// | ||
| + | |||
| + | You'll need to check and potentially edit mod-jk.conf and workers.properties | ||
| + | |||
| + | **mod-js.conf** | ||
| + | For the Grails applications, | ||
| + | |||
| + | Add the **JkMount** lines at the bottom for the relevant applications: | ||
| + | |||
| + | < | ||
| + | JkMount / | ||
| + | JkMount / | ||
| + | </ | ||
| + | |||
| + | **workers.properties** | ||
| + | At the very top, make sure your application LoadBalancer entry is in the list | ||
| + | |||
| + | < | ||
| + | # Create virtual workers | ||
| + | worker.list=jkstatus, | ||
| + | </ | ||
| + | |||
| + | Next, add the lines to configure the loadbalancer instances | ||
| + | < | ||
| + | #Configure ReportingManager load balanced instances | ||
| + | worker.ReportingManagerLoadBalancer.type=lb | ||
| + | worker.ReportingManagerLoadBalancer.sticky_session=1 | ||
| + | |||
| + | # Declare Tomcat server workers 1 through n | ||
| + | |||
| + | worker.ReportingManagerWorker1.reference=worker.ajptemplate | ||
| + | worker.ReportingManagerWorker1.host=qascoapps1.err | ||
| + | worker.ReportingManagerWorker1.port=8011 | ||
| + | worker.ReportingManagerWorker1.reply_timeout=600000 | ||
| + | </ | ||
| + | |||
| + | Finally, at the end of the file add those instances to the application loadbalancer worker | ||
| + | |||
| + | < | ||
| + | worker.ReportingManagerLoadBalancer.balance_workers=ReportingManagerWorker1 | ||
| + | </ | ||
| + | |||
| + | Save those files, and restart the **httpd** service | ||
| + | |||
| + | < | ||
| + | sudo service httpd restart | ||
| + | </ | ||
resolution_area/openstack.1645134267.txt.gz · Last modified: 2022/02/17 21:44 by 10.91.120.28
Page Tools
