Troubleshooting

These are some basic troubleshooting steps and reminders in case you run into an issue with the script itself. Also check here for known issues and common mistakes. This will only cover problems with running the script to completion, not how it functions after as a result of the options and parameters provided to it by a user.

Considerations:

1. Are you running RHEL or CentOS, at least version 7.0 or higher? If not this is a requirement.
2. Did you download the script direct from the official source on Github at https://github.com/Zer0CoolX/guacamole-install-rhel/blob/master/guac-install.sh? If not download it from this source.
3. Have you reviewed the script according to the directions on this page? If not read over the post and ensure all variables in the script are current and meet your needs.
4. Did you set the guac-install.sh script to be executable as per the directions in the README? If not do so.
5. Did you run the script as a sudo user or as root? If not do so.
6. Does the server you are installing on have an internet connection? If not this is required for the script to work.
7. Has this server ever had (currently or previously) Guacamole server/client, Nginx, MariaDB, Tomcat or any other of Guacamole's dependencies installed previously? If so this is not supported and is likely to cause issues. This script is meant to install Guacamole and its dependent programs for the first time on a "fresh" system.

Steps to resolving issues with the script running:

Presuming the above considerations have been checked and are as they should be, do the following:

1. If there is output on the screen while running the script take not of the exact message. It may specify a specific line number within the script that has failed. Researching any visible error from the on screen output of the script is the best first step to resolving issues.
2. Check the output of the log file. Usually, if the script has failed the failure will be the last line(s) of the log file. See this Page regarding the log file generated by the script.
3. Re-try the script, it may have been an odd, one-off issue. Take each step slowly and deliberately to ensure there is no human error in the process. You may even consider starting all over by re-downloading the script and following the steps to run it from the start.
4. You may attempt putting SELinux in permissive mode via setenforce 0 (1 sets it back to enforcing) as a temporary measure. This, however, should not be required as the script should not need any SEL context/booleans set for itself to run and actually sets the proper context and booleans itself for Guacamole to function with SEL on and enforcing.
5. Consider checking other common logs like /var/log/messages, journalctl, systemctl status service_name_here, etc. These logs may point to other issues in the configuration of the machine that may prevent the script from running and/or point to issues with the script itself.
6. Take a break. I know this is not always possible but I have found numerous occasions where a small typo slips by and I dont notice it until I look at it later with a fresh perspective. Re-check variables and the answers to the prompts to ensure they are all the proper/expected syntax and also correct for your setup/environment.

If you are unable to resolve an issue yourself, consider submitting an issue report via the Issues tab here in the Github repo. Before doing so check this thread for guidance on the best way to submit requests for help.