On Fri, Oct 30, 2020 at 1:05 PM Arpit Agarwal <[email protected]> wrote:

> Hello,
>
> I am getting the error message "The remote desktop server is currently
> unreachable" in case of some RDP access while it is accessible by a normal
> RDP client. The RDP has windows 2016 os and working fine. This is an issue
> some time for some RDP only not for all. The other RDP which are accessible
> also has the same os. Please help me to solve this issue. The log is below.
> I am not techy so please help me to solve this issue.
>

The logs below are Tomcat logs - can you also pull your logs for guacd and
see what they are showing?


> 30-Oct-2020 03:02:45.776 WARNING [http-nio-80-exec-10] 
> org.apache.ibatis.logging.jdk14.Jdk14LoggingImpl.warn
> Execution of ping query 'SELECT 1' failed: The last packet successfully
> received from the server was 51,251,740 milliseconds ago. The last packet
> sent successfully to the server was 51,251,740 milliseconds ago. is longer
> than the server configured value of 'wait_timeout'. You should consider
> either expiring and/or testing connection validity before use in your
> application, increasing the server configured values for client timeouts,
> or using the Connector/J connection property 'autoReconnect=true' to avoid
> this problem.
> 30-Oct-2020 03:02:45.843 WARNING [http-nio-80-exec-10] 
> org.apache.ibatis.logging.jdk14.Jdk14LoggingImpl.warn
> Execution of ping query 'SELECT 1' failed: The last packet successfully
> received from the server was 51,251,903 milliseconds ago. The last packet
> sent successfully to the server was 51,251,903 milliseconds ago. is longer
> than the server configured value of 'wait_timeout'. You should consider
> either expiring and/or testing connection validity before use in your
> application, increasing the server configured values for client timeouts,
> or using the Connector/J connection property 'autoReconnect=true' to avoid
> this problem.
> 30-Oct-2020 03:02:45.856 WARNING [http-nio-80-exec-10] 
> org.apache.ibatis.logging.jdk14.Jdk14LoggingImpl.warn
> Execution of ping query 'SELECT 1' failed: The last packet successfully
> received from the server was 50,908,390 milliseconds ago. The last packet
> sent successfully to the server was 50,908,390 milliseconds ago. is longer
> than the server configured value of 'wait_timeout'. You should consider
> either expiring and/or testing connection validity before use in your
> application, increasing the server configured values for client timeouts,
> or using the Connector/J connection property 'autoReconnect=true' to avoid
> this problem.
> 30-Oct-2020 03:02:45.867 WARNING [http-nio-80-exec-10] 
> org.apache.ibatis.logging.jdk14.Jdk14LoggingImpl.warn
> Execution of ping query 'SELECT 1' failed: The last packet successfully
> received from the server was 49,473,066 milliseconds ago. The last packet
> sent successfully to the server was 49,473,066 milliseconds ago. is longer
> than the server configured value of 'wait_timeout'. You should consider
> either expiring and/or testing connection validity before use in your
> application, increasing the server configured values for client timeouts,
> or using the Connector/J connection property 'autoReconnect=true' to avoid
> this problem.
> 30-Oct-2020 03:02:45.907 WARNING [http-nio-80-exec-10] 
> org.apache.ibatis.logging.jdk14.Jdk14LoggingImpl.warn
> Execution of ping query 'SELECT 1' failed: The last packet successfully
> received from the server was 47,613,050 milliseconds ago. The last packet
> sent successfully to the server was 47,613,050 milliseconds ago. is longer
> than the server configured value of 'wait_timeout'. You should consider
> either expiring and/or testing connection validity before use in your
> application, increasing the server configured values for client timeouts,
> or using the Connector/J connection property 'autoReconnect=true' to avoid
> this problem.
>
>
I'm not sure where your guacamole server is in relation to the RDP server,
but the above messages indicate that there are some connectivity issues
between Guacamole Client and the MySQL database - traffic is either getting
blocked, or delayed in a huge way (the times above are like 10-15 hours).
So, it looks like there are probably some network issues with your
Guacamole server - we're going to need a lot more detailed information
(architecture, logs, etc.) to figure out what.

-Nick

Reply via email to