Guacd not responding

[Manoj Patil <ma...@gmail.com>]

Dear,

Suddenly i have issue with guacd it is not responding and using high cpu

Mar 13 16:31:57 lapp56te guacd[5015]: guacd[11063]: INFO:        Last user
of connection "$626a20bb-f032-49b5-8abb-85f4b1a53b31" disconnected
Mar 13 16:31:57 lapp56te guacd[11714]: User is not responding.
Mar 13 16:31:57 lapp56te guacd[5015]: guacd[11714]: ERROR:        User is
not responding.

-- 
Thanks & Regards,

Manoj Patil.(Asst. Manager DBA)
Netwin Systems & Softwares(I) Pvt.Ltd
Nasik.
Mobile No -+91-9922507588
Email- manoj2patil@gmail.com

Re: Guacd not responding

[Nick Couchman <vn...@apache.org>]

On Sat, Mar 13, 2021 at 6:05 AM Manoj Patil <ma...@gmail.com> wrote:

> Dear,
>
> Suddenly i have issue with guacd it is not responding and using high cpu
>
> Mar 13 16:31:57 lapp56te guacd[5015]: guacd[11063]: INFO:        Last user
> of connection "$626a20bb-f032-49b5-8abb-85f4b1a53b31" disconnected
> Mar 13 16:31:57 lapp56te guacd[11714]: User is not responding.
> Mar 13 16:31:57 lapp56te guacd[5015]: guacd[11714]: ERROR:        User is
> not responding.
>
>
Manoj,
This does not say that guacd is not responding, this is guacd saying that
it has detected that the user is not responding. This means that guacd is
not receiving the responses it believes it should from the client
associated with that instance.

There are several things that could cause this...
- If you're running guacd on the same system as Guacamole Client and you're
seeing high CPU utilization on that system, it could be that you do not
have the required resources for the number and/or type of client traffic
you're seeing and that you need to add resources to the system or move
components around to better balance resource utilization.
- This could also be caused by high resource utilization on the system
running the web browser that is accessing Guacamole. This happens to me
occasionally - I have too many tabs opened in my browser, or a particularly
nasty banner ad eats up all of my system resources, and it causes Guacamole
to disconnect.
- The final more obvious cause would be network issues somewhere between
the user's browser and guacd, including between Tomcat and guacd, but I
don't think these would generally be accompanied by high CPU utilization,
so this sounds unlikely.

If none of the above fit what you're seeing, then you're going to have to
do some more thorough investigation to figure out what is causing guacd to
believe that the user is not responding and shut down the connection. It
certainly isn't out of the realm of possibility that you've encountered a
bug somewhere in guacd, but, as this behavior isn't being widely-reported
among the user community, it seems unlikely.

-NIck