Print

Print


Hi Santanu,

if I create my own condor submission file and use condor_submit I don't 
have any problems because condor.pm is not needed. Or in other words I 
bypass GLOBUS. Condor.pm is needed by GLOBUS when a job enters submitted 
via RB/WMS or globus-job-run. This script should generate the condor 
submission file and submit it to the WNs. Right now it does not...

As far as I know you are using condor in production. So can you give me 
the output of rpm -qa | grep -i vdt ? Only if your batch system still 
works ;-)

Thanks,
Christian.


Santanu Das wrote:
> Hi Christian,
>
> As far as I can recap, condor.pm is required by condor itself, hence 
> the error if the file is missing. Try submitting a pure condor job 
> (using condor_submit) and see if you can get the debug info that you 
> put in the condor.pm file.
>
> Cheers,
> Santanu
>
>
> Christian Neissner wrote:
>> Hi experts,
>>
>> because of the last update of VDT to lcg-CE 3.1 my CONDOR batch 
>> system broke. The problem is that the jobmanager file 
>> /opt/globus/lib/perl/Globus/GRAM/JobManager/condor.pm is completely 
>> ignored when I submit a job to the CE. The strange thing is that its 
>> existence is still required (if I remove it I get the error of 
>> missing script), but it's not used to create the condor submission 
>> file. Well, it's not used anyway as I can see putting some debugging 
>> infos into the file that never reach me. Instead a default submission 
>> file is created (I don't know what script is doing that) that does 
>> not work because of default requirements I don't want to fulfill. If 
>> somebody knows the new mechanism of creating the condor submission 
>> file  I can live with the new VDT version. If not I would have to do 
>> a rollback.
>>
>> Thanks in advance,
>> Christian.
>