From lists-wp at mercurycloud.net  Fri Aug  1 17:41:18 2008
From: lists-wp at mercurycloud.net (Will Prater)
Date: Fri, 1 Aug 2008 14:41:18 -0700
Subject: Intermittent Internal 500 Error with mongrel
Message-ID: <4CB7CC59-0585-468C-A9D9-178300F18420@mercurycloud.net>

I'm having a very strange issue that is difficult to debug.  I've  
tried running merb with $DEBUG = true and verbose logging mode.  When  
we receive these 500 Internal Server errors, there is nothing  
outputted to the logs to STDOUT.

I've tried running through proxy (apache, nginx) and also direct  
mongrel.

I cannot seem to track the cause of the issue and it is very random,  
does not appear to happen on any one action.

Any ideas for further debugging of the issue is greatly appreciated.


Regards,

Will

From gianni.jacklone at gmail.com  Fri Aug  1 18:23:42 2008
From: gianni.jacklone at gmail.com (Gianni Jacklone)
Date: Fri, 1 Aug 2008 18:23:42 -0400
Subject: Intermittent Internal 500 Error with mongrel
In-Reply-To: <4CB7CC59-0585-468C-A9D9-178300F18420@mercurycloud.net>
References: <4CB7CC59-0585-468C-A9D9-178300F18420@mercurycloud.net>
Message-ID: <207004DA-BDF5-42C6-AA28-7C7913E9C5EC@gmail.com>

hmm, maybe set your config/environments/production.rb log_level  
to :debug and restart your merbs. Also try installing the  
merb_exceptions gem, it works great for me.

- Gianni

On Aug 1, 2008, at 5:41 PM, Will Prater wrote:

> I'm having a very strange issue that is difficult to debug.  I've  
> tried running merb with $DEBUG = true and verbose logging mode.   
> When we receive these 500 Internal Server errors, there is nothing  
> outputted to the logs to STDOUT.
>
> I've tried running through proxy (apache, nginx) and also direct  
> mongrel.
>
> I cannot seem to track the cause of the issue and it is very random,  
> does not appear to happen on any one action.
>
> Any ideas for further debugging of the issue is greatly appreciated.
>
>
> Regards,
>
> Will
> _______________________________________________
> Merb-devel mailing list
> Merb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/merb-devel


From lists-wp at mercurycloud.net  Sat Aug  2 14:10:59 2008
From: lists-wp at mercurycloud.net (Will Prater)
Date: Sat, 2 Aug 2008 11:10:59 -0700
Subject: Intermittent Internal 500 Error with mongrel
In-Reply-To: <207004DA-BDF5-42C6-AA28-7C7913E9C5EC@gmail.com>
References: <4CB7CC59-0585-468C-A9D9-178300F18420@mercurycloud.net>
	<207004DA-BDF5-42C6-AA28-7C7913E9C5EC@gmail.com>
Message-ID: <1D2A4A07-B621-4368-A7CB-0D71ABA6CFEC@mercurycloud.net>

I've tried setting the error level higher and used debug mode.   
Nothing is logged when they 500 get sent back.

That gem sounds great, but I don think it will work too well in my  
case, since there does not seem to be any exceptions thrown.

Regards,

On Aug 1, 2008, at 3:23 PM, Gianni Jacklone wrote:

> hmm, maybe set your config/environments/production.rb log_level  
> to :debug and restart your merbs. Also try installing the  
> merb_exceptions gem, it works great for me.
>
> - Gianni
>
> On Aug 1, 2008, at 5:41 PM, Will Prater wrote:
>
>> I'm having a very strange issue that is difficult to debug.  I've  
>> tried running merb with $DEBUG = true and verbose logging mode.   
>> When we receive these 500 Internal Server errors, there is nothing  
>> outputted to the logs to STDOUT.
>>
>> I've tried running through proxy (apache, nginx) and also direct  
>> mongrel.
>>
>> I cannot seem to track the cause of the issue and it is very  
>> random, does not appear to happen on any one action.
>>
>> Any ideas for further debugging of the issue is greatly appreciated.
>>
>>
>> Regards,
>>
>> Will
>> _______________________________________________
>> Merb-devel mailing list
>> Merb-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/merb-devel
>