I have opened a bug about this issue: http://bugs.mysql.com/bug.php?id=44914
Joel
On Tue, May 12, 2009 at 10:55 PM, Joel Heenan jo...@planetjoel.com wrote:
Mysql List,
I have a crash that has occured a number of times on a production CentOS
4.4 machine. It occurs when using a product called
Mysql List,
I have a crash that has occured a number of times on a production CentOS 4.4
machine. It occurs when using a product called Interspire Email Marketer and
doing an import of some 30,000 email addresses. Unfortunately, I have not
been able to reproduce the crash myself (I have tried
David -
Sorry for the delayed response. ulimit is unlimited.
I am using the RPMs for RH EL3 downloaded from a
mirror so I would assumed they have been built to
allow 2GB archives.
I am most likely going a different route at this point
as my query response time is much too slow even with a
1GB
Hello.
It is strange for me that there isn't a stack trace. If you can
- switch to the debug version of MySQL and run it under gdb
to find out where it is crashing. See:
http://dev.mysql.com/doc/refman/5.0/en/crashing.html
http://dev.mysql.com/doc/refman/5.0/en/debugging-server.html
Marc:
Define crashing the server. Does the whole machine shut down? The
mysqld process? What do error logs say? What version of MySQL are
you using? What's the create table statement? what's the current
avg_row_length and max_rows? What is ulimit -f as the MySQL user say?
-Sheeri
On
: Marc Rossi [mailto:[EMAIL PROTECTED]
Sent: Thursday, 17 November 2005 3:16 PM
To: mysql@lists.mysql.com
Subject: mysqld crash with archive engine 2gb
I am trying to populate a table using the archive
engine that I estimate will take up ~ 8gb of disk
space when finished. Right now I am crashing
Is there any message in the log files? or any error
message from the OS?
David -
When the mysqld process restarts, there is nothing in
the logfile except the basic startup info. I have
listed it below:0:33).
051116 10:06:33 [Note] /usr/sbin/mysqld: ready for
connections.
Version:
); mysql@lists.mysql.com
Subject: Re: mysqld crash with archive engine 2gb
Is there any message in the log files? or any error
message from the OS?
David -
When the mysqld process restarts, there is nothing in
the logfile except the basic startup info. I have
listed it below:0:33).
051116 10
I am trying to populate a table using the archive
engine that I estimate will take up ~ 8gb of disk
space when finished. Right now I am crashing the
server as soon as my file gets to the 2gb mark. OS is
linux and there are other files on the same filesystem
that are 30gb+ so I know the fs has
]
Inviato: lunedi 14 giugno 2004 21.56
A: Leonardo Francalanci
Cc: [EMAIL PROTECTED]
Oggetto: Re: R: query string make mysqld crash (mysqld 4.0.20)
Leonardo Francalanci wrote:
I have a similar problem with a list of union(s) (see my email, one
hour before yours).
It seems
(
JobStatus = 'xyz'
)
;
This imply a mysqld crash (and restart) each time I run the request !
I encontred
PROTECTED]
Inviato: lunedi 14 giugno 2004 16.49
A: [EMAIL PROTECTED]
Oggetto: query string make mysqld crash (mysqld 4.0.20)
Hi,
Using Mysql 4.0.20-standard-log since a few days
I encontred an error that I had never seen before.
Here is what I have done :
1_ create an innodb table
Leonardo Francalanci wrote:
I have a similar problem with a list of union(s) (see my email, one
hour before yours).
It seems there is something in the way mysql parses the string
that makes it crash. I tried with version 4.1.2 as well, but
it keeps on crashing.
Due to the architecture of the
. The query always appears to run successfully after the restart.
Fix:
The automatic restart of mysqld solves the problem, however the
server going down is now my problem.
Submitter-ID: RustyShanklin
Organization: Pikeville Medical Center
MySQL support: NONE
Synopsis: mysqld crash - Possible
Description:
I'm experiencing a Linux-related only problem with a simple UDF which call
mysql_real_connect()
How-To-Repeat:
A very simple function:
#include stdio.h
#include stdlib.h
#include string.h
Abdulla,
- Original Message -
From: Paizulaev Abdula [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Monday, April 05, 2004 7:43 AM
Subject: mysqld crash, got following
InnoDB: Error: record field 3 len 4294967207
Heap no too big 5888 93
Error in page 117145 in index
InnoDB: Error: record field 3 len 4294967207
Heap no too big 5888 93
Error in page 117145 in index PRIMARY
Record has 654 fields, should have 24
InnoDB: record RECORD: info bits 0 0:
040405 8:36:56 InnoDB: Assertion failure in thread 9226 in file
../include/page0page.ic line 482
InnoDB: We
Hi!
On Jan 12, Holm Tiffe wrote:
Description:
mysqld 4.0.17 crash on FreeBSD 5.1-current-alpha
How-To-Repeat:
Any acces over IP (not domain socket) crashes mysqld:
#/usr/local/bin/mysqladmin: connect to server at 'install' failed
error: 'Lost connection to MySQL server during query'
Hi!
On Jan 12, Holm Tiffe wrote:
Description:
mysqld 4.0.17 crash on FreeBSD 5.1-current-alpha
How-To-Repeat:
Any acces over IP (not domain socket) crashes mysqld:
#/usr/local/bin/mysqladmin: connect to server at 'install' failed
error: 'Lost connection to MySQL server during query'
several versions of mysql, all with the same result.
PostgreSQL is running fine on this machine.
Fix:
none known
Submitter-Id: holm
Originator:Holm Tiffe
Organization:
FreibergNet Internet Systems
MySQL support: none
Synopsis: mysqld Crash on FreeBSD Alpha
Severity: critical
Description:
Upon starting mysql client with the following command:
mysql -ppassword radiant
Immediately error message where displayed, one per table, saying that
the table existed, however no columns/fields where found.
Unfortunately I do not have the
]
Newsgroups: mailing.database.myodbc
Sent: Friday, October 03, 2003 4:24 PM
Subject: mysqld crash
Description:
Upon starting mysql client with the following command:
mysql -ppassword radiant
Immediately error message where displayed, one per table, saying that
the table existed, however no columns
our current situation is a mysqld crash, it hits an assertion
in my_seek.c.
Assertion failed: pos != (~(my_off_t) 0), file
c:\build\build\mysql-4.0.14\mysys\my_seek.c, line 31
This is with a myisam table containing variable length text fields.
I'm not expecting any solution from this list
Hi,
I downloaded and compiled mysql 4.0.9 gamma this morning, and
still get the same error. This doesn't seem to be related to reverse
DNS. I've got the crash from both types of client hosts (with and without reverse).
The official 4.0.9 binary version seems to work well.
What did I miss ?
At 17:13 16/01/2003 +0100, JC wrote:
Hi,
Hi,
I downloaded and compiled mysql 4.0.9 gamma this morning, and
still get the same error. This doesn't seem to be related to reverse
DNS. I've got the crash from both types of client hosts (with and without
reverse).
Was found that for some GLIBC
Description:
MySQL 4.0.8, both compiled my me and the official release version
crashes whenever receiving a network connection from a system without a DNS
entry. Connecting from a system that resolves on reverse (eithor from DNS
or a local hosts file entry) works find. This system is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher E. Brown wrote:
Description:
MySQL 4.0.8, both compiled my me and the official release version
crashes whenever receiving a network connection from a system without a DNS
entry. Connecting from a system that resolves on reverse (eithor
Diana Soares wrote:
Hi, just sending a reply in case that someone else has the same problem.
I solved the problem by decreasing the key-buffer from 320M to 288M.
We tried that among many other things. It turns out that their is some
kind of problem related to temporary tables. MySQL AB is
Hi, just sending a reply in case that someone else has the same problem.
I solved the problem by decreasing the key-buffer from 320M to 288M.
On Wed, 2002-07-03 at 12:24, Diana Soares wrote:
Hi,
I have 2 machine dual-processor Pentium III, with 1G of memory.
They have the same software,
On Fri, 2002-07-26 at 18:43, Mike Wexler wrote:
Diana Soares wrote:
Hi, just sending a reply in case that someone else has the same problem.
I solved the problem by decreasing the key-buffer from 320M to 288M.
We tried that among many other things. It turns out that their is some
Diana Soares wrote:
On Fri, 2002-07-26 at 18:43, Mike Wexler wrote:
Diana Soares wrote:
Hi, just sending a reply in case that someone else has the same problem.
I solved the problem by decreasing the key-buffer from 320M to 288M.
We tried that among many other things. It
Hi,
I have 2 machine dual-processor Pentium III, with 1G of memory.
They have the same software, same architecture, with one-way replication
beetween. Versions:
[root@localhost tmp]# mysql -V
mysql Ver 11.18 Distrib 3.23.51, for pc-linux-gnu (i686)
[root@localhost tmp]# cat /etc/redhat-release
Diana,
Wednesday, July 03, 2002, 2:24:51 PM, you wrote:
DS I have 2 machine dual-processor Pentium III, with 1G of memory.
DS They have the same software, same architecture, with one-way replication
DS beetween. Versions:
DS [root@localhost tmp]# mysql -V
DS mysql Ver 11.18 Distrib 3.23.51,
Hi,
I'm trying to make use of the new(ish) merge table
type, and am running into two problems. The first is
unexpected behaviour, the second is a straight MySQL
server crash. I have tested 3.23.47, 3.23.49 and
3.23.51 with similar results. Details below refer to
3.23.51. I have also tested on
I just attempted to upgrade a 3.23.41-max server on Linux 2.4.12 to
3.23.47-max. Before starting up 3.23.47-max, I added several Innodb
options to the my.cnf file:
---snip---
innodb_data_file_path = ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata4:2000M
innodb_data_home_dir =
Hi!
InnoDB seems to have created the database and started ok. This does not look
like an InnoDB bug.
I think gethostbyaddr asks from a connection the hostname, and subsequent
code checks that the host has access rights to mysqld.
For some reason gethostbyaddr_r crashes.
Hmm.. if you could run
-
From: Sinisa Milivojevic [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, February 04, 2002 1:27 PM
Subject: Re: mysqld crash stack trace from 3.23.47-max (with InnoDB)
Jeremy Zawodny writes:
I just attempted to upgrade a 3.23.41-max server on Linux 2.4.12
jocelyn fournier writes:
Hi,
About glibc, I saw the 2.2.5 release included the spinlock.c patch, part of
the internals.h (except the following part :
-#define STACK_SIZE (2 * 1024 * 1024)
+#define STACK_SIZE (128 * 1024)
)
The local_lim.h is also partially patched :
The following
Subject: Re: mysqld crash stack trace from 3.23.47-max (with InnoDB)
jocelyn fournier writes:
Hi,
About glibc, I saw the 2.2.5 release included the spinlock.c patch, part
of
the internals.h (except the following part :
-#define STACK_SIZE (2 * 1024 * 1024)
+#define STACK_SIZE (128 * 1024
On Mon, Feb 04, 2002 at 02:27:01PM +0200, Sinisa Milivojevic wrote:
Jeremy,
It could also be a bug in glibc.
As you are using Linux, can you try out binary ??
That was your binary on Linux.
Strangely, I just started up that exact same copy of 3.23.47-max and
it worked fine after a
On Monday 04 February 2002 02:30 am, Jeremy Zawodny wrote:
0x807bb5f handle_segfault__Fi + 383
0x82a94aa pthread_sighandler + 154
0x7cb80076 __evoke_link_warning_llseek + 1954074198
0x7cb7fe19 __evoke_link_warning_llseek + 1954073593
0x7cb713e6 __evoke_link_warning_llseek + 1954013638
Jeremy Zawodny writes:
On Mon, Feb 04, 2002 at 02:27:01PM +0200, Sinisa Milivojevic wrote:
That was your binary on Linux.
Strangely, I just started up that exact same copy of 3.23.47-max and
it worked fine after a machine reboot.
That's most unusual (and troubling).
Thanks,
On Mon, Feb 04, 2002 at 07:15:33PM +0200, Sinisa Milivojevic wrote:
Yes, this is troubling ...
It could be hardware, though ...
Can you find anything in MySQL log and especially in /var/log/dmesg
or /var/log/messages.
Nope.
Sometimes, not often, Linux kernel is capable of noticing
On Monday 04 February 2002 11:59 am, Jeremy Zawodny wrote:
?This does look like a libc bug. How did you build either one of the
binaries?
They're your binaries. ?I don't buld my own binaries on Linux to save
the hassle of using libraries that are different from what you folks
use. :-)
On Mon, Feb 04, 2002 at 02:33:40PM -0700, Sasha Pachev wrote:
On Monday 04 February 2002 11:59 am, Jeremy Zawodny wrote:
?This does look like a libc bug. How did you build either one of the
binaries?
They're your binaries. ?I don't buld my own binaries on Linux to save
the hassle of
]
Description:
Crash with full /tmp
How-To-Repeat:
Fill up /tmp and allow mysqld to continue running
Fix:
Don't fill up /tmp
Submitter-Id: submitter ID
Originator:Mercury Admin
Organization:
Infinity Solutions
MySQL support: [none at the moment
Synopsis: mysqld crash on full
Originator: Mercury Admin
Organization:
Infinity Solutions
MySQL support: [none at the moment
Synopsis:mysqld crash on full /tmp
Severity:critical
Priority:medium
Category:mysql
Class: sw-bug
Release: mysql-3.23.40 (Source distribution)
Server: /usr/local
Heikki,
Mysql-3.23.36, Solaris 2.8.
My mysqld crashes when I create a TEMPORARY InnoDB table from the console
if I do a SELECT COUNT(*) before exiting from the console.
No problem with MyISAM tables, no problem with no TEMPORARY table.
mysql CREATE TEMPORARY TABLE mybuffer ( id int
Alex,
MySQL obviously tries to drop the table when you exit
from the mysql client, since the table is temporary.
I have not tested TEMPORARY tables. I just tried on prerelease .38 and
it does not work in that version either.
I will fix it in .38 if Monty has not yet put out it.
Regards,
Heikki sent his response to the wrong address...
-- Forwarded Message --
Subject: Re: TEMPORARY + InnoDB + select coun(*) + Bye = mysqld crash
Date: 25 Apr 2001 17:18:06 -
From: Heikki Tuuri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Alex,
MySQL obviously tries to drop
January 12, 2001 1:31
Subject: index corruption and mysqld crash
Hello,
I have switched this morning our Web server from mSQL to MySQL.
I am using MySQL 3.22.32 installed from MySQL-3.22.32-1.i386.rpm
on a Linux server (RedHat 6.2).
mysqld dies very ofen (uptime is between 2mn and 20mn)
I can think of only one suggestion. See if there is a cron job or something
killing a process. I doubt it though. Hope it helps.
- Original Message -
From: "Joseph Bueno" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 12, 2001 1:31
Subject: index corruption
52 matches
Mail list logo
