[
https://issues.apache.org/jira/browse/GUACAMOLE-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271380#comment-17271380
]
Dominik Borkowski commented on GUACAMOLE-1271:
----------------------------------------------
Thank you for the reply, and your input on what's happening with the
application (clean shutdown as opposed to a failure/crash) pointed me to the
right direction.
With guacamole 1.3.0 no longer bundling Apache Tomcat Manager, AWS load
balancer checks for HTTP 20X response codes on / URL were failing, causing the
target group to take down the task definition. After reconfiguring the load
balancer to check /guacamole/ instead, everything is back to normal.
Thank you, please consider this issue to be solved, though it may be worth
mentioning that in the Changelog, if somebody else runs into similar issues.
Cheers!
> Debugging failing guacamole client container in AWS ECS
> -------------------------------------------------------
>
> Key: GUACAMOLE-1271
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1271
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
> Affects Versions: 1.3.0
> Environment: Amazon ECS (Amazon Linux 2)
> Reporter: Dominik Borkowski
> Priority: Minor
>
> Hello,
> We use both the client and server guacamole images in Amazon ECS. With recent
> attempt to switch to version 1.3.0 the client containers seem to die upon
> start with the following error:
> {code:none}
> 19-Jan-2021 20:17:21.304 INFO [localhost-startStop-1]
> org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
> application archive [/usr/local/tomcat/webapps/guacamole.war] has finished in
> [4,873] ms
> 19-Jan-2021 20:17:21.307 INFO [main] org.apache.coyote.AbstractProtocol.start
> Starting ProtocolHandler ["http-nio-8080"]
> 19-Jan-2021 20:17:21.316 INFO [main]
> org.apache.catalina.startup.Catalina.start Server startup in 4981 ms
> 19-Jan-2021 20:19:55.238 INFO [Thread-4]
> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> ["http-nio-8080"]
> 19-Jan-2021 20:19:55.254 INFO [Thread-4]
> org.apache.catalina.core.StandardService.stopInternal Stopping service
> [Catalina]
> 19-Jan-2021 20:19:55.285 WARNING [localhost-startStop-2]
> org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The
> web application [guacamole] appears to have started a thread named
> [com.google.inject.internal.util.$Finalizer] but has failed to stop it. This
> is very likely to create a memory leak. Stack trace of thread:
> java.lang.Object.wait(Native Method)
> java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
> java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
> com.google.inject.internal.util.$Finalizer.run(Finalizer.java:114)
> 19-Jan-2021 20:19:55.296 INFO [Thread-4]
> org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler
> ["http-nio-8080"]
> 19-Jan-2021 20:19:55.299 INFO [Thread-4]
> org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler
> ["http-nio-8080"]
> {code}
> Additional information:
> * Affected image is `guacamole/guacamole:1.3.0`, while
> `guacamole/guacamole:1.2.0` works just fine, as do all the earlier versions
> * Switching back and forth reliably shows that 1.3.0 fails, while 1.2.0
> works fine
> * `guacamole/guacd:1.3.0` works fine
> * Local execution of `guacamole/guacamole:1.3.0` works fine
> * Building from source code at branch 1.3.0 and using that with ECS shows
> the same exact error
>
> I'm a bit at a loss as to how to debug this further. Guacd has an option for
> additional debugging that can be enabled via an environment variable, but I
> can't seem to find one for the client.
> I'd appreciate any input, thank you in advance!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
