Gnucash in "MySQL server has gone away" loop
Christopher X. Candreva
chris at westnet.com
Tue Oct 4 14:41:29 EDT 2011
On Tue, 4 Oct 2011, John Ralls wrote:
> So, try jacking up the max_allowed_packet on the server side (apparently
> in /etc/my.cnf) and see if that makes a difference.
It can also be done via an SQL command. I just did and was able to load from
the database successfully, without the loop or SQL error in gnucash.trace
> I also had a look at the error-handling code. We just try to reconnect on
> a 2006, and the message we emit doesn't report the error message... so I
> think that the server is responding to our connection attempts with
> another 2006. We could close the connection and re-initialize, but that's
> really not going to help much with the actual error -- we'll still get
> another 2006 as soon as we retry whatever query caused the problem, so I
> guess bailing with a helpful error message is the best we can do. If
> jacking up the max_allowed_packet works, then we can make that a
> recommendation in the error message.
That sounds like the best idea.
==========================================================
Chris Candreva -- chris at westnet.com -- (914) 948-3162
WestNet Internet Services of Westchester
http://www.westnet.com/
More information about the gnucash-user
mailing list