hi there, from one day to another, my mysql in 2 machines with 2 different 
mysql version crashed after a quite long query,

i've run mysql server with the log option, here are the details:

in hostname.err:

mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
Attempting backtrace. You can use the following information to find out
where mysqld died.  If you see no messages after this, something went
terribly wrong...
Stack range sanity check OK, backtrace follows:
0x4008847b
0x80f83c0
0x80f9e6e
0x80f9a5a
0x80f8b9e
0x80f8842
0x80de518
0x80d9d5a
0x80c0cd3
0x80c3d8b
0x80c008f
0x80bf599
Stack trace successful, trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x82a0ca8 = SELECT Site.nome , Section.descricao , 
Location.descricao , BuyingType.descricao , Dimension.descricao , 
(0+impressoescompradas+impressoesoferta) as totalimpressoes , sum(siteviews) 
, sum(systemclicks) , ifnull(max(Accounting_site.data), 'N/A') , '0' AS 
ocupation , '2001-01-01' AS month , Site.site_id , Location.location_id , 
Section.section_id , CampaignSite.dimension_id
FROM Dimension,Site,Location,Section,BuyingType,CampaignSite LEFT JOIN  
Accounting_site USING (campaign_id, site_id, section_id, location_id,
 dimension_id)  LEFT JOIN  Accounting_sys USING (campaign_id, site_id, 
section_id, location_id, dimension_id)
WHERE
   Accounting_site.campaign_id = '1'   and CampaignSite.site_id = 
Site.site_id  and CampaignSite.location_id = Location.location_id  and 
CampaignSite.section_id = Section.section_id  and CampaignSite.buyingtype_id 
= BuyingType.buyingtype_id  and CampaignSite.dimension_id = 
Dimension.dimension_id  and CampaignSite.campaign_id = 1
   GROUP BY Site.site_id, Section.section_id, Location.
thd->thread_id = 1
Successfully dumped variables, if you ran with --log,
take a look at the details of what thread 1 did to cause the crash.
In some cases of really bad corruption, this value may be invalid
Please use the information above to create a repeatable
test case for the crash, and send it to [EMAIL PROTECTED]
 
Number of processes running now: 0
010521 12:55:01  mysqld restarted

the mysql details on this machine is:
mysqlclient:
mysql> \s
--------------
mysql  Ver 11.13 Distrib 3.23.36, for pc-linux-gnu (i686)
 
Connection id:          1
Current pager:          stdout
Using outfile:          ''
Server version:         3.23.36-log
Protocol version:       10
Connection:             Localhost via UNIX socket
Client characterset:    latin1
Server characterset:    latin1
UNIX socket:            /var/lib/mysql/mysql.sock
--------------
mysqlserver:
[brandon@lamatra brandon]$ mysqladmin version
mysqladmin  Ver 8.18 Distrib 3.23.36, for pc-linux-gnu on i686
Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license
 
Server version          3.23.36-log
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 7 min 56 sec


On the second machine and different version the stacktrace is empty here it 
goes:

hostname.err:
010521 12:06:39  mysqld ended
 
010521 12:07:04  mysqld started
/usr/sbin/mysqld: ready for connections
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died
Attemping backtrace. You can use the following information to find out
where mysqld died.  If you see no messages after this, something went
terribly wrong
Bogus stack limit or frame pointer, aborting backtrace

mysqlclient:

mysql> \s
--------------
mysql  Ver 11.12 Distrib 3.23.33, for pc-linux-gnu (i686)
 
Connection id:          3
Current pager:          stdout
Using outfile:          ''
Server version:         3.23.33-log
Protocol version:       10
Connection:             Localhost via UNIX socket
Client characterset:    latin1
Server characterset:    latin1
UNIX socket:            /var/lib/mysql/mysql.sock

mysqlserver:
mysqladmin  Ver 8.15 Distrib 3.23.33, for pc-linux-gnu on i686
Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license
 
Server version          3.23.33-log
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 4 min 11 sec

it's quite strange, i'm almost think it's an hardware bug, but i have 2 other 
machine that work correctly with the same query's, and some have the same 
version's like these one's.

thx.


-- 
WEBSOLUT - Soluções Internet
Emailto: [EMAIL PROTECTED] 
Personal Info: http://websolut.net/people/rui.html

As informações contidas neste email são confidenciais
e destinam-se apenas à(s) pessoa(s) a quem foi enviado:
http://websolut.net/confidencialidade-responsabilidade.html

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to