search for: lapomme00

I''ve now got 5 processes auto started. But I when I query the MiddleMan for their keys (in script/console), it doesn''t find them. Looking at the start script, it looks like it might be creating a new MiddleMan object for each autostart BackgrounDRb::MiddleMan.new.new_worker(:class => entry[''class''], Even changing it to

Ezra, Sorry for inundating the list. In using the autostart, repeat_every, and first_run, I noticed a behaviour I didn''t expect. I would like the job to run starting at 2am, and then every 24 hours. So I set first_run to Time.now.beginning_of_day + 2.hours, and repeat_every to 24.hours. The problem is if backgroundrb starts up at 6am (due to a code change or server bump), then the

I tried using the killall -USR1 mongrel_rails to check on a problem, and all I get is mongrel_rails: no process killed Nothing shows in the log. Any ideas? I''m using the latest pre-release, and a ''ps'' shows my cluster is running. Cheers, Brett

I''ve used Railscron in a couple instances, and I liked that fact that it has a rake task for checking the status of the process. Many times I use it in the admin interface to allow me to double check that everything is up and running. I couldn''t find one for backgroundrb, so here is a simple one. Probably obvious to everyone, and no doubt there is a better way to do it:

Any news on the Apache Best Practice Deployment instructions? I''m getting ready to set up a production server, and would prefer to use Apache and Mongrel/Cluster. Don''t think I''ll be able to get the latest Apache though. Do I have to proxy through Pound or something to handle multiple mongrel instances? Any pointers? Any help appreciated, Brett

I''m using RailsCron, and it''s working out very well for me. However, I''m having one problem right now. I use the acts_as_background on one of my model objects. In order to get it to add the cron job to the table, I have to make sure the model is loaded in environment.rb. MyObject.load However, I''m running 2-3 fcgi process on my server. Most of the time when

Hi all, I''m trying to create a worker to send a mail to all the users in my db. Right now I''m doing the tests, this is the code in my worker (Masivo is the ActionMailer subclass): def do_work(args) @progress = 0 @logger.info("MAILER: starting job") records = Record.find(:all) total = records.size records.each_with_index do |record, idx|

Recently while i turned on USR1 debugging...mongrel running behind Apache2.2threw following debugging messages: Thu Sep 07 15:58:30 IST 2006: 0 threads sync_waiting for /charts/%5EBSESN, 1 still active in mongrel. Thu Sep 07 15:58:40 IST 2006: 0 threads sync_waiting for /images/tab_but_normal1.png, 3 still active in mongrel. Thu Sep 07 15:58:40 IST 2006: 0 threads sync_waiting for

When deploying with Capistrano, what''s the recommended start ordering for BackgrounDRb? mongrel_stop backgroundrb_restart mongrel_start - or - mongrel_restart backgroundrb_restart - or - backgroundrb_restart mongrel_restart Or does it matter? Cheers, Brett

If I use repeat_every for a worker, if the do_work function has not completed by the time the next interval rolls around, will a new thread be started, resulting in 2 threads for the same worker? Looking at start_process, it seems like the thread gets created (which spins off the thread and then continues to execute the start_process method, right?), then sets the @next_start. So if the

I have one small suggestion, after just upgrading to the 0.13.4 pre-release. What about putting the version number in the log? This way it''s easy to verify what version we''re running. Maybe Starting Mongrel (v0.13.4) listening at 127.0.0.1:8000 or something. Cheers, Brett

I''ve found a conflict in the way the configuration file is handled, in particular effecting the setting of the ENV[''RAILS_ENV''] value. When I attempted to run a worker in production, it would run fine the first time - the second time would fail because it was trying to access the development database. I had created a ''backgroundrb_prodcution.yml'' file

I''ve created a couple of tasks in my deploy.rb file for starting and stopping backgroundrb on the remote server. The stop task runs fine and kills the process. And the start task *seems* to run successfully, but backgroundrb is never started on the remote host. Has anyone had success with this? Here are my deploy tasks: desc ''Start backgroundrb server (default