Print

Print


On Sat, 7 May 2005 [log in to unmask] wrote:

> On Fri, 6 May 2005, Anja Vest wrote:
> 
> > [...]
> > submit-helper script running on host ekp-lcg-ce gave error: 
> > cache_export_dir (/usr/users/dcms002/.lcgjm/globus-cache-export.XgmvIH) 
> > on gatekeeper did not contain a cache_export_dir.tar archive
> 
> This is answered in the job submission section of the Wiki FAQ:
> 
>     http://goc.grid.sinica.edu.tw/gocwiki/SiteProblemsFollowUpFaq
> 
> In particular:
> 
> http://goc.grid.sinica.edu.tw/gocwiki/submit-helper_script_%2e%2e%2e_gave_error%3a_cache_export_dir_%2e%2e%2e
> 
> Indeed, a test shows your WNs cannot globus-url-copy to/from your CE:
> 
> -----------------------------------------------------------------------------
> error: globus_l_ftp_control_send_cmd_cb: gss_init_sec_context failed
> 
>  GSS failure:
> GSS Major Status: Unexpected Gatekeeper or Service Name
> GSS Minor Status Error Chain:
> 
> init_sec_context.c:251: gss_init_sec_context: Mutual authentication failed:
> The target name (/O=GermanGrid/OU=EKP/CN=host/ekp-lcg-ce.physik.uni-karlsruhe.de)
> in the context, and the target name (/CN=host/ekp-lcg-ce.ekpplus.cluster)
> passed to the function do not match
> -----------------------------------------------------------------------------
> 
> The problem is due to this entry in /etc/hosts on your WN (e.g. ekpplus020):
> 
> -----------------------------------------------------------------------------
> 192.168.101.231 ekp-lcg-ce.ekpplus.cluster         ekp-lcg-ce
> -----------------------------------------------------------------------------
> 
> You could change that line as follows (all on a single line):
> 
> -----------------------------------------------------------------------------
> 192.168.101.231 ekp-lcg-ce.physik.uni-karlsruhe.de
>                 ekp-lcg-ce.ekpplus.cluster         ekp-lcg-ce
> -----------------------------------------------------------------------------
> 
> That is, fake that the private interface also has the external name.
> 
> A simpler/cleaner solution is not to use the private interface at all:
> 
> -----------------------------------------------------------------------------
> 129.13.133.12   ekp-lcg-ce.physik.uni-karlsruhe.de ekp-lcg-ce
> -----------------------------------------------------------------------------

A third solution would be to rename the private interface to something like this:

    ekp-lcg-ce-local.physik.uni-karlsruhe.de

Then you can use this on the WN:

-----------------------------------------------------------------------------
192.168.101.231 ekp-lcg-ce-local.physik.uni-karlsruhe.de         ekp-lcg-ce
-----------------------------------------------------------------------------

For host DN comparisons Globus considers "foo.bar.org" equivalent to
"foo-xyz.bar.org", where "xyz" would indicate an alternative interface.