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
