Hello Mike and thank you for your help. De : Mike Jumper <[email protected]> Envoyé : mardi 16 juillet 2019 19:59 À : [email protected] Objet : Re: Guacd buggy connexion cannot be killed
On Tue, Jul 16, 2019 at 8:48 AM Nicolas CHARREL <[email protected]<mailto:[email protected]>> 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:[email protected]] [cid:[email protected]] 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:[email protected]] 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
