-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to access tomcat server #331
Comments
Hi @Ayushyadav19, Are there any errors in the tomcat logs? Since arcgis-cookbook/cookbooks/esri-tomcat/recipes/firewalld.rb Lines 46 to 52 in 237b0e3
Thanks, |
Hi @Ayushyadav19, I actually believe the 404 error you are receiving is by design. The esri-tomcat cookbook deletes the root folder which contains the index.html. Could you instead check the full web adaptor url? curl https://localhost/<wa_name>/webadaptor --insecure -v or curl http://localhost/<wa_name>/webadaptor -v |
Hi @cameronkroeker, Thanks for providing us with the info. Unfortunately, we are still facing issues with the web-adaptor configuration. Below is the screenshot attached for the same:- We already opened all the required ports on the ec2 instance firewall. Below is the screenshot attached for the same:- Any help/suggestions/thoughts will be much appreciated. Thanks |
Hi @Ayushyadav19, Looks like the web adaptor url is unavailable or timing out. What happens when running the following command?
Thanks, |
Hi @cameronkroeker,
We are deploying ArcGIS Enterprise v1091 on Linux RHEL - 7.9 on AWS using this AMI - ami-030e754805234517e. We are facing issues with the apache tomcat server (v9.0.65) installation. The recipe esri-tomcat, didn't throw any error during the deployment but when we try to access the tomcat URL - http://localhost:8080 we are encountering a 404 error. Refer to the below screenshot
And when we are following the manual steps to deploy tomcat it starts working as usual and we are able to access the URL http://localhost:8080.
For your reference, I am attaching the chef script. Kindly note that we are using "forward_ports": false due to your suggestion in the issue
BEDLinuxServer2.txt
Looking forward to your thoughts/suggestions.
Thanks
Ayush
The text was updated successfully, but these errors were encountered: