On Mon, 18 Apr 2005, Juan Jose Pardo Navarro wrote: > Dear all, > > I have added a new SE to UAM-LCG2. > ******* > CE: grid003 > SE default: grid002 (dcache) > SE extra : grid004 (classic) > ******* > > now I can not see the SARoot of grid004 from BDII. But if I execute > ldapsearch to grid004, I can see SARoot: > > > % ldapsearch -x -H ldap://grid004.ft.uam.es:2135 -b \ > mds-vo-name=local,o=grid | grep > > SARoot > dn: > GlueSARoot=atlas:atlas,GlueSEUniqueID=grid004.ft.uam.es,Mds-Vo-name=local, > GlueSARoot: atlas:atlas > dn: > GlueSARoot=dteam:dteam,GlueSEUniqueID=grid004.ft.uam.es,Mds-Vo-name=local, > GlueSARoot: dteam:dteam > dn: > GlueSARoot=gvmuam:gvmuam,GlueSEUniqueID=grid004.ft.uam.es,Mds-Vo-name=loca > GlueSARoot: gvmuam:gvmuam > dn: > GlueSARoot=zeus:zeus,GlueSEUniqueID=grid004.ft.uam.es,Mds-Vo-name=local,o= > GlueSARoot: zeus:zeus > > > > which is it the problem? Those entries are refused by the BDII, because they have empty attributes for GlueSAStateAvailableSpace and GlueSAStateUsedSpace: ------------------------------------------------------------------------------ dn: GlueSARoot=atlas:atlas,GlueSEUniqueID=grid004.ft.uam.es,Mds-Vo-name=local, o=grid objectClass: GlueSATop objectClass: GlueSA objectClass: GlueSAPolicy objectClass: GlueSAState objectClass: GlueSAAccessControlBase objectClass: GlueKey objectClass: GlueSchemaVersion GlueSARoot: atlas:atlas GlueSAUniqueID: grid004.ft.uam.es GlueSAPolicyMaxFileSize: 2000000 GlueSAPolicyMinFileSize: 00 GlueSAPolicyMaxData: 00 GlueSAPolicyMaxNumFiles: 00 GlueSAPolicyMaxPinDuration: 10 GlueSAPolicyQuota: 00 GlueSAPolicyFileLifeTime: permanent GlueSAStateAvailableSpace: GlueSAStateUsedSpace: GlueSAAccessControlBaseRule: atlas GlueChunkKey: GlueSEUniqueID=grid004.ft.uam.es GlueSchemaVersionMajor: 1 GlueSchemaVersionMinor: 1 ------------------------------------------------------------------------------ You need to figure out why the dynamic info provider is not returning anything for those attributes. Is the script executable? Try running it as "edginfo".