Re: [gridengine users] Fwd: eqw for qsub jobs

> Am 28.09.2016 um 17:06 schrieb Dan Hyatt : > > Thanks, > > after what you said, suggests it is something the user is doing. But she is > saying some of the jobs are working and some are being dumped because its > full. Maybe with "full" she refers to the diskspace

Re: [gridengine users] Fwd: eqw for qsub jobs

As Chris says, the output of "qstat -j " should be the first place to look. It should explain why the job is in an error state. Ian On Wed, Sep 28, 2016 at 8:06 AM, Dan Hyatt wrote: > Thanks, > > after what you said, suggests it is something the user is doing. But she

Re: [gridengine users] Fwd: eqw for qsub jobs

Thanks, after what you said, suggests it is something the user is doing. But she is saying some of the jobs are working and some are being dumped because its full. On 09/28/2016 09:41 AM, Chris Dagdigian wrote: I think the "queue instance dropped because ... full" is not related to your

Re: [gridengine users] Fwd: eqw for qsub jobs

I think the "queue instance dropped because ... full" is not related to your user/job problem. The dropped message is a sign from the job placement process that the queue instance was skipped during the active host select-and-job-dispatch round because it had no more job slots free to take

[gridengine users] Fwd: eqw for qsub jobs

I am trying to narrow down what would cause this. I searched google and the sge resources and could not find a reason for queue instance "VeryHighMem@blade5-5-8" dropped because it is full queue instance "HighMem@blade5-1-4" dropped because it is full This is that one user almost every