[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223475#comment-17223475
 ] 

Arpit Agarwal commented on GUACAMOLE-1202:
------------------------------------------

Below is the message got for a bounce back

 

 

Hi. This is the qmail-send program at [apache.org|http://apache.org/].
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[[email protected]|mailto:[email protected]]>:
Must be sent from an @apache.org address or a subscriber address or an address 
in LDAP.

--- Below this line is a copy of the message.

Return-Path: <[[email protected]|mailto:[email protected]]>
Received: (qmail 45457 invoked by uid 99); 30 Oct 2020 07:27:29 -0000
Received: from [spamproc1-he-de.apache.org|http://spamproc1-he-de.apache.org/] 
(HELO [spamproc1-he-de.apache.org|http://spamproc1-he-de.apache.org/]) 
(116.203.196.100)
   by [apache.org|http://apache.org/] (qpsmtpd/0.29) with ESMTP; Fri, 30 Oct 
2020 07:27:29 +0000
Received: from localhost (localhost [127.0.0.1])
 by [spamproc1-he-de.apache.org|http://spamproc1-he-de.apache.org/] (ASF Mail 
Server at [spamproc1-he-de.apache.org|http://spamproc1-he-de.apache.org/]) with 
ESMTP id B28811FF39C
 for <[[email protected]|mailto:[email protected]]>; Fri, 30 
Oct 2020 07:27:28 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
[spamproc1-he-de.apache.org|http://spamproc1-he-de.apache.org/]
X-Spam-Flag: NO
X-Spam-Score: 0.005

> Guacamole server error "The remote desktop server is currently unreachable" 
> even RDP is working from default remote desktop connect
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1202
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1202
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>    Affects Versions: 1.2.0
>         Environment: 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
>            Reporter: Arpit Agarwal
>            Priority: Blocker
>
> 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.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to