[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625882#comment-16625882
]
emma commented on GUACAMOLE-567:
Hi Michael, i've made a quick test few days ago with github version an seems
better, no such warning message during connection or disconnection process.
Sounds good :).
Still waiting the new release to deploy in production
Thank you
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png, guacd-0.9.4.txt,
> guacd-1.0.0.txt, image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608098#comment-16608098
]
Mathias commented on GUACAMOLE-567:
---
I have attached my logs. [^guacd-1.0.0.txt] [^guacd-0.9.4.txt]
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png, guacd-0.9.4.txt,
> guacd-1.0.0.txt, image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16608087#comment-16608087
]
Mathias commented on GUACAMOLE-567:
---
I have tested your last Docker (mjumper/guacd) build from
2018-08-30T16:32:38.050Z. I get a connection problem with XRDP 0.9.5.
{code:JSON}
{"log":"guacd[8]: INFO:\u0009Guacamole proxy daemon (guacd) version 1.0.0
started\n","stream":"stderr","time":"2018-09-08T14:46:55.0
86034103Z"}
{"log":"guacd[8]: INFO:\u0009Listening on host 0.0.0.0, port
4822\n","stream":"stderr","time":"2018-09-08T14:46:55.086120414Z"}
{"log":"guacd[8]: INFO:\u0009Creating new client for protocol
\"rdp\"\n","stream":"stderr","time":"2018-09-08T14:48:40.351180304Z"}
{"log":"guacd[8]: INFO:\u0009Connection ID is
\"$6849814c-f86b-4cb8-80f3-5ae6cb6bba18\"\n","stream":"stderr","time":"2018-09-08T14:4
8:40.352306635Z"}
{"log":"guacd[152]: INFO:\u0009Security mode:
ANY\n","stream":"stderr","time":"2018-09-08T14:48:40.727309741Z"}
{"log":"guacd[152]: INFO:\u0009Resize method:
none\n","stream":"stderr","time":"2018-09-08T14:48:40.727356256Z"}
{"log":"guacd[152]: INFO:\u0009User \"@103648c7-d1ac-4686-809b-dd9184a7746b\"
joined connection \"$6849814c-f86b-4cb8-80f3-5ae6cb6bb
a18\" (1 users now
present)\n","stream":"stderr","time":"2018-09-08T14:48:40.727453014Z"}
{"log":"guacd[152]: INFO:\u0009Loading keymap
\"base\"\n","stream":"stderr","time":"2018-09-08T14:48:40.752714426Z"}
{"log":"guacd[152]: INFO:\u0009Loading keymap
\"de-de-qwertz\"\n","stream":"stderr","time":"2018-09-08T14:48:40.752762824Z"}
{"log":"connected to
192.168.10.100:3389\n","stream":"stderr","time":"2018-09-08T14:48:40.805155915Z"}
{"log":"Unable to find a match for unix timezone:
Etc/UTC\n","stream":"stderr","time":"2018-09-08T14:48:40.841940371Z"}
{"log":"guacd[152]: INFO:\u0009guacdr
connected.\n","stream":"stderr","time":"2018-09-08T14:48:40.852888275Z"}
{"log":"guacd[152]: INFO:\u0009guacsnd
connected.\n","stream":"stderr","time":"2018-09-08T14:48:40.854257982Z"}
{"log":"guacd[152]: INFO:\u0009Accepted format: 16-bit PCM with 2 channels at
44100 Hz\n","stream":"stderr","time":"2018-09-08T14:48:41.524993399Z"}
{"log":"guacd[152]: INFO:\u0009Accepted format: 16-bit PCM with 2 channels at
22050 Hz\n","stream":"stderr","time":"2018-09-08T14:48:41.525145575Z"}
{"log":"guacd[152]: INFO:\u0009Connected to RDPDR 1.12 as client
0x9e318c3d\n","stream":"stderr","time":"2018-09-08T14:48:41.525174676Z"}
{"log":"guacd[152]: INFO:\u0009User logged
on\n","stream":"stderr","time":"2018-09-08T14:48:41.526519476Z"}
{"log":"guacd[152]: INFO:\u0009Registered device 0 (Guacamole
Filesystem)\n","stream":"stderr","time":"2018-09-08T14:48:41.526543578Z"}
{"log":"guacd[152]: INFO:\u0009All supported devices
sent.\n","stream":"stderr","time":"2018-09-08T14:48:41.526646673Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609384846Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609427163Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609440924Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609452655Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609464175Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609475653Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609487112Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609498472Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609509813Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609521246Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609532682Z"}
{"log":"WaitForSingleObject: unknown handle type
1158295964924184330\n","stream":"stderr","time":"2018-09-08T14:48:41.609544047Z"}
{/code}
Docker container guacamole/gaucd:0.9.4 is working well.
{code:text}
guacd[1]: INFO: Guacamole proxy daemon (guacd) version 0.9.14 started
guacd[1]: INFO: Listening on host 0.0.0.0, port 4822
guacd[1]: INFO: Creating new client for protocol "rdp"
guacd[1]: INFO: Connection ID is "$b6fd74a6-3230-4528-844e-372e67db875f"
guacd[23]: INFO:Security mode: ANY
guacd[23]: INFO:Resize method: none
guacd[23]: INFO:User "@2450c796-2eac-4fc1-8976-03716ad26a70" joined
connection
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607571#comment-16607571
]
Michael Jumper commented on GUACAMOLE-567:
--
OK - I believe I have this fixed through adding actual, explicit stability
tests which are independent of the Guacamole connection:
https://github.com/apache/guacamole-client/pull/312
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583676#comment-16583676
]
Mathias commented on GUACAMOLE-567:
---
Hello Michael Jumper,
I have tested your Docker images (mjumper/guacamole and mjumper/guacd -
2018-08-11), with xRDP version 0.9.5.
I get immediately a connection problem.
The solution was, to switch back to Guacd version 0.9.14 from Docker
(guacamole/guacd).
The connection is working stable with Guacamole 1.0.0 (Docker images
mjumper/guacamole:latest) and Guacd 0.9.14 Docker image
(guacamole/guacd:latest).
I did not analyze Guacd's changes, but it needs more tested and investigated.
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495262#comment-16495262
]
emma commented on GUACAMOLE-567:
Hi,
today i just build from github the release 1.0.0 with new improvements,
patches, bug fixes on my Ubuntu Server 16.04.3 LTS (GNU/Linux 4.4.0-62-generic
x86_64) with Tomcat8 and that's it, nothing more, nothing less.
This server is my test server and previously i was running github 1.0.0.
version builded March the 3rd.
So i test connection on my differents servers (2003/2008/2012) and for most of
them i notice i get during the first connection the message with logo about
"Network connection unstable" despite the fact i am testing on my local
network, not on remote through internet.
Then once im connected and Windows session is opened, i disconnect from my
Windows server and the closing session seems to hang few seconds then i get
connection error screen.
!Network_Connection1.png!
!Network_Connection2.png!
If i reconnect on the same server, this kind of message disappeared and
disconnection seems to works fine on 2003 and 2008 servers. On my 2012 server i
almost always get "Network connection unstable" and "error connection" message
on disconnect !
It looks like, if there is a long time you didn't initiate a connection on a
server, then you get "network connection unstable" message with logo, once you
made at least one successful connection then disconnect works normally without
any "connection error" screen, except on 2012 server where i almost always
encounter this "problem" and message.
Or it is like at the very first connection on a server you get message during
disconnection process
!Network_Connection4.png!
then you get the message
!Network_Connection5.png!
If i wait or click Reconnect and then cancel without logging for example, the
disconnection works fine
!Network_Connection6.png!
Made another test with a 2003 Server and first time i am connecting on with
that new version of guacamole, then i get the same behavior
!Network_Connection7.png!
!Network_Connection8.png!
It is just a test but before that "Network connection problem
acknowledgement/feedback" case, i never have this behavior during disconnection
screen !
Don't know if other testers can confirm that fact ?
Many thanks for your great job, Guacamole rocks !
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492925#comment-16492925
]
Michael Jumper commented on GUACAMOLE-567:
--
I don't believe so. When the API docs are regenerated (in this case by running
JSDoc), they will naturally pick up the documentation for the parts of the API
that changed, as that documentation was part of the code that was merged.
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492544#comment-16492544
]
Nick Couchman commented on GUACAMOLE-567:
-
Guessing there's also some API documentation that needs to be updated for this
one before it gets closed?
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
