On Tue, Mar 1, 2022 at 6:59 AM Adam Cherrett <adamcherr...@gmail.com> wrote:
> I need some help troubleshooting my attempt to get 1.4.0 running (for use > on my local network). I am working with a clean installation of Ubuntu > 21.10, and have been following the steps in > https://computingforgeeks.com/install-and-use-guacamole-on-ubuntu/ > > How about the Guacamole manual? Have you followed the documentation there? > Tomcat 9 appears to be running fine (and I can access the manager app > through the browser): > > > systemctl status tomcat > ● tomcat.service - Tomcat 9 servlet container > Loaded: loaded (/etc/systemd/system/tomcat.service; enabled; vendor > prese > t: enabled) > Active: active (running) since Mon 2022-02-28 13:28:23 CET; 23h ago > Process: 13902 ExecStart=/opt/tomcat/tomcatapp/bin/startup.sh > (code=exited > , status=0/SUCCESS) > Main PID: 13909 (java) > Tasks: 39 (limit: 38299) > Memory: 340.4M > CPU: 1min 44.670s > CGroup: /system.slice/tomcat.service > └─13909 /usr/lib/jvm/java-11-openjdk-amd64/bin/java > -Djava.util.l > ogging.config.file=/opt/tomcat/tomcatapp/conf/logging.properties > -Djava.util.l > ogging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.security.egd=file: > ///dev/urandom -Djava.awt.headless=true -Djdk.tls.ephemeralDHKeySize=2048 > -Dja > va.protocol.handler.pkgs=org.apache.catalina.webresources > -Dorg.apache.catalin > a.security.SecurityListener.UMASK=0027 -Xms512M -Xmx1024M -server > -XX:+UsePara > llelGC -Dignore.endorsed.dirs= -classpath > /opt/tomcat/tomcatapp/bin/bootstrap. > jar:/opt/tomcat/tomcatapp/bin/tomcat-juli.jar > -Dcatalina.base=/opt/tomcat/tomc > atapp -Dcatalina.home=/opt/tomcat/tomcatapp > -Djava.io.tmpdir=/opt/tomcat/tomca > tapp/temp org.apache.catalina.startup.Bootstrap start > > Feb 28 13:28:23 blackbox systemd[1]: Starting Tomcat 9 servlet container... > Feb 28 13:28:23 blackbox startup.sh[13902]: Tomcat started. > Feb 28 13:28:23 blackbox systemd[1]: Started Tomcat 9 servlet container. > > guacd appears to be fine: > ● guacd.service - LSB: Guacamole proxy daemon > Loaded: loaded (/etc/init.d/guacd; generated) > Active: active (running) since Mon 2022-02-28 13:28:41 CET; 23h ago > Docs: man:systemd-sysv-generator(8) > Process: 13992 ExecStart=/etc/init.d/guacd start (code=exited, > status=0/SU > CCESS) > Tasks: 1 (limit: 38299) > Memory: 9.4M > CPU: 15ms > CGroup: /system.slice/guacd.service > └─13996 /usr/local/sbin/guacd -p /var/run/guacd.pid > > Feb 28 13:28:41 blackbox systemd[1]: Starting LSB: Guacamole proxy > daemon... > Feb 28 13:28:41 blackbox guacd[13994]: Guacamole proxy daemon (guacd) > version > 1.4.0 started > Feb 28 13:28:41 blackbox guacd[13992]: Starting guacd: > Feb 28 13:28:41 blackbox guacd[13994]: guacd[13994]: INFO: > Guacamole pr > oxy daemon (guacd) version 1.4.0 started > Feb 28 13:28:41 blackbox guacd[13992]: SUCCESS > Feb 28 13:28:41 blackbox guacd[13996]: Listening on host 127.0.0.1, port > 4822 > Feb 28 13:28:41 blackbox systemd[1]: Started LSB: Guacamole proxy daemon. > > I can restart both tomcat and guacd without problems. I suspect the > problem lies with the guacamole client. I have tried prerolled versions and > compiling my own - neither of them works. Browsing to > http://127.0.0.1:8080/guacamole gives a 404 error. The Tomcat manager > shows a number of applications running, and shows guacamole is not. Trying > to start it from the browser gives the error "FAIL - Application at context > path [/guacamole] could not be started". > > Here are some log entries: > > in catalina.YYYY-MM-DD.log (duplicated in catalina.out): > 01-Mar-2022 12:27:33.610 INFO [http-nio-8080-exec-18] > org.apache.jasper.servle > t.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained > no T > LDs. Enable debug logging for this logger for a complete list of JARs that > wer > e scanned but no TLDs were found in them. Skipping unneeded JARs during > scanni > ng can improve startup time and JSP compilation time. > 01-Mar-2022 12:27:33.611 SEVERE [http-nio-8080-exec-18] > org.apache.catalina.co > re.StandardContext.startInternal One or more listeners failed to start. > Full d > etails will be found in the appropriate container log file > 01-Mar-2022 12:27:33.612 SEVERE [http-nio-8080-exec-18] > org.apache.catalina.co > re.StandardContext.startInternal Context [/guacamole] startup failed due > to pr > evious errors > > Can you just post the output of catalina.out? It may have some more information that would be useful in determining why the deploy failed. -Nick
