Rue Turner
2008-Mar-04 10:32 UTC
[Backgroundrb-devel] failing on start (Errno::EADDRINUSE)
(first post - be gentle with me)
Just when I thought it was going well ;)
I''m getting the following on `ruby script/backgroundrb start`. The box
is fairly freshly built and has a pretty small gem list (also below)
It''s also freshly booted and there aren''t any spurious
dead/zombie
processes running.
here''s the output:
/.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in
`initialize'': Address already in use - bind(2) (Errno::EADDRINUSE)
from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in
`new''
from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in
`start_server''
from /.../vendor/plugins/backgroundrb/server/master_worker.rb:166:in
`initialize''
from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:18:in
`run''
from /.../vendor/plugins/backgroundrb/server/master_worker.rb:163:in
`initialize''
from script/backgroundrb:41:in `new''
from script/backgroundrb:41
/.../vendor/plugins/backgroundrb/lib/../framework/packet/nbio.rb:23:in
`read_data'': Packet::DisconnectError (Packet::DisconnectError)
from /.../vendor/plugins/backgroundrb/framework/packet/worker.rb:47:in
`handle_internal_messages''
from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:158:in
`start_reactor''
from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:156:in
`each''
from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:156:in
`start_reactor''
from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:147:in
`loop''
from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:147:in
`start_reactor''
from /.../vendor/plugins/backgroundrb/framework/packet/worker.rb:21:in
`start_worker''
from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:139:in
`fork_and_load''
from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:116:in
`start_worker''
from /.../vendor/plugins/backgroundrb/server/master_worker.rb:165:in
`initialize''
from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:18:in
`run''
from /.../vendor/plugins/backgroundrb/server/master_worker.rb:163:in
`initialize''
from script/backgroundrb:41:in `new''
from script/backgroundrb:41
and the config:
---
:backgroundrb:
:port: 11007
:ip: 127.0.0.1
:environment: development
:log: foreground
The same error occurs even on a brand new rails app so I''m thinking it
could be a clashing gem issue?
*** LOCAL GEMS ***
actionmailer (2.0.2)
actionpack (2.0.2)
activerecord (2.0.2)
activeresource (2.0.2)
activesupport (2.0.2)
chronic (0.2.3)
gemsonrails (0.7.2)
graticule (0.2.6)
hoe (1.5.0)
mini_exiftool (0.5.0)
packet (0.1.5)
piston (1.4.0)
railroad (0.4.0)
rails (2.0.2)
rake (0.8.1)
ruby-openid (2.0.4)
rubyforge (0.4.4)
rubygems-update (1.0.1)
slave (1.2.1)
any help appreciated.
#rubyonrails / montyw
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080304/d753815a/attachment-0001.html
Ger Apeldoorn
2008-Mar-04 10:46 UTC
[Backgroundrb-devel] failing on start (Errno::EADDRINUSE)
Hi, Seems like it is: - already running in the background (use "ps -ef | grep ruby" to see if that''s true) - some other process is using that exact port.. (Unlikely) Good luck, Ger Apeldoorn On Tue, 2008-03-04 at 10:32 +0000, Rue Turner wrote:> (first post - be gentle with me) > > > Just when I thought it was going well ;) > > I''m getting the following on `ruby script/backgroundrb start`. The box > is fairly freshly built and has a pretty small gem list (also below) > It''s also freshly booted and there aren''t any spurious dead/zombie > processes running. > > here''s the output: > > /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in > `initialize'': Address already in use - bind(2) (Errno::EADDRINUSE) > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in > `new'' > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in > `start_server'' > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:166:in > `initialize'' > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:18:in `run'' > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:163:in > `initialize'' > from script/backgroundrb:41:in `new'' > from script/backgroundrb:41 > /.../vendor/plugins/backgroundrb/lib/../framework/packet/nbio.rb:23:in > `read_data'': Packet::DisconnectError (Packet::DisconnectError) > > from /.../vendor/plugins/backgroundrb/framework/packet/worker.rb:47:in > `handle_internal_messages'' > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:158:in > `start_reactor'' > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:156:in > `each'' > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:156:in > `start_reactor'' > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:147:in > `loop'' > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:147:in > `start_reactor'' > > from /.../vendor/plugins/backgroundrb/framework/packet/worker.rb:21:in > `start_worker'' > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:139:in `fork_and_load'' > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:116:in `start_worker'' > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:165:in > `initialize'' > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:18:in `run'' > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:163:in > `initialize'' > from script/backgroundrb:41:in `new'' > from script/backgroundrb:41 > > and the config: > > --- > :backgroundrb: > :port: 11007 > :ip: 127.0.0.1 > :environment: development > :log: foreground > > The same error occurs even on a brand new rails app so I''m thinking it > could be a clashing gem issue? > > *** LOCAL GEMS *** > actionmailer (2.0.2) > actionpack (2.0.2) > activerecord (2.0.2) > activeresource (2.0.2) > activesupport (2.0.2) > chronic (0.2.3) > gemsonrails (0.7.2) > graticule (0.2.6) > hoe (1.5.0) > mini_exiftool (0.5.0) > packet (0.1.5) > piston (1.4.0) > railroad (0.4.0) > rails (2.0.2) > rake (0.8.1) > ruby-openid (2.0.4) > rubyforge (0.4.4) > rubygems-update (1.0.1) > slave (1.2.1) > > > any help appreciated. > > > #rubyonrails / montyw > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel
hemant kumar
2008-Mar-04 11:54 UTC
[Backgroundrb-devel] failing on start (Errno::EADDRINUSE)
On Tue, 2008-03-04 at 11:46 +0100, Ger Apeldoorn wrote:> Hi, > > Seems like it is: > - already running in the background (use "ps -ef | grep ruby" to see if > that''s true) > - some other process is using that exact port.. (Unlikely) >Yes, thats right. Some application is already running on that port ( if not backgroundrb). You can try changing the port.
Rue Turner
2008-Mar-04 12:34 UTC
[Backgroundrb-devel] failing on start (Errno::EADDRINUSE)
*shamed* thanks Ger, you were right with the first one. Not sure how it was still happening after reboot - kubuntu does seem to start processes that you last had running in their last state which is useful for general play but worth taking care when you need a ''fresh'' environment. On Tue, 2008-03-04 at 11:46 +0100, Ger Apeldoorn wrote:> Hi, > > Seems like it is: > - already running in the background (use "ps -ef | grep ruby" to see if > that''s true) > - some other process is using that exact port.. (Unlikely) > > Good luck, > Ger Apeldoorn > > On Tue, 2008-03-04 at 10:32 +0000, Rue Turner wrote: > > (first post - be gentle with me) > > > > > > Just when I thought it was going well ;) > > > > I''m getting the following on `ruby script/backgroundrb start`. The box > > is fairly freshly built and has a pretty small gem list (also below) > > It''s also freshly booted and there aren''t any spurious dead/zombie > > processes running. > > > > here''s the output: > > > > /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in > > `initialize'': Address already in use - bind(2) (Errno::EADDRINUSE) > > > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in > > `new'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:137:in > > `start_server'' > > > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:166:in > > `initialize'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:18:in `run'' > > > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:163:in > > `initialize'' > > from script/backgroundrb:41:in `new'' > > from script/backgroundrb:41 > > /.../vendor/plugins/backgroundrb/lib/../framework/packet/nbio.rb:23:in > > `read_data'': Packet::DisconnectError (Packet::DisconnectError) > > > > from /.../vendor/plugins/backgroundrb/framework/packet/worker.rb:47:in > > `handle_internal_messages'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:158:in > > `start_reactor'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:156:in > > `each'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:156:in > > `start_reactor'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:147:in > > `loop'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/core.rb:147:in > > `start_reactor'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/worker.rb:21:in > > `start_worker'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:139:in `fork_and_load'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:116:in `start_worker'' > > > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:165:in > > `initialize'' > > > > from /.../vendor/plugins/backgroundrb/framework/packet/packet_master.rb:18:in `run'' > > > > from /.../vendor/plugins/backgroundrb/server/master_worker.rb:163:in > > `initialize'' > > from script/backgroundrb:41:in `new'' > > from script/backgroundrb:41 > > > > and the config: > > > > --- > > :backgroundrb: > > :port: 11007 > > :ip: 127.0.0.1 > > :environment: development > > :log: foreground > > > > The same error occurs even on a brand new rails app so I''m thinking it > > could be a clashing gem issue? > > > > *** LOCAL GEMS *** > > actionmailer (2.0.2) > > actionpack (2.0.2) > > activerecord (2.0.2) > > activeresource (2.0.2) > > activesupport (2.0.2) > > chronic (0.2.3) > > gemsonrails (0.7.2) > > graticule (0.2.6) > > hoe (1.5.0) > > mini_exiftool (0.5.0) > > packet (0.1.5) > > piston (1.4.0) > > railroad (0.4.0) > > rails (2.0.2) > > rake (0.8.1) > > ruby-openid (2.0.4) > > rubyforge (0.4.4) > > rubygems-update (1.0.1) > > slave (1.2.1) > > > > > > any help appreciated. > > > > > > #rubyonrails / montyw > > _______________________________________________ > > Backgroundrb-devel mailing list > > Backgroundrb-devel at rubyforge.org > > http://rubyforge.org/mailman/listinfo/backgroundrb-devel-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080304/d8d50ab5/attachment.html