Product: Xtradyne I-DBC
Version: ALL
Description:
Determining the DBC Proxy / SPS Status
Solution:
One of the first steps to take when something goes wrong is to check whether the I-DBC Proxy or WS-DBC Proxy respectively and the Security Policy Server are up and running.
Their status can be determined with the scripts xdn_sps, xdn_idbc, and xdn_wsdbc with the option status (you must be root to execute this):
/etc/init.d/xdn_sps status
/etc/init.d/xdn_idbc status
/etc/init.d/xdn_wsdbc status
The scripts yield “OK” if the Security Policy Server/DBC Proxy is up and running. If not, you will get “no process”. Note that the SPS and the Proxy will start up but refuse to work until a valid license file is installed (in this case, the status scripts will yield “OK” too, but you will see an error message reading “error loading license FileOpenException(0): could not open file: license.txt).” in the log file located in <INSTALLDIR>/sps/adm/sps.log on the Security Policy Server host and in dbc.log in the adm directory on the DBC Proxy host).
Useful Status Scripts
For more information about the status of the SPS and the I-DBC Proxy or WS-DBC Proxy respectively like the number of Proxy Processes, the ports of the DBC Proxy and the Security Policy Server, and their current connections you can use the scripts:
<INSTALLDIR>/idbc/bin/checkproxy.sh
<INSTALLDIR>/wsdbc/bin/checkproxy.sh
<INSTALLDIR>/sps/bin/checksps.sh
Scripts Do Not Work
Domain Boundary Controller - Administrator’s Guide 215 Example
~:/usr/xtradyne/idbc/bin/checkproxy.sh
proxy ... 2 processes/threads
proxymanager ... 12 processes/threads
Listening on
tcp 0 0 192.168.1.90:7384 0.0.0.0:* LISTEN 31038/proxy
tcp 0 0 192.168.1.90:8885 0.0.0.0:* LISTEN 31038/proxy
tcp 0 0 0.0.0.0:15000 0.0.0.0:* LISTEN 31038/proxy
Current connections:
tcp 0 0 192.168.1.90:2316 192.168.1.90:15000ESTABLISHED31038/proxy
tcp 0 0 192.168.1.90:15000192.168.1.90:2315 ESTABLISHED31038/proxy
In this example an I-DBC Proxy is listening on the ports 7384 (external plain IIOP listener), 8885 (external IIOP/SSL listener) and 15000 (listener port for the connection to the Security Policy Server). The I-DBC Proxy has currently two connections: one from the Security Policy Server and one to the Security Policy Server.
Note that checksps.sh yields information not only about the Security Policy Server(s) but also about the DBC Proxy in your installation. If you start, for example, a Security Policy Server but do not start the DBC Proxies and then call the script, the output will read like this:
SecurityServer ... 2 processes/threads
dbcCluster1:myhost1 ... not started
dbcCluster1:myhost2 ... not started
EMERGENCY: All DBCs down!
The script will also indicate when some of the DBC Proxies in a cluster could not be started. If everything is up and running the exit status of the script is 0.
#OpenFusion
#KnowledgeDocs
