Your message dated Fri, 23 Feb 2007 22:17:06 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403721: fixed in mysql-dfsg-5.0 5.0.32-3etch1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mysql-server-5.0
Version: 5.0.32-3
Hi,
I was playing around with the CMS Joomla! Version 1.0.12.
While clicking around in the admin panel the mysql server crashed.
I have a log of the crash and I have done a stack trace like described on the
mysql page.
I can reproduce this error. I allready deleted the database and recreated it,
but get the same error.
Log of the crash:
Feb 12 02:08:34 server mysqld[31084]: mysqld got signal 6;
Feb 12 02:08:34 server mysqld[31084]: This could be because you hit a bug. It
is also possible that this binary
Feb 12 02:08:34 server mysqld[31084]: or one of the libraries it was linked
against is corrupt, improperly built,
Feb 12 02:08:34 server mysqld[31084]: or misconfigured. This error can also be
caused by malfunctioning hardware.
Feb 12 02:08:34 server mysqld[31084]: We will try our best to scrape up some
info that will hopefully help diagnose
Feb 12 02:08:34 server mysqld[31084]: the problem, but since we have already
crashed, something is definitely wrong
Feb 12 02:08:34 server mysqld[31084]: and this may fail.
Feb 12 02:08:34 server mysqld[31084]:
Feb 12 02:08:34 server mysqld[31084]: key_buffer_size=16777216
Feb 12 02:08:34 server mysqld[31084]: read_buffer_size=131072
Feb 12 02:08:34 server mysqld[31084]: max_used_connections=3
Feb 12 02:08:34 server mysqld[31084]: max_connections=100
Feb 12 02:08:34 server mysqld[31084]: threads_connected=1
Feb 12 02:08:34 server mysqld[31084]: It is possible that mysqld could use up to
Feb 12 02:08:34 server mysqld[31084]: key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 233983 K
Feb 12 02:08:34 server mysqld[31084]: bytes of memory
Feb 12 02:08:34 server mysqld[31084]: Hope that's ok; if not, decrease some
variables in the equation.
Feb 12 02:08:34 server mysqld[31084]:
Feb 12 02:08:34 server mysqld[31084]: thd=0x8ad8b98
Feb 12 02:08:34 server mysqld[31084]: Attempting backtrace. You can use the
following information to find out
Feb 12 02:08:34 server mysqld[31084]: where mysqld died. If you see no messages
after this, something went
Feb 12 02:08:34 server mysqld[31084]: terribly wrong...
Feb 12 02:08:34 server mysqld[31084]: Cannot determine thread, fp=0xb3f58ab8,
backtrace may not be correct.
Feb 12 02:08:34 server mysqld[31084]: Stack range sanity check OK, backtrace
follows:
Feb 12 02:08:34 server mysqld[31084]: 0x81c0649
Feb 12 02:08:34 server mysqld[31084]: 0xb7f68410
Feb 12 02:08:34 server mysqld[31084]: 0xb7cc2fb9
Feb 12 02:08:34 server mysqld[31084]: 0xb7cf6c8a
Feb 12 02:08:34 server mysqld[31084]: 0xb7cfe51f
Feb 12 02:08:34 server mysqld[31084]: 0xb7cfe5c2
Feb 12 02:08:34 server mysqld[31084]: 0x8484df3
Feb 12 02:08:34 server mysqld[31084]: 0x820a289
Feb 12 02:08:34 server mysqld[31084]: 0x8213c65
Feb 12 02:08:34 server mysqld[31084]: 0x82bf766
Feb 12 02:08:34 server mysqld[31084]: 0x8221b48
Feb 12 02:08:34 server mysqld[31084]: 0x822244e
Feb 12 02:08:34 server mysqld[31084]: 0x81d7495
Feb 12 02:08:34 server mysqld[31084]: 0x81dba07
Feb 12 02:08:34 server mysqld[31084]: 0x81dbec0
Feb 12 02:08:34 server mysqld[31084]: 0x81dd188
Feb 12 02:08:34 server mysqld[31084]: 0x81ddb94
Feb 12 02:08:34 server mysqld[31084]: 0xb7f29240
Feb 12 02:08:34 server mysqld[31084]: 0xb7d6432e
Feb 12 02:08:34 server mysqld[31084]: New value of fp=(nil) failed sanity
check, terminating stack trace!
Feb 12 02:08:34 server mysqld[31084]: Please read
http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow
instructions on how to resolve the stack trace. Resolved
Feb 12 02:08:34 server mysqld[31084]: stack trace is much more helpful in
diagnosing the problem, so please do
Feb 12 02:08:34 server mysqld[31084]: resolve it
Feb 12 02:08:34 server mysqld[31084]: Trying to get some variables.
Feb 12 02:08:34 server mysqld[31084]: Some pointers may be invalid and cause
the dump to abort...
Feb 12 02:08:34 server mysqld[31084]: thd->query at 0x8b405c0 = SELECT c.*,
c.checked_out as checked_out_contact_category, g.name AS groupname, u.name AS
editor,COUNT( DISTINCT s2.checked_out ) AS checked_out
Feb 12 02:08:34 server mysqld[31084]: , z.title AS section_name
Feb 12 02:08:34 server mysqld[31084]: FROM jos_categories AS c
Feb 12 02:08:34 server mysqld[31084]: LEFT JOIN jos_users AS u ON u.id =
c.checked_out
Feb 12 02:08:34 server mysqld[31084]: LEFT JOIN jos_groups AS g ON g.id =
c.access
Feb 12 02:08:34 server mysqld[31084]: LEFT JOIN `jos_content` AS s2 ON
s2.catid = c.id AND s2.checked_out > 0
Feb 12 02:08:34 server mysqld[31084]: LEFT JOIN jos_sections AS z ON z.id =
c.section
Feb 12 02:08:34 server mysqld[31084]: WHERE c.section NOT LIKE '%com_%'
Feb 12 02:08:34 server mysqld[31084]: AND c.published != -2
Feb 12 02:08:34 server mysqld[31084]: GROUP BY c.id
Feb 12 02:08:34 server mysqld[31084]: ORDER BY c.section, c.ordering, c.name
Feb 12 02:08:34 server mysqld[31084]: LIMIT 30
Feb 12 02:08:34 server mysqld[31084]: thd->thread_id=17
Feb 12 02:08:34 server mysqld[31084]: The manual page at
http://www.mysql.com/doc/en/Crashing.html
Stack trace:
resolve_stack_dump -s mysqld.sym -n stack
0x81c0649 handle_segfault + 681
0xb7f68410 _end + -1350043328
0xb7cc2fb9 _end + -1352817431
0xb7cf6c8a _end + -1352605254
0xb7cfe51f _end + -1352574385
0xb7cfe5c2 _end + -1352574222
0x8484df3 free_root + 67
0x820a289 _Z14free_tmp_tableP3THDP8st_table + 201
0x8213c65 _ZN4JOIN7destroyEv + 165
0x82bf766 _ZN13st_select_lex7cleanupEv + 38
0x8221b48
_Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel
+ 152
0x822244e _Z13handle_selectP3THDP6st_lexP13select_resultm + 318
0x81d7495 _Z21mysql_execute_commandP3THD + 9557
0x81dba07 _Z11mysql_parseP3THDPcj + 471
0x81dbec0 _Z16dispatch_command19enum_server_commandP3THDPcj + 1120
0x81dd188 _Z10do_commandP3THD + 136
0x81ddb94 handle_one_connection + 2308
0xb7f29240 _end + -1350301840
0xb7d6432e _end + -1352157090
Regards
Michael
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
--- End Message ---
--- Begin Message ---
Source: mysql-dfsg-5.0
Source-Version: 5.0.32-3etch1
We believe that the bug you reported is fixed in the latest version of
mysql-dfsg-5.0, which is due to be installed in the Debian FTP archive:
libmysqlclient15-dev_5.0.32-3etch1_i386.deb
to pool/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-3etch1_i386.deb
libmysqlclient15off_5.0.32-3etch1_i386.deb
to pool/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-3etch1_i386.deb
mysql-client-5.0_5.0.32-3etch1_i386.deb
to pool/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-3etch1_i386.deb
mysql-client_5.0.32-3etch1_all.deb
to pool/main/m/mysql-dfsg-5.0/mysql-client_5.0.32-3etch1_all.deb
mysql-common_5.0.32-3etch1_all.deb
to pool/main/m/mysql-dfsg-5.0/mysql-common_5.0.32-3etch1_all.deb
mysql-dfsg-5.0_5.0.32-3etch1.diff.gz
to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.32-3etch1.diff.gz
mysql-dfsg-5.0_5.0.32-3etch1.dsc
to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.32-3etch1.dsc
mysql-server-4.1_5.0.32-3etch1_i386.deb
to pool/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-3etch1_i386.deb
mysql-server-5.0_5.0.32-3etch1_i386.deb
to pool/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-3etch1_i386.deb
mysql-server_5.0.32-3etch1_all.deb
to pool/main/m/mysql-dfsg-5.0/mysql-server_5.0.32-3etch1_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christian Hammers <[EMAIL PROTECTED]> (supplier of updated mysql-dfsg-5.0
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 18 Feb 2007 22:33:05 +0100
Source: mysql-dfsg-5.0
Binary: libmysqlclient15-dev mysql-client mysql-client-5.0 mysql-server
mysql-server-4.1 mysql-server-5.0 mysql-common libmysqlclient15off
Architecture: source all i386
Version: 5.0.32-3etch1
Distribution: testing-proposed-updates
Urgency: high
Maintainer: Christian Hammers <[EMAIL PROTECTED]>
Changed-By: Christian Hammers <[EMAIL PROTECTED]>
Description:
libmysqlclient15-dev - mysql database development files
libmysqlclient15off - mysql database client library
mysql-client - mysql database client (meta package depending on the latest
versi
mysql-client-5.0 - mysql database client binaries
mysql-common - mysql database common files (e.g. /etc/mysql/my.cnf)
mysql-server - mysql database server (meta package depending on the latest
versi
mysql-server-4.1 - mysql database server (transitional package)
mysql-server-5.0 - mysql database server binaries
Closes: 403721 409750 409780
Changes:
mysql-dfsg-5.0 (5.0.32-3etch1) testing-proposed-updates; urgency=high
.
* Backported upstream patch for a bug that crashed the server when using
certain join/group/limit combinations.
Users of the Joomla CMS seemed to be affected by this. Closes: #403721
* The debian-start script that runs on every server start now first upgrades
the system tables (if neccessary) and then check them as it sometimes did
not work the other way around (e.g. for MediaWiki). The script now uses
mysql_update instead of mysql_update_script as recommended. Closes: 409780
* The old_passwords setting that is set according to a Debconf question is
now written to /etc/mysql/conf.d/old_passwords.cnf instead directly to the
conffile /etc/mysql/my.cnf which would be fobidden by policy (thanks to
Robert Bihlmeyer). Closes: #409750
* Added bison to build dependencies.
* Synced Debconf translations with 5.0.32-7.
Files:
73676f169052a1911225b98eb5ad5f36 1125 misc optional
mysql-dfsg-5.0_5.0.32-3etch1.dsc
48a9d0d7a3036c1af3dc98504300380e 148467 misc optional
mysql-dfsg-5.0_5.0.32-3etch1.diff.gz
eb888555fbcd6c92b553d660eee9f035 52190 misc optional
mysql-common_5.0.32-3etch1_all.deb
ce014d2086dfbc3272e25ac4414d1a09 45932 misc optional
mysql-server_5.0.32-3etch1_all.deb
874d302be253cb46c0d9cc7dfe8aa696 43858 misc optional
mysql-client_5.0.32-3etch1_all.deb
e520ec93426c1fb99ffe70b82b4f918f 1789948 libs optional
libmysqlclient15off_5.0.32-3etch1_i386.deb
09f487bed4b0653d91f4e691dcc02764 6956110 libdevel optional
libmysqlclient15-dev_5.0.32-3etch1_i386.deb
0420f6cb6c6a447ed1c27bcaec18955d 7192098 misc optional
mysql-client-5.0_5.0.32-3etch1_i386.deb
3f62978c6333293492244519a2c027cd 25285658 misc optional
mysql-server-5.0_5.0.32-3etch1_i386.deb
a3285020389fd673e49a7a11698a9f06 45962 oldlibs extra
mysql-server-4.1_5.0.32-3etch1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iEYEARECAAYFAkXfXqoACgkQkR9K5oahGOb/JQCg1xoWxjbDLelZXur5sLDyRJJh
gl8AnRWjIhBa3hRiNChlnhdZa5xHITWe
=zlFn
-----END PGP SIGNATURE-----
--- End Message ---
