<div>I didn't know i could use the Logger class like that, pretty sweet.</div>
<div> </div>
<div>Do people know if rotating the logs via Logger is the issue or just rotating in general?</div>
<div> </div>
<div>.: Michael :.<br><br> </div>
<div><span class="gmail_quote">On 1/2/07, <b class="gmail_sendername">Michael Kovacs</b> <<a href="mailto:kovacs@gmail.com">kovacs@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hmm... thanks for the suggestion I'll give that a look as well as<br>search the archives here.<br><br>
I do have the logger rotating daily right now:<br>config.logger = Logger.new(config.log_path, 'daily')<br><br>I think I'll remove that and see if this occurs again. The thing that<br>still bothers me though<br>
is that if one mongrel is broken from this shouldn't they all be? I<br>can always count on 1 of 4 mongrels<br>working so that every 3rd request is successful :-) In order to<br>monitor that I'd have to hit the site twice to
<br>ensure that I'm not just getting the good mongrel on the first hit.<br>Not very fresh.<br><br>-Michael<br><a href="http://javathehutt.blogspot.com">http://javathehutt.blogspot.com</a><br><br>On Jan 2, 2007, at 1:36 PM, Joey Geiger wrote:
<br><br>> This may have to do with log rotation. There was a thread about<br>> similar issue posted in I believe December. You might want to try<br>> searching the mailing list archives.<br>><br>> You're probably rotating your logs based on a specific size, which is
<br>> why it's happening every couple hours, instead of nightly.<br>><br>> On 1/2/07, Michael Kovacs <<a href="mailto:kovacs@gmail.com">kovacs@gmail.com</a>> wrote:<br>>> Hi all,<br>>><br>>> I've been having problems with the apache
2.2-mod_proxy_balancer-<br>>> mongrel<br>>> setup.<br>>><br>>> My setup is:<br>>><br>>> CentOS 4.3<br>>> apache 2.2.3 (compiled from source) with mod_proxy_balancer<br>>> mysql
4.1<br>>> ruby 1.8.4<br>>> mongrel 0.3.14 (I know I need to update but I think this problem is<br>>> independent of the mongrel version)<br>>> mongrel_cluster 0.2.0<br>>> rails_machine 0.1.1<br>
>><br>>> I have apache setup as per Coda's configuration on his blog<br>>> posting from<br>>> several months back.<br>>> <a href="http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-">
http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-</a><br>>> rails-mongrel-apache-capistrano-and-you/<br>>><br>>> I have 4 mongrels in my cluster.<br>>><br>>> Things work fine for periods of time but after several hours of
<br>>> inactivity<br>>> (I think 8 hours or so) I experience oddness where only 1 of the 4<br>>> mongrels<br>>> is properly<br>>> responding. I end up getting a "500 internal server error" 3 out of 4
<br>>> requests as they round robin from mongrel to mongrel. There is<br>>> nothing in<br>>> the production<br>>> log file nor in the mongrel log. I've reproduced this problem on<br>>> my staging
<br>>> box as well as my production box.<br>>><br>>> The last time I reproduced the problem I decided to run "top" and<br>>> see what's<br>>> going on when I hit the server.<br>
>> Mongrel does receive every request but mysql is only active on the<br>>> 1 request<br>>> that works. In the other mongrels it never spikes up in CPU usage.<br>>><br>>> Looking at the mysql process list revealed that all of the
<br>>> processes had<br>>> received the "sleep" command but one of the processes is still<br>>> working properly. I've played with connection timeouts other than<br>>> to set the<br>>> timeout in my application's environment
<br>>> (ActiveRecord::Base.verification_timeout = 14400) as well as the<br>>> mysql<br>>> interactive_timeout variable but it seems that all the mongrels<br>>> should work<br>>> or they shouldn't. The fact that 1 out of 4 always works is rather
<br>>> puzzling<br>>> to me.<br>>><br>>> Trying a 'killall -USR1 mongrel_rails" to turn debug on simply<br>>> killed the 4<br>>> threads running mongrel. So now I'm running the cluster in debug
<br>>> mode and am<br>>> going to just let it sit there for several hours until it happens<br>>> again and<br>>> hopefully get some idea of where the breakdown is happening. I<br>>> still think
<br>>> it has to be a mysql connection timeout but again, the fact that 1<br>>> of the 4<br>>> always works doesn't lend credence to the timeout theory.<br>>><br>>> Has anyone experienced this phenomenon themselves?
<br>>><br>>> Thanks for any tips/pointers and thanks Zed for all your hard work<br>>> with<br>>> mongrel.<br>>><br>>><br>>><br>>> -Michaelhttp://javathehutt.blogspot.com<br>
>><br>>><br>>> _______________________________________________<br>>> Mongrel-users mailing list<br>>> <a href="mailto:Mongrel-users@rubyforge.org">Mongrel-users@rubyforge.org</a><br>>>
<a href="http://rubyforge.org/mailman/listinfo/mongrel-users">http://rubyforge.org/mailman/listinfo/mongrel-users</a><br>>><br>>><br>> _______________________________________________<br>> Mongrel-users mailing list
<br>> <a href="mailto:Mongrel-users@rubyforge.org">Mongrel-users@rubyforge.org</a><br>> <a href="http://rubyforge.org/mailman/listinfo/mongrel-users">http://rubyforge.org/mailman/listinfo/mongrel-users</a><br><br>_______________________________________________
<br>Mongrel-users mailing list<br><a href="mailto:Mongrel-users@rubyforge.org">Mongrel-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/mongrel-users">http://rubyforge.org/mailman/listinfo/mongrel-users
</a><br></blockquote></div><br>