tronyx

Same result, even with the other 0.9.14 tags. I removed the catalina.out file between each one. I even blew away the container completely, including the appdata dir, recreated the container with the latest image and still see the same issue.

There was only the catalina.out file. I deleted it, restarted the container and got the same result. The permissions did look correct. I looked into the catalina.out file and I am seeing the following error, which seems like the culprit: INFO: Starting Servlet Engine: Apache Tomcat/8.0.32 (Ubuntu) Sep 25, 2018 7:08:21 PM org.apache.catalina.valves.AccessLogValve open SEVERE: Failed to open access log file [/var/lib/tomcat8/logs/localhost_access_log.2018-09-25.txt] java.io.FileNotFoundException: /var/lib/tomcat8/logs/localhost_access_log.2018-09-25.txt (Permission denied) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at org.apache.catalina.valves.AccessLogValve.open(AccessLogValve.java:579) at org.apache.catalina.valves.AccessLogValve.startInternal(AccessLogValve.java:609) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at org.apache.catalina.core.StandardPipeline.startInternal(StandardPipeline.java:170) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:930) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) However, it doesn't appear that I'm able to exec any commands on the container or just into the container. Any suggestions?

Just updated to your latest image and now Tomcat is failing to start. No other changes on my end, and even previous images using their respective tags are no longer working. Seeing the following in the Docker logs for the container: *** Running /etc/my_init.d/firstrun.sh... Using existing properties file. Using existing MySQL extension. No permissions changes needed. *** Running /etc/rc.local... * Starting Tomcat servlet engine tomcat8 ...fail! guacd[37]: INFO: Guacamole proxy daemon (guacd) version 0.9.14 started Starting guacd: SUCCESS *** Booting runit daemon... *** Runit started as PID 40 Database exists. Database upgrade not needed. Starting MariaDB... 180925 18:32:42 mysqld_safe Logging to '/config/databases/guacamole.local.err'. 180925 18:32:42 mysqld_safe Starting mysqld daemon with databases from /config/databases Sep 25 18:32:42 guacamole syslog-ng[46]: syslog-ng starting up; version='3.5.6'

Having an issue with Flood seeming to become unresponsive after about a day. Sometimes restarting the container corrects it, but other times I need to blow away the container and recreate it. I have DEBUG set to true, but there is nothing in the container logs. Is this an already known issue? The port seems to still be responsive, but the webUI times out.