[Backgroundrb-devel] Setting up release-1.0.1
hemant
gethemant at gmail.com
Mon Jan 28 21:15:49 EST 2008
On Tue, Jan 29, 2008 at 5:43 AM, Andre Borrelly <andre at myavalaunch.com> wrote:
>
>
> Hello,
>
> I am unable to get the backgroundrb server to run.
>
> Initially I got:
>
>
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:263:in
> `load_missing_constant': uninitialized constant BackgrounDRb::MasterProxy
> (NameError)
> from
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:453:in
> `const_missing'
> from ./script/backgroundrb:41
>
> Then after doing this:
>
> Index: script/backgroundrb
> ===================================================================
> --- script/backgroundrb (revision 313)
> +++ script/backgroundrb (working copy)
> @@ -6,8 +6,10 @@
> WORKER_ROOT = rails_root + "/lib/workers"
> SERVER_LOGGER = rails_root + "/log/backgroundrb_server.log"
>
> -["server","framework","lib"].each { |x| $LOAD_PATH.unshift(PACKET_APP +
> "/#{x}")}
> -$LOAD_PATH.unshift(WORKER_ROOT)
> +#["server","framework","lib"].each { |x| $LOAD_PATH.unshift(PACKET_APP +
> "/#{x}")}
> +["server","framework","lib"].each { |x| $:.push(PACKET_APP + "/#{x}")}
> +#$LOAD_PATH.unshift(WORKER_ROOT)
> +$:.push(WORKER_ROOT)
>
> require RAILS_HOME + '/config/boot.rb'
> require "active_record"
>
>
> and adding in "environment.rb"
>
> config.load_paths +=
> Dir["#{RAILS_ROOT}/vendor/plugins/backgroundrb/server"]
> config.load_paths +=
> Dir["#{RAILS_ROOT}/vendor/plugins/backgroundrb/framework"]
>
> I get this:
>
>
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:249:in
> `load_missing_constant': Expected
> RAILS_HOME/vendor/plugins/backgroundrb/server/master_worker.rb to define
> MasterWorker (LoadError)
> from
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:453:in
> `const_missing'
> from
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:465:in
> `const_missing'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:96:in
> `const_get'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:96:in
> `load_workers'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:93:in
> `each'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:93:in
> `load_workers'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:19:in
> `run'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/server/master_worker.rb:163:in
> `initialize'
> from ./script/backgroundrb:62:in `new'
> from ./script/backgroundrb:62
> RAILS_HOME/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:23:in
> `read_data': Packet::DisconnectError (Packet::DisconnectError)
> from RAILS_HOME/vendor/plugins/backgroundrb/framework/worker.rb:47:in
> `handle_internal_messages'
> from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:158:in
> `start_reactor'
> from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:156:in
> `each'
> from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:156:in
> `start_reactor'
> from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:147:in
> `loop'
> from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:147:in
> `start_reactor'
> from RAILS_HOME/vendor/plugins/backgroundrb/framework/worker.rb:21:in
> `start_worker'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:134:in
> `fork_and_load'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:115:in
> `start_worker'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/server/master_worker.rb:165:in
> `initialize'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:18:in
> `run'
> from
> RAILS_HOME/vendor/plugins/backgroundrb/server/master_worker.rb:163:in
> `initialize'
> from ./script/backgroundrb:62:in `new'
> from ./script/backgroundrb:62
>
Did you actually delete your old, script/backgroundrb file and ran
rake backgroundrb:setup
Often you get start problems with new releases, because your plugin is
upgraded, but start/stop script is not.
Which OS you are on?
More information about the Backgroundrb-devel
mailing list