LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  September 2015

XROOTD-L September 2015

Subject:

Re: help in setting up a supervisor

From:

Andrew Hanushevsky <[log in to unmask]>

Reply-To:

Support use of xrootd by HEP experiments <[log in to unmask]>

Date:

Thu, 3 Sep 2015 15:22:35 -0700

Content-Type:

MULTIPART/MIXED

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (199 lines)

Hi Tommaso,

Comments interspersed....

On Fri, 28 Aug 2015, Tommaso Boccali 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' )
>
The above may be fine except that if you are running a supervisor on the 
same node as the managerr then you really need to differentiate it using 
an instance name. You do this using the '-n' option (e.g. '-n sup1') 
otherwise the two daemons will stomp on each other which is not good. 
Instance names are described in:

http://xrootd.org/doc/dev42/xrd_config.htm#_Toc411375787

Yes, you need to start an xrootd/cmsd pair.

> while in the supervisor cmsd  log I see
> 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:
> ...
Well, this is why I recommend not turning on debugging. This is output 
from debugging and the log will be flooded with these kinds of messages 
(usually leading to a logfile that is several gigabytes long). All it 
means is that the manager asked the supervisor to lookup a file but there 
were no subscribers to the supervisor so the lookup could not occur. Quite 
normal.

> 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
Yes, you need to start a suprevisor xrotd/cmsd pair.

> 1 - is the erorr expected with my config ?
Yes, because full debugging is turned on (I would not recommend that).

> 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?
Yes, in fact the supervisor forces arbitrary port number assignment. There 
is no need to give supervisors a specific port.

> 3 - should I see some servers being "moved" by the manager to the
> supervisor?
No, the only time a supervisor is used is when the 65th connection is made 
to the manager. In that case, the connectee is told to connect 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?
Well, then we may have a problem here. What is exactly firewalled here? 
That is where do you restrict port number usage?

As for teh config:

>
> [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.
!!! Note that this causes problems for the xrdmapc command and isn't fixed
     until 4.2.3 (Marian has the details). 
> all.export / r/w
>
> # Hosts allowed to use this xrootd cluster
> cms.allow host *
> # Logging verbosity
> xrootd.trace emsg login stall redirect
!!!Unless there is a reason to turn on complete debugging, I strongly 
advise against it as it produces a humongous amount of log output, most of 
which is useless in the general case.

> 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
>
> ########################################################################
> 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

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use