 |
 |
Hi Maarten, yes, at last I was able to reconfigure correctly the lcg-CE. I reset the correct BDII_CE value and had to reenable the variables VO_$VO_QUEUE values which I had understood that were not needed anymore. Cheers Vega "Maarten Litmaath, CERN" <[log in to unmask]> Sent by: LHC Computer Grid - Rollout <[log in to unmask]> 25/04/2007 22:19 Please respond to LHC Computer Grid - Rollout <[log in to unmask]> To [log in to unmask] cc Subject Re: [LCG-ROLLOUT] - Production - lcg-CE - Update 21 On Thu, 19 Apr 2007, Vega Forneris wrote: > Hi *, > > I've just reconfigred my CE (lcg like), it works if targeted by > globus-job-run (both fork and lcgpbs scheduler), but it disappeard from > top BDII. > > > > Looking in the specific release note, I found: > > > In the site-info.def file is necessary to define the BDII_CE_URL parameter > as follows: > > BDII_CE_URL="ldap://$CE_HOST:2170/mds-vo-name=resource,o=grid" It says to do that when the site BDII is _not_ on the CE. Furthermore, AFAIK it only applies to the gLite CE; the LCG-CE still runs an MDS on port 2135 instead. > so I changed the value accordly (well...just cut and paste!) and launched > the reconfiguration of the bdii side: > > /opt/glite/yaim/bin/yaim -r -s /home/shared/conf/esrin-site-info.def -n > lcg-CE_torque -n BDII_site -f config_bdii > > but nothing changed...should I wait (maybe it needs to repopulate the top > BDII) or should I be worried? The repopulation is done about every 2 minutes... Apparently you fixed it somehow: your CE does appear now.