Mongrel_rails restart not working

Hi,

On os x.3.9, with ruby 1.8.4 installed through darwinports and mongrel
through gems,
everything works until I restart:
mongrel_rails restart
adds the logs:
** USR2 signal received.
** Restarting with arguments: ruby
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails
start -p 3001 -d
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:134:
in exec': Operation not supported - ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails start -p 3001 -d (Errno::EOPNOTSUPP) from /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:134: inrun’
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/lib/mongrel/
command.rb:211:in `run’
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:227
from /opt/local/bin/mongrel_rails:18

What does Errno::EOPNOTSUPP mean ?

On Wed, 2006-06-21 at 02:42 +0200, Jean-Christophe M. wrote:

Hi,

On os x.3.9, with ruby 1.8.4 installed through darwinports and mongrel
through gems,
everything works until I restart:
mongrel_rails restart
adds the logs:
** USR2 signal received.
** Restarting with arguments: ruby

What does Errno::EOPNOTSUPP mean ?

Odd, you’re the second person who’s had this happen, but nobody else
complains. Are you running it with sudo? That seemed to be the
deciding factor on it.


Zed A. Shaw


http://mongrel.rubyforge.org/

Hi Zed,

Le 21 juin 06, à 03:16, Zed S. a écrit :

Odd, you’re the second person who’s had this happen, but nobody else
complains. Are you running it with sudo? That seemed to be the
deciding factor on it.

no, but I didn’t think it was necessary since I started mongrel as user.
Works well with debian, the error must be linked to the way (or
versions) installed with darwinports.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs