Re: [Condor-users] Condor-G error

[Alain Roy <roy@xxxxxxxxxxx>]

> The job logfile says job erminated with code 0 but the output file is blank

Globus doesn't report the real job exit code, so normally Condor-G does not 
know how the program exited. This is a pain.

> and in the err file I have these lines;
> /home/anayar/.globus/.gass_cache/local/md5/6d/b79a6f3509c347511288b4d7fd7023/md5/bf/da2251026d9ef45506b9d515b4378b/data: 
> /lib/i686/libc.so.6:
> version `GLIBC_2.3' not found (required
> by 
> /home/anayar/.globus/.gass_cache/local/md5/6d/b79a6f3509c347511288b4d7fd7023/md5/bf/da2251026d9ef45506b9d515b4378b/data)

Section 5.3.3 of the Condor manual says:

> By default, Condor transfers the executable, as well as any files 
> specified by the input command. Note that this executable must be compiled 
> for the correct intended platform.

(There is a lot of stuff in the manual, so don't feel bad that you didn't 
notice this earlier.)

If you do globus-job-run ... /bin/date, the executable is not transferred. 
This is one big difference.

So Condor-G sent over a version of /bin/date that was not compiled 
correctly for the computer that you ran it on. I don't know about your 
version of date, but my version is dynamically linked. Dynamic linking is 
always a pain when transferring executables.

You have two options:

1) Select an executable that will work on the remote computer.
2) Tell Condor not to transfer the executable, but to use the one at the 
remote site:

transfer_executable = FALSE

Either one of these should help you out.

-alain