Re: NOT [solved] Re: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5)

2008-05-24 Thread Moon's Father
You can manually restart the slave process. On Wed, May 21, 2008 at 9:11 PM, Dominik Klein [EMAIL PROTECTED] wrote: Hello mysql list I posted this problem to the list earlier this month: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5) I was then told

Re: NOT [solved] Re: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5)

2008-05-24 Thread Dominik Klein
Moon's Father schrieb: You can manually restart the slave process. Sure I can. But that's not sufficient. For now, I scripted some log watch thing that re-starts the slave in the particular situation. But this is not good. On Wed, May 21, 2008 at 9:11 PM, Dominik Klein [EMAIL PROTECTED]

NOT [solved] Re: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5)

2008-05-21 Thread Dominik Klein
Hello mysql list I posted this problem to the list earlier this month: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5) I was then told to upgrade to the newest version, which I did and which seemed to solve the problem. Today, I got this in my log:

Re: [solved] Re: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5)

2008-05-20 Thread Moon's Father
The general version can not be replaced *frequently * On Fri, May 9, 2008 at 4:23 PM, Dominik Klein [EMAIL PROTECTED] wrote: Upgrade to 5.0.51b seems to have solved the problem. On wednesday, I saw the problem about a dozen times during a peak time. Upgraded wednesday night and have not seen

[solved] Re: Error reading packet from server: Out of memory (Needed 6560 bytes) ( server_errno=5)

2008-05-09 Thread Dominik Klein
Upgrade to 5.0.51b seems to have solved the problem. On wednesday, I saw the problem about a dozen times during a peak time. Upgraded wednesday night and have not seen the error since. Thanks Dominik Juan Eduardo Moreno wrote: Hi, This error occur when slave servers could incorrectly