similar to: Deploying to production with backgroundrb (capistrano)

Hello ~ I am using the Capistrano recipe outlined in this post to restart my backgroundrb server: http://rubyforge.org/pipermail/backgroundrb-devel/2007-February/000718.html My Version: ~~~~~~~~~~~~ task :before_restart, :roles => :app do restart_backgroundrb end task :start_backgroundrb, :roles => :app do sudo "nohup

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

Hi there, We''ve been using previous version of bdrb (drb based one) for a while and it was running relatively OK. We recently attempted to upgrade to the new version to keep up / use supported version but we ended up reverting to the older version. Here are the things that moved us to revert : 1) With the workers we never manage to pass this error: '''' You have a nil

so i have an after_create method on my track model that kicks off a background process that converts an mp3 to a swf. this is working fine locally on my machine, but upon moving it to my production server, i am getting the following error. I''ve only been using backgroundRB for like 48 hours, so i''m not really sure what this means or where to go. any ideas?

Hi. I am using BackgrounDRb to process thumbnails and upload to S3 - things are hunky-dory in development (thumbs are generated, these are uploaded to S3, the metadata is saved to trhe DB, and I get a nice status page updated by periodic calls via ask_status), but when I tried to deploy to our staging server and stop/start BackgrounDRb via Capistrano, things blew up - well, not exactly,

ok, i was wrong. the failure on deployment using capistrano is 100% using these commands ## Our Handlers desc "Restart BackgrounDrb" task :restart_uploader, :roles => :app do run "#{current_path}/script/backgroundrb stop" run "#{current_path}/script/backgroundrb start" end here is the console post deploy on the remote server ######## [current]$

i get this: undefined method `object'' for nil:NilClass when i try to get the status of a worker after backgroundrb has been restarted using a job key saved in the DB. how do i get around this? i know the process is nonexistent, but shouldnt it return something more friendly if it doesnt exist? am i forgetting something? Thanks! -Jerrod Jerrod Blavos ph. 919.341.0143 fx.

Help, I've been having a difficult time trying to create 3d partial dependence plots using "rgl". It looks like this question has been asked a couple times, but I'm unable to find a clear answer googling. I've tried creating x, y, and z variables by extracting them from the partialPlot output to no avail. I've seen these plots used several times in articles, and I

Hi there I''m using the latest release (r300) and ''script/backgroundrb start'' works perfectly when executed on the server, but when put inside a Rake task, it doesn''t launch the worker processes. The Rake task is as follows: task :start_backgroundrb do run "cd #{current_path} && ./script/backgroundrb start" end When I run this task, the

Hi, I''m running a ubuntu 8.04.2 LTS server. Using ruby 1.8.6 and Rails 2.0.2 I added the mongrel_rails start -d -c /app/ to the /etc/rc.local sofar so good.. Mongrel will start but will log Missing the rails 2.0.2 gem. Please ''gem install -v=2.0.2 ..... and then terminate When I log onto the the console I can start mongrel_rails and it will locate the right gems any ideas

Im checking out the mongrel_upload_progress plugin and have it working beautifully on my dev box. however, now that i am ready to push this up into production i have run into a few gotchas that i cannot seem to find any documentation or examples for. the lib/upload.rb doesnt seem to want to run in the background. perhaps im doing something wrong? Does anyone have any experience

is it possible to use these together? im asking because in the sample docs for mongrel_upload_progress, it has you start by hand a druby instance. This doesnt work very well when moving to production. as in, i cant seem to get that particular process to either stop or restart after a new deploy. I posted to the mongrel-users list about this and have not gotten any sort of response.

Hi Oscar, For development, CMake is working great for me. I rarely get build errors related to the project file being out-of-date. Is it true that CMake only generates absolute paths? Any idea on the difficulty of generating relative paths? I consider this a pretty big obstacle... Thanks for all your hard work on this, snaroff On Jan 15, 2009, at 9:46 AM, Óscar Fuentes wrote: >

Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190 Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix whatever to the questions posed as fsck runs. What does this all mean? Thanks, -Clint -- This message has been scanned for viruses and dangerous content by MailScanner,