[RAS] barro problem

Ivan Kurmanov duraley at gmail.com
Wed Jul 22 05:23:56 CDT 2009


I don't know what is /tmp/barro.log, but you definitely can solve this
by setting max_allowed_packet to a large enough value.

http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html says:

"Both the client and the server have their own max_allowed_packet
variable, so if you want to handle big packets, you must increase this
variable both in the client and in the server."

you should be able to set both server and client variables in /etc/my.cnf

max_allowed_packet=16M

in the [mysqld] section (for the server) and probably the [client]
section for the client.

-i

On Wed, Jul 22, 2009 at 2:38 AM, Thomas Krichel<krichel at openlib.org> wrote:
>  Ivan Kurmanov writes
>
>> check the sql.log, what does it say?
>
>  execute res: Got a packet bigger than 'max_allowed_packet' bytes
>
>  This gives you an idea about the size
>
> aras at nebka:~$ ls -lt /tmp/barro.log
> -rw-r--r-- 1 aras aras 4618246 2009-07-21 19:32 /tmp/barro.log
>
>  Should I study the docs to see how to raise the limit?
>
>
>  Cheers,
>
>  Thomas Krichel                    http://openlib.org/home/krichel
>                                RePEc:per:1965-06-05:thomas_krichel
>                                               skype: thomaskrichel
>



More information about the RAS-run mailing list