Troubleshooting why your Grid service isn't in the caBIG Portal
From CaGrid
Contents |
Introduction
This page helps you isolate any problems with your Grid service that prevent proper registration with the caBIG Portal.
Obtaining and Verifying your Grid Service URL
- First, identify the URL of your Grid service (you should already know this). If you do not know your Grid service URL, do the following:
- Identify the hostname for your Grid service. Open up the server-config.wsdd file in your container. The following link specifies the location of this file in your container: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Appendix
- If this file does NOT specify a "logicalHost" parameter, then the hostname of your Grid service is the same as the hostname of the machine on which your Grid service resides.
- Otherwise, the hostname is what is specified in this file.
- Next, identify the port for your Grid service. This will be specified in the "server.xml" file in your container. The location of this file can be found at the following link: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Appendix
- Example:
- Identify the hostname for your Grid service. Open up the server-config.wsdd file in your container. The following link specifies the location of this file in your container: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Appendix
<Connector port="8080" address="${jboss.bind.address}" maxThreads="250" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"/>
The above file specifies a connector on port 8080 (the default). If your Grid service is not secure, your port will be this port.
- Otherwise, a secure port will be specified. For example:
<Connector port="8443" address="${jboss.bind.address}" maxThreads="100" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" scheme="https" secure="true" clientAuth="false" keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore" keystorePass="rmi+ssl" sslProtocol = "TLS" />
- Next, identify the PATH of your Grid service URL. To do that open up the jndi-config.xml file. The location of that is specified at the following URL: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Appendix
- Look for the following right near the beginning of that file: <service name="cagrid/TestDataServiceQuery">
- Next, identify the PATH of your Grid service URL. To do that open up the jndi-config.xml file. The location of that is specified at the following URL: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Appendix
- At this point, you have the hostname, port, and path of your service, so you should be able to re-construct the URL. Here is an example Grid service URL: http://cabiogrid32.nci.nih.gov/wsrf/services/cagrid/CaBIO32GridSvc
- Next, verify the URL is correct by entering the URL in your web browser. You should see a result similar to the following:
“Hi there, this is an AXIS service!”
Using the caBIG Portal to diagnose your service
Next, please go to the caBIG portal to check the status of your service. The link to the portal is: http://cagrid-portal.nci.nih.gov/web/guest/discovery. Enter your Grid service URL in the “Service Diagnostics” pane and click “Diagnose.” Check the results using the following method:
- The results will be similar to the following:
Index
If the result is not “Service found in the INDEX”:
Please follow the instructions at the following page: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Make_sure_your_container_is_publishing_the_right_host_name
Status in Portal
Service is in ACTIVE status
This will show up ACTIVE if the other checks are successful.
Ping Service
If the result does not say “Successfully pinged service”, please check you have the correct Grid Service URL and that you have no firewall or proxy preventing the Grid from contacting your service.
If you use a proxy, check the following steps to configure your container appropriately: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Changing_your_port_when_using_a_web_proxy_.28Apache.29_in_front_of_your_service
If you use a firewall, check that your firewall settings are configured properly.
To repeat this check yourself, enter the service URL in a web browser that is "on the Internet" (meaning outside your firewall).
Service Metadata
If the result is not “Service Metadata retrieved successfully”, please follow these instructions to check that your service is properly advertising metadata: http://www.cagrid.org/wiki/CaGrid:How-To:TroubleshootIndexService#Make_sure_the_service.27s_metadata_is_accessible
Finding out what is wrong
Check the logs of your container to identify the specific problem. Here are the locations of the log file:
- Tomcat: $CATALINA_HOME/logs/catalina.out
- JBoss: $JBOSS_HOME/server/default/log
Additional Steps
Peruse the instructions at the following page: http://www.cagrid.org/wiki/CaGrid:How-To:EnsureSucessfulGridNodeDeployment