Hello Nick, Technically we can understand what you are trying to tell us and we are appreciating your reply too.
But after digging so much we haven't found any work around for our problem which we are facing. Also we have deployed our solution on production for lots of our clients. so at least at this stage we need some kind of work around for problem instead of root cause solution. Will you please guide us on how to initiate socket close/disconnect request to xrdp from guacamole to release CLOSE_WAIT STATE ? Your guidance will be greatly appreciated. On Wed, 5 Feb 2020 at 17:38, Nick Couchman <[email protected]> wrote: > On Wed, Feb 5, 2020 at 5:38 AM Manoj Patil <[email protected]> wrote: > >> It seems that XRDP is not cleaning sockets(CLOSE_WAIT state) as because >> it's not receiving last close acknowledgment from guacamole/client side. >> >> > Really? It seems to me that the Guacamole side has properly disconnected > - there are no remaining sockets open between Guacamole and xrdp. How can > this be something that Guacamole is not doing properly? > > Also, I tried it in my environment, where I have Guacamole connecting to a > CentOS 7 Linux system running xrdp, and it disconnects cleanly and I see no > waiting CLOSE_WAIT entries in netstat output. > > >> Can we initiate socket close from guacamole periodically ? >> > > This would be a work-around to actually fixing the issue - if Guacamole is > not "properly" disconnecting, it should be fixed to properly disconnect. > Issuing periodic socket close commands from Guacamole is just ignoring the > root issue. > > That said, I doubt it would actually help, anyway, since Guacamole isn't > the one leaving the sockets open - it's xrdp, and it's not between > Guacamole and xrdp, it's between xrdp components (looks like between xrdp > and xrdp-sesman). The issue needs to be addressed in the xrdp components. > > -Nick > -- Thanks & Regards, Manoj Patil.(Asst. Manager DBA) Netwin Systems & Softwares(I) Pvt.Ltd Nasik. Mobile No -+91-9922507588 Email- [email protected]
