Package: mysql-server-4.1
Version: 4.1.10-1
Severity: important
the query in question:
select *,id as mmenuid from menu
where
(parent=1)and
( (select groupid from permissions where menuid=mmenuid )
in
(select groupid from usergroups where userid=
(select id from users where nick='balint'))
)
order by oid
dump of table structures:
-- Table structure for table `menu`
--
CREATE TABLE `menu` (
`id` int(11) NOT NULL auto_increment,
`oid` varchar(11) NOT NULL default '0',
`hint` varchar(100) NOT NULL default '',
`display` varchar(50) NOT NULL default '',
`parent` int(11) NOT NULL default '0',
`proc` varchar(20) NOT NULL default '',
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=65 ;
-- Table structure for table `permissions`
--
CREATE TABLE `permissions` (
`menuid` int(11) NOT NULL default '0',
`groupid` int(11) NOT NULL default '0',
UNIQUE KEY `menuid` (`menuid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
-- Table structure for table `usergroups`
--
CREATE TABLE `usergroups` (
`id` int(11) NOT NULL auto_increment,
`groupid` int(11) NOT NULL default '0',
`userid` int(11) NOT NULL default '0',
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=13 ;
-- Table structure for table `users`
--
CREATE TABLE `users` (
`id` int(11) NOT NULL auto_increment,
`nick` varchar(10) NOT NULL default '',
`passwd` varchar(10) NOT NULL default '',
`name` varchar(200) NOT NULL default '',
PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=7 ;
error:
mysql said: "MySQL server has gone away"
for: "select * from menu where id='1'"
syslog:
Mar 2 11:33:50 fp mysqld[9649]: /usr/sbin/mysqld: ready for
connections.
Mar 2 11:33:50 fp mysqld[9649]: Version: '4.1.10-Debian_1-log' socket:
'/var/run/mysqld/mysqld.sock' port: 0 Source distribution
Mar 2 11:38:10 fp mysqld[9649]: mysqld got signal 11;
Mar 2 11:38:10 fp mysqld[9649]: This could be because you hit a bug. It
is also possible that this binary
Mar 2 11:38:10 fp mysqld[9649]: or one of the libraries it was linked
against is corrupt, improperly built,
Mar 2 11:38:10 fp mysqld[9649]: or misconfigured. This error can also
be caused by malfunctioning hardware.
Mar 2 11:38:10 fp mysqld[9649]: We will try our best to scrape up some
info that will hopefully help diagnose
Mar 2 11:38:10 fp mysqld[9649]: the problem, but since we have already
crashed, something is definitely wrong
Mar 2 11:38:10 fp mysqld[9649]: and this may fail.
Mar 2 11:38:10 fp mysqld[9649]:
Mar 2 11:38:10 fp mysqld[9649]: key_buffer_size=4194304
Mar 2 11:38:10 fp mysqld[9649]: read_buffer_size=131072
Mar 2 11:38:10 fp mysqld[9649]: max_used_connections=1
Mar 2 11:38:10 fp mysqld[9649]: max_connections=10
Mar 2 11:38:10 fp mysqld[9649]: threads_connected=1
Mar 2 11:38:10 fp mysqld[9649]: It is possible that mysqld could use up
to
Mar 2 11:38:10 fp mysqld[9649]: key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 25855 K
Mar 2 11:38:10 fp mysqld[9649]: bytes of memory
Mar 2 11:38:10 fp mysqld[9649]: Hope that's ok; if not, decrease some
variables in the equation.
Mar 2 11:38:10 fp mysqld[9649]:
Mar 2 11:38:10 fp mysqld[9649]: thd=0x86a63f8
Mar 2 11:38:10 fp mysqld[9649]: Attempting backtrace. You can use the
following information to find out
Mar 2 11:38:10 fp mysqld[9649]: where mysqld died. If you see no
messages after this, something went
Mar 2 11:38:10 fp mysqld[9649]: terribly wrong...
Mar 2 11:38:10 fp mysqld[9649]: Cannot determine thread, fp=0xbf5fea08,
backtrace may not be correct.
Mar 2 11:38:10 fp mysqld[9649]: Stack range sanity check OK, backtrace
follows:
Mar 2 11:38:10 fp mysqld[9649]: 0x818795d
Mar 2 11:38:10 fp mysqld[9649]: 0x40058825
Mar 2 11:38:10 fp mysqld[9649]: 0x8160be0
Mar 2 11:38:10 fp mysqld[9649]: 0x815fea7
Mar 2 11:38:10 fp mysqld[9649]: 0x81c1b4f
Mar 2 11:38:10 fp mysqld[9649]: 0x816045b
Mar 2 11:38:10 fp mysqld[9649]: 0x815d5d2
Mar 2 11:38:10 fp mysqld[9649]: 0x81374f1
Mar 2 11:38:10 fp mysqld[9649]: 0x81bcfd3
Mar 2 11:38:10 fp mysqld[9649]: 0x81c1a8a
Mar 2 11:38:10 fp mysqld[9649]: 0x81c513f
Mar 2 11:38:10 fp mysqld[9649]: 0x81c18d2
Mar 2 11:38:10 fp mysqld[9649]: 0x819ba56
Mar 2 11:38:10 fp mysqld[9649]: 0x81a10c0
Mar 2 11:38:10 fp mysqld[9649]: 0x819a577
Mar 2 11:38:10 fp mysqld[9649]: 0x819a166
Mar 2 11:38:10 fp mysqld[9649]: 0x81998c8
Mar 2 11:38:10 fp mysqld[9649]: 0x40052e51
Mar 2 11:38:10 fp mysqld[9649]: 0x401d96ea
Mar 2 11:38:10 fp mysqld[9649]: New value of fp=(nil) failed sanity
check, terminating stack trace!
Mar 2 11:38:10 fp mysqld[9649]: Please read
http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow
instructions on how to resolve the stack trace. Resolved
Mar 2 11:38:10 fp mysqld[9649]: stack trace is much more helpful in
diagnosing the problem, so please do
Mar 2 11:38:10 fp mysqld[9649]: resolve it
Mar 2 11:38:10 fp mysqld[9649]: Trying to get some variables.
Mar 2 11:38:10 fp mysqld[9649]: Some pointers may be invalid and cause
the dump to abort...
Mar 2 11:38:10 fp mysqld[9649]: thd->query at 0x86cb2d8 = select *,id
as mmenuid from menu
Mar 2 11:38:10 fp mysqld[9649]: where
Mar 2 11:38:10 fp mysqld[9649]: (parent=1)and
Mar 2 11:38:10 fp mysqld[9649]: (
Mar 2 11:38:10 fp mysqld[9649]: (select groupid from
permissions where menuid=mmenuid ) in
Mar 2 11:38:10 fp mysqld[9649]: (select groupid from
usergroups where userid=
Mar 2 11:38:10 fp mysqld[9649]: (select id from
users where nick='balint')))
Mar 2 11:38:10 fp mysqld[9649]: order by oid
Mar 2 11:38:10 fp mysqld[9649]: thd->thread_id=11
Mar 2 11:38:10 fp mysqld[9649]: The manual page at
http://www.mysql.com/doc/en/Crashing.html contains
Mar 2 11:38:10 fp mysqld[9649]: information that should help you find
out what is causing the crash.
i may rewrite the query, but this situation still would not work.
it may not be a real bug, it may be my mistake somewhere,
but since i did not get any help on #mysql i hope it'll be resolved
here.
the problem exists since last update of mysql-server-4.1 (i think).
version mysql-server-4.1 4.1.9-2 is doing it fine.
version mysql-server-4.1 4.1.10-1 does the crash.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages mysql-server-4.1 depends on:
ii adduser 3.59 Add and remove users and groups
ii debconf 1.4.30.11 Debian configuration management sy
ii gawk 1:3.1.4-2 GNU awk, a pattern scanning and pr
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libdbi-perl 1.46-6 Perl5 database interface by Tim Bu
ii libmysqlclient14 4.1.10-1 mysql database client library
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii libreadline4 4.3-11 GNU readline and history libraries
ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-6 Wietse Venema's TCP wrappers libra
ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii mysql-client-4.1 4.1.10-1 mysql database client binaries
ii mysql-common-4.1 4.1.10-1 mysql database common files (e.g.
ii passwd 1:4.0.3-30.9 change and administer password and
ii perl 5.8.4-6 Larry Wall's Practical Extraction
ii psmisc 21.5-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.2-3 compression library - runtime
-- debconf information:
* mysql-server-4.1/start_on_boot: true
mysql-server-4.1/postrm_remove_databases: false
* mysql-server-4.1/mysql_install_db_notes:
mysql-server-4.1/mysql_update_hints1:
mysql-server-4.1/nis_warning:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
