librelist archives

« back to archive

scheduler

scheduler

From:
Andrea Campolonghi
Date:
2013-02-20 @ 09:33
Hi,

does someone had luck on setting up a monitoring for resque-scheduler with
upstart ?
I also need to kill the process after any deploy to let upstart fire them again.
With Resque is easy cause it stores the pid inside Resque object but with 
the scheduler I cannot find the way to get the correct pid.

Any suggestion? 

Andrea Campolonghi
acampolonghi@gmail.com


Re: [resque] scheduler

From:
Eugen Funk
Date:
2013-02-21 @ 21:11
Hi,

you may try "kill -9 `cat resque.pid`"
for this you have to find the file "resque.pid" which is created on
starting the daemon



2013/2/20 Andrea Campolonghi <acampolonghi@gmail.com>

> Hi,
>
> does someone had luck on setting up a monitoring for resque-scheduler with
> upstart ?
> I also need to kill the process after any deploy to let upstart fire them
> again.
> With Resque is easy cause it stores the pid inside Resque object but with
> the scheduler I cannot find the way to get the correct pid.
>
> Any suggestion?
>
> Andrea Campolonghi
> acampolonghi@gmail.com
>
>
>
>

Re: [resque] scheduler

From:
Adam Tucker
Date:
2013-02-22 @ 00:32
I was digging through the source code and in lib/resque_scheduler/tasks.rb
it looks like you can pass an env variable PIDFILE when starting the 
scheduler, giving you a way to monitor the demonized process.

Let me know if you have any luck with that; I've never tried it but have 
seen resque-scheduler act strange under monit, probably because of this. 

-Adam 


On Wednesday, February 20, 2013 at 4:33 AM, Andrea Campolonghi wrote:

> Hi,
> 
> does someone had luck on setting up a monitoring for resque-scheduler 
with upstart ?
> I also need to kill the process after any deploy to let upstart fire them again.
> With Resque is easy cause it stores the pid inside Resque object but 
with the scheduler I cannot find the way to get the correct pid.
> 
> Any suggestion? 
> 
> Andrea Campolonghi
> acampolonghi@gmail.com (mailto:acampolonghi@gmail.com)
> 
> 

Re: [resque] scheduler

From:
Andrea Campolonghi
Date:
2013-02-22 @ 08:19
Thanks.

The problem is exactly this.
When I launch the scheduler in background and I ask to create the pidfile 
upstart looks like is not able to monitor the correct pid.
I tried using both:

expect fork or expect daemon

with no luck.

Andrea 

On Feb 22, 2013, at 1:32 AM, Adam Tucker <adam.j.tucker@gmail.com> wrote:

> I was digging through the source code and in 
lib/resque_scheduler/tasks.rb it looks like you can pass an env variable 
PIDFILE when starting the scheduler, giving you a way to monitor the 
demonized process.
> 
> Let me know if you have any luck with that; I've never tried it but have
seen resque-scheduler act strange under monit, probably because of this.
> 
> -Adam
> On Wednesday, February 20, 2013 at 4:33 AM, Andrea Campolonghi wrote:
> 
>> Hi,
>> 
>> does someone had luck on setting up a monitoring for resque-scheduler 
with upstart ?
>> I also need to kill the process after any deploy to let upstart fire 
them again.
>> With Resque is easy cause it stores the pid inside Resque object but 
with the scheduler I cannot find the way to get the correct pid.
>> 
>> Any suggestion?
>> 
>> Andrea Campolonghi
>> acampolonghi@gmail.com
> 


Andrea Campolonghi
ac@fractalgarden.com

Fractalgarden S.r.l.
Via Giuseppe Mazzini 33 - 20099 Sesto San Giovanni (MI) - Italy Office: 
+39 02 87212138 - Fax: +39 02 36596358 
www.fractalgarden.com