[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Condor-G error
- Date: Mon, 04 Oct 2004 14:03:38 -0500
- From: Alain Roy <roy@xxxxxxxxxxx>
- Subject: Re: [Condor-users] Condor-G error
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;
version `GLIBC_2.3' not found (required
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
transfer_executable = FALSE
Either one of these should help you out.