[Swift-devel] gram4 detecting own host identity

[Martin Feller]

Maybe also interesting: from Bens description it seems that this
just happens sometimes and not always. I don't know about the details
of hostname settings and updates of hostnames and stuff in Linux well
enough, but this sounds a bit odd.


----- Original Message -----
From: "Mihael Hategan" <hategan at mcs.anl.gov>
To: "Martin Feller" <feller at mcs.anl.gov>
Cc: "Ben Clifford" <benc at hawaga.org.uk>, "Rachana Ananthakrishnan" <ranantha at mcs.anl.gov>, swift-devel at ci.uchicago.edu
Sent: Sunday, May 18, 2008 8:15:01 PM GMT -06:00 US/Canada Central
Subject: Re: [Swift-devel] gram4 detecting own host identity


On Sun, 2008-05-18 at 16:47 -0500, Martin Feller wrote:
> Ben:
> 
> I assume you mean the NotificationConsumer in the context of a subscription for job status
> notifications, which is created on the client-side and used in a job submission to Gram4 to
> create a subscription resource, right?
> How is the NotificationConsumer with the defective address created on the client-side:
> using Gram4's GramJob, or by other means?
> 
> I think in any event it goes down to Java WS Core, since it's there where the address
> of the NotificationConsumer is generated.
> (NotificationConsumerManager.createNotificationConsumer() ->
>  ClientNotificationConsumerManager.getURL() -> ServiceContainer.getURL()
>  and finally the host seems to come from ServiceHost.getHost())
> Gram4 does not set addresses in endpoints of NotificationConsumers itself.

Eventually the thing ends in the jglobus CoGProperties.getHostname() or
CoGProperties.getIP().

It's somewhat of a known problem. Java is poor at figuring such kind of
information.

Ben, can you do an ifconfig -a (or ask Andrew) on that machin?

> 
> Maybe Rachana can shed some light on this, or correct me if I'm wrong.
> 
> Does setting GLOBUS_HOSTNAME solve the issue? I know, you mentioned that you think
> this complicates the matter, but for debugging ...
> 
> Is this 4.0 or upcoming 4.2 specific, or do you experience that problem for both?
> 
> Martin
> 
> 
> ----- Original Message -----
> From: "Ian Foster" <foster at mcs.anl.gov>
> To: "Ben Clifford" <benc at hawaga.org.uk>
> Cc: swift-devel at ci.uchicago.edu, "Stuart Martin" <smartin at mcs.anl.gov>, "Martin Feller" <feller at mcs.anl.gov>
> Sent: Sunday, May 18, 2008 3:01:09 PM GMT -06:00 US/Canada Central
> Subject: Re: [Swift-devel] gram4 detecting own host identity
> 
> Ben:
> 
> I'd recommend talking to your colleagues in the GRAM team--Stu Martin  
> and Martin Feller in particular.
> 
> Ian.
> 
> On May 18, 2008, at 12:45 PM, Ben Clifford wrote:
> 
> >
> > (I just sent this by accident to the secret SWFT list - it was  
> > intended
> > for this list, swift-devel)
> >
> > A couple (or maybe three) times in the past few days I've seen the  
> > GRAM4
> > submission be extremely bad at detecting its own identity to use in
> > WS-Notification subscriptions - it seems to end up using 'localhost'
> > rather than the global-scope hostname...
> >
> > Here is one from andrew.bsd.uchicago.edu, for example (it also  
> > happens on
> > wiggum and on my laptop):
> >
> > <ns1:ConsumerReference><wsa:Address>https://localhost:50000/
> > wsrf/services/NotificationConsumerService</wsa:Address>
> >
> > [...]
> >
> > These machines, as far as any sane unix person would think, are  
> > correctly
> > identifying themselves with the hostname command, have proper  
> > forward and
> > reverse DNS set up, and the like; pretty much everything else can  
> > figure
> > out the local identity correctly; so the workaround 'set  
> > GLOBUS_HOSTNAME
> > to your hostname' seems unnecessarily complicated in these cases.
> >
> > -- 
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> 
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel