Make sure that both the httpd and info services
are running; both are required for publishing information. By
default, the info service is started as an admin-node
responsibility; but it is possible to configure dCache so it
runs on a different node. You should run only one info service
per dCache instance.
The info service is not the infoProvider
service
The info-provider needs accurate, up-to-date information about
a dCache instance so it can publish correct values. A
component of dCache, rather confusingly also called
infoProvider, used to provide this up-to-date
information. By default, the infoProvider would run
in its own domain (infoProviderDomain) and could be
started and stopped like any other domain.
The job of collecting accurate, up-to-date information is now
handled by the info service. This is completely
independent of the infoProvider service, so the latter
is no longer needed and may be switched off.
For more details please see the section called “Decommissioning the old info provider”.
If necessary, you may start the info service manually:
[root] #/opt/d-cache/bin/dcache start infoDomainStarting infoDomain done
You can check which services are running on the local node using the status command:
[root] #/opt/d-cache/bin/dcache statusDomain Status PID dCacheDomain running 30582 dirDomain running 30625 adminDoorDomain running 30667 httpdDomain running 30711 utilityDomain running 30760 gPlazma-dcache-hostDomain running 30844 namespaceDomain running 30921 dcache-hostDomain running 30971 infoDomain running 15530
Output may look different
One feature of dCache is that domains may be run on
different nodes. Because of this, the list of domains running
on the node running the info service may be different.
You can also verify both services (httpd and info)
are running with the following wget command.
This command assumes that you run it on the node that has the
httpd service (by default, the admin node). If may run
the command on any node by replacing localhost with the hostname of
the node running the httpd service.
The following example shows the output when the info
service is running correctly
[root] #wget -O/dev/null http://localhost:2288/info--17:57:38-- http://localhost:2288/info Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:2288... connected. HTTP request sent, awaiting response... 200 Document follows Length: 372962 (364K) [application/xml] Saving to: `/dev/null' 100%[=========================================================================== ===>] 372,962 --.-K/s in 0.001s 17:57:38 (346 MB/s) - `/dev/null' saved [372962/372962]
If the httpd service isn’t running then the command will
generate the following output:
[root] #wget -O/dev/null http://localhost:2288/info--10:05:35-- http://localhost:2288/info => `/dev/null' Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:2288... failed: Connection refused.
To fix the problem, start the httpd service with the
following command on the appropriate dCache node.
[root] #/opt/d-cache/bin/dcache start httpdDomainStarting httpdDomain done
If running the wget command gives the following output:
[root] #wget -O/dev/null http://localhost:2288/info--10:03:13-- http://localhost:2288/info => `/dev/null' Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:2288... connected. HTTP request sent, awaiting response... 503 Unable to contact the info cell. Pl ease ensure the info cell is running. 10:03:13 ERROR 503: Unable to contact the info cell. Please ensure the info cel l is running..
then the info service is not running. Instructions for
starting the info service are given above.