Re: [Condor-users] Condor killing jobs when other are completed?

[Erik Aronesty <erik@xxxxxxx>]

My experience was that on a new installation, vanilla jobs will get killed if

) they are vacated because the server is too busy (usually because
they over-fork)

or

) there's a problem in communicating "ALIVE" messages (this happened
to me because DNS is handled a bit counterinutitively in condor)

Double check that

) the IP address that ths ubmitting machine knows itself as is the
same ip address that the executing machine can ping the submitter at

2) vanilla jobs are never allowed to be vacated or preempted ... since
it just kills them and thats probably not what you want


On Thu, Dec 16, 2010 at 6:17 AM, Sónia Liléo <sonia.lileo@xxxxx> wrote:
> Hi!
>
>
>
> I am submitting several jobs to my condor pool and I have noticed that most
> of the submitted jobs are killed before being executed.
>
>
>
> The same account is being used to execute all the jobs.
>
> Is it so that if this account is configured as dedicated, all jobs belonging
> to that user will be terminated when a job is completed?
>
>
>
> The execute nodes are Linux machines while the submitter is a Windows
> machine.
>
> Neither of the variables EXECUTE_LOGIN_IS_DEDICATED nor
> DEDICATED_EXECUTE_ACCOUNT_REGEXP are defined in none of my machines.
>
>
>
> How should I solve this problem?
>
>
>
> Best regards,
>
> Sónia
>
>
>
>
>
>
>
>
>
> Sónia Liléo
> O2 Strandvägen 5B 114 51 Stockholm
> Tel: +46 8 559 310 37 Mobile: +46 73 752 95 74
>
> www.o2.se
>
>
>
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>
>