Bug #20541 | MySQL Server segfaults when issuing 'mysqladmin refresh' | ||
---|---|---|---|
Submitted: | 19 Jun 2006 16:51 | Modified: | 20 Jul 2006 19:10 |
Reporter: | Sander Smeenk | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.22 | OS: | Linux (Debian GNU/Linux kernel 2.6.15.1) |
Assigned to: | CPU Architecture: | Any |
[19 Jun 2006 16:51]
Sander Smeenk
[23 Jun 2006 9:50]
Valeriy Kravchuk
Thank you for a problem report. Please, send your my.cnf file content. Does this happen on each and every 'mysqladmin refresh'? Do you have anything unusual in the error log?
[23 Jun 2006 10:04]
Sander Smeenk
[23 Jun 11:50] Valeriy Kravchuk > Thank you for a problem report. Please, send your my.cnf file content. Okay! I will post it with the bugreport. > Does this happen on each and every 'mysqladmin refresh'? Yes. Each and every time i type 'mysqladmin refresh' it segfaults the server. So if you want more gdb traces, i can reproduce the problem. > Do you have anything unusual in the error log? Nothing at all, actually. Except the segfault error which is: mysqld[8199]: mysqld got signal 11; mysqld[8199]: This could be because you hit a bug. It is also possible that this binary mysqld[8199]: or one of the libraries it was linked against is corrupt, improperly built, mysqld[8199]: or misconfigured. This error can also be caused by malfunctioning hardware. mysqld[8199]: We will try our best to scrape up some info that will hopefully help diagnose mysqld[8199]: the problem, but since we have already crashed, something is definitely wrong mysqld[8199]: and this may fail. mysqld[8199]: mysqld[8199]: key_buffer_size=33554432 mysqld[8199]: read_buffer_size=131072 mysqld[8199]: max_used_connections=1 mysqld[8199]: max_connections=100 mysqld[8199]: threads_connected=1 mysqld[8199]: It is possible that mysqld could use up to mysqld[8199]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 250367 K mysqld[8199]: bytes of memory mysqld[8199]: Hope that's ok; if not, decrease some variables in the equation. mysqld[8199]: mysqld_safe[8227]: Number of processes running now: 0 mysqld_safe[8229]: restarted mysqld[8232]: 060623 8:30:46 InnoDB: Started; log sequence number 0 43655 mysqld[8232]: 060623 8:30:46 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=oranje-relay mysqld[8232]: 060623 8:30:46 [Note] /usr/sbin/mysqld: ready for connections. mysqld[8232]: Version: '5.0.22-Debian_2-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian Etch distribution mysqld[8232]: 060623 8:30:46 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000467' at position 101558505, relay log './oranje-relay-bin.002496' position: 235 mysqld[8232]: 060623 8:30:46 [Note] Slave I/O thread: connected to master 'vgl_repl@zwart.hostname.tld:3306', replication started in log 'mysql-bin.000467' at position 101558505
[20 Jul 2006 19:10]
Valeriy Kravchuk
As you have expire-logs-days = 1, it is, almost surely, a duplicate of bug #17733. Refresh means "Flush all tables and close and open log files."