On Fri, Aug 14, 2020 at 10:54 AM Devine, Harry (FAA) <[email protected]> wrote:
> I copied the LDAP settings from /etc/guacamole/guacamole.properties on the > machine that’s working and replaced it in the same file on the server that > is not working, restarted guacd, and still get the same error. Still no > update to catalina.out (it’s a 0 length file) in /var/log/tomcat. But I > appreciated the response. > > > guacd does not deal with LDAP at all, so restarting guacd is not going to help you. You need to restart Tomcat, which is where Guacamole Client runs, and the piece that talks to LDAP. Regarding the catalina.out file - if you're running the version of Tomcat included in the RHEL7 packages, then it may be just logging everything to syslog, which you can see with either "journalctl" or in the contents of /var/log/messages. If you've installed a custom version of Tomcat then the logs may be written elsewhere - for example, I usually install a newer version of Tomcat (9.x) and put it in /opt/tomcat. In my installation, the logs end up being written to /opt/tomcat/logs, with the most useful output written to catalina.out in that directory. As a side note, and not really relevant to your current issue, Red Hat (= IBM) has chosen to discontinue including Tomcat in the latest version of RHEL, instead pushing people toward JBoss. While I know there has been some frustration expressed by people at that decision, they are so far behind on the version of Tomcat included with RHEL7, anyway, that I'm not sure it matters much. I think RHEL7 generally comes with an older 7.0 version of Tomcat, while the project has released many versions of 8.0, 8.5, and 9.0 in that time. At some point you'll probably want to just grab the latest Tomcat binaries from the project site and install them rather than relying on the ancient packages included with RHEL7, and which will not be included with RHEL8. Or, switch over to JBoss....although, that comes with its own baggage :-). -Nick >
