[GE users] Job causes queues to go into error state

reuti reuti at staff.uni-marburg.de
Thu Dec 4 11:12:43 GMT 2008


Hi,

Am 04.12.2008 um 00:05 schrieb Iwona Sakrejda:

> I have this one user whose jobs are flushing through hosts and  
> pushing queues into error state.
> I cannot figure it out. Here is a snippet from an e-mail generated  
> by suvh a job.
>
> 12/03/2008 14:27:51 [171:13726]: wait3 returned 13727 (status:  
> 32512; WIFSIGNALED: 0,  WIFEXITED: 1, WEXITSTATUS: 127)
> 12/03/2008 14:27:51 [171:13726]: prolog exited with exit status 127
> 12/03/2008 14:27:51 [171:13726]: reaped "prolog" with pid 13727
> 12/03/2008 14:27:51 [171:13726]: prolog exited not due to signal
> 12/03/2008 14:27:51 [171:13726]: prolog exited with status 127
> 12/03/2008 14:27:51 [171:13726]: exit_status of prolog = 127
> 12/03/2008 14:27:51 [171:13726]: no epilog script to start
>
> Other jobs are running happily on those nodes.
> Could you suggest where to start looking for the cause?

is the user known on the hosts? What's the prolog doing?

-- Reuti

>
> Thanks a lot,
>
> iwona
>
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do? 
> dsForumId=38&dsMessageId=90973
>
> To unsubscribe from this discussion, e-mail: [users- 
> unsubscribe at gridengine.sunsource.net].

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=91090

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list