Sorry about that. It's RHEL 8 with Tomcat 10 on a Hyper-V VM. I haven't configured any sort of authentication. I went through the manual from start to that chapter, so nothing else other than installing guac-server and guacamole.war
Content of Catalina.out during a fresh execution today: 06-Oct-2021 08:19:14.024 INFO [http-nio-8080-exec-12] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 06-Oct-2021 08:19:14.027 SEVERE [http-nio-8080-exec-12] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file 06-Oct-2021 08:19:14.027 SEVERE [http-nio-8080-exec-12] org.apache.catalina.core.StandardContext.startInternal Context [/guacamole] startup failed due to previous errors Content of Catalina.2021-10-06.log also during a fresh execution today: 06-Oct-2021 08:19:14.024 INFO [http-nio-8080-exec-12] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 06-Oct-2021 08:19:14.027 SEVERE [http-nio-8080-exec-12] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file 06-Oct-2021 08:19:14.027 SEVERE [http-nio-8080-exec-12] org.apache.catalina.core.StandardContext.startInternal Context [/guacamole] startup failed due to previous errors As far as syslog goes, I'm not sure which of these logs is important for analysis. [adminserv@cvadguacamole-dev tomcat10]$ cd /var/log [adminserv@cvadguacamole-dev log]$ ls -l total 2796 drwxr-xr-x. 2 root root 4096 Sep 30 10:50 anaconda drwx------. 2 root root 23 Sep 30 11:23 audit -rw-------. 1 root root 0 Oct 6 03:40 boot.log -rw-------. 1 root root 16778 Oct 1 03:31 boot.log-20211001 -rw-------. 1 root root 49655 Oct 4 11:25 boot.log-20211004 -rw-------. 1 root root 20164 Oct 6 03:40 boot.log-20211006 -rw-rw----. 1 root utmp 768 Oct 5 21:38 btmp -rw-rw----. 1 root utmp 0 Sep 30 10:33 btmp-20211001 drwxr-xr-x. 2 chrony chrony 6 Mar 1 2021 chrony -rw-------. 1 root root 19372 Oct 6 08:01 cron drwxr-xr-x. 2 lp sys 57 Sep 30 10:37 cups -rw-r--r--. 1 root root 91182 Oct 6 08:11 dnf.librepo.log -rw-r--r--. 1 root root 336144 Oct 6 08:11 dnf.log -rw-r--r--. 1 root root 18644 Oct 6 08:11 dnf.rpm.log -rw-r-----. 1 root root 1860 Oct 5 21:12 firewalld drwx--x--x. 2 root gdm 6 Jan 27 2021 gdm drwxr-xr-x. 2 root root 21 Sep 30 10:48 glusterfs -rw-rw-rw-. 1 root root 8520 Oct 6 08:11 hawkey.log drwx------. 2 root root 33 Sep 30 10:48 insights-client -rw-r--r--. 1 root root 6741 Oct 5 21:13 kdump.log -rw-rw-r--. 1 root utmp 292584 Oct 6 08:11 lastlog drwx------. 3 root root 18 Sep 30 10:36 libvirt -rw-------. 1 root root 0 Sep 30 10:34 maillog -rw-------. 1 root root 2026539 Oct 6 08:17 messages drwx------. 2 root root 6 Sep 30 10:33 private drwxr-xr-x. 2 root root 6 Jul 21 17:27 qemu-ga drwxr-xr-x. 2 root root 43 Sep 30 11:23 rhsm drwx------. 3 root root 17 Sep 30 10:34 samba -rw-------. 1 root root 63149 Oct 6 08:17 secure drwx------. 2 root root 6 Dec 10 2018 speech-dispatcher -rw-------. 1 root root 0 Sep 30 10:34 spooler drwxr-x---. 2 sssd sssd 93 Sep 30 11:26 sssd drwxr-xr-x. 3 root root 21 Sep 30 10:36 swtpm drwxr-xr-x. 2 root root 23 Sep 30 11:23 tuned -rw-rw-r--. 1 root utmp 14208 Oct 6 08:11 wtmp -rw-r--r--. 1 root gdm 17693 Oct 5 21:13 Xorg.0.log -rw-r--r--. 1 root gdm 17693 Oct 5 13:40 Xorg.0.log.old -rw-r--r--. 1 root adminserv 17853 Oct 4 11:44 Xorg.1.log -rw-r--r--. 1 root adminserv 17994 Oct 4 09:52 Xorg.1.log.old -rw-r--r--. 1 root root 18137 Sep 30 11:24 Xorg.9.log Thank you, Yo Khoe CVAD IT University of North Texas From: ivan marcus <[email protected]> Sent: Tuesday, October 5, 2021 11:26 PM To: [email protected] Subject: [EXT] Re: Should I see the Login Page at this point in time following the documentation? Yes, once you've installed Guacamole & necessary support packages, including Tomcat, and configured per the page you reference, you should get the initial login screen. You've not said what distribution you're using, or what auth type you've configured, but it might pay to have a look at your log files to see if they carry useful information regarding the error you have? In particular syslog and/or catalina.out may well give you sufficient detail to resolve the problem. If that doesn't help, and you need to post back here, please include your distribution and config detail, and excerpts from your log files where you've restarted guacd and tomcat, and attempted a login. Thanks. On Wednesday, 6 October 2021, 04:23:48 pm NZDT, Khoe, Yonathan <[email protected]<mailto:[email protected]>> wrote: Hello, I'm slowly getting a test build going for Guac and currently on the Deployment section of the doc. At the last section on restarting tomcat and starting guac "After restarting Tomcat and startingguacd, Guacamole is successfully installed, though it will not be fully running. In its current state, it is completely unconfigured, and further steps are required to add at least one Guacamole user and a few connections. This is covered in Chapter 5, Configuring Guacamole<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fguacamole.apache.org%2Fdoc%2Fgug%2Fconfiguring-guacamole.html&data=04%7C01%7CYonathan.Khoe%40unt.edu%7C4d161c6ce562480bfe7308d988816cc3%7C70de199207c6480fa318a1afcba03983%7C0%7C0%7C637690912313800695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Z%2F0ucFC4WxltE4wEHZx13J0Ps9zGMcr6XhARHT0hMoE%3D&reserved=0>." Should I already be able to see the guacamole login screen at [ip]:8080/guacamole ? I'm getting the following error on tomcat manager. [cid:[email protected]] I just wanted to make sure this is normal behavior and if I should continue configuring the rest (i.e. auth, database, etc.) Thank you, Yo Khoe CVAD IT University of North Texas
