Yes, that's where the non-logicalHost name is defined (I thought it might be in a configuration file generated by the install somewhere):
<ns1:host xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xsi:type="xsd:string">grid.gc.cuny.edu</ns1:host> and <ns1:host xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xsi:type="xsd:string">grid.gc.cuny.edu</ns1:host> Now this works, except for a problem (concerning postgres database access) that will be the subject of another thread: [EMAIL PROTECTED] ~/gt4/etc/gram-service $ globusrun-ws -s -submit -c /bin/date Delegating user credentials...Done. Submitting job...Done. Job ID: uuid:ee69de16-6556-11dc-bd2c-0002b323da69 Termination time: 09/18/2007 19:48 GMT Current job state: Active Current job state: CleanUp-Hold Mon Sep 17 15:48:16 EDT 2007 Current job state: CleanUp Current job state: Failed Destroying job...Done. Cleaning up any delegated credentials...Done. globusrun-ws: Job failed: Staging error for RSL element fileCleanUp. [EMAIL PROTECTED] ~/gt4/etc/gram-service $ This particular configuraion looks sufficiently non-obvious to me that it might be documented, for users planning on deployment on multi-homed hosts. Thanks again! FL -----Original Message----- From: Charles Bacon [mailto:[EMAIL PROTECTED] Sent: Mon 9/17/2007 3:27 PM To: Lengyel, Florian Cc: [email protected] Subject: Re: [gt-user] logicalHost -- when does globus decide to use hostname? I'm sorry it took me so long to see what's happening. You're right, it was something that got setup when the GLOBUS_LOCATION was first installed. I had missed that the job executed correctly and that only the Cleanup directive was failing. When you install GT, it creates $GLOBUS_LOCATION/etc/gram-service/ globus_gram_fs_map_config.xml. That file tells GRAM what GridFTP servers to use for file staging and cleanup operations. I assume that has the old hostname embedded in it. Changing the hostname in there and restarting the container should fix it. Charles On Sep 17, 2007, at 2:20 PM, Lengyel, Florian wrote: > > From /etc/hosts > > 127.0.0.1 localhost localhost > 10.10.32.248 m248.gc.cuny.edu m248 > 146.96.129.99 grid.gc.cuny.edu grid > > I've included the name in the external DNS as well. > > Thanks again. > > -----Original Message----- > From: Charles Bacon [mailto:[EMAIL PROTECTED] > Sent: Mon 9/17/2007 3:18 PM > To: Lengyel, Florian > Cc: [email protected] > Subject: Re: [gt-user] logicalHost -- when does globus decide to > use hostname? > > You don't necessarily need DNS setup, but you might need to make some > changes to your /etc/hosts. What are the entries for m248, grid, and > localhost in /etc/hosts? > > > -c > > On Sep 17, 2007, at 2:11 PM, Lengyel, Florian wrote: > > > Thanks for this. > > > > How do you check this reverse lookup? m248.gc.cuny.edu has ip > address > > 10.10.32.248 and is not in any DNS. It's in /etc/hosts > > > > [EMAIL PROTECTED] ~ $ host 10.10.32.248 > > Host 248.32.10.10.in-addr.arpa not found: 3(NXDOMAIN) > > [EMAIL PROTECTED] ~ $ host 146.96.129.99 > > 99.129.96.146.in-addr.arpa domain name pointer grid.gc.cuny.edu. > > [EMAIL PROTECTED] ~ $ > > > > > > Incidentally, even after changing the hostname to m248.gc.cuny.edu > > and regenerating host and containerkey certificates, I still have > the > > same behavior. Does this mean I need to set up DNS services for > > the internal network? > > > > > > > > [EMAIL PROTECTED] ~ $ globusrun-ws -s -submit -c /bin/hostname > > Delegating user credentials...Done. > > Submitting job...Done. > > Job ID: uuid:ce8a6d50-6550-11dc-9e6a-0002b323da69 > > Termination time: 09/18/2007 19:04 GMT > > Current job state: Active > > Current job state: CleanUp-Hold > > globusrun-ws: ignoring error while streaming gsiftp:// > > grid.gc.cuny.edu:2811/home/m248/globus/ > > ce8a6d50-6550-11dc-9e6a-0002b323da69.0.stdout: > > globus_ftp_control: gss_init_sec_context failed > > GSS Major Status: Unexpected Gatekeeper or Service Name > > globus_gsi_gssapi: Authorization denied: The name of the remote > > host (m248.gc.cuny.edu), and the expected name for the remote host > > (grid.gc.cuny.edu) do not match. This happens when the name in the > > host certificate does not match the information obtained from DNS > > and is often a DNS configuration problem. > > globusrun-ws: ignoring error while streaming gsiftp:// > > grid.gc.cuny.edu:2811/home/m248/globus/ > > ce8a6d50-6550-11dc-9e6a-0002b323da69.0.stderr: > > globus_ftp_control: gss_init_sec_context failed > > GSS Major Status: Unexpected Gatekeeper or Service Name > > globus_gsi_gssapi: Authorization denied: The name of the remote > > host (m248.gc.cuny.edu), and the expected name for the remote host > > (grid.gc.cuny.edu) do not match. This happens when the name in the > > host certificate does not match the information obtained from DNS > > and is often a DNS configuration problem. > > Current job state: CleanUp > > Current job state: Failed > > Destroying job...Done. > > Cleaning up any delegated credentials...Done. > > globusrun-ws: Job failed: Staging error for RSL element fileCleanUp. > > [EMAIL PROTECTED] ~ $ > > > > > > -----Original Message----- > > From: Charles Bacon [mailto:[EMAIL PROTECTED] > > Sent: Mon 9/17/2007 3:02 PM > > To: Lengyel, Florian > > Cc: [email protected] > > Subject: Re: [gt-user] logicalHost -- when does globus decide to > > use hostname? > > > > The client machine is doing a reverse-IP lookup on the address it > > connects to. The issue here does not appear to be with the server > > hostname configuration, but the client's resolution process. I see > > that you're connecting from the same machine - is it possible that > > it's getting 127.0.0.1 as the server's address, then reverse-looking > > that up to the wrong name? Does the same thing happen from a second > > machine? > > > > > > Charles > > > > On Sep 17, 2007, at 12:44 PM, Lengyel, Florian wrote: > > > > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] on behalf of Lengyel, Florian > > > Sent: Mon 9/17/2007 1:35 PM > > > To: [email protected] > > > Subject: [gt-user] logicalHost -- when does globus decide to use > > > hostname? > > > > > > > > > I have had a persistent problem with the globus toolkit for > several > > > years now. > > > The problem concerns the semantics of logicalHost. The idea of > > > logicalHost is > > > that it overrides hostname. At least it should, only I haven't > seen > > > it do this > > > consistently in all of the years that I have been using the globus > > > toolkit. > > > If I try to set the hostname to the logicalHost that I want > > > globus to use, even if that means breaking other systems that > might > > > have > > > depended on my original hostname, then globus seems to use the > > > hostname > > > under which it was compiled. > > > > > > > > > > > > Here's an example. Originally I compiled globus on a machine with > > > hostname grid.gc.cuny.edu. That was the hostname under which > > > the simpleCA was created--perhaps this is related. > > > > > > I wanted the logicalHost name to be m248.gc.cuny.edu, > > > which refers to a different interface. The following error occurs > > > > > > a) with hostname grid.gc.cuny.edu and logicalHost m248.gc.cuny.edu > > > b) with hostname m248.gc.cuny.edu and logicalHost m248.gc.cuny.edu > > > > > > It's clear that the command /bin/hostname executes - I have the > > > output. Only the attempt by globus to return the output fails, > > > because for some reason globus expects to see grid.gc.cuny.edu as > > > the hostname, even though it is running on m248.gc.cuny.edu, > > > and that is the hostname. > > > > > > [EMAIL PROTECTED] ~ $ globusrun-ws -s -submit -c /bin/hostname > > > Delegating user credentials...Done. > > > Submitting job...Done. > > > Job ID: uuid:dfa17d24-6544-11dc-88ad-0002b323da69 > > > Termination time: 09/18/2007 17:38 GMT > > > Current job state: Active > > > Current job state: CleanUp-Hold > > > globusrun-ws: ignoring error while streaming gsiftp:// > > > grid.gc.cuny.edu:2811/home/m248/globus/ > > > dfa17d24-6544-11dc-88ad-0002b323da69.0.stdout: > > > globus_ftp_control: gss_init_sec_context failed > > > GSS Major Status: Unexpected Gatekeeper or Service Name > > > globus_gsi_gssapi: Authorization denied: The name of the remote > > > host (m248.gc.cuny.edu), and the expected name for the remote host > > > (grid.gc.cuny.edu) do not match. This happens when the name in the > > > host certificate does not match the information obtained from DNS > > > and is often a DNS configuration problem. > > > globusrun-ws: ignoring error while streaming gsiftp:// > > > grid.gc.cuny.edu:2811/home/m248/globus/ > > > dfa17d24-6544-11dc-88ad-0002b323da69.0.stderr: > > > globus_ftp_control: gss_init_sec_context failed > > > GSS Major Status: Unexpected Gatekeeper or Service Name > > > globus_gsi_gssapi: Authorization denied: The name of the remote > > > host (m248.gc.cuny.edu), and the expected name for the remote host > > > (grid.gc.cuny.edu) do not match. This happens when the name in the > > > host certificate does not match the information obtained from DNS > > > and is often a DNS configuration problem. > > > Current job state: CleanUp > > > Current job state: Failed > > > Destroying job...Done. > > > Cleaning up any delegated credentials...Done. > > > globusrun-ws: Job failed: Staging error for RSL element > fileCleanUp. > > > [EMAIL PROTECTED] ~ $ > > > > > > > > > > > >
