# Mongrel\_rails cluster::stop not working **URL:** \ **Category:** Mongrel\ **Created:** [June 12, 2008, 4:58pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-stop-not-working/140285 "2008-06-12T16:58:28Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![aathisankar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4491bb/32.png) [@aathisankar](https://www.ruby-forum.com/u/aathisankar)\ **Post date:** [June 12, 2008, 4:58pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-stop-not-working/140285/1 "2008-06-12T16:58:28Z")
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 ---
**Author:** ![aathisankar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4491bb/32.png) [@aathisankar](https://www.ruby-forum.com/u/aathisankar)\ **Post date:** [June 12, 2008, 5:06pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-stop-not-working/140285/2 "2008-06-12T17:06:38Z")
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: > * * * > > g all, even group leaders! -u by effective user ID (supports > \*\*\*\*\*\*\*\*\* misc options \*\*\*\*\*\*\*\*\* – Jonathan R. Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu ---
**Author:** ![aathisankar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4491bb/32.png) [@aathisankar](https://www.ruby-forum.com/u/aathisankar)\ **Post date:** [June 14, 2008, 9:45am UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-stop-not-working/140285/3 "2008-06-14T09:45:51Z")
Jonathan R. 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. ---
**Author:** ![aathisankar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4491bb/32.png) [@aathisankar](https://www.ruby-forum.com/u/aathisankar)\ **Post date:** [October 23, 2008, 10:54am UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-stop-not-working/140285/4 "2008-10-23T10:54:58Z")
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 removed\_email\_address@domain.invalid ---
**Author:** ![aathisankar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4491bb/32.png) [@aathisankar](https://www.ruby-forum.com/u/aathisankar)\ **Post date:** [January 2, 2009, 11:20pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-stop-not-working/140285/5 "2009-01-02T23:20:54Z")
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 ---
**Author:** ![aathisankar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4491bb/32.png) [@aathisankar](https://www.ruby-forum.com/u/aathisankar)\ **Post date:** [January 12, 2009, 7:25pm UTC](https://www.ruby-forum.com/t/mongrel-rails-cluster-stop-not-working/140285/6 "2009-01-12T19:25:46Z")
> \*\* 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 containing > cache\_template\_loading to make it work. Cheers,