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
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails
start -C config/mongrel.yml (Errno::EOPNOTSUPP)
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:in
`run''
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/command.rb:203:in
`run''
from
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:231
from /opt/local/bin/mongrel_rails:18
I tried ''ruby
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails
start -C config/mongrel.yml'' from the commandline and
it started up Mongrel.
Joe
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Jason A. Hoffman
2006-Aug-29 00:28 UTC
[Mongrel] restart - `exec'': Operation not supported
On Aug 28, 2006, at 5:15 PM, Joe Ruby wrote:> 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 > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails > start -C config/mongrel.yml (Errno::EOPNOTSUPP) > from > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ > mongrel_rails:142:in > `run'' > from > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ > command.rb:203:in > `run'' > from > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ > mongrel_rails:231 > from /opt/local/bin/mongrel_rails:18 > > I tried ''ruby > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails > start -C config/mongrel.yml'' from the commandline and > it started up Mongrel. > > JoeWhat operating system is this? And did it install properly? /opt/ local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails isn''t where it should be, from that I''d think it would be at /opt/local/bin/ mongrel_rails? - Jason
It''s OS 10.4.7. I installed using ''sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/'' (and, yes, it did appear to install properly). Yep, there''s also a mongrel_rails in /opt/local/bin -- its size is 490, the other is 7960. Both have timestamps of Aug 28 15:24. Should I delete one of them? Joe --- What operating system is this? And did it install properly? /opt/ local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails isn''t where it should be, from that I''d think it would be at /opt/local/bin/ mongrel_rails? - Jason --- Joe Ruby <joeat303 at yahoo.com> wrote:> 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 >/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails> start -C config/mongrel.yml (Errno::EOPNOTSUPP) > from >/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:in> `run'' > from >/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/command.rb:203:in> `run'' > from >/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:231> from /opt/local/bin/mongrel_rails:18 > > I tried ''ruby >/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails> start -C config/mongrel.yml'' from the commandline > and > it started up Mongrel. > > Joe > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com >__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Jason A. Hoffman
2006-Aug-29 00:45 UTC
[Mongrel] restart - `exec'': Operation not supported
Try the command Jason-17% which mongrel_rails /usr/local/bin/mongrel_rails And then just cd into the rails application directory and try mongrel_rails to see what happens (rather than using the full path to the build directory). - Jason On Aug 28, 2006, at 5:40 PM, Joe Ruby wrote:> > It''s OS 10.4.7. I installed using ''sudo gem install > mongrel > --source=http://mongrel.rubyforge.org/releases/'' (and, > yes, it did appear to install properly). Yep, there''s > also a mongrel_rails in /opt/local/bin -- its size is > 490, the other is 7960. Both have timestamps of Aug 28 > 15:24. Should I delete one of them? > > Joe > > --- > What operating system is this? And did it install > properly? /opt/ > local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails > isn''t > where it should be, from that I''d think it would be at > /opt/local/bin/ > mongrel_rails? > > - Jason > > --- Joe Ruby <joeat303 at yahoo.com> wrote: > >> 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 >> > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails >> start -C config/mongrel.yml (Errno::EOPNOTSUPP) >> from >> > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ > mongrel_rails:142:in >> `run'' >> from >> > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ > command.rb:203:in >> `run'' >> from >> > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ > mongrel_rails:231 >> from /opt/local/bin/mongrel_rails:18 >> >> I tried ''ruby >> > /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails >> start -C config/mongrel.yml'' from the commandline >> and >> it started up Mongrel. >> >> Joe >> >> __________________________________________________ >> Do You Yahoo!? >> Tired of spam? Yahoo! Mail has the best spam >> protection around >> http://mail.yahoo.com >> >> __________________________________________________ >> Do You Yahoo!? >> Tired of spam? Yahoo! Mail has the best spam >> protection around >> http://mail.yahoo.com >> > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
Here''s what I get: ~/rails $ which mongrel_rails /opt/local/bin/mongrel_rails ~/rails $ cd /opt/local/bin/ /opt/local/bin $ ./mongrel_rails Usage: mongrel_rails <command> [options] Available commands are: - cluster::configure - cluster::restart - cluster::start - cluster::stop - restart - start - stop Each command takes -h as an option to get help. I have been using just ''mongrel_rails'' (with no path) in my Rails root dir. It starts and stops fine, just not restart. Joe --- Try the command Jason-17% which mongrel_rails /usr/local/bin/mongrel_rails And then just cd into the rails application directory and try mongrel_rails to see what happens (rather than using the full path to the build directory). - Jason __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Jason A. Hoffman
2006-Aug-29 01:00 UTC
[Mongrel] restart - `exec'': Operation not supported
On Aug 28, 2006, at 5:52 PM, Joe Ruby wrote:> Here''s what I get: > > ~/rails $ which mongrel_rails > /opt/local/bin/mongrel_rails > > ~/rails $ cd /opt/local/bin/ > > Each command takes -h as an option to get help. > > I have been using just ''mongrel_rails'' (with no path) > in my Rails root dir. It starts and stops fine, just > not restart. > > JoeAre you doing something like I move into a rails app Jason-17% cd jasonrailsapp Jason-17% ls README components doc public tmp Rakefile config lib script vendor app db log test I start it Jason-17% mongrel_rails start -d Restarts fine Jason-17% mongrel_rails restart Sending USR2 to Mongrel at PID 305...Done. I stop it Jason-17% mongrel_rails stop Sending TERM to Mongrel at PID 308...Done. I become root Jason-17% sudo -s I start the process as root Jason-17:~/Desktop/jasonrailsapp root# mongrel_rails start -d Jason-17:~/Desktop/jasonrailsapp root# exit exit I become a normal user and I try to restart and get an operation not permitted. Jason-17% mongrel_rails restart /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails: 154:in `kill'': Operation not permitted (Errno::EPERM) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:154:in `send_signal'' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:226:in `run'' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ mongrel/command.rb:199:in `run'' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 Is this being entirely run as you? Try doing a sudo mongrel_rails restart And see if that works for you. - Jason
On Mon, 2006-08-28 at 17:15 -0700, Joe Ruby wrote:> 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.ymlWell, I''d need to know what''s in mongrel.yml, but my first guess is that you''re starting with --user/--group, which could cause problems with permissions. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
Nope, I''m not sudo''ing -- I''m always logged in as the
same user. I am starting MOngrel with ''mongrel_rails
-C config.mongrel.yml''. I tried ''sudo mongrel_rails
restart'' and got the same error as before (in my first
email).
Joe
---
Are you doing something like
I move into a rails app
Jason-17% cd jasonrailsapp
Jason-17% ls
README components doc public
tmp
Rakefile config lib script
vendor
app db log test
I start it
Jason-17% mongrel_rails start -d
Restarts fine
Jason-17% mongrel_rails restart
Sending USR2 to Mongrel at PID 305...Done.
I stop it
Jason-17% mongrel_rails stop
Sending TERM to Mongrel at PID 308...Done.
I become root
Jason-17% sudo -s
I start the process as root
Jason-17:~/Desktop/jasonrailsapp root# mongrel_rails
start -d
Jason-17:~/Desktop/jasonrailsapp root# exit
exit
I become a normal user and I try to restart and get an
operation not
permitted.
Jason-17% mongrel_rails restart
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:
154:in `kill'': Operation not permitted (Errno::EPERM)
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/
mongrel_rails:154:in `send_signal''
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/
mongrel_rails:226:in `run''
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/
mongrel/command.rb:199:in `run''
from
/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/
mongrel_rails:235
from /usr/local/bin/mongrel_rails:18
Is this being entirely run as you? Try doing a
sudo mongrel_rails restart
And see if that works for you.
- Jason
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Here''s my config/mongrel.yml: --- :port: 3000 :debug: false :daemon: true - mongrel :log_file: log/mongrel.log :environment: development I''m starting with ''mongrel_rails -C config/mongrel.yml'' in the root of my Rails app. Joe --- Well, I''d need to know what''s in mongrel.yml, but my first guess is that you''re starting with --user/--group, which could cause problems with permissions. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Jason A. Hoffman
2006-Aug-29 02:44 UTC
[Mongrel] restart - `exec'': Operation not supported
On Aug 28, 2006, at 7:37 PM, Joe Ruby wrote:> Nope, I''m not sudo''ing -- I''m always logged in as the > same user.Yes but trying sudo''ing it. - Jason
On Mon, 2006-08-28 at 19:39 -0700, Joe Ruby wrote:> Here''s my config/mongrel.yml: > > --- > :port: 3000 > :debug: false > :daemon: true > - mongrel > :log_file: log/mongrel.log > :environment: development > > I''m starting with ''mongrel_rails -C > config/mongrel.yml'' in the root of my Rails app. >Hmm, I don''t have a mac to test this on, but I can''t see any reason that would fail like that. Maybe try without the -C with: mongrel_rails start -d (All the stuff you''ve got in the .yml are defaults anyway except -d daemon). -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
Hi Zed,
I can attest that on OS X (PPC at least) both 0.13.3.1 and 0.13.3.4
pre-release (downloaded tonight) exhibit this behavior:
** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mon
3.13.4/bin/mongrel_rails start
/opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:
c'': Operation not supported - ruby
/opt/local/lib/ruby/gems/1.8/gems/mong
.13.4/bin/mongrel_rails start (Errno::EOPNOTSUPP)
from /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongr
s:142:in `run''
from /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongr
and.rb:203:in `run''
from /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongr
s:231
When USR2 sent to mongrel in development mode. I''m running
development mode, no cluster, no config, not even in with -d (tried
both, made no difference). I''ll do testing on Intel in the morning
and see if I can''t track things down a little more.
Cheers,
Rob Kaufman
On 8/28/06, Zed Shaw <zedshaw at zedshaw.com>
wrote:> On Mon, 2006-08-28 at 19:39 -0700, Joe Ruby wrote:
> > Here''s my config/mongrel.yml:
> >
> > ---
> > :port: 3000
> > :debug: false
> > :daemon: true
> > - mongrel
> > :log_file: log/mongrel.log
> > :environment: development
> >
> > I''m starting with ''mongrel_rails -C
> > config/mongrel.yml'' in the root of my Rails app.
> >
>
> Hmm, I don''t have a mac to test this on, but I can''t see
any reason that
> would fail like that. Maybe try without the -C with:
>
> mongrel_rails start -d
>
> (All the stuff you''ve got in the .yml are defaults anyway except
-d
> daemon).
>
>
> --
> Zed A. Shaw
> http://www.zedshaw.com/
> http://mongrel.rubyforge.org/
> http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
I just tried that and ''mongrel_rails restart'' results in Mongrel dying with the same error. Joe --- Hmm, I don''t have a mac to test this on, but I can''t see any reason that would fail like that. Maybe try without the -C with: mongrel_rails start -d (All the stuff you''ve got in the .yml are defaults anyway except -d daemon). -- Zed A. Shaw __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
I tried the same steps on Intel based OS X and had the same results (the exception) Rob Kaufman On 8/28/06, Joe Ruby <joeat303 at yahoo.com> wrote:> I just tried that and ''mongrel_rails restart'' results > in Mongrel dying with the same error. > > Joe > > --- > Hmm, I don''t have a mac to test this on, but I can''t > see any reason that > would fail like that. Maybe try without the -C with: > > mongrel_rails start -d > > (All the stuff you''ve got in the .yml are defaults > anyway except -d > daemon). > > > -- > Zed A. Shaw > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >