 |
 |
Zero in xrootd means assume 1094 (this is not done automatically by xrdmapc -- a known issue). The reason it get reported as zero is that the cmsd started before the xrootd and the cmsd apparently was told it didn't need to wait for the xrootd to start up. I can confirm that if you give me the config file for one of the zerers showing port 0. You also should send the command line used to start the cmsd as well. Either will work: ps -fp <pid> cat /proc/<pid>/cmdline where <pid> is the process ID of the cmsd. Andy On Wed, 13 Sep 2017, Adrian Sevcenco wrote: > Hi! I have a very strange problem with the reporting of registered > servers (xrootd 4.6.1) : > > [Wednesday 13.09.17 23:53] adrian@sev : ~ $ > /usr/bin/xrdmapc --list s -r rd.spacescience.ro:1094 > 0**** rd.spacescience.ro:1094 > Srv storage04.spacescience.ro:1094 > Srv storage05.spacescience.ro:0 > Srv storage07.spacescience.ro:1094 > Srv storage06.spacescience.ro:0 > Srv storage02.spacescience.ro:1094 > > the thing is that excluding oss.cache all the configuration is identical > among servers ... does anyone have any idea why the reported port would > be 0 ? > > Thank you!! > Adrian > > > ######################################################################## > 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