similar to: Any luck using Rails 2.1 config.gem?

Hi, I still have the following error while loading backgroundrb : /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/gems/ packet-0.1.14/lib/packet/packet_master.rb:116:in `exec'': No such file or directory - packet_worker_runner 14:11:maintenance_worker:64:/home/ antz/declix.com/production/lib/workers (Errno::ENOENT) from

Hi, I am playing around with backgroundrb 1.0.3. I have the following backgroundrb.yml, --- :backgroundrb: :port: 11006 :ip: 0.0.0.0 :schedules: :task_worker: :run: :trigger_args: */10 * * * * * My task worker is just, class TaskWorker < BackgrounDRb:MetaWorker set_worker_name :task_worker def run logger.info "begin" sleep 60 logger.info

Hi, New BackgrounDrb user struggling for a couple of days to get things up an going. System: Ruby 1.8.6 Packet 0.1.5 chronic 0.2.3 BackgrounDrb 1.0.3 (downloaded 4/02/08 and 4/03/08) I installed the packet and chronic gems as per instructions. I used git to download BDrb as per instructions and ran the rake setup script. When I run script/backgroundrb from my rails app main directory, I get

I''m a bit surprised I can''t find anything about this in the mailing list archives. Basically since Mongrel 1.0.1 I''ve had Mongrels fall asleep without any real cause. A deep sleep, actually more like a coma. The mongrel in question (I''m using a cluster of three) can not be revived. A cluster::stop, then cluster::start is nessesary. A ::restart would not

Forms without explicit enctype are submitted as application/x-www-form- urlencoded. This is the default behaviour in Rails. However, this enctype does not allow transmission of binary data (files). Would it not make sense to specify the enctype multipart/form-data by default instead? i.e. all the form_for helpers would add this enctype to the form tag, unless overriden by the developer. This

I''m using backgroundrb in a rails project, with packet and chronic unpacked in the vendor folder, to make backgroundrb I''ve added the following line to scribts/backgroundrb $LOAD_PATH << File.join(RAILS_HOME, "vendor") Do you believe it''s a good idea? I don''t like depend on the installed gems ciao ciao paolo -------------- next part

Hi, I''ve got a Rails 2.2.2 app and I''m trying to get BackgrounDRb running. I''m just following the simple example in Advanced Rails Recipes. I installed BackgrounDRb from Git, installed the packet and chronic gems, ran ''rake backgroundrb:setup'', generated a worker, and then tried to run ''script/backgroundrb start'' but I get:

People, I''m trying to run autotest on rails 2.3 I get a NoMethodError. Here is what I see: Sat Mar 21 20:47 /b/tmp/myfc23 maco$ Sat Mar 21 20:47 /b/tmp/myfc23 maco$ autotest loading autotest/rails_rspec ./vendor/plugins/rspec/lib/autotest/rspec.rb:24:in `initialize'': undefined method `failed_results_re='' for #<Autotest::RailsRspec:0x1205b88> (NoMethodError)

Hi, Would greatly appreciate some help with this. Is the following error caused by an incorrect worker name? You have a nil object when you didn''t expect it! The error occurred while evaluating nil.send_request /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:44:in `ask_worker'' Here''s what I''m doing in my rails console.

When I run rake test:units I get this error: 292 tests, 350 assertions, 2 failures, 13 errors rake aborted! Command failed with status (1): [/usr/local/bin/ruby -I"lib:test" "/ usr/loc...] This error just showed up yesterday --- I have no idea how I caused it. Here is my gem list in case that helps: actionmailer (2.3.2, 2.2.2) actionpack (2.3.2, 2.2.2) activerecord (2.3.2, 2.2.2)

Hi, I have successfully crossed all the hurdles to install Ruby on rails on a redhat 5 Linux based system. But the last and the biggest hurdle i am facing at this moment is installing backgrounrb :( I followed all the steps from the http://backgroundrb.rubyforge.org/ 1. sudo gem install chronic packet 2. script/plugin install svn://rubyforge.org/var/svn/backgroundrb [IMP:::: I had to drop

Hi, I''ve on hostmonster.com and i''ve run into a small problem that I just can''t get. When I push my application into my hosting environment and try to run rake db:migrate, I get an error message from rake telling me to install the missing gem my environment.rb file has: config.gem "formtastic" config.gem "authlogic" So I installed them but I still

People, I''m getting an error from Rake I''d like to debug. Here is a screendump: Fri Mar 20 23:28 /b/tmp/myfc23 maco$ rake doc:plugins:rspec (in /b/tmp/myfc23) rdoc -o doc/plugins/rspec --title ''Rspec Plugin Documentation'' --line- numbers --inline-source --charset utf-8 -T html vendor/plugins/rspec/ lib/autotest/discover.rb major-snip 95% [107/112]

Short update: It seems that the workers go into some state in which they do not have a correct Rails environment (or db connection). When they enter this state it goes wrong all the time :( Joost Hietbrink (YelloYello) wrote: > Hi all, > > We''re experiencing some problems with Backgroundrb. > > Why is "# master_reactor_instance.result_hash = {}" commented in

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

XXXXXXXXXX:~/.coupa-1.5#gem list *** LOCAL GEMS *** actionmailer (2.3.8) actionpack (2.3.8) activerecord (2.3.8) activeresource (2.3.8) activesupport (2.3.8) acts_as_ferret (0.4.1) daemons (1.0.10) gem_plugin (0.2.3) gemsonrails (0.7.2) minitest (1.6.0) mongrel (1.2.0.pre2) mysql (2.8.1) rack (1.1.0) rails (2.3.8) rake (0.8.7) rdoc (2.5.8) rtf (0.1.0) rubygems-update (1.3.7) rvm (0.1.45)

I had posted a thread couple of weeks ago whereby mongrel just mysteriously stops interacting with my application after an idle period...usually less than 8 hours. http://rubyforge.org/pipermail/mongrel-users/2007-February/002908.html I had hoped this would go away after a few upgrades but to know avail. Interestingly, the process does not die...it still accepts HTTP requests but does not

I am using ubuntu 10.04.1 ............. I want to run my coupa application all required gems FOR COUPA-1.5 are 1. gem install rails –v 1.2.3 ------------------------------ But i have installed gem install rails (2.3.8) 2. gem install ferret –v 0.11.4 ------------------------------ But i have installed gem install sdsykes-ferret (0.11.6.19) 3. gem install -y -v 0.4.1 acts_as_ferret 4. gem

I lost my "connection lost" error.. but now I''ve got a "Mysql::Error: MySQL server has gone away" error.. It comes from: /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.6/lib/active_record/connection_adapters/abstract_adapter.rb:128:in ''log''. I''m not sure if Rails / BackgroundRb uses it .. but i''ve got the mysql (2.7) gem

Hi all, Using the Chronic.parse method, I see some weird behavior. Perhaps someone can set me straight or confirm that it is indeed weird. Note that the date changes to one day earlier in the last example below. Since the date and time are uniquely specified using the hh:mm:ss notation -- though in the future -- I would expect the same result as when I specify the time as in