 |
 |
ciao, any advice? thanks tom On Fri, Aug 28, 2015 at 2:23 PM, Tommaso Boccali <[log in to unmask]> wrote: > ciao, > the supervisor (started by hand with > 'cmsd -d -l /var/log/xrootd/superv.log -c > /etc/xrootd/xrootd-redir-cms-superv.cfg -k 7' and > 'xrootd -d -l /var/log/xrootd/superv-x.log -c > /etc/xrootd/xrootd-redir-cms-superv.cfg -k 7' ) > > fileis below * > > in the manager cmsd.log I just see: > > 150828 14:08:52 28267 XrdSched: running main accept inq=0 > 150828 14:08:52 27343 ?:80@xrootd XrdPoll: FD 80 attached to poller 1; > num=22 > 150828 14:08:52 27343 Protocol: Primary supervisor.28781:80@xrootd:33530 > logged in suspended. > =====> Routing for xrootd.ba.infn.it: local pub4 prv4 > =====> Route all4: xrootd.ba.infn.it Dest=[::90.147.66.75]:33530 > > > while in the supervisor cmsd log I see > > 150828 14:08:52 28799 Pander supervisor services to xrootd.ba.infn.it:1213 > 150828 14:08:52 28799 Pander trying to connect to lvl 0 > xrootd.ba.infn.it:1213 > 150828 14:08:52 28799 XrdInet: Connected to xrootd.ba.infn.it:1213 > 150828 14:08:52 28820 XrdXeq: Worker thread started > 150828 14:08:52 28799 Add xrootd.ba.infn.it to manager config; id=0 > > which seems good, but then a series of: > > ... > 150828 14:08:54 28799 manager.0:25@xrootd do_StateFWD: *Path find failed > for state* > /store/test/xrootd/T2_MY_UPM_BIRUNI/store/mc/HC/GenericTTbar/GEN-SIM-RECO/CMSSW_7_0_4_START70_V7-v1/00000/D00E55FF-F6CC-E311-9B51-02163E00E88E.root > 150828 14:08:54 28799 Dispatch manager.0:25@xrootd for state dlen=148 > 150828 14:08:54 28799 manager.0:25@xrootd do_State: > /store/test/xrootd/T2_MY_UPM_BIRUNI/store/mc/HC/GenericTTbar/GEN-SIM-RECO/CMSSW_7_0_4_START70_V7-v1/00000/4463C61D-03CD-E311-AF1A-02163E00F338.root > 150828 14:08:54 28799 manager.0:25@xrootd do_StateFWD: *Path find failed > for state* > /store/test/xrootd/T2_MY_UPM_BIRUNI/store/mc/HC/GenericTTbar/GEN-SIM-RECO/CMSSW_7_0_4_START70_V7-v1/00000/4463C61D-03CD-E311-AF1A-02163E00F338.root > ... > > > and nothing else. > > So I have a few questions > > 0 - very naive: for the supervisor do I need to start cmsd AND xrootd? If > I do not do that, I see no effect at all > 1 - is the erorr expected with my config ? > 2 - I did not set explicitly the port numbers to the supervisor, and they > of course cannot be 1094/1213 since they are already taken by the manager. > I just have > xrd.port any > > is that enough? > > 3 - should I see some servers being "moved" by the manager to the > supervisor? > 4 - atm I have not opened any additional port on the firewall, since with > 'any' I do not know which port will be used. Should I open something? > > > thanks a lot and sorry for all the questions > > > > *: > > [root@xrootd xrootd]# cat /etc/xrootd/xrootd-redir-cms-superv.cfg > > xrd.port any > all.role supervisor > # The known managers > all.manager xrootd.ba.infn.it 1213 > > # Allow any path to be exported; this is further refined in the authfile. > all.export / r/w > > # Hosts allowed to use this xrootd cluster > cms.allow host * > # Logging verbosity > xrootd.trace emsg login stall redirect > ofs.trace all -debug > xrd.trace all -debug > cms.trace all -debug > > > > On Thu, Aug 27, 2015 at 5:26 PM, Marian Zvada <[log in to unmask]> > wrote: > >> Hi Tom, >> >> I haven't tried it though, but looks good to me. >> >> One more thing, we should not use thread limit by hard from whatever >> v4.x.x version, I think. This is well cared of within recent fixes I >> believe. I don't recall details right now but can search through if needed. >> >> So, feel free remove the line "xrd.sched maxt 16000". >> >> -Marian >> >> On 8/27/15 3:49 AM, Tommaso Boccali wrote: >> >>> Ciao, I am trying to see if there is the need for a supervisor on one of >>> our CMS EU redirs. >>> In the logs, I never really see anything like 'If you suspect this, >>> check the manager’s log. It will contain warnings about orphaned data >>> servers' >>> >>> so I am not sure we have a problem, but still we a re very close to the >>> 64 limit so better to be proactive. >>> >>> >>> What I want to do as step #1 is to run the supervisor as an additional >>> daemon on the redirector (it is a test, I really want to see what >>> happens first, and the machine is big so should not be an issue) >>> >>> I looked at the documentation below, but I have to admit it is a bit >>> obscure (to me). >>> >>> So, I have a cmsd/xrootd (the eu redir) running on ports 1213/1094, and >>> redirecting "up" if needed (to the global redirector). >>> Starting from their config, I just wanted to prepare a config for the >>> supervisor. >>> >>> The minimal one I am trying to guess from the documentation would be >>> === >>> xrd.port any >>> all.role supervisor >>> # The known managers >>> all.manager xrootd.ba.infn.it <http://xrootd.ba.infn.it> 1213 >>> >>> # Allow any path to be exported; this is further refined in the authfile. >>> all.export / r/w >>> >>> # Hosts allowed to use this xrootd cluster >>> cms.allow host * >>> # Logging verbosity >>> xrootd.trace emsg login stall redirect >>> ofs.trace all -debug >>> xrd.trace all -debug >>> cms.trace all -debug >>> >>> cms.fxhold 8h >>> xrd.sched maxt 16000 >>> === >>> >>> but again , this is a sort of guess .... Do you have an example of a >>> standalone cfg file for a supervisor? >>> >>> >>> thanks >>> >>> tom >>> >>> http://xrootd.org/doc/dev42/cms_config.htm#_Toc405927050 >>> >>> -- >>> Tommaso Boccali >>> INFN Pisa >>> >>> ------------------------------------------------------------------------ >>> >>> 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 >>> >>> > > > -- > Tommaso Boccali > INFN Pisa > -- Tommaso Boccali INFN Pisa ######################################################################## 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