You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Manoj Patil <ma...@gmail.com> on 2020/02/05 08:26:12 UTC
Scoket in CLOSE_WAIT
Dear,
When i am connecting xrdp through guacamole i see a error
tcp 3 0 127.0.0.1:3350 0.0.0.0:* LISTEN
8256/xrdp-sesman
tcp 0 1 127.0.0.1:29380 127.0.0.1:3350
SYN_SENT 406/xrdp
tcp 130 0 127.0.0.1:3350 127.0.0.1:26992
CLOSE_WAIT -
tcp 130 0 127.0.0.1:3350 127.0.0.1:26882
CLOSE_WAIT -
tcp 0 1 127.0.0.1:29394 127.0.0.1:3350
SYN_SENT 502/xrdp
tcp 0 1 127.0.0.1:29400 127.0.0.1:3350
SYN_SENT -
tcp 131 0 127.0.0.1:3350 127.0.0.1:26980
CLOSE_WAIT -
tcp 0 1 127.0.0.1:29392 127.0.0.1:3350
SYN_SENT 422/xrdp
tcp 0 1 127.0.0.1:29382 127.0.0.1:3350
SYN_SENT 437/xrdp
tcp 0 1 127.0.0.1:29384 127.0.0.1:3350
SYN_SENT 450/xrdp
--
Thanks & Regards,
Manoj Patil.(Asst. Manager DBA)
Netwin Systems & Softwares(I) Pvt.Ltd
Nasik.
Mobile No -+91-9922507588
Email- manoj2patil@gmail.com
Re: Scoket in CLOSE_WAIT
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Feb 5, 2020 at 8:09 AM Manoj Patil <ma...@gmail.com> wrote:
> 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 ?
>
>
First, I would suggest that you try another RDP client and validate that
the behavior is the same. If you use, for example, Microsoft Remote
Desktop Client instead of Guacamole, do you see the same behavior. I would
be willing to wager some money you will.
Beyond that, I'd suggest that you reach out within the xrdp community and
get support from them. There may be some resources within their community
that would be able to help track down why the xrdp<->sesman connection
hangs open and suggest what you might be able to do to resolve the
problem. I do not think there is anything - workaround or permanent fix -
on the Guacamole side that will resolve this issue.
-Nick
Re: Scoket in CLOSE_WAIT
Posted by Manoj Patil <ma...@gmail.com>.
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 <vn...@apache.org> wrote:
> On Wed, Feb 5, 2020 at 5:38 AM Manoj Patil <ma...@gmail.com> 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- manoj2patil@gmail.com
Re: Scoket in CLOSE_WAIT
Posted by Nick Couchman <vn...@apache.org>.
On Wed, Feb 5, 2020 at 5:38 AM Manoj Patil <ma...@gmail.com> 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
Re: Scoket in CLOSE_WAIT
Posted by Manoj Patil <ma...@gmail.com>.
It seems that XRDP is not cleaning sockets(CLOSE_WAIT state) as because
it's not receiving last close acknowledgment from guacamole/client side.
Can we initiate socket close from guacamole periodically ?
On Wed, 5 Feb 2020 at 16:02, Manoj Patil <ma...@gmail.com> wrote:
> when close_wait occures that time user can not connect to server through
> guacamole.
>
> On Wed, 5 Feb 2020 at 14:39, Mike Jumper <mj...@apache.org> wrote:
>
>> On Wed, Feb 5, 2020, 00:26 Manoj Patil <ma...@gmail.com> wrote:
>>
>>> Dear,
>>>
>>> When i am connecting xrdp through guacamole i see a error
>>>
>>> tcp 3 0 127.0.0.1:3350 0.0.0.0:*
>>> LISTEN 8256/xrdp-sesman
>>> tcp 0 1 127.0.0.1:29380 127.0.0.1:3350
>>> SYN_SENT 406/xrdp
>>> tcp 130 0 127.0.0.1:3350 127.0.0.1:26992
>>> CLOSE_WAIT -
>>> tcp 130 0 127.0.0.1:3350 127.0.0.1:26882
>>> CLOSE_WAIT -
>>> tcp 0 1 127.0.0.1:29394 127.0.0.1:3350
>>> SYN_SENT 502/xrdp
>>> tcp 0 1 127.0.0.1:29400 127.0.0.1:3350
>>> SYN_SENT -
>>> tcp 131 0 127.0.0.1:3350 127.0.0.1:26980
>>> CLOSE_WAIT -
>>> tcp 0 1 127.0.0.1:29392 127.0.0.1:3350
>>> SYN_SENT 422/xrdp
>>> tcp 0 1 127.0.0.1:29382 127.0.0.1:3350
>>> SYN_SENT 437/xrdp
>>> tcp 0 1 127.0.0.1:29384 127.0.0.1:3350
>>> SYN_SENT 450/xrdp
>>>
>>
>> What error? This looks to be the output from netstat, showing several
>> sockets which have been closed by the client (presumably Guacamole) but the
>> XRDP side has not yet cleaned things up.
>>
>> - Mike
>>
>>
>
> --
> Thanks & Regards,
>
> Manoj Patil.(Asst. Manager DBA)
> Netwin Systems & Softwares(I) Pvt.Ltd
> Nasik.
> Mobile No -+91-9922507588
> Email- manoj2patil@gmail.com
>
--
Thanks & Regards,
Manoj Patil.(Asst. Manager DBA)
Netwin Systems & Softwares(I) Pvt.Ltd
Nasik.
Mobile No -+91-9922507588
Email- manoj2patil@gmail.com
Re: Scoket in CLOSE_WAIT
Posted by Manoj Patil <ma...@gmail.com>.
when close_wait occures that time user can not connect to server through
guacamole.
On Wed, 5 Feb 2020 at 14:39, Mike Jumper <mj...@apache.org> wrote:
> On Wed, Feb 5, 2020, 00:26 Manoj Patil <ma...@gmail.com> wrote:
>
>> Dear,
>>
>> When i am connecting xrdp through guacamole i see a error
>>
>> tcp 3 0 127.0.0.1:3350 0.0.0.0:*
>> LISTEN 8256/xrdp-sesman
>> tcp 0 1 127.0.0.1:29380 127.0.0.1:3350
>> SYN_SENT 406/xrdp
>> tcp 130 0 127.0.0.1:3350 127.0.0.1:26992
>> CLOSE_WAIT -
>> tcp 130 0 127.0.0.1:3350 127.0.0.1:26882
>> CLOSE_WAIT -
>> tcp 0 1 127.0.0.1:29394 127.0.0.1:3350
>> SYN_SENT 502/xrdp
>> tcp 0 1 127.0.0.1:29400 127.0.0.1:3350
>> SYN_SENT -
>> tcp 131 0 127.0.0.1:3350 127.0.0.1:26980
>> CLOSE_WAIT -
>> tcp 0 1 127.0.0.1:29392 127.0.0.1:3350
>> SYN_SENT 422/xrdp
>> tcp 0 1 127.0.0.1:29382 127.0.0.1:3350
>> SYN_SENT 437/xrdp
>> tcp 0 1 127.0.0.1:29384 127.0.0.1:3350
>> SYN_SENT 450/xrdp
>>
>
> What error? This looks to be the output from netstat, showing several
> sockets which have been closed by the client (presumably Guacamole) but the
> XRDP side has not yet cleaned things up.
>
> - Mike
>
>
--
Thanks & Regards,
Manoj Patil.(Asst. Manager DBA)
Netwin Systems & Softwares(I) Pvt.Ltd
Nasik.
Mobile No -+91-9922507588
Email- manoj2patil@gmail.com
Re: Scoket in CLOSE_WAIT
Posted by Mike Jumper <mj...@apache.org>.
On Wed, Feb 5, 2020, 00:26 Manoj Patil <ma...@gmail.com> wrote:
> Dear,
>
> When i am connecting xrdp through guacamole i see a error
>
> tcp 3 0 127.0.0.1:3350 0.0.0.0:*
> LISTEN 8256/xrdp-sesman
> tcp 0 1 127.0.0.1:29380 127.0.0.1:3350
> SYN_SENT 406/xrdp
> tcp 130 0 127.0.0.1:3350 127.0.0.1:26992
> CLOSE_WAIT -
> tcp 130 0 127.0.0.1:3350 127.0.0.1:26882
> CLOSE_WAIT -
> tcp 0 1 127.0.0.1:29394 127.0.0.1:3350
> SYN_SENT 502/xrdp
> tcp 0 1 127.0.0.1:29400 127.0.0.1:3350
> SYN_SENT -
> tcp 131 0 127.0.0.1:3350 127.0.0.1:26980
> CLOSE_WAIT -
> tcp 0 1 127.0.0.1:29392 127.0.0.1:3350
> SYN_SENT 422/xrdp
> tcp 0 1 127.0.0.1:29382 127.0.0.1:3350
> SYN_SENT 437/xrdp
> tcp 0 1 127.0.0.1:29384 127.0.0.1:3350
> SYN_SENT 450/xrdp
>
What error? This looks to be the output from netstat, showing several
sockets which have been closed by the client (presumably Guacamole) but the
XRDP side has not yet cleaned things up.
- Mike