 |
 |
Last time I recall and remember sending bug-report, there were issues with supervisor and Xrootd-4.0.4 and it was claimed to be solved in 4.1. It might be a separate issue ! It feels backward to try with -v4 and with xrootd-4.1 because xrootd-4 is supposed to provide IPv6 connectivity and we would like to use it in our cluster. -Tapas > On Apr 3, 2015, at 3:29 PM, Yang, Wei <[log in to unmask]> wrote: > > I vaguely remember that there was issues in 4.x (perhaps 4.1) when dealing with certain format of IPv6. that is why I suggested to test with ipv4 only option (-I v4). > > Wei Yang | [log in to unmask] | 650-926-3338(O) > > > > On Apr 3, 2015, at 11:09 AM, Tapas Sarangi <[log in to unmask]> wrote: > >> Hi Wei, >> >> >>> On Apr 3, 2015, at 12:33 PM, Yang, Wei <[log in to unmask]> wrote: >>> >>> 1. does your cluster have more than 64 nodes (I mean data servers + supervisors) >> >> We have about 300 nodes. >> >>> 2. it seems to me that the supervisor can’t find any data servers to manage. >> >> This is not true because (1) is not true and all these supervisors were managing plenty of data servers prior to xrootd-4.1 ! >> >>> Are you using IPv6? if you are still on IPv4, can you add -I v4 to the command line in cmsd and xrootd? (see /etc/sysconfig/xrootd) >> >> We have Dual Stack network for our cluster. Every single node has public IPV6 connectivity and ability. >> >> >> Thanks >> -Tapas > ######################################################################## 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