Print

Print


On 27/05/14 22:31, Ulf Tigerstedt wrote:
>>    Sw[::193.166.0.114]:1094 in fact is server's answer to a kXR_locate
>> request. So what you likely did was asking for a directory listing. This
>> triggered a kXR_locate request and you dCache server told the client to
>> go to [::193.166.0.114]:1094 over IPv4 which the client did. What you
>> see is a dCache bug, not xrootd.
>
> 193.166.0.114 is a dualstacked box running xrootd 4.0.0rc3 (It's
> actually my testbox against dcache). It is running the xrootd daemon
> from 4.0.0rc3 to have something to compare dcache to.

    Then it's likely mis-configured or there is some subtle bug related 
to your particular setup. Andy, can you help?

    Lukasz

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

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