search for: stopserv

Dear All In an environment , I have 20 centos servers running together . For shutting them down , I need to issue the followings on each of the servers : #./stopServer #init 0 This is cumbersome to try to issue these on huge amount of servers to keep them safely going shutdown. Can you please let me know how can I automate it and say let just one server send stop processes and shutdown commands to the other ones and then goes shutdown himself? Thank you

Thread #<Thread:0xb7ac9dd4 sleep> is too old, killing. Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out thread.> I''m getting lockups I''ve seen this too: Shutdown waited 1 for 9 requests, could take 10 seconds.^MThread #<Thread:0xb7815fa8 sleep> is too old, killing. Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out thread.> /usr/lib/ruby...

...This was working well for a few days, until this weekend it crashed with the following stack trace. It''s running on redhat enterprise linux 4. ruby 1.8.4 (from the mongrel log) Thread #<Thread:0xb795d924 sleep> is too old, killing. Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out thread.> /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel.rb:472:in `lock'' /usr/lib/ruby/1.8/thread.rb:133:in `synchronize'' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel/rails.rb:64:in`process'' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.12....

...top (no restart). ** Rails signals registered. HUP => reload (without restart). It might not work well. ** Mongrel available at 0.0.0.0:4321 ** Writing PID file to /tmp/m.pid ** USR2 signal received. /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:800:in `run'': Mongrel::StopServer (Mongrel::StopServer) from /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' from /opt/local/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' from /opt/local/lib/ruby/gems/1.8/gems/mong...

...and there''s nothing unusual in my rails log. Once I do a "mongrel_rails restart," I get a bunch of the following dumped into the mongrel.log (I assume one for each thread that''s chillin'' at @guard.synchronize)... Error calling Dispatcher.dispatch #<Mongrel::StopServer: Timed out thread.> /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.12.4/lib/mongrel.rb:472:in`lock'' /usr/local/lib/ruby/1.8/thread.rb:133:in `synchronize'' /usr/local/lib/ruby/gems/1.8/gems/mongrel- 0.3.12.4/lib/mongrel/rails.rb:64:in `process'' /usr/local/lib/ruby/gems...

http://bugs.freedesktop.org/show_bug.cgi?id=13257 Summary: using nouveau on NV17 kills the KDE VNC server Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be kill''ed in the middle of the request. (at the bottom of mongrel.rb): http://mongrel.ru...