FYI: I took this offline to discuss with Andy and resolved off the
thread. It's been just red-herring assumptions and nothing of a real
problem here. Sorry for the noise.
Thanks,
Marian
On 3/24/20 7:26 PM, Marian Zvada wrote:
> Hi Andy
>
> On 3/24/20 7:16 PM, Andrew Hanushevsky wrote:
>> Hi Marian,
>>
>> Well, it should have spit out some error messages of my it couldn't.
>> Can I see those?
>
> The log of cmsd and xrootd look pretty normal, that's also the weird
> part what could go south in this case. See them attached, please.
>
> Thanks,
> Marian
>
>> Andy
>>
>>
>> On Tue, 24 Mar 2020, Marian Zvada wrote:
>>
>>> Hi,
>>>
>>> I have a machine that can't start cmsd/xrootd on the IPv4 interface
>>> and prefers IPv6-only:
>>>
>>> [root@cms-xrd-global01 ~]# netstat -plunta | grep "xrootd\|cmsd"
>>> tcp6 0 0 :::1094 :::* LISTEN
>>> 21496/xrootd
>>> tcp6 0 0 :::1098 :::* LISTEN 21497/cmsd
>>> tcp6 0 0 :::2094 :::* LISTEN
>>> 18113/xrootd
>>> tcp6 0 0 2001:1458:201:e5::45532 2001:1458:301:69:::1098
>>> ESTABLISHED 21496/xrootd
>>> tcp6 0 0 2001:1458:201:e5::45994 2001:1458:201:a4:::1098
>>> ESTABLISHED 21496/xrootd
>>> udp 0 0 0.0.0.0:40819 0.0.0.0:*
>>> 21496/xrootd
>>>
>>> ifconfig looks normal to me:
>>>
>>> [root@cms-xrd-global01 ~]# ifconfig
>>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>>> inet 188.184.29.87 netmask 255.255.255.0 broadcast
>>> 188.184.29.255
>>> inet6 fe80::16:3eff:fe01:805e prefixlen 64 scopeid 0x20<link>
>>> inet6 2001:1458:201:e5::100:49 prefixlen 128 scopeid
>>> 0x0<global>
>>> ether 02:16:3e:01:80:5e txqueuelen 1000 (Ethernet)
>>> RX packets 131401700 bytes 11719643914 (10.9 GiB)
>>> RX errors 0 dropped 17 overruns 0 frame 0
>>> TX packets 1222209 bytes 1214320471 (1.1 GiB)
>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>>
>>> The other, supposedly identical, host starts on both interfaces, IPv4
>>> and IPv6:
>>> [root@cms-xrd-global02 ~]# netstat -plunta | grep "xrootd\|cmsd"
>>> tcp 0 0 188.184.30.79:50006 188.184.161.66:1098
>>> ESTABLISHED 1367/xrootd
>>> tcp 0 0 188.184.30.79:34626 188.184.67.41:1098
>>> ESTABLISHED 1367/xrootd
>>> tcp6 0 0 :::1094 :::* LISTEN 1367/xrootd
>>> tcp6 0 0 :::1098 :::* LISTEN 1364/cmsd
>>> tcp6 0 0 :::2094 :::* LISTEN 1370/xrootd
>>> udp 0 0 0.0.0.0:60460 0.0.0.0:* 1364/cmsd
>>> udp 0 0 0.0.0.0:57015 0.0.0.0:* 1367/xrootd
>>> udp 0 0 0.0.0.0:59700 0.0.0.0:* 1367/xrootd
>>> udp6 0 0 :::33509 :::* 1364/cmsd
>>> udp6 0 0 :::50038 :::* 1367/xrootd
>>>
>>> Both machines use xrootd version 4.11.2.
>>>
>>> Thoughts, please?
>>>
>>> Thanks,
>>> Marian
>>>
>>> ########################################################################
>>> 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
>>>
>
> ########################################################################
> 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
########################################################################
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
|