On Mon, Oct 25, 2010 at 05:53:05PM +0100, Chris Withers wrote:
> On 25/10/2010 15:57, Paul Winkler wrote:
> > On Sun, Oct 24, 2010 at 05:55:05PM +0100, Chris Withers wrote:
> >> Restarting Zope appeared to fixed the problem, but I'm slightly confused
> >> as I can't find any entries in the logs of
On 25/10/2010 15:57, Paul Winkler wrote:
> On Sun, Oct 24, 2010 at 05:55:05PM +0100, Chris Withers wrote:
>> Restarting Zope appeared to fixed the problem, but I'm slightly confused
>> as I can't find any entries in the logs of the Apache instance that sits
>> in front of the test instances for the
On Sun, Oct 24, 2010 at 05:55:05PM +0100, Chris Withers wrote:
> Restarting Zope appeared to fixed the problem, but I'm slightly confused
> as I can't find any entries in the logs of the Apache instance that sits
> in front of the test instances for the failed requests...
Maybe turn on Zope's tr
On 23/10/2010 18:48, Shane Hathaway wrote:
> On 10/23/2010 01:29 AM, Chris Withers wrote:
>> Hi Shane,
>>
>> With the server I'm testing on, when coming back to test after a couple
>> of days working on something else, I get the following logged at Warning:
>>
>> Reconnecting load_conn: (2006, 'MyS
On 10/23/2010 01:29 AM, Chris Withers wrote:
> Hi Shane,
>
> With the server I'm testing on, when coming back to test after a couple
> of days working on something else, I get the following logged at Warning:
>
> Reconnecting load_conn: (2006, 'MySQL server has gone away')
>
> Does this mean the re
Hi Shane,
With the server I'm testing on, when coming back to test after a couple
of days working on something else, I get the following logged at Warning:
Reconnecting load_conn: (2006, 'MySQL server has gone away')
Does this mean the reconnection is being handled by RelStorage or that I
need
