Uploaded image for project: 'Guacamole'
  1. Guacamole
  2. GUACAMOLE-1202

Guacamole server error "The remote desktop server is currently unreachable" even RDP is working from default remote desktop connect

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Invalid
    • 1.2.0
    • None
    • guacamole
    • None
    • Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-52-generic x86_64)
      10 CPU cores, 60 GB RAM (guaranteed), 1600 GB disk space (100% SSD), 100% SSD disk space, UNLIMITED traffic, 1 Gbit/s port
    • Important

    Description

      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.

      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.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            asquare Arpit Agarwal
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: