Hi , If you are following commits, I have pushed following changes: 1. Now, you can specify :environment option in config file to load production environment and stuff. 2. Exeptions that were exposed to the user has been changed to BdrbConnError if rails is not able to connect to bdrb server. 3. loading mechanism has been changed, so remove backgroundrb script from your backgroundrb directory and do a rake backgroundrb:setup and you should be good to go. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org
hemant kumar wrote:> 3. loading mechanism has been changed, so remove backgroundrb script > from your backgroundrb directory and do a rake backgroundrb:setup and > you should be good to go. >Probably the new loading mechanism is causing this error after update: /var/apps/ror_trunk/vendor/plugins/backgroundrb/server/master_worker.rb:114:in `initialize'': uninitialized constant MasterProxy::YAML (NameError) from script/backgroundrb:22:in `new'' from script/backgroundrb:22 requiring Yaml causes it to fail on ERB, then Packet.
On Thu, 2007-12-13 at 18:55 +0300, Ivan Manida wrote:> hemant kumar wrote: > > 3. loading mechanism has been changed, so remove backgroundrb script > > from your backgroundrb directory and do a rake backgroundrb:setup and > > you should be good to go. > > > > Probably the new loading mechanism is causing this error after update: > > /var/apps/ror_trunk/vendor/plugins/backgroundrb/server/master_worker.rb:114:in > `initialize'': uninitialized constant MasterProxy::YAML (NameError) > from script/backgroundrb:22:in `new'' > from script/backgroundrb:22 > > requiring Yaml causes it to fail on ERB, then Packet.Probably, You have slightly old code. Do a svn up now and remove backgroundrb script from script directory and do a "rake backgroundrb:setup" ( this is important and should be always done , when you update your plugin ) -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org
hemant kumar wrote:> Probably, You have slightly old code. Do a svn up now and remove > backgroundrb script from script directory and do a "rake > backgroundrb:setup" ( this is important and should be always done , when > you update your plugin ) > >Hemant, Yes, I did that, and sources were recent - just got another file updated few minutes ago, which fixed that problem, but now mongrels won''t start: ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with production environment... /usr/local/lib/ruby/gems/1.8/gems/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:266:in `load_missing_constant'': uninitialized constant BackgrounDRb (NameError) from /usr/local/lib/ruby/gems/1.8/gems/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:452:in `const_missing'' from /usr/local/lib/ruby/gems/1.8/gems/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:464:in `const_missing'' from /var/apps/ror_trunk/vendor/plugins/backgroundrb/lib/bdrb_conn_error.rb:1 <.. standard mongrel log cut ..> Is there some other configuration step that''s needed now?
On Thu, 2007-12-13 at 19:37 +0300, Ivan Manida wrote:> hemant kumar wrote: > > Probably, You have slightly old code. Do a svn up now and remove > > backgroundrb script from script directory and do a "rake > > backgroundrb:setup" ( this is important and should be always done , when > > you update your plugin ) > > > > > > Hemant, > > Yes, I did that, and sources were recent - just got another file updated > few minutes ago, which fixed that problem, but now mongrels won''t start: > > ** Starting Mongrel listening at 0.0.0.0:3000 > ** Starting Rails with production environment... > /usr/local/lib/ruby/gems/1.8/gems/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:266:in > `load_missing_constant'': uninitialized constant BackgrounDRb (NameError) > from > /usr/local/lib/ruby/gems/1.8/gems/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:452:in > `const_missing'' > from > /usr/local/lib/ruby/gems/1.8/gems/gems/activesupport-1.4.4/lib/active_support/dependencies.rb:464:in > `const_missing'' > from > /var/apps/ror_trunk/vendor/plugins/backgroundrb/lib/bdrb_conn_error.rb:1 > <.. standard mongrel log cut ..> > > Is there some other configuration step that''s needed now?No no, there was a problem with code base. Fixed now. update your code please. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org