JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


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

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  April 2007

LCG-ROLLOUT April 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: VOs sgm & prd accounts get permission denied fromDPM server

From:

Alexander Piavka <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Mon, 23 Apr 2007 17:36:36 +0300

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (91 lines)

 Hi Maarten,

The script has fixed the problem.

> On your DPM server as root run the attached script like this:
>
>      sh dpns-fix-acl.txt alice atlas biomed cms dteam lhcb ops

 one thing is that  the script does not check is, if both the lcgadmin & production
really exist for the specific VO. (like in case with OPS vo)

>
> With DPM version 1.6.4 one will no longer need to do that.
>

 but who should be responible for running 'dpns-entergrpmap --group "$VO/Role=lcgadmin"'
YAIM or the group is auto created then sgm user tries to access the dpm,
(and this is why only atlas/Role=lcgadmin & ops/Role=lcgadmin were created)?

 and shouldn't the YAIM run
dpns-setacl -m "g:$VO/Role=lcgadmin:rwx,m:rwx" /dpm/$domain/home/$VO
for each vo?

ps.

 Also yesterday i've upgraded to yaim-3.0.1-x
and added new VOs to the site
and there were errors ,at most of the node types, during configuration like:
 group atlasprd,atlas does not exists
*althought i have wiped out all the existing vo accounts on all nodes
before configuration from /etc/group /etc/gshadow /etc/passwd /etc/shadow and /home/*)
these errors were present only for the new VOs i've added.

The users.conf has enties like:
43001:atlassgm001:43001,43000:atlassgm,atlas:atlas:sgm:
43002:atlassgm002:43001,43000:atlassgm,atlas:atlas:sgm:
43003:atlassgm003:43001,43000:atlassgm,atlas:atlas:sgm:
43004:atlasprd001:43004,43000:atlasprd,atlas:atlas:prd:
43005:atlasprd002:43004,43000:atlasprd,atlas:atlas:prd:
43006:atlasprd003:43004,43000:atlasprd,atlas:atlas:prd:
43007:atlas001:43000:atlas:atlas::
...

The unix group were correctly defined
atlas:x:43000:atlas001,atlas002,atlas003,atlas004,...,atlasprd001,atlasprd002,atlasprd003,atlassgm001,atlassgm002,atlassgm003
atlasprd:x:43004:
atlassgm:x:43001:

but at least on gCE the groupmapfile has different entries for old and new VOs
----------------------------------
old vo
# fgrep dteam groupmapfile
"/dteam/Role=lcgadmin/Capability=NULL" dteamsgm
"/dteam/Role=lcgadmin" dteamsgm
"/dteam/Role=production/Capability=NULL" dteamprd
"/dteam/Role=production" dteamprd
"/dteam/Role=NULL/Capability=NULL" dteam
"/dteam" dteam
/dteam dteam
/dteam/* dteam

new vo
# fgrep atlas groupmapfile
"/atlas/Role=lcgadmin/Capability=NULL" atlassgm
"/atlas/Role=lcgadmin" atlassgm
"/atlas/Role=production/Capability=NULL" atlasprd
"/atlas/Role=production" atlasprd
"/atlas/Role=NULL/Capability=NULL" atlas
"/atlas" atlas
/atlas atlassgm,atlas
/atlas/* atlassgm,atlas
----------------------------------

 and it looks like the
/atlas atlassgm,atlas
/atlas/* atlassgm,atlas
 are not correct, and were created probably since yaim does not split the
group field :atlassgm,atlas:  from entries like
43001:atlassgm001:43001,43000:atlassgm,atlas:atlas:sgm:
40001:dteamsgm001:40001,40000:dteamsgm,dteam:dteam:sgm:
and thus the error messages like:
group atlasprd,atlas does not exists
during configuration

previously i had older entries like
40001:dteamprd:40001:dteam:dteam:prd:
so it worked ok.

 Thanks
 Alex

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 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
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 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
November 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
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 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
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

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