similar to: (OS X) Address binding still exists after terminating session

Displaying 20 results from an estimated 10000 matches similar to: "(OS X) Address binding still exists after terminating session"

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
2006 Jun 22
5
changing user/group on port 80
I''m trying to run mongrel on port 80 and switch to a different user/group from root. As root, this works: mongrel_rails 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
2006 Sep 03
4
Mongrel 0.3.13.4 Pre-Release -- Docs and more Docs
Hi Everyone, Just want to get out another ping on the Mongrel pre-release saga. I''ve updated a bunch of the documentation to include documents people have donated and to beef up the FAQ for most of the questions people have asked over the past month. INSTALL gem install mongrel --source=http://mongrel.rubyforge.org/releases/ CHANGES * Fixed memory leak by switching to Sync rather
2006 Aug 29
13
restart - `exec'': Operation not supported
I''m using the latest Mongrel (0.3.13.4) and restarting causes Mongrel to die. From mongrel.log: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails start -C config/mongrel.yml /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:in `exec'': Operation not supported - ruby
2006 Aug 14
4
Mongrel 0.3.13.4 -- PIDs Work, Win32 Gem
Alright, this time a small announce going out to *just* the mongrel list so I can get some early testing. There''s a new pre-release of 0.3.13.4 out that includes the win32 version of the gem. ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** ***** BUT NOT ON PRODUCTION SYSTEMS. ****** As usual, you install it with: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/
2007 Dec 11
2
Mongrel not starting: `initialize_without_backlog'': Cannot assign requested address - bind(2) (Errno::EADDRNOTAVAIL)
Hi I have a rather strange problem with mongrel and I would be grateful if anyone could assist me with resolving. 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:
2006 Jul 15
6
Mongrel 0.3.13.4 Pre-Release -- All Fixed Up Now
Hello Everyone, This is a short announce to get people to try the 0.3.13.4 pre-release with their applications. This release features a few things that folks have asked for, and a backport of an enhancement from the 0.4 release coming later. The features are: 1) A new --prefix command line option for people who want to mount their rails app at a different base URI. Thanks to Scott for the
2006 Sep 18
2
Random(?) action hanging
Is this the behavior that supposedly indicates a problem with a particular action? Mongrel in development mode randomly hangs on random actions. Further requests cause USR1 logs like: Mon Sep 18 13:04:03 PDT 2006: 0 threads sync_waiting for /, 2 still active in mongrel. Mon Sep 18 13:07:52 PDT 2006: 1 threads sync_waiting for /public/stylesheets/table.css, 3 still active in mongrel. Mon Sep 18
2006 Sep 03
10
Documentation Day!
I''m spending today writing documentation. I''ll be updating quite a few documents, doing some edits, and adding some user contributed docs. If anyone has documentation suggestions, FAQ questions they''d like included, or things they think are old and stale, then let me know. Swing by the Lingr room: http://www.lingr.com/room/3yXhqKbfPy8 And drop me a line if you want
2006 Oct 18
4
Segmentation bug - file_column?
Hi there everybody, We''re having mongrel processes slowly die on us, with a segmentation fault. I''ve seen a few other people mention similar issues. Any info or suggestions would be nice: Error: /var/www/apps/heritage/current/config/../vendor/plugins/file_column/ lib/magick_file_column.rb:7: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i386-linux] Server:
2006 Aug 12
2
Mongrel 0.3.13.4 headers seem a bit broken...
I''m running a Rails (r4720) app on OS X 10.4.6. Mongrel 0.3.13.3 works perfectly for me. Mongrel 0.3.13.4, not so much. Redirects don''t work, for one thing. This rails code : redirect_to :action => ''login'' correctly redirects me on 0.3.13.3. Here''s the header I get back : HTTP/1.1 302 Moved Temporarily Content-Length: 93 Connection: close
2006 Jul 10
4
Test Mongrel 0.3.13.4 Please
Hey Folks, There''s a nasty little bug in 0.3.13.3 when running in development mode which could cause all sorts of problems. Please grab the pre-release of 0.3.13.4 and tell me if it works for you: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Thanks! -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need
2006 Sep 21
2
proxying and mongrel 0.3.13.4
I have been running a proxied mongrel-hosted app behind apache 2.0 (don''t need clustering) for several months, and loving it. In that instance, I am proxying the root of the virtual host to mongrel. I am now in a situation where I need to proxy a directory name to mongrel for a new application, and not having any success. I saw Zed''s mention of the --prefix option in 0.3.13.4,
2006 Sep 18
11
Finally! Mongrel 0.3.13.4 Official (for Unix)
Hello! Today I''m announcing a "soft but official" release of Mongrel 0.3.13.4 for the Unix fans in the crowd. It''s been running stable for quite some time now for many people, and should be great for nearly everyone. You can read the announce at: http://mongrel.rubyforge.org/ This release includes new versions of mongrel_upload_progress and mongrel_cluster.
2008 May 30
3
Mongrel error since updating to OSX 10.5.3
Howdy, I''m getting an error message when trying to run one 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
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
2006 Sep 13
7
Mongrel spewing backtraces and nanosleeping
Hi list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel
2007 Jan 03
12
Frustrating Error
I am followint this article, http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-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
2008 Nov 11
1
Problem Starting Mongrel
Hi, I am newbie started learning ruby on rails i had an application which used to run pretty well latter i upgraded from webbrick to mongrel 1.1.5 then I am getting the foloowing errors and a default application runs on port 3000 i have attached its screen shot as an attachement and error which i get in terminal below => Booting Mongrel (use ''script/server webrick'' to force
2006 Apr 21
10
"Client closed socket" spewage
Hi all, Ruby 1.8.4 Rails 1.1.2 Mongrel 0.3.12 I''m seeing this output from the Mongrel server: Client closed socket requesting file C:/eclipse/workspace/dslscheduler/public/javascripts/prototype.js: Invalid argument It seems to be harmless, but I''m curious as to what''s causing it. Any ideas? Thanks, Dan