@mchaudhary@mostlyjason, The actual issue with the script was if we have provided the correct CATALINA_HOME path manually using the -ch option but the script fails to find the tomcat service at the path /etc/init.d/ then it also checks for the startup.sh file at location $LOGGLY_CATALINA_HOME/bin/startup.sh. As I had also added this systemctl command in Nginx and Apache scripts to find the Nginx and Apache service, here the same things need to be added for Tomcat service. That's what I have done here. If Tomcat service couldn't be found at location /etc/ini.d/ then check with systemctl command.
Now the script is working fine if we provide the correct Catalina home path and script is able to find the tomcat service.
logMsgToConfigSysLog "INFO""INFO: Tomcat is not configured as a service."
if [ !-f"$LOGGLY_CATALINA_HOME/bin/startup.sh" ];then
logMsgToConfigSysLog "WARN""WARN: Unable to find bin/startup.sh file within $LOGGLY_CATALINA_HOME."
eval$1="false"
fi
fi
fi
}
ProTip!
Use n and p to navigate between commits in a pull request.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more
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
Add TLS support in Tomcat Script #105
Add TLS support in Tomcat Script #105
Changes from 1 commit
f52091595f82e769fb261280bdfaFile filter...
Jump to…
Added systemctl command to check for tomcat service
Shwetajain148Oct 26, 2017
Author
Contributor
@mchaudhary @mostlyjason, The actual issue with the script was if we have provided the correct CATALINA_HOME path manually using the -ch option but the script fails to find the tomcat service at the path /etc/init.d/ then it also checks for the startup.sh file at location $LOGGLY_CATALINA_HOME/bin/startup.sh. As I had also added this systemctl command in Nginx and Apache scripts to find the Nginx and Apache service, here the same things need to be added for Tomcat service. That's what I have done here. If Tomcat service couldn't be found at location /etc/ini.d/ then check with systemctl command.
Now the script is working fine if we provide the correct Catalina home path and script is able to find the tomcat service.