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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  August 2018

XROOTD-L August 2018

Subject:

Re: XRootD instances with different config

From:

George Patargias - UKRI STFC <[log in to unmask]>

Reply-To:

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

Date:

Thu, 30 Aug 2018 14:50:20 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (177 lines)

Hi Andrew,


Thanks again for your reply.


So I tried to set up three xrootd instances according to your instructions:

1) xrootd@lhc (/etc/xrootd/xrootd-alice.cfg, xrd.port 12000)

2) xrootd@alice (/etc/xrootd/xrootd-alhc.cfg, xrd.port 12100)

3) xrootd@redirector (/etc/xrootd/xrootd-redirector.cfg)


The cfg files of 1) and 2) are the same containing the if statements.


The xrootd-redirector.cfg looks like this


all.export /
all.pidpath /var/run/xrootd
xrootd.seclib /usr/lib64/libXrdSec.so
sec.protocol /usr/lib64/ gsi
sec.protocol gsi -crl:3 -gmapopt:2 -gmapto:3600 -d:0
sec.protbind * only gsi

xrootd.redirect castor-stager.gridpp.rl.ac.uk:12000 /castor/ads.rl.ac.uk/prod/alice
xrootd.redirect castor-stager.gridpp.rl.ac.uk:12100 ? /castor/ads.rl.ac.uk/prod

But the instances fail to start: alice and lhc because


terminate called after throwing an instance of 'castor::exception::Communication'
  what(): Failed to bind: Port in use: 35000


and the redirector because


180830 15:40:00 12623 XrdOpen: Unable to bind socket to port 1094; address already in use
180830 15:40:00 12623 XrdConfig: Unable to create home directory //redirector; permission denied


Do I need to stop exisring xroot@manager service?


George




________________________________
From: Andrew Hanushevsky <[log in to unmask]>
Sent: 22 August 2018 21:33:15
To: Patargias, George (STFC,RAL,SC)
Cc: [log in to unmask]
Subject: Re: XRootD instances with different config

Hi George,

On Wed, 22 Aug 2018, George Patargias - UKRI STFC wrote:

> Is the directive xrd.port the one I should be using to define the port
> number for each instance (inside the if block)?
You can have in the confg file gaurded by an if. Some people prefer to
specify t on he start-up command line. It really depends on your
philosophy, either will work.

> Does the redirector need to be a seperate machine or it can be DNS
> alias of all the nodes where both xrootd instances are running? Can I
> use xrootd.redirect to forward the incoming requests from the standard
> port 1094 to the ports of the two instances?
The redirector can run on any machine you want here, including the one
that hosts the two instances, it becomes a third instance. Note that since
you will run a simple rediretor (i.e. onl xrootd no cmsd) please don't
specify the "all.role" directive -- that's only meant for installations
using the cmsd. Yes, the xrootd.redirect specifies the host name (here the
same one) and the port number.

Andy

  >
> George
>
> ________________________________
> From: Andrew Hanushevsky <[log in to unmask]>
> Sent: 17 August 2018 18:00:34
> To: Patargias, George (STFC,RAL,SC)
> Cc: [log in to unmask]
> Subject: Re: XRootD instances with different config
>
> Hi George,
>
> It is completely possible and the complexity is only driven by how
> transparent you wish this to be. Let first start with running two xrootd
> instances on the same node. The steps:
>
> a) Each instance would be started with a different instnace name (see the
> -n option on the xrootd command line). Of course, the first instance can
> deault to no name which he other would have a name, say "-n alice".
> http://xrootd.org/doc/dev47/xrd_config.htm#_Toc483004720
>
> b) A single configuration file can be used by special casing direcyives
> using the "if" directive. For instance,
>
> if named alice
> <directives specific to the alice instance>
> else
> <directives specific to the non-alice instance>
> fi
> <common directives>
> http://xrootd.org/doc/dev42/Syntax_config.htm#_Toc427321307
>
> c) Each instnace would be assigned its own port number. This can be done
> in the config file or via command line. This is likely the one requirement
> that is most annoying but is one required by all OS's.
>
> Now, say you want to use the same port nuber for both instance. Youcan do
> that by layering both instance with a redirector. The redirector would
> have the standard port number (say 1094) and evryone would connect to it.
> It would then decide in the incomming client needs to go to the un-named
> instance or to the special alice instance and redirect the client to the
> "right" one. Each of hose would simply be running on soe abitrary port.
>
> If the decision can be made based on file path then you need not write any
> plugin but use the xrootd.redirect directive to accomplish this.
> http://xrootd.org/doc/dev48/xrd_config.htm#_Toc496911346
>
> Otherwise, you will need to write a plugin to do more detailed decision
> making. Since, I don't know enough here I can't tell in this note.
> However, feel free to contact me if a plugin is warrented in this case.
>
> Andy
>
> On Fri, 17 Aug 2018, George Patargias - UKRI STFC wrote:
>
>> Hello,
>>
>>
>> Apologies if this issue has been discussed before.
>>
>>
>> This is in relation to the use of xrootd as part of the CASTOR storage service in RAL Tier-1. We are planning to set up a single CASTOR storage instance for all LHC and no-LHC VOs.
>>
>>
>> Right now, there is a xrootd@manager service running on each CASTOR headnode controlled by /etc/xrootd/xrootd-manager.cfg. However, one VO
>>
>> (ALICE in particular) needs certain lines (for authorization) in the xrootd-manager.cfg that other VOs do not need (and don't want).
>>
>>
>> My question. Is it possible to set up two xrootd instances running on each headnode each one with its own xrootd-alice.cfg? I mean one "generic" instance (e.g. xrootd@lhc) for all LHC VOs (including those non-LHC VOs that do not need special authorisation config in xrootd) and one instance (e.g. xrootd@alice) that will by used only by the ALICE VO in which the xrootd-alice.cfg will contain the neccessary ALICE-specific directives.
>>
>>
>> If this is possible what other xrootd config directives (all.export ?) we need so that given a single endpoint (root://castor-stager.gridpp.rl.ac.uk//) the ALICE users will be directed to the xrootd@alice service and all the other users will be directed to the xrootd@lhc service?
>>
>>
>> Many thanks in advance,
>>
>>
>> George
>>
>> ########################################################################
>> 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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
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