 |
 |
On 07/11/2013 09:13 AM, Andrew Hanushevsky wrote: > Hi Gang, > > Quite odd. Could you send me the part of the log file that includes the > start-up (i.e. at start-up)? Looks to me like a strange DNS problem. inside CERN, "root" resolves to root.cern.ch resoves to lxroot02.cern.ch .. typo in the URL perhaps - mixup between protocol and hostname? Cheers jan > > Andy > > On Tue, 9 Jul 2013, qing wrote: > >> Dear Expert: >> >> From /var/log/xrootd/cnsdlog on one data server I see that's it's >> always trying to connect to lxroot02.cern.ch and fail: >> >> 130709 00:00:04 13825 Xrd: XrdClientConn: Trying to connect to >> 128.142.172.96:1095 >> 130709 00:00:04 13825 Xrd: Connect: Creating a logical connection... >> 130709 00:00:04 13825 Xrd: Connect: Physical connection not found. >> Creating a new one... >> 130709 00:00:04 13825 Xrd: Connect: Connecting to [lxroot02.cern.ch:1095] >> 130709 00:00:04 13825 Xrd: ClientSock::TryConnect_low: Trying to >> connect to lxroot02.cern.ch(128.142.172.96):1095 Windowsize=0 Timeout=120 >> 130709 00:00:04 13825 Xrd: ClientSock::TryConnect_low: Connection >> tolxroot02.cern.ch:1095 failed. (-1) >> 130709 00:00:04 13825 Xrd: Connect: can't open connection to >> [lxroot02.cern.ch:1095] >> 130709 00:00:04 13825 Xrd: PhyConnection: Disconnecting socket... >> 130709 00:00:04 13825 Xrd: Connect: Connect(lxroot02.cern.ch, 1095) >> returned -1 >> 130709 00:00:04 13825 Xrd: XrdNetFile: Error creating logical >> connection to lxroot02.cern.ch:1095 >> 130709 00:00:04 13825 Xrd: Connect: Disconnecting. >> 130709 00:00:04 13825 Xrd: Connect: Connection attempt failed. >> Sleeping 5 seconds. >> 130709 00:00:09 13825 Xrd: XrdClientUrlSet: parsing: >> root://lxroot02.cern.ch:1095//tmp >> 130709 00:00:09 13825 Xrd: XrdClientUrlSet: protocol: root >> 130709 00:00:09 13825 Xrd: XrdClientUrlSet: file: /tmp >> >> >> But in our cluster there is no machine called lxroot02, may I know >> where does this lxroot02 comes from? In our cluster, the xrootd >> redirector is valtical.cern.ch, and the dataservers are >> valtical*.cern.ch) >> >> [root@valtical06 ~]# cat /etc/xrootd/xrootd-clustered.cfg >> all.export /data/xrootdfs >> all.export /localdisk/xrootd >> all.export /localdisk/proofbox >> set xrdr=valtical.cern.ch >> all.manager $(xrdr):1213 >> if $(xrdr) && named cns >> all.export /data/inventory >> xrd.port 1095 >> else if $(xrdr) >> all.role manager >> xrd.port 1094 >> else >> all.role server >> oss.localroot / >> #oss.localroot /local/xrootd >> ofs.notify closew create mkdir mv rm rmdir trunc | >> /usr/bin/XrdCnsd -d -D 2 -i 90 -b root://$(xrdr):2094 >> #add cms.space if you have less the 11GB >> # cms.space options >> http://xrootd.slac.stanford.edu/doc/dev/cms_config.htm >> cms.space min 2g 5g >> fi >> >> Cheers,Gang >> >> ######################################################################## >> 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