[AG-TECH] GLOBUS_HOSTNAME problems

[Julia Mullen]

Hi Tom,

I have to support Darin's experience here as we had exactly the same thing
happen with Ray Chen at U Maryland that day.  You may recall an exchange of 
email - we had the added complexity of removing the previous expired
cert - but once that was removed the anonymous cert still gave us the
globus-host error.
Once Ray was able to use his own cert the error went away and we were able to 
connect and test.

Ray, can you grab the logfiles from the machine you used and send them to 
Tom?

Thanks,

  Julie


On 8/24/05, Thomas D. Uram <turam at mcs.anl.gov> wrote:
> Darin:
> 
> I'd be very interested to see logfiles from your machines to understand
> what went wrong.
> 
> There is no relationship whatsoever between the certificate and the
> hostname, so switching from an anonymous certificate to an identity
> certificate can not have been the solution to the problem.
> 
> If you can send the VenueClient.log from the display machine, and the
> ServiceManager.log from any remote machine(s) involved, we should be
> able to identify the problem.
> 
> Thanks in advance for your help, Darin.
> 
> Tom
> 
> 
> Darin Oman wrote:
> > Mike, you RULE! I replaced the anonymous certificate with a good,
> > approved cert and it's back to normal! Is this a bug or something done
> > on purpose? Either way, people should know about this with DHCP nodes.
> > Thanks again! And Julie, thanks for verifying the fix.
> >
> > Darin
> >
> >
> > On Aug 16, 2005, at 11:52 AM, Michael Miller wrote:
> >
> >> I've had the same trouble when trying to use an anonymous cert.  not
> >> sure how to fix tho'.  What does nslookup give for your IP, and
> >> conversely for your domain name?  They should match up of course, but
> >> I've seen the name resolve to a different IP before...
> >>
> >> MYK
> >>
> >> Darin Oman wrote:
> >>
> >>> When I try to "manage my node," I'm told I need to specify the node
> >>> service URL, then I'm told that the machine "can not open node
> >>> management at https://..." I know this is a problem with DHCP
> >>> machines. I've tried set GLOBUS_HOSTNAME and I've also tried to
> >>> remove the environment variable. The problem there is that there is
> >>> no reference anywhere to GLOBUS_HOSTNAME. No environment variable,
> >>> nothing. I've tried removing and reinstalling the Globus parts as
> >>> well as the toolkit a number of times. I've also dug through the
> >>> registry. The result is always the same. Does anybody have any idea
> >>> what I'm missing?
> >>>
> >>> Thanks,
> >>> Darin
> >>>
> >>>
> >>
> >> --
> >> Thanx,
> >>
> >> Michael Miller
> >> System Engineer
> >> Video Technology Services
> >> Persistent Infrastructure Directorate
> >> National Center for Supercomputing Applications
> >> University of Illinois - UC
> >> 217-649-0747
> >>
> >> "If you're clear in your vision and trust the people in your team with
> >> clear objectives, they will invariably do their best to achieve
> >> everything desired, and usually deliver everything you could have
> >> hoped for and even more." -Paul Debevec
> >>
> >
> >
> 
>