Print

Print


Or better, write a program that tries to connect to the host:port twice 
(on the socket level is enough).

    Lukasz

On 03.12.2013 11:41, Lukasz Janyst wrote:
> By twice I mean having two connections active at the same time.
>
>     Lukasz
>
> On 03.12.2013 11:39, Lukasz Janyst wrote:
>> Hi Andy,
>>
>>     no, b is not the problem. There was an issue like the one you
>> mention, but it was introduced after migration to IPv6 in master only
>> and fixed immediately after it was discovered. It was never introduced
>> to the stable-3.3.x branch.
>>
>>     Matevz, what you see is really strange. It looks like the system
>> won't let you connect to the host twice... A router issue perhaps? Can
>> you telnet twice to this host:port from your test box?
>>
>> Cheers,
>>     Lukasz
>>
>> On 03.12.2013 07:34, Andrew Hanushevsky wrote:
>>> Hi Matevz,
>>>
>>> On Mon, 2 Dec 2013, Matevz Tadel wrote:
>>>
>>>>> Why don't you just setup an overlay xrootd and try it with that one.
>>>>> You can
>>>>> then trace it, or at least run with '-d'.
>>>>
>>>> Sorry, I'm drawing a blank card from my head on this one :) What
>>>> overlay xrootd? For the server side?
>>> Ah, now I understand the issue. Redirector works fine so you don't even
>>> need to use it. So, you should have drawn a blank card :-)
>>>
>>> Now, that said, in the logs you provided I never see a single successful
>>> connection. You may want to set client debugging at the dump level.
>>>
>>> Anyway, as you know, the client first does a locate for that file and
>>> the connect to each of the end-points to produce a composite dirlist.
>>> While hat does not appear in the trace output it does seem to have
>>> occurred. But the connect to the locate response doesn't work. So,
>>>
>>> a) Can you actually ssh to the machine using the IP address
>>> 169.228.130.92? You probably can.
>>>
>>> b) What version are you running of the client? Older versions (probably
>>> 3.3.3 or below) didn't always properly handle an IP address that was
>>> returned in deprecated format. Try 3.3.4 or x5.
>>>
>>> c) Actually, Lukasz can tell you when that issue was fixed.
>>>
>>> I suspect that (b) is the culprit issue here.
>>>
>>> Andy
>>>
>>>   > >> Anyway, I think the problem is on your
>>>>> end....
>>>>
>>>> Yes, I know :) but I can't figure it out ...
>>>>
>>>>> On Mon, 2 Dec 2013, Matevz Tadel wrote:
>>>>>
>>>>>>>> 1a. Connecting with 3.3.3 client, error is "host not found":
>>>>>>>> http://uaf-2.t2.ucsd.edu/~matevz/xrd/ls-fun/3.3.3-slc5--3.3.3-slc5.clog
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> http://uaf-2.t2.ucsd.edu/~matevz/xrd/ls-fun/3.3.3-slc5--3.3.3-slc5.clogstrace
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> This is the same issue as the one below....
>>>>>
>>>>>>>> 1b. Connecting with master client, error is "connection timeout"
>>>>>>>> http://uaf-2.t2.ucsd.edu/~matevz/xrd/ls-fun/3.3.3-slc5--master-f19.clog
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> http://uaf-2.t2.ucsd.edu/~matevz/xrd/ls-fun/3.3.3-slc5--master-f19.clogstrace
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> Well of course, because it was actually trying to connect to
>>>>> nfs-5.t2.ucsd.edu and there seems to eb a firewall preventing it from
>>>>> getting
>>>>> there. Why where you trying to go there? Presumably because it got
>>>>> redirect when
>>>>> you did "ls /nfs-5/".
>>>>
>>>> Yes, but this is the same machine I connected to originally ... and it
>>>> worked ok for the first connection / login ... and then client is told
>>>> to connect one more time to the same machine/port to issue the ls
>>>> request. See below the client log when this actually succeeds on a
>>>> slc6 machine at UCSD.
>>>>
>>>>> So, I don't see a problem other then you are goingto a machine which
>>>>> is behind a
>>>>> firewall and you happento be onthe other side.
>>>>
>>>> Yes, I know it looks like that ... but it isn't. The same happens if I
>>>> stop iptables completely.
>>>>
>>>> Matevz
>>>>
>>>>
>>>> matevz@desire ~> XRD_CONNECTIONWINDOW=50 XRD_LOGLEVEL=Debug xrdfs
>>>> cabinet-10-10-10.t2.ucsd.edu:9940 ls /opt
>>>> [2013-12-02 21:52:01.457868 -0800][Debug  ][App               ]
>>>> Executing: ls /opt
>>>> [2013-12-02 21:52:01.457994 -0800][Debug  ][App               ]
>>>> Attempting to list: /opt
>>>> [2013-12-02 21:52:01.458120 -0800][Debug  ][Poller            ]
>>>> Available pollers: built-in
>>>> [2013-12-02 21:52:01.458141 -0800][Debug  ][Poller            ]
>>>> Attempting to create a poller according to preference:
>>>> built-in,libevent
>>>> [2013-12-02 21:52:01.458153 -0800][Debug  ][Poller            ]
>>>> Creating poller: built-in
>>>> [2013-12-02 21:52:01.458165 -0800][Debug  ][Poller            ]
>>>> Creating and starting the built-in poller...
>>>> [2013-12-02 21:52:01.458369 -0800][Debug  ][TaskMgr           ]
>>>> Starting the task manager...
>>>> [2013-12-02 21:52:01.458425 -0800][Debug  ][TaskMgr           ] Task
>>>> manager started
>>>> [2013-12-02 21:52:01.458446 -0800][Debug  ][JobMgr            ]
>>>> Starting the job manager...
>>>> [2013-12-02 21:52:01.458511 -0800][Debug  ][JobMgr            ] Job
>>>> manager started, 3 workers
>>>> [2013-12-02 21:52:01.458531 -0800][Debug  ][TaskMgr           ]
>>>> Registering task: "FileTimer task" to be run at: [2013-12-02 21:52:01
>>>> -0800]
>>>> [2013-12-02 21:52:01.458576 -0800][Debug  ][PostMaster        ]
>>>> Creating new channel to: cabinet-10-10-10.t2.ucsd.edu:9940 1 stream(s)
>>>> [2013-12-02 21:52:01.458618 -0800][Debug  ][PostMaster        ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0] Stream parameters: Network
>>>> Stack: IPAll, Connection Window: 50, ConnectionRetry: 5, Stream Error
>>>> Widnow: 1800
>>>> [2013-12-02 21:52:01.460855 -0800][Debug  ][TaskMgr           ]
>>>> Registering task: "TickGeneratorTask for:
>>>> cabinet-10-10-10.t2.ucsd.edu:9940" to be run at: [2013-12-02 21:52:16
>>>> -0800]
>>>> [2013-12-02 21:52:01.462712 -0800][Debug  ][PostMaster        ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940] Found 1 address(es):
>>>> [::ffff:169.228.130.155]:9940
>>>> [2013-12-02 21:52:01.462752 -0800][Debug  ][AsyncSock         ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] Attempting connection to
>>>> [::ffff:169.228.130.155]:9940
>>>> [2013-12-02 21:52:01.462803 -0800][Debug  ][Poller            ] Adding
>>>> socket 0x636c50 to the poller
>>>> [2013-12-02 21:52:01.463421 -0800][Debug  ][AsyncSock         ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] Async connection call returned
>>>> [2013-12-02 21:52:01.463470 -0800][Debug  ][XRootDTransport   ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] Sending out the initial hand
>>>> shake + kXR_protocol
>>>> [2013-12-02 21:52:01.465042 -0800][Debug  ][XRootDTransport   ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] Got the server hand shake
>>>> response (type: server [], protocol version 297)
>>>> [2013-12-02 21:52:01.465083 -0800][Debug  ][XRootDTransport   ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] kXR_protocol successful
>>>> (type: server [], protocol version 297)
>>>> [2013-12-02 21:52:01.465203 -0800][Debug  ][XRootDTransport   ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] Sending out kXR_login
>>>> request, username: matevz
>>>> [2013-12-02 21:52:01.465768 -0800][Debug  ][XRootDTransport   ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] Logged in
>>>> [2013-12-02 21:52:01.465805 -0800][Debug  ][PostMaster        ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0] Stream 0 connected.
>>>> [2013-12-02 21:52:01.465823 -0800][Debug  ][Utility           ]
>>>> Monitor library name not set. No monitoring
>>>> [2013-12-02 21:52:01.466736 -0800][Debug  ][PostMaster        ]
>>>> Creating new channel to: 169.228.130.155:9940 1 stream(s)
>>>> [2013-12-02 21:52:01.466769 -0800][Debug  ][PostMaster        ]
>>>> [169.228.130.155:9940 #0] Stream parameters: Network Stack: IPAll,
>>>> Connection Window: 50, ConnectionRetry: 5, Stream Error Widnow: 1800
>>>> [2013-12-02 21:52:01.468959 -0800][Debug  ][TaskMgr           ]
>>>> Registering task: "TickGeneratorTask for: 169.228.130.155:9940" to be
>>>> run at: [2013-12-02 21:52:16 -0800]
>>>> [2013-12-02 21:52:01.469001 -0800][Debug  ][PostMaster        ]
>>>> [169.228.130.155:9940] Found 1 address(es):
>>>> [::ffff:169.228.130.155]:9940
>>>> [2013-12-02 21:52:01.469022 -0800][Debug  ][AsyncSock         ]
>>>> [169.228.130.155:9940 #0.0] Attempting connection to
>>>> [::ffff:169.228.130.155]:9940
>>>> [2013-12-02 21:52:01.469056 -0800][Debug  ][Poller            ] Adding
>>>> socket 0x63c570 to the poller
>>>> [2013-12-02 21:52:01.469458 -0800][Debug  ][AsyncSock         ]
>>>> [169.228.130.155:9940 #0.0] Async connection call returned
>>>> [2013-12-02 21:52:01.469490 -0800][Debug  ][XRootDTransport   ]
>>>> [169.228.130.155:9940 #0.0] Sending out the initial hand shake +
>>>> kXR_protocol
>>>> [2013-12-02 21:52:01.470843 -0800][Debug  ][XRootDTransport   ]
>>>> [169.228.130.155:9940 #0.0] Got the server hand shake response (type:
>>>> server [], protocol version 297)
>>>> [2013-12-02 21:52:01.470884 -0800][Debug  ][XRootDTransport   ]
>>>> [169.228.130.155:9940 #0.0] kXR_protocol successful (type: server [],
>>>> protocol version 297)
>>>> [2013-12-02 21:52:01.470945 -0800][Debug  ][XRootDTransport   ]
>>>> [169.228.130.155:9940 #0.0] Sending out kXR_login request, username:
>>>> matevz
>>>> [2013-12-02 21:52:01.471323 -0800][Debug  ][XRootDTransport   ]
>>>> [169.228.130.155:9940 #0.0] Logged in
>>>> [2013-12-02 21:52:01.471352 -0800][Debug  ][PostMaster        ]
>>>> [169.228.130.155:9940 #0] Stream 0 connected.
>>>> /opt/xrootd-master
>>>> /opt/xrootd
>>>> /opt/xrootd-3.3.3
>>>> [2013-12-02 21:52:01.472283 -0800][Debug  ][JobMgr            ]
>>>> Stopping the job manager...
>>>> [2013-12-02 21:52:01.472749 -0800][Debug  ][JobMgr            ] Job
>>>> manager stopped
>>>> [2013-12-02 21:52:01.472776 -0800][Debug  ][TaskMgr           ]
>>>> Stopping the task manager...
>>>> [2013-12-02 21:52:01.472868 -0800][Debug  ][TaskMgr           ] Task
>>>> manager stopped
>>>> [2013-12-02 21:52:01.472892 -0800][Debug  ][Poller            ]
>>>> Stopping the poller...
>>>> [2013-12-02 21:52:01.473043 -0800][Debug  ][TaskMgr           ]
>>>> Requesting unregistration of: "TickGeneratorTask for:
>>>> 169.228.130.155:9940"
>>>> [2013-12-02 21:52:01.473070 -0800][Debug  ][PostMaster        ]
>>>> [169.228.130.155:9940 #0] Destroying stream
>>>> [2013-12-02 21:52:01.473086 -0800][Debug  ][AsyncSock         ]
>>>> [169.228.130.155:9940 #0.0] Closing the socket
>>>> [2013-12-02 21:52:01.473098 -0800][Debug  ][Poller            ]
>>>> <[::ffff:132.239.186.42]:44701><--><[::ffff:169.228.130.155]:9940>
>>>> Removing socket from the poller
>>>> [2013-12-02 21:52:01.473134 -0800][Debug  ][TaskMgr           ]
>>>> Requesting unregistration of: "TickGeneratorTask for:
>>>> cabinet-10-10-10.t2.ucsd.edu:9940"
>>>> [2013-12-02 21:52:01.473148 -0800][Debug  ][PostMaster        ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0] Destroying stream
>>>> [2013-12-02 21:52:01.473158 -0800][Debug  ][AsyncSock         ]
>>>> [cabinet-10-10-10.t2.ucsd.edu:9940 #0.0] Closing the socket
>>>> [2013-12-02 21:52:01.473167 -0800][Debug  ][Poller            ]
>>>> <[::ffff:132.239.186.42]:44700><--><[::ffff:169.228.130.155]:9940>
>>>> Removing socket from the poller
>>>>
>>>> ########################################################################
>>>>
>>>> Use REPLY-ALL to reply to list
>>>>
>>>> To unsubscribe from the XROOTD-DEV list, click the following link:
>>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
>>>>
>>>
>>> ########################################################################
>>> Use REPLY-ALL to reply to list
>>>
>>> To unsubscribe from the XROOTD-DEV list, click the following link:
>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
>>
>

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1