Bug #24165 mysql signal 11 on use db with specific GRANTS
Submitted: 10 Nov 2006 3:53 Modified: 10 Dec 2006 8:31
Reporter: Adam Dixon (Candidate Quality Contributor) Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.22 OS:
Assigned to: CPU Architecture:Any
Tags: crash, Signal 11

[10 Nov 2006 3:53] Adam Dixon
Description:
I have an issue with mysqld signal 11 crashing when simple connecting and 'use db', I am not able to reproduce this on my test cluster however... but its hard without know exactly what area of the setup is triggering it.)
When some clients are connecting, and those clients have prohibitive GRANT access to a database, say, a 50 table db, and they have SELECT on 1 table, and nothing else, when connecting and 'use db' the mysqld will crash.

The only reason i feelthat this has anything to do with grants is that this never happens if the connecting user has full permissions to all tables in a db.

Possibly related to http://bugs.mysql.com/bug.php?id=22778 however not quite the same. Ive had this problem for a while but never been able to get anything other than 'signal 11' crash info, this morning however I did get a little extra info...

-----------------------------
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
.....
and this may fail.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=158
max_connections=200
threads_connected=76
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 443390 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

mysqld: my_new.cc:51: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed.
Fatal signal 6 while backtracing

Number of processes running now: 0
061110 10:30:50  mysqld restarted
-----------------------------

mysqld: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped

Linux c1m1.adnap.net.au 2.6.9-5.ELsmp #1 SMP Tue May 3 07:25:41 CDT 2005 x86_64 x86_64 x86_64 GNU/Linux

             total       used       free     shared    buffers     cached
Mem:       4041824    1540024    2501800          0     193396    1149128
-/+ buffers/cache:     197500    3844324
Swap:      6144852          0    6144852

[mysql@c1m1 bin]$ ulimit -aS
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
file size               (blocks, -f) unlimited
pending signals                 (-i) 1024
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 38912
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

[mysql@c1m1 bin]$ ulimit -aH
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
file size               (blocks, -f) unlimited
pending signals                 (-i) 1024
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 38912
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

How to repeat:
In my production setup all I do is connect, and 'use dbname' where the connected user has quite defined grants, and it crashes with signal 11.
[10 Nov 2006 8:31] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a latest version, 5.0.27, and inform about the results.
[11 Dec 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".