Displaying 15 results from an estimated 15 matches for "tcphack".
2006 Nov 16
12
OSX requires sudo for using ports < 1024
I assume some of you have run into this error before when trying to run
mongrel on port 80 (or another port < 1024) in OSX:
$ mongrel_rails start -p 80
** Starting Mongrel listening at 0.0.0.0:80
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.14/lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Permission denied - bind(2) (Errno::EACCES)
from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.14/lib/mongrel/tcphack.rb:12:in
`initialize''
from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.14/lib/mongrel.rb:536:in
`initializ...
2007 Dec 11
2
Mongrel not starting: `initialize_without_backlog'': Cannot assign requested address - bind(2) (Errno::EADDRNOTAVAIL)
...solving.
I have an application running mongrel 1.1.1 and rails 1.2.5 with ruby 1.8.6.
It was all working fine and starting as expected. But I did a server reboot
once and mongrel has refused to start up since. I get the following error:
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.1/bin/../lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Cannot assign requested address - bind(2)
(Errno::EADDRNOTAVAIL)
from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.1/bin/../lib/mongrel/tcphack.rb:12:in
`initialize''
from /usr/lib/ruby/1.8/drb/drb.rb:865:in `open''...
2011 May 18
9
Address already in use - bind(2) (Errno::EADDRINUSE)
I made a new rails app and when i started the server ,it gave
following error message.
=> Booting Mongrel
=> Rails 2.3.8 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
/usr/lib/ruby/1.8/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Address already in use - bind(2)
(Errno::EADDRINUSE)
from /usr/lib/ruby/1.8/mongrel/tcphack.rb:12:in `initialize''
from /usr/lib/ruby/1.8/mongrel.rb:93:in `new''
from /usr/lib/ruby/1.8/mongrel.rb:93:in `initialize''
from /v...
2009 Sep 26
2
Config XLSUITE in Windows
...;script/server webrick'' to force WEBrick)
=> Rails 2.2.0 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
Exiting
c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/tcphack.
rb:13:in `listen'': An operation on a socket could not be performed
because the s
ystem lacked sufficient buffer space or because a queue was full. -
listen(2) (E
rrno::ENOBUFS)
from
c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mon
grel/tcphack.rb:13:in `initiali...
2010 Nov 04
11
Address already in use - bind(2) (Errno::EADDRINUSE)
...pt/server"
(using mogrel) I get:
=> Booting Mongrel
=> Rails 2.3.8 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Address already in use - bind(2)
(Errno::EADDRINUSE)
from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize''
from
/System/Library/Frameworks/Ruby.frame...
2008 Nov 11
1
Problem Starting Mongrel
...g Mongrel (use ''script/server webrick'' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
Exiting
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Address already in use - bind(2)
(Errno::EADDRINUSE)
from
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize''
from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:93:in
`new''
from /Libra...
2007 Jan 03
12
Frustrating Error
...apistrano-and-you/
...but I keep getting this error in the log...not sure what to try next...
** Daemonized, any open files are closed. Look at log/mongrel.8000.pid and
log/mongrel.log for info.
** Starting Mongrel listening at 127.0.0.1:8000
/usr/lib/ruby/gems/1.8/gems/mongrel-1.0/lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Address already in use - bind(2)
(Errno::EADDRINUSE)
from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0/lib/mongrel/tcphack.rb:12:in
`initialize''
from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0/lib/mongrel.rb:560:in `new''
from /usr/lib/...
2008 May 30
3
Mongrel error since updating to OSX 10.5.3
...of my rails
apps, which seems to have started after updating to 10.5.3.
mattdaw-2:v1.5_patch mdaw$ mongrel_rails start
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
/usr/local/ruby-patched/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../
lib/mongrel/tcphack.rb:12:in `initialize_without_backlog'':
getaddrinfo: nodename nor servname provided, or not known (SocketError)
from /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/
mongrel-1.1.5/bin/../lib/mongrel/tcphack.rb:12:in `initialize''
from /usr/local/ruby-patched/lib/...
2006 Jun 10
1
mongrel (0.3.12.4) blows up
...TERM => stop. USR2 => restart. INT => stop (no
restart).
** Rails signals registered. HUP => reload (without restart). It
might not work well.
** Running 0.0.0.0:3000 listener.
** Mongrel available at 0.0.0.0:3000
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel/
tcphack.rb:6:in `initialize_without_backlog'': Address already in use
- bind(2) (Errno::EADDR
INUSE)
from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/
mongrel/tcphack.rb:6:in `initialize''
from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/
mongrel....
2008 Nov 11
7
problem starting mongrel server
...g Mongrel (use ''script/server webrick'' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
Exiting
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Address already in use - bind(2)
(Errno::EADDRINUSE)
from
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize''
from /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:93:in
`new''
from /Libra...
2011 Mar 14
7
Rails server not works - yesterday worked fine
...server" is here:
=> Booting Mongrel
=> Rails 3.0.5 application starting in development on
http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Address already in use - bind(2)
(Errno::EADDRINUSE)
from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/tcphack.rb:12:in
`initialize''
from
/System/Library/Frameworks/Ruby.frame...
2006 Jun 22
5
changing user/group on port 80
...ls start -p 3000 -u rails --group rails
This:
mongrel_rails start -p 80 -u rails --group rails
dies with:
---------------------------
** Changing group to rails.
** Changing user to rails.
** Starting Mongrel listening at 0.0.0.0:80
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.1/lib/mongrel/tcphack.rb:24:in
`initialize_without_backlog'': Permission denied - bind(2)
(Errno::EACCES) from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.1/lib/mongrel/tcphack.rb:24:in
`initialize''
from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.1/lib/mongrel.rb:500:in
`initia...
2008 Dec 23
1
server won't start!
...webrick'' to force WEBrick)
=> Rails 2.1.0 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
Exiting
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mon
grel/tcphack.rb:12:in `initialize_without_backlog'': Bad file descriptor
- bind(2
) (Errno::EBADF)
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin
32-60/lib/mongrel/tcphack.rb:12:in `initialize''
from
C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/mongrel-1....
2007 Dec 13
4
Weird Mongrel error: Not starting.
...for one particular
application though I have other applications running on the same server
without any issues. This is the error that I get:
** Starting Mongrel listening at 0.0.0.0:3013
** Starting Rails with development environment...
/usr/lib/ruby/gems/1.8/gems/mongrel- 1.1.1/bin/../lib/mongrel/tcphack.rb:12:in
`initialize_without_backlog'': Cannot assign requested address - bind(2)
(Errno::EADDRNOTAVAIL)
from /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.1/bin/../lib/mongrel/tcphack.rb:12:in
`initialize''
from /usr/lib/ruby/1.8/drb/drb.rb:865:in `open''...
2006 Jul 13
8
(OS X) Address binding still exists after terminating session
...X 10.4.7]
I have a slightly annoying issue under OS X: If i terminate the
session that ran the mongrel process (by closing terminal window --
hey, it happens!), subsequent attempts to start mongrel give me the
following error:
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/
tcphack.rb:12:in `initialize_without_backlog'': Address already in use
- bind(2) (Errno::EADDRINUSE)
I suppose, because mongrel wasn''t stopped properly, the address
binding still exists somewhere. However, since the actual mongrel
process has been killed, i have no idea how to unbin...