|
|
| (34 intermediate revisions by 10 users not shown) |
| Line 1: |
Line 1: |
| − | == Check pool accounts ==
| |
| − | Apparently things can go wrong if we have e.g.
| |
| | | | |
| − | dteamsm01
| |
| − |
| |
| − | and
| |
| − |
| |
| − | dteam001
| |
| − |
| |
| − | as pool accounts for 'dteamsm' and 'dteam' ... because 'dteamsm01' is a valid
| |
| − | pool account for .dteam. Check and repair.
| |
| − | == Fix to VOBOX ==
| |
| − | See the following email from Simone Campana:
| |
| − |
| |
| − | Dear sites.
| |
| − |
| |
| − | A major bug has been found in the VOBOX implementation of the proxy-renewal service. A new RPM has been
| |
| − | produced and you can find it in the following AFS location.
| |
| − |
| |
| − | /afs/cern.ch/project/gd/RpmDir_i386-sl3/external/lcg-vobox-1.0.1-3.noarch.rpm
| |
| − |
| |
| − | Could the sites who already installed a VOBOX please upgrade?
| |
| − |
| |
| − | If you currently have installed version lcg-vobox-1.0.1-2.noarch.rpm, you will just need to upgrade the RPM and restart
| |
| − | the VOBOX proxyrenewal services, i.e. <voname>-proxyrenewal.
| |
| − |
| |
| − | If you currently have installed a lower version, you also need to reconfigure the VOBOX. With yaim you can do:
| |
| − |
| |
| − | /opt/lcg/yaim/scripts/run_function /opt/lcg/yaim/examples/site-info.def config_vobox
| |
| − |
| |
| − | == Fixes needed for information published to BDII ==
| |
| − | There are a number of new attributes in the GlueVOView blocks that are not yet being published,
| |
| − | like the software dir and data dir. This is going to require some serious quattor work and
| |
| − | is not a task to be taken lightly.
| |
| − |
| |
| − | Also there is a warning in the GIIS monitor that our
| |
| − | publishing of teras.sara.nl as a close SE is failing some sanity checks. This last one may
| |
| − | be a fault in the test, someone needs to looks carefully at this.
| |
| − | == Update of Resource Broker ==
| |
| − | See [http://www.listserv.rl.ac.uk/cgi-bin/webadmin?A2=ind0509&L=lcg-rollout&F=&S=&P=34762 message on LCG-ROLLOUT]
| |
| − | == R-GMA GIN Update ==
| |
| − | See [http://www.listserv.rl.ac.uk/cgi-bin/webadmin?A2=ind0510&L=lcg-rollout&F=&S=&P=391 message on LCG-ROLLOUT]
| |
| − | == LFC and DPM Updates ==
| |
| − | After we get a DPM, we need to install [http://www.listserv.rl.ac.uk/cgi-bin/webadmin?A2=ind0510&L=lcg-rollout&F=&S=&P=43649 these updates ]
| |
| − | == FTS client ==
| |
| − | Once we get a DPM we can start doing service challenge stuff. For this we will need an
| |
| − | FTS client. Here is some info from Gavin McCance:
| |
| − |
| |
| − | Clients:
| |
| − |
| |
| − | Either manually: [ https://uimon.cern.ch/twiki/bin/view/LCG/FtsClientInstall13 Link]
| |
| − |
| |
| − | or with whatever comes with LCG-2.6.0 (yaim?)
| |
| − |
| |
| − | The difficulty is the FTS server URL (i.e. "where does my client commandline
| |
| − | tool point to"). Currently, we have not finished our integration with the
| |
| − | BDII (or indeed any information system) so we use a file in the local
| |
| − | filesystem. An XML file as well.
| |
| − |
| |
| − | [ https://uimon.cern.ch/twiki/bin/view/LCG/FtsClientInstall13 Link]
| |
| − |
| |
| − | describes the format of this services.xml file - but it really only suitable
| |
| − | to point to client commandline tool to *one* FTS server. It is possible to
| |
| − | point it to multiple servers and use the "-s" option of the commandlinme
| |
| − | tool to select between them, but it's a hack that will have to go away once
| |
| − | we do it properly with the BDII, so I wouldn't rely on it.
| |
| − |
| |
| − | Clients at NIKHEF: point to the SARA server.
| |
| − |
| |
| − | Clients at SARA: point to either CERN T0 server or the local SARA server. If
| |
| − | the same client on a given machine needs to point to both servers (the CERN
| |
| − | one to manage the T0-T1 and the SARA on to manage the T1-T2) then use the
| |
| − | "-s" option with two entries in the service.xml file.
| |
| − |
| |
| − | hope this helps,
| |
| − | cheers,
| |
| − | gav
| |
| − | == Cleanpool Script ==
| |
| − | The '''bad''' version of the cleanpool script is in /export/perm/adm/bin.
| |
| − | It needs to have the apostrophes removed, be put back into test mode.
| |
| − | This means to replace the "rm -fr" and "rmdir" stuff with "ls -l"
| |
| − | and see what it thinks it will do. If this all looks OK, it needs to
| |
| − | be tested with the "rm" commands put back, but in a sandboxed environment,
| |
| − | say copy a pool directory somewhere and try there.
| |
