Hi Brad,
Absolutely nothing about these jobs in the handler logs?
--nate
On Wed, Nov 30, 2016 at 8:20 PM, Langhorst, Brad wrote:
>
> On Nov 30, 2016, at 4:27 PM, Nate Coraor wrote:
>
> Seems on the up 'n up. Can you check the `handler` column of the job table
> in the database for the jobs in
On Nov 30, 2016, at 4:27 PM, Nate Coraor
mailto:n...@bx.psu.edu>> wrote:
Seems on the up 'n up. Can you check the `handler` column of the job table in
the database for the jobs in question?
id |create_time | state | handler |
537202 | 2016-11-30 05:49:35.363694 | new
Seems on the up 'n up. Can you check the `handler` column of the job table
in the database for the jobs in question?
On Wed, Nov 30, 2016 at 4:14 PM, Langhorst, Brad wrote:
> nope -
> I limit local jobs to 8, but no jobs go to that destination
>
> 2 handlers, a few jobs that reserve more cores.
nope -
I limit local jobs to 8, but no jobs go to that destination
2 handlers, a few jobs that reserve more cores.
here’s my job.conf
/opt/gridengine/lib/linux-x64/libdrmaa.so
Hi Brad,
Do you have any kind of strange job mapping going on, or job limits
configured?
--nate
On Wed, Nov 30, 2016 at 1:01 AM, Langhorst, Brad wrote:
> Hi:
>
> I have one user who’s jobs won’t execute on my local instance.
>
> The user was mysteriously listed as inactive.
> I reactivated and
Hi:
I have one user who’s jobs won’t execute on my local instance.
The user was mysteriously listed as inactive.
I reactivated and restored the handlers, still jobs are not executing.
The user has plenty of quota (82% used)
Anybody have an idea about what might be wrong with this user?
I have
