Re: [Mongrel] Mongrel restart script in .sh file is not working
try breaking your script down into multiple lines and not using the operator and then add the back in once you get the script working it looks like there are some spots in the shell script where there should be a break, such as between the 'rm', 'pkill' and the 'cd' On Oct 3, 2012, at 3:48 AM, Dipali Barapatre li...@ruby-forum.com wrote: When I run script to restart mongrel written in .sh file , It is not working properly. Below are the commands written in .sh file. cd /home/apps/stage/bd/log rm mongrel.pid -f pkill -9 mongrel_rails -u bandega cd /home/apps/stage/bd mongrel_rails start -e production -p 4184 -d But when I manually run all above commands one by one on terminal, It is working properly and server is started properly. Is there are some problems while running script in .sh file? Thanks in advance. -- Posted via http://www.ruby-forum.com/. ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
Re: [Mongrel] Mongrel restart script in .sh file is not working
try breaking your script down into multiple lines and not using the operator it looks like there are some spots in the shell script where there should be a break, such as between the 'rm', 'pkill' and the 'cd' On Oct 3, 2012, at 3:48 AM, Dipali Barapatre li...@ruby-forum.com wrote: When I run script to restart mongrel written in .sh file , It is not working properly. Below are the commands written in .sh file. cd /home/apps/stage/bd/log rm mongrel.pid -f pkill -9 mongrel_rails -u bandega cd /home/apps/stage/bd mongrel_rails start -e production -p 4184 -d But when I manually run all above commands one by one on terminal, It is working properly and server is started properly. Is there are some problems while running script in .sh file? Thanks in advance. -- Posted via http://www.ruby-forum.com/. ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
Re: [Mongrel] patched ruby seems to break mongrel?
Also, 1.8.7 is a little shaky right now; I recommend avoiding it. This is off topic, but can your or Luis provide some information, or links, on what makes 1.8.7 shaky or unsuitable for production? thank you very much - jw ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
Re: [Mongrel] best practices for monitoring mongrels with monit?
well, something doesn't seem right: - mongrel_rails_8001' failed protocol test [HTTP] at INET[127.0.0.1:8018] ^ 127.0.0.1:8018 - port 8018? or do you want port 8001? also i leave the host parameter out of the monit config. if failed port 8015 protocol http with timeout 20 seconds then restart On Mar 26, 2008, at 5:53 PM, Michael Engelhart wrote: Does anyone have any tips for checking to see if the mongrel instance is responding to HTTP? I just tried doing this: if failed host 127.0.0.1 port 8001 protocol http with timeout 10 seconds then restart but when I have that code in my monit script it gives me this error: mongrel_rails_8001' failed protocol test [HTTP] at INET[127.0.0.1:8018] via TCP Thanks for any tips. Mike ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
[Mongrel] logger debug level
greetings, i am getting the below error message in my mongrel log and I want to turn that 22 levels into a full trace. but i am unsure where or how to configure the debug level for mongrel. any advice? thanks - john /usr/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/cli/ruby-debug/ interface.rb:24:in `join': can't convert nil into String (TypeError) from /usr/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/cli/ruby- debug/interface.rb:24 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb: 27:in `gem_original_require' from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb: 27:in `require' from /var/www/foo/live/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:496:in `require' from /var/www/foo/live/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in' from /var/www/foo/live/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:496:in `require' from /usr/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/cli/ruby- debug/processor.rb:1 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb: 27:in `gem_original_require' ... 22 levels... from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ command.rb:211:in `run' from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/bin/ mongrel_rails:243 from /usr/bin/mongrel_rails:16:in `load' from /usr/bin/mongrel_rails:16 ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
Re: [Mongrel] logger debug level
cool, thanks guys On Dec 12, 2007, at 1:53 PM, Evan Weaver wrote: Actually, the trace snip level is hard-compiled into Ruby. Find the place where the traceback occurs, rescue the exception, and print out e.traceback (or whatever it is) instead. Then you'll see the whole thing. Evan On Dec 12, 2007 1:27 PM, Wayne E. Seguin [EMAIL PROTECTED] wrote: -B http://mongrel.rubyforge.org/docs/howto.html ~Wayne ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users -- Evan Weaver Cloudburst, LLC ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users ___ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
