Sites that were previously using the old (Java-based) info provider should ensure that they no longer using it. This is because, if so configured, GIP will obtain information from both the (new) info-based info provider and the Java-based info provider and attempt to merge the results. This will likely lead to a confusing description of dCache, which may prevent clients from working correctly.
The Java-based info provider has two configuration files and a symbolic link within GIP. They are:
The file
/opt/lcg/var/gip/ldif/lcg-info-static-SE.ldif,The file:
/opt/lcg/var/gip/ldif/lcg-info-static-dSE.ldif,The symbolic link
/opt/glite/etc/gip/plugin, which points to/opt/d-cache/jobs/infoDynamicSE-plugin-dcache.
The two files (lcg-info-static-SE.ldif and
lcg-info-static-dSE.ldif) may appear within
a different directory if the static_dir
variable is configured. You will find the
static_dir variable in one of two
configuration files: either
/opt/glite/etc/gip/glite-info-generic.conf
or /opt/lcg/etc/lcg-info-generic.conf.
Delete the above three entries:
lcg-info-static-SE.ldif,
lcg-info-static-dSE.ldif and the plugin symbolic link.
The directory defined in the static_dir
variable (/opt/lcg/var/gip/ldif by default)
may contain other static LDIF entries that are relics of
previous info-providers. These may have filenames like
static-file-SE.ldif.
Delete any such files that contain information about dCache. All LDIF information now comes directly from the info-provider and there should be no static LDIF files.
The infoProvider component of dCache, usually running
in its own domain (infoProviderDomain), collects information
for the infoDynamicSE-plugin-dcache
program. Since this program is now obsolete the
infoProviderDomain should be switched off. This may be
achieved with the dcache script:
[root] #/opt/d-cache/bin/dcache stop infoProviderDomainStopping infoProviderDomain (pid=15528) 0 done
You can confirm that the infoProviderDomain domain is no
longer running by querying the current status of the components:
[root] #/opt/d-cache/bin/dcache status | grep ^infoProviderinfoProviderDomain stopped /var/log/infoProviderDomain.log
To prevent dCache from starting the infoProviderDomain
domain when the machine next reboots, you should edit
/opt/d-cache/etc/node_config and ensure
that the infoProvider option is configured to
no. You can verify that
infoProviderDomain is no longer listed as a service with the
following command:
[root] #/opt/d-cache/bin/dcache services | grep ^infoProvider
You should see no output from running the command.