Once you have configured glue-1.3.xml to reflect your site’s configuration, you may test that the info provider produces meaningful results.

Run the info-provider script should produce GLUE information in LDIF format; for example:

[root] # /opt/d-cache/libexec/infoProvider/info-based-infoProvider.sh
  #
  #  LDIF generated by Xylophone v0.1
  #
  #  XSLT processing using libxslt 1.0 (http://xmlsoft.org/XSLT/)
  #


  dn: GlueSEUniqueID=dcache-host.example.org,mds-vo-name=resource,o=grid
  objectClass: GlueSETop
  objectClass: GlueSE
  objectClass: GlueKey
  objectClass: GlueSchemaVersion
  GlueSEStatus: Production
  GlueSEUniqueID: dcache-host.example.org
  GlueSEArchitecture: multidisk
  GlueSEImplementationName: dcache
Many similar lines follow

The actual values you see will be site-specific and depend on the contents of the glue-1.3.xml file and your dCache configuration.

To verify that there are no problems, redirect standard-out to /dev/null to show only the error messages:

[root] # /opt/d-cache/libexec/infoProvider/info-based-infoProvider.sh >/dev/null

If you see two error messages, which may be repeated several times, of the form:

[root] # /opt/d-cache/libexec/infoProvider/info-based-infoProvider.sh >/dev/null
  error : Operation in progress
  warning: failed to load external entity "http://localhost:2288/info"

then it is likely that either the httpd or info service have not been started. Use the above wget test to check that both services are running. You can also see which services are available by running the command: dcache status.