Hi,
We have some error in GSTA info:
Hostname Monitored Downtime GOCDB NodeTypes BDII ServiceTypes Missing Services History
site-bdii Y N Site-BDII bdii_site alert_history
lfcatlas Y N LFC local-data-location-interface,lcg-local-file-catalog Local-LFC,lcg-file-catalog alert_history
lfclhcb Y N LFC local-data-location-interface,lcg-local-file-catalog Local-LFC,lcg-file-catalog alert_history
For site-bdii:
$ ldapsearch -x -H ldap://site-bdii.pic.es:2170 -b mds-vo-name=pic,o=grid '(GlueServiceType=bdii_site)'
version: 2
#
# filter: (GlueServiceType=bdii_site)
# requesting: ALL
#
# sitebdii02.pic.es_bdii_site_3877936872, pic, grid
dn: GlueServiceUniqueID=sitebdii02.pic.es_bdii_site_3877936872,Mds-Vo-name=pic
,o=grid
objectClass: GlueTop
objectClass: GlueService
objectClass: GlueKey
objectClass: GlueSchemaVersion
GlueServiceUniqueID: sitebdii02.pic.es_bdii_site_3877936872
GlueServiceName: pic-bdii_site
GlueServiceType: bdii_site
GlueServiceVersion: 3.0.0
GlueServiceEndpoint: ldap://sitebdii.pic.es:2170/mds-vo-name=pic,o=grid
GlueServiceStatus: OK
GlueServiceStatusInfo: bdii OK
GlueServiceSemantics: https://twiki.cern.ch/twiki/bin/view/EGEE/BDII
GlueServiceStartTime: 2008-10-01T14:57:27+02:00
GlueForeignKey: GlueSiteUniqueID=pic
GlueSchemaVersionMajor: 1
GlueSchemaVersionMinor: 3
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
So, why it complains about Missing Services? for not publishing the
alias site-bdii?¿
And we have some errors in both LFC. I check what are we publishing:
For lfcatlas, querying site-bdii:
#ldapsearch -x -H ldap://site-bdii.pic.es:2170 -b
mds-vo-name=pic,o=grid '(GlueServiceType=local-data-location-interface) '
# local-http://lfcatlas.pic.es:8085/, pic, grid
dn: GlueServiceUniqueID=local-http://lfcatlas.pic.es:8085/,Mds-Vo-name=pic,o=g
rid
objectClass: GlueTop
objectClass: GlueService
GlueServiceUniqueID: local-http://lfcatlas.pic.es:8085/
GlueServiceName: pic-lfc-dli
GlueServiceType: local-data-location-interface
GlueServiceEndpoint: http://lfcatlas.pic.es:8085/
GlueServiceURI: http://lfcatlas.pic.es:8085/
GlueServiceAccessPointURL: http://lfcatlas.pic.es:8085/
GlueServiceStatus: OK
GlueServiceStatusInfo: No Problems
GlueServiceWSDL: unset
GlueServiceSemantics: unset
GlueForeignKey: GlueSiteUniqueID=pic
GlueServiceStartTime: 2008-09-22 08:23:18.000000000 +0200
GlueServiceVersion: 1.6.11
GlueServiceOwner: atlas
GlueServiceOwner: ops
GlueServiceAccessControlRule: atlas
GlueServiceAccessControlRule: ops
#ldapsearch -x -H ldap://site-bdii.pic.es:2170 -b
mds-vo-name=pic,o=grid '(GlueServiceType=lcg-local-file-catalog)
# local-lfcatlas.pic.es, pic, grid
dn: GlueServiceUniqueID=local-lfcatlas.pic.es,Mds-Vo-name=pic,o=grid
objectClass: GlueTop
objectClass: GlueService
GlueServiceUniqueID: local-lfcatlas.pic.es
GlueServiceName: pic-lfc
GlueServiceType: lcg-local-file-catalog
GlueServiceEndpoint: lfcatlas.pic.es
GlueServiceURI: lfcatlas.pic.es
GlueServiceAccessPointURL: lfcatlas.pic.es
GlueServiceStatus: OK
GlueServiceStatusInfo: No Problems
GlueServiceWSDL: unset
GlueServiceSemantics: unset
GlueForeignKey: GlueSiteUniqueID=pic
GlueServiceStartTime: 2008-09-22 08:23:18.000000000 +0200
GlueServiceVersion: 1.6.11
GlueServiceOwner: atlas
GlueServiceOwner: ops
GlueServiceAccessControlRule: atlas
GlueServiceAccessControlRule: ops
I don't find what are we publishing in a wrong way... I've been
comparing our LFC info with other site were is well configured (SARA)
and I don't find the error...
Any clue, please?
Cheers,
Arnau
|