thr3ads.net - Mongrel users - [Mongrel] mongrel_rails cluster::stop not working [Jun 2008]

If this information is useful, please help other people find it:
Share via:

Sankar Ganesh

2008-Jun-12 14:58 UTC

[Mongrel] mongrel_rails cluster::stop not working

Hi

am a newbie to mongrel. am using mongrel cluster in my ruby application.

When i start mongrel cluster it is working fine and when i stop it it
says already stopped port 8000.

it is giving the error as  follows

********* simple selection *********  ********* selection by list
*********
-A all processes                      -C by command name
-N negate selection                   -G by real group ID (supports
names)
-a all w/ tty except session leaders  -U by real user ID (supports
names)
-d all except session leaders         -g by session leader OR by group
name
-e all processes                      -p by process ID
T  all processes on this terminal     -s processes in the sessions given
a  all w/ tty, including other users  -t by tty
g  all, even group leaders!           -u by effective user ID (supports
names)
r  only running processes             U  processes for specified users
x  processes w/o controlling ttys     t  by tty
*********** output format **********  *********** long options
***********
-o,o user-defined  -f full            --Group --User --pid --cols
-j,j job control   s  signal          --group --user --sid --rows
-O,O preloaded -o  v  virtual memory  --cumulative --format --deselect
-l,l long          u  user-oriented   --sort --tty --forest --version
                   X  registers       --heading --no-heading
                    ********* misc options *********
-V,V show version       L  list format codes  f  ASCII art forest
-m,m show threads       S  children in sum    -y change -l format
-n,N set namelist file  c  true command name  n  numeric WCHAN,UID
-w,w wide output        e  show environment   -H process heirarchy
already stopped port 8001


it is not taking the process ids from the pid file.

Please help me to solve this problem
-- 
Posted via http://www.ruby-forum.com/.

Jonathan Rochkind

2008-Jun-12 15:05 UTC

head link

[Mongrel] mongrel_rails cluster::stop not working

When "mongrel_rails cluster::start" is run but does NOT actually 
succesfully start up your mongrels, it doesn''t neccesarily give you any
error messages. Is what I have noticed. I have had cluster::start fail 
but not give me any error messages.

So if cluster::stop is telling you "already stopped", I think that
means
that you never succesfully started it in the first place, you just 
didn''t realize it.

So now the real question is, Why didn''t it succesfully start in the 
first place, and how do you figure that out?  That''s the trick,
I''m not
sure.

Jonathan

Sankar Ganesh wrote:> Hi
>
> am a newbie to mongrel. am using mongrel cluster in my ruby application.
>
> When i start mongrel cluster it is working fine and when i stop it it
> says already stopped port 8000.
>
> it is giving the error as  follows
>
> ********* simple selection *********  ********* selection by list
> *********
> -A all processes                      -C by command name
> -N negate selection                   -G by real group ID (supports
> names)
> -a all w/ tty except session leaders  -U by real user ID (supports
> names)
> -d all except session leaders         -g by session leader OR by group
> name
> -e all processes                      -p by process ID
> T  all processes on this terminal     -s processes in the sessions given
> a  all w/ tty, including other users  -t by tty
> g  all, even group leaders!           -u by effective user ID (supports
> names)
> r  only running processes             U  processes for specified users
> x  processes w/o controlling ttys     t  by tty
> *********** output format **********  *********** long options
> ***********
> -o,o user-defined  -f full            --Group --User --pid --cols
> -j,j job control   s  signal          --group --user --sid --rows
> -O,O preloaded -o  v  virtual memory  --cumulative --format --deselect
> -l,l long          u  user-oriented   --sort --tty --forest --version
>                    X  registers       --heading --no-heading
>                     ********* misc options *********
> -V,V show version       L  list format codes  f  ASCII art forest
> -m,m show threads       S  children in sum    -y change -l format
> -n,N set namelist file  c  true command name  n  numeric WCHAN,UID
> -w,w wide output        e  show environment   -H process heirarchy
> already stopped port 8001
>
>
> it is not taking the process ids from the pid file.
>
> Please help me to solve this problem
>   
-- 
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886 
rochkind (at) jhu.edu

Sankar Ganesh

2008-Jun-14 07:45 UTC

head link

[Mongrel] mongrel_rails cluster::stop not working

Jonathan Rochkind wrote:> When "mongrel_rails cluster::start" is run but does NOT actually
> succesfully start up your mongrels, it doesn''t neccesarily give
you any
> error messages. Is what I have noticed. I have had cluster::start fail
> but not give me any error messages.
> 
> So if cluster::stop is telling you "already stopped", I think
that means
> that you never succesfully started it in the first place, you just
> didn''t realize it.
> 
> So now the real question is, Why didn''t it succesfully start in
the
> first place, and how do you figure that out?  That''s the trick,
I''m not
> sure.
> 
> Jonathan

how to find out the errors?

but it is not showing any error when it is starting.
-- 
Posted via http://www.ruby-forum.com/.

T.ragahvendra Shet

2008-Oct-23 08:54 UTC

head link

[Mongrel] mongrel_rails cluster::stop not working

Mongrel clusters are processes running with determined PID''s , so if
the
server cluster is running the pid is available, you can check this using 
the grep method, for mongrel or else use the mongrel_rails cluster::stop 
|| mongrel_rails cluster::restart.

still if you face problems may be you must contact zedshaw at zedshaw.com

-- 
Posted via http://www.ruby-forum.com/.

Andi Geheim

2009-Jan-02 22:20 UTC

head link

[Mongrel] mongrel_rails cluster::stop not working

I have the same problem:

andreasP:/var/www/web1/bla# mongrel_rails cluster::start
starting port 3000
andreasP:/var/www/web1/bla# mongrel_rails cluster::stop
already stopped port 3000

And no pid file will be created after starting the mongrel.


log_file: log/mongrel.log
port: "3000"
cwd: /var/www/web1/bla
environment: production
pid_file: tmp/pids/mongrel.pid
address: xxx.xxx.xxx.xxx (the server ip)
servers: 1


rails -v
Rails 2.2.2
ruby -v
ruby 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux]



** Daemonized, any open files are closed.  Look at 
tmp/pids/mongrel.3000.pid and log/mongrel.3000.log for info.
** Starting Mongrel listening at xxx.xxx.xxx.xxx:3000
** Starting Rails with production environment...
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:530:in 
`send'': undefined method `cache_template_loading='' for 
ActionView::Base:Class (NoMethodError)
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:530:in 
`initialize_framework_settings''
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:529:in 
`each''
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:529:in 
`initialize_framework_settings''
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:526:in 
`each''
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:526:in 
`initialize_framework_settings''
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:154:in 
`process''
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in 
`send''
  from 
/usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:112:in 
`run''
  from /var/www/web1/aekschen/config/environment.rb:13
  from 
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
`gem_original_require''
  from 
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in 
`require''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:147:in
`rails''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:113:in 
`cloaker_''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:149:in
`call''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:149:in
`listener''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:99:in 
`cloaker_''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:50:in
`call''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:50:in
`initialize''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:84:in 
`new''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:84:in 
`run''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/command.rb:212:in
`run''
  from 
/usr/local/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281
  from /usr/local/bin/mongrel_rails:19:in `load''
  from /usr/local/bin/mongrel_rails:19



I dont know whats wrong!

Greetings Chaos
-- 
Posted via http://www.ruby-forum.com/.

Surendra Singhi

2009-Jan-12 18:13 UTC

head link

[Mongrel] mongrel_rails cluster::stop not working

> ** Daemonized, any open files are closed.  Look at
> tmp/pids/mongrel.3000.pid and log/mongrel.3000.log for info.
> ** Starting Mongrel listening at xxx.xxx.xxx.xxx:3000
> ** Starting Rails with production environment...
> /usr/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:530:in
> `send'': undefined method `cache_template_loading='' for
it seems your project was developed for an earlier version of rails.
>From your rails environment config files you have to remove the line
containingcache_template_loading to make it work.

Cheers,
-- 
Surendra Singhi
http://ssinghi.kreeti.com, http://www.kreeti.com

Apparently Analagous Threads

Search for more possibly parallel threads

Mongrel users - Jun 2008 - mongrel_rails cluster::stop not working

[Mongrel] mongrel_rails cluster::stop not working

[Mongrel] mongrel_rails cluster::stop not working

[Mongrel] mongrel_rails cluster::stop not working

[Mongrel] mongrel_rails cluster::stop not working

[Mongrel] mongrel_rails cluster::stop not working

[Mongrel] mongrel_rails cluster::stop not working

Apparently Analagous Threads