Skip to Content.
Sympa Menu

en - Re: [sympa-users] error : MySQL server has gone away

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Vyacheslav <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] error : MySQL server has gone away
  • Date: Tue, 26 Apr 2016 11:06:14 +0300

Steve, thanx for answer, but it don't looks mysql issue. Mysql running on the same host, i increased limits to over sympa requirements, and turned on all logs. How it is looks like: when i distribute about 20mb via list, i see in queries' log heavy long-running INSERTion into bulkspool_table, but if i increase distribution up to 30mb i don't see INSERT query at all. I don't know "inner" sympa's procession, but it seems like it trying to "estimate" some volume of distribution (or maybe perl mysql module, i dunno) and failing against some limits before trying to insert it into mysql table. I try to find functions in source-code, but i just found "$size = &Bulk::store_test(21000); ## will test message until a 21 Mo message." and it seems not my option.

26.04.2016 1:03, Steve Shipway (via sympa-users Mailing List) пишет:
error : MySQL server has gone away Apr 25 13:42:50 mailserver
sympa[23150]: err

This message appears when a remote MySQL server cuts the connection before
it should.

There are a couple of potential causes for this --

- A very long query, and an intervening firewall. If you have a very long
running query (like about 1 minute), then some firewalls will remove the
state table entry and effectively kill the connection.
- A very long query, and a small local timeout. If the query runs for 1
minute but your client timeout is 20s then you'll get this.
- A server fault. Maybe your mysql server is out of memory or resource
- A very big query, and you have a too small max_allowed_packet . Make sure
your max_allowed_packet is big enough, maybe set it to 50,000,000 in the
my.cnf
- something else

If you have max_allowed_packet set big, then check for slow queries. Have
your mysql server log slow queries with something like
log_slow_queries=/var/log/mysqld.slow.log
long_query_time=2
If you find slow queries, increase resource to your mysql instance -- try
raising query_cache_limit=1M, query_cache_size=32M, key_buffer=256M,
sort_buffer_size=2M, read_buffer_size=2M, myisam_sort_buffer_size=64M (these
values are tuned for a 4G host so YMMV). These settings may also help with
exhausted resources.


Steve

Steve Shipway
T: +64 9 3737 599 ext 86487
E: address@concealed


--
Vyacheslav




Archive powered by MHonArc 2.6.19+.

Top of Page