Bug 5325 – Automatic upstream registration failing

Bug 5325 - Automatic upstream registration failing

Summary:

Automatic upstream registration failing

Status:	NEW

Product:	MDS4
Component:	wsrf_index
Version:	4.0.3
Platform:	All All

Importance:	P3 major
Target Milestone:	---
Assigned To:	Laura Pearlman

URL:
Keywords:	Teragrid

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-05-23 17:26 by John-Paul Navarro
Modified:	2008-06-25 16:42 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From John-Paul Navarro 2007-05-23 17:26:09

The TeraGrid has a standalone MDS4 container (disabled WS GRAM, MDS) based on
VDT 1.6.1/GT 4.0.3 (with patches). In globus_wsrf_mds_index/server-config.wsdd
under <service name="DefaultIndexServiceEntry"... we have <parameter
name="loadOnStartup" value="true"/>.

When we started using loadOnStartup it did help upstream registrations work
automatically on some platforms, but it appears it is not be working on all our
platforms.

What can we do to debug this issue? Specific logging options and logging output
for the developers, or something else?

Thanks.

------- Comment #1 From John-Paul Navarro 2007-05-23 17:40:11 -------

Sorry, I should have said "(disabled WS GRAM, RFT)"...

------- Comment #2 From Laura Pearlman 2007-05-23 21:22:21 -------

Can you please get us the upstream.xml, hierarchy.xml, and server-config.wsdd
files from $GLOBUS_LOCATION/etc/globus_wsrf_mds_index on the downstream hosts
(at IU and SDSC), and the container logs from those hosts and the central index
service?

Thanks.

------- Comment #3 From Laura Pearlman 2007-07-12 16:10:52 -------

JP has put me in touch with one of the resource admins who should be able to
give me log files, etc.