The issue still happens. I may have found the cause. The MySQL data dir is
stored on a tmpfs to speed things up and the disk usage there grows over
time. It's possible that a 3GB tmpfs (it's 2GB on Ubuntu 14.04 machines) is
too small and that if enough MySQL builds are running concurrently, it
great!
2016-08-05 19:19 GMT-03:00 Tim Graham :
> I spun up a new machine and haven't seen this issue on it, so the problem
> may have been either hardware related or something that was fixed with a
> fresher install of Ubuntu 16.04.
>
> On Wednesday, August 3, 2016 at 11:07:54 AM UTC-4, gilberto
I spun up a new machine and haven't seen this issue on it, so the problem
may have been either hardware related or something that was fixed with a
fresher install of Ubuntu 16.04.
On Wednesday, August 3, 2016 at 11:07:54 AM UTC-4, gilberto dos santos
alves wrote:
>
> hummm! thanks. i will conti
hummm! thanks. i will continue search for more precise aswers and
solutions. regards.
2016-08-02 17:27 GMT-03:00 Tim Graham :
> I'm not sure exceeding max_connections is the issue. We have up to 8
> executors on each machine and the tests aren't running in parallel, so I
> think we wouldn't have
Aside the obvious (hardware issues), which is I think unlikely if your
datadir is on tmpfs, can you check the error logs for what queries were
being executed when it crashes?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Djan
I think this is better directed at a MySQL list. MySQL shouldn't crash, nothing
I see indicates that this is a Django issue.
Of course, it's best if you can reproduce the error. Barring that, you'll get a
much more useful stack trace if you build MySQL with debugging symbols. A quick
look at th
I'm not sure exceeding max_connections is the issue. We have up to 8
executors on each machine and the tests aren't running in parallel, so I
think we wouldn't have more than 8 connections unless running the tests can
open more than 1 connection? Also, we don't expect 8 all executors to all
be
hi. IMO vars for django may uses this values inside [MYSQLD], cause
max_connections default is 100
innodb_buffer_pool_instances=8
max_connections=255
you could verify your environment using console command
mysql -u your-user -p[your-password-whit-nospace]
show variables like '%connec%';
show v
Here you are:
[client]
port= 3306
socket= /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently
parsed.
[mysqld_safe]
socket
hi. please post your /etc/my.ini (or your equiv. mysql ini config file).
2016-08-01 21:05 GMT-03:00 Tim Graham :
> Sometimes the MySQL 5.7.13 builds on Ubuntu 16.04 are failing with "Lost
> connection to MySQL server during query" because the MySQL server restarts
> during the tests. I wonder if
Sometimes the MySQL 5.7.13 builds on Ubuntu 16.04 are failing with "Lost
connection to MySQL server during query" because the MySQL server restarts
during the tests. I wonder if anyone has an idea about how to solve this.
Looking through the MySQL error log, I think this is the root cause:
2016
11 matches
Mail list logo
