You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Nicolas CHARREL <ni...@fiducialcloud.fr> on 2019/07/16 15:48:16 UTC
Guacd buggy connexion cannot be killed
Hello,
I have a lot of buggy connexion on my active sessions:
[https://issues.apache.org/jira/secure/attachment/12974840/12974840_image-2019-07-16-17-22-11-245.png]
When I try to delete all the connexion I have this :
[https://issues.apache.org/jira/secure/attachment/12974839/12974839_image-2019-07-16-17-23-57-145.png]
Nothing on Guacd
root@bastion:~# guacd -L trace -f
guacd[2709]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
guacd[2709]: DEBUG: Unable to bind socket to host ::1, port 4822: Address family not supported by protocol
guacd[2709]: DEBUG: Unable to bind socket to host 127.0.0.1, port 4822: Address already in use
guacd[2709]: ERROR: Unable to bind socket to any addresses.
root@bastion:~# service guacd stop
root@bastion:~# guacd -L trace -f
guacd[2739]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
guacd[2739]: DEBUG: Unable to bind socket to host ::1, port 4822: Address family not supported by protocol
guacd[2739]: DEBUG: Successfully bound socket to host 127.0.0.1, port 4822
guacd[2739]: INFO: Listening on host 127.0.0.1, port 4822
When I go back on active session:
[https://issues.apache.org/jira/secure/attachment/12974838/12974838_image-2019-07-16-17-24-42-688.png]
My only way to have a reset is to reboot tomcat.
Could you help me to resolve this bug ?
PS: You can find a copy of this message on Jira here : https://issues.apache.org/jira/browse/GUACAMOLE-845
Thanks.
[cid:part1.A5D99575.889B3CB1@fiducial.net]<http://www.fiducialcloud.fr/>
PARIS | LYON | MARSEILLE
[cid:image003.jpg@01D25B80.0C241B00]
Nicolas CHARREL
Ingénieur Sécurité
Direct : +33 4 69 16 38 82
19 Rue Cottin - 69009 LYON
www.fiducialcloud.fr<http://www.fiducialcloud.fr/>
Re: Guacd buggy connexion cannot be killed
Posted by Mike Jumper <mj...@apache.org>.
On Sat, Jul 20, 2019 at 12:45 PM Nick Couchman <vn...@apache.org> wrote:
> On Wed, Jul 17, 2019 at 4:35 AM Nicolas CHARREL <
> nicolas.charrel@fiducialcloud.fr> wrote:
>
>> ...
>>
> You should also check the logs from Guacamole (the Tomcat logs).
>>
>>
>>
>> In catalina.out I have nothing
>>
>
> There should be something there. Restart and monitor both catalina.out
> and the guacd output from the time that you start the "buggy" connection(s).
>
Depending on how things were installed and the Linux distribution in use,
Tomcat may be logging to the systemd journal.
- Mike
Re: Guacd buggy connexion cannot be killed
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Jul 17, 2019 at 4:35 AM Nicolas CHARREL <
nicolas.charrel@fiducialcloud.fr> wrote:
> Hello Mike and thank you for your help.
>
>
>
> *De :* Mike Jumper <mj...@apache.org>
> *Envoyé :* mardi 16 juillet 2019 19:59
> *À :* user@guacamole.apache.org
> *Objet :* Re: Guacd buggy connexion cannot be killed
>
>
>
> On Tue, Jul 16, 2019 at 8:48 AM Nicolas CHARREL <
> nicolas.charrel@fiducialcloud.fr> wrote:
>
> Hello,
>
> I have a lot of buggy connexion on my active sessions:
>
>
>
> What do you mean by "buggy"? When I tried to open a connexion which is
> not working (bad password, no open ports…)
>
>
>
> When I try to delete all the connexion I have this :
>
>
>
> Is there anything on the network which might be rejecting HTTP DELETE
> requests?
>
>
>
> On the browser I see this:
>
>
>
> On the RP (apache):
>
> - - [17/Jul/2019:10:21:56 +0200] "PATCH
> /api/session/data/mysql/activeConnections?token=E88A4E84738F275EBDA6CE72048ADF9691992F0F66E8197AEF6DD3FA9A097DED
> HTTP/1.1" 204 429 "https://guaca/" "Mozilla/5.0 (Windows NT 10.0; Win64;
> x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100
> Safari/537.36"
>
>
>
> On Tomcat:
>
>
>
> Seems to work, isn’t it ?
>
>
>
> Nothing on Guacd
>
> root@bastion:~# guacd -L trace -f
>
> guacd[2709]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
>
> guacd[2709]: DEBUG: Unable to bind socket to host ::1, port 4822: Address
> family not supported by protocol
>
> guacd[2709]: DEBUG: Unable to bind socket to host 127.0.0.1, port 4822:
> Address already in use
>
> guacd[2709]: ERROR: Unable to bind socket to any addresses.
>
> root@bastion:~# service guacd stop
>
> root@bastion:~# guacd -L trace -f
>
> guacd[2739]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
>
> guacd[2739]: DEBUG: Unable to bind socket to host ::1, port 4822: Address
> family not supported by protocol
>
> guacd[2739]: DEBUG: Successfully bound socket to host 127.0.0.1, port 4822
>
> guacd[2739]: INFO: Listening on host 127.0.0.1, port 4822
>
>
>
> Are you running this after the previous attempt to kill the connections?
> If this is before the attempt to kill connections, there should be log
> output from when those connections were established. If this is after, you
> would need to reproduce what you saw before in order to see any messages
> from guacd. The relevant process would be the one you stopped with "service
> guacd stop", and the relevant log messages would be in syslog.
>
>
>
> I just start the deamon guacd to have a clean logs but all my buggy
> connexion was already in guacamole client before I start my guacd. And When
> I tried to remove those connexion I have the above logs on guacd.
>
You can restart Tomcat to clear out the active connections. I'd suggest
restarting both guacd and Tomcat before debugging any further so that you
have a clean slate.
>
>
> You should also check the logs from Guacamole (the Tomcat logs).
>
>
>
> In catalina.out I have nothing
>
There should be something there. Restart and monitor both catalina.out and
the guacd output from the time that you start the "buggy" connection(s).
-Nick
>
RE: Guacd buggy connexion cannot be killed
Posted by Nicolas CHARREL <ni...@fiducialcloud.fr>.
Hello Mike and thank you for your help.
De : Mike Jumper <mj...@apache.org>
Envoyé : mardi 16 juillet 2019 19:59
À : user@guacamole.apache.org
Objet : Re: Guacd buggy connexion cannot be killed
On Tue, Jul 16, 2019 at 8:48 AM Nicolas CHARREL <ni...@fiducialcloud.fr>> wrote:
Hello,
I have a lot of buggy connexion on my active sessions:
What do you mean by "buggy"? When I tried to open a connexion which is not working (bad password, no open ports…)
When I try to delete all the connexion I have this :
Is there anything on the network which might be rejecting HTTP DELETE requests?
On the browser I see this:
[cid:image001.png@01D53C89.D3ECB830]
[cid:image003.png@01D53C8B.0D4564F0]
On the RP (apache):
- - [17/Jul/2019:10:21:56 +0200] "PATCH /api/session/data/mysql/activeConnections?token=E88A4E84738F275EBDA6CE72048ADF9691992F0F66E8197AEF6DD3FA9A097DED HTTP/1.1" 204 429 "https://guaca/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36"
On Tomcat:
[cid:image004.png@01D53C8B.0D4564F0]
Seems to work, isn’t it ?
Nothing on Guacd
root@bastion:~# guacd -L trace -f
guacd[2709]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
guacd[2709]: DEBUG: Unable to bind socket to host ::1, port 4822: Address family not supported by protocol
guacd[2709]: DEBUG: Unable to bind socket to host 127.0.0.1, port 4822: Address already in use
guacd[2709]: ERROR: Unable to bind socket to any addresses.
root@bastion:~# service guacd stop
root@bastion:~# guacd -L trace -f
guacd[2739]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
guacd[2739]: DEBUG: Unable to bind socket to host ::1, port 4822: Address family not supported by protocol
guacd[2739]: DEBUG: Successfully bound socket to host 127.0.0.1, port 4822
guacd[2739]: INFO: Listening on host 127.0.0.1, port 4822
Are you running this after the previous attempt to kill the connections? If this is before the attempt to kill connections, there should be log output from when those connections were established. If this is after, you would need to reproduce what you saw before in order to see any messages from guacd. The relevant process would be the one you stopped with "service guacd stop", and the relevant log messages would be in syslog.
I just start the deamon guacd to have a clean logs but all my buggy connexion was already in guacamole client before I start my guacd. And When I tried to remove those connexion I have the above logs on guacd.
You should also check the logs from Guacamole (the Tomcat logs).
In catalina.out I have nothing
Could you help me to resolve this bug ?
It is unlikely that this is a bug [1], but yes, we should be able to help figure out what's wrong in your setup.
- Mike
[1] http://guacamole.apache.org/faq/#probably-not-a-bug
Re: Guacd buggy connexion cannot be killed
Posted by Mike Jumper <mj...@apache.org>.
On Tue, Jul 16, 2019 at 8:48 AM Nicolas CHARREL <
nicolas.charrel@fiducialcloud.fr> wrote:
> Hello,
>
> I have a lot of buggy connexion on my active sessions:
>
What do you mean by "buggy"?
When I try to delete all the connexion I have this :
>
Is there anything on the network which might be rejecting HTTP DELETE
requests?
Nothing on Guacd
>
> root@bastion:~# guacd -L trace -f
>
> guacd[2709]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
>
> guacd[2709]: DEBUG: Unable to bind socket to host ::1, port 4822: Address
> family not supported by protocol
>
> guacd[2709]: DEBUG: Unable to bind socket to host 127.0.0.1, port 4822:
> Address already in use
>
> guacd[2709]: ERROR: Unable to bind socket to any addresses.
>
> root@bastion:~# service guacd stop
>
> root@bastion:~# guacd -L trace -f
>
> guacd[2739]: INFO: Guacamole proxy daemon (guacd) version 1.0.0 started
>
> guacd[2739]: DEBUG: Unable to bind socket to host ::1, port 4822: Address
> family not supported by protocol
>
> guacd[2739]: DEBUG: Successfully bound socket to host 127.0.0.1, port 4822
>
> guacd[2739]: INFO: Listening on host 127.0.0.1, port 4822
>
>
Are you running this after the previous attempt to kill the connections? If
this is before the attempt to kill connections, there should be log output
from when those connections were established. If this is after, you would
need to reproduce what you saw before in order to see any messages from
guacd. The relevant process would be the one you stopped with "service
guacd stop", and the relevant log messages would be in syslog.
You should also check the logs from Guacamole (the Tomcat logs).
Could you help me to resolve this bug ?
>
It is unlikely that this is a bug [1], but yes, we should be able to help
figure out what's wrong in your setup.
- Mike
[1] http://guacamole.apache.org/faq/#probably-not-a-bug