need to kill endless-looping job

Hi. I have a job that is spinning and, of course, burning
all the  
memory and cpu on my bric server. Anyway, I tried to cancel
the job  
in Job Manager (GUI), but it keeps responding that
"Cannot cancel  
"[job name here]" because it is currently
executing." So, how can I  
kill this job. I have stopped the server with something
something  
initd, but I cannot remember the syntax, and out tech guy is
out  
today. We are using version 1.10.2. Thanks.

--------------------

This email message is for the sole use of the intended
recipient(s) and
may contain privileged information. Any unauthorized review,
use,
disclosure or distribution is prohibited. If you are not the
intended
recipient, please contact the sender by reply email and
destroy all copies
of the original message.

On Fri, 17 Aug 2007, Ashlee Caul wrote:
> Hi. I have a job that is spinning and, of course,
burning all the memory and
> cpu on my bric server. Anyway, I tried to cancel the
job in Job Manager
> (GUI), but it keeps responding that "Cannot cancel
"[job name here]" because
> it is currently executing."

I'm not sure that would help anyway, if the template is
going wild.


> So, how can I kill this job. I have stopped the
> server with something something initd, but I cannot
remember the syntax,
> and out tech guy is out today. We are using version
1.10.2. Thanks.

Probably

   # /etc/init.d/bricolage restart

if you're using a script from contrib/start_scripts/ .

On Aug 17, 2007, at 10:43 AM, Scott Lanning wrote:

> On Fri, 17 Aug 2007, Ashlee Caul wrote:
>> Hi. I have a job that is spinning and, of course,
burning all the  
>> memory and
>> cpu on my bric server. Anyway, I tried to cancel
the job in Job  
>> Manager
>> (GUI), but it keeps responding that "Cannot
cancel "[job name  
>> here]" because
>> it is currently executing."
>
> I'm not sure that would help anyway, if the template is
going wild.
>
>
>> So, how can I kill this job. I have stopped the
>> server with something something initd, but I cannot
remember the  
>> syntax,
>> and out tech guy is out today. We are using version
1.10.2. Thanks.
>
> Probably
>
>   # /etc/init.d/bricolage restart
>
> if you're using a script from contrib/start_scripts/ .

Well, I did run that command. When bric restarted, the job
resumed,  
and I still can't kill it. :( Any other thoughts?


--------------------

This email message is for the sole use of the intended
recipient(s) and
may contain privileged information. Any unauthorized review,
use,
disclosure or distribution is prohibited. If you are not the
intended
recipient, please contact the sender by reply email and
destroy all copies
of the original message.

On Fri, 17 Aug 2007, Ashlee Caul wrote:
>> Probably
>>
>>  # /etc/init.d/bricolage restart
>> 
>> if you're using a script from
contrib/start_scripts/ .
>
> Well, I did run that command. When bric restarted, the
job resumed, and I 
> still can't kill it. :( Any other thoughts?

Kill the job queue server.

# ps ax | grep bric_queued

(syntax could vary depending on the system)
then for each $PID number in the first column,

# kill $PID

or

# kill -9 $PID


Or if you know which job to cancel,
set executing='f' in the job table
for that job.

>>> Hi. I have a job that is spinning and, of
course, burning all the  
>>> memory and
>>> cpu on my bric server. Anyway, I tried to
cancel the job in Job  
>>> Manager
>>> (GUI), but it keeps responding that
"Cannot cancel "[job name  
>>> here]" because
>>> it is currently executing."
>>
>> I'm not sure that would help anyway, if the
template is going wild.
>>
>>
>>> So, how can I kill this job. I have stopped
the
>>> server with something something initd, but I
cannot remember the  
>>> syntax,
>>> and out tech guy is out today. We are using
version 1.10.2. Thanks.
>>
>> Probably
>>
>>   # /etc/init.d/bricolage restart
>>
>> if you're using a script from
contrib/start_scripts/ .
>
> Well, I did run that command. When bric restarted, the
job resumed,  
> and I still can't kill it. :( Any other thoughts?

Aha! I sudo executed init.d stop. While bric was stopped, I
went into  
Postgres and set executing=f, failed=t, expired=t for the
job that  
was looping. Then I init.d started bric again and was able
to cancel  
the job. I don't know if that was the right thing to do, so
I am  
keeping my fingers crossed that nothing blows up. Thanks.



--------------------

This email message is for the sole use of the intended
recipient(s) and
may contain privileged information. Any unauthorized review,
use,
disclosure or distribution is prohibited. If you are not the
intended
recipient, please contact the sender by reply email and
destroy all copies
of the original message.

Ashlee Caul wrote:
> Aha! I sudo executed init.d stop. While bric was
stopped, I went into 
> Postgres and set executing=f, failed=t, expired=t for
the job that was 
> looping. Then I init.d started bric again and was able
to cancel the job. I 
> don't know if that was the right thing to do, so I am
keeping my fingers 
> crossed that nothing blows up. Thanks.

That's what I would have done.

-mark

-- 
............................................................
.....
       :  Mark Jaroski      
       :  Room 9016            
       :  World Health Organization
       :  +41 22 791 16 65
       :                             
............................................................
.....
Any email message you receive which purports to be from me
should be
digitally signed.  Otherwise it is likely not in fact from
me.
............................................................
.....