On 07/15/2013 07:54 AM, Luis H. Forchesatto wrote:
Greetings.
I'm receiving the following error log often on my MySQL database server:
[SNIP]
I suggest you report a bug as suggested.
--
Rares Aioanei
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscri
Greetings.
I'm receiving the following error log often on my MySQL database server:
130715 8:40:18InnoDB: Assertion failure in thread 2974165904 in file
btr0cur.c line 160
InnoDB: Failing assertion: page_is_comp(get_page) == page_is_comp(page)
InnoDB: We intentionally generate a memory trap.
Inn
ge-
From: Ben Clewett [mailto:b...@clewett.org.uk]
Sent: Tuesday, October 09, 2012 4:47 AM
To: mysql@lists.mysql.com
Subject: Query Cache Crashing
Hi MySql,
Since upgrading to 5.5.27 (5.5.27-ndb-7.2.8-cluster-gpl-log to be
exact) I have experienced problems with the query cache. I am
wondering if I a
a reproducible test case, submit to bugs.mysql.com .
> -Original Message-
> From: Ben Clewett [mailto:b...@clewett.org.uk]
> Sent: Tuesday, October 09, 2012 4:47 AM
> To: mysql@lists.mysql.com
> Subject: Query Cache Crashing
>
> Hi MySql,
>
> Since upgrading to 5.5.27 (5.5.
Hi MySql,
Since upgrading to 5.5.27 (5.5.27-ndb-7.2.8-cluster-gpl-log to be exact)
I have experienced problems with the query cache. I am wondering if I
am the only one?
Twice I have had a core-dump (show at end of mail) on two separate
servers running this version.
Now I had a complete l
Log sequence in the future means that, for whatever reason, the update in the
data pages
happened but update in the Innodb's log didn't.The InnoDB by itself,
without backups, is not
protected against media failures, and this happens to be just that.
Innodb_force_recovery is
not really a re
Am 06.11.2011 06:05, schrieb Kevin Wang:
> I stopped mysql only to find that it wouldn't come back up, /etc/init.d/mysql
> start only outputs . . . . . . failed. I've narrowed it down to an issue
> with InnoDB. The database starts when innodb_force_recovery = 5 and nothing
> lower. When I "check
I stopped mysql only to find that it wouldn't come back up, /etc/init.d/mysql
start only outputs . . . . . . failed. I've narrowed it down to an issue
with InnoDB. The database starts when innodb_force_recovery = 5 and nothing
lower. When I "check table" for my MyISAM tables, they check fine, but t
Okie cool, Can you paste the error log details when it came up with force
recovery 6.
On Wed, Apr 20, 2011 at 6:16 PM, Brent Clark wrote:
> On 20/04/2011 10:10, Suresh Kuna wrote:
>
>> It will, try it out.
>>
>
> Thanks for replying.
>
> My Colleague and I, we tried a different route.
>
> We retr
On 20/04/2011 10:10, Suresh Kuna wrote:
It will, try it out.
Thanks for replying.
My Colleague and I, we tried a different route.
We retried innodb_force_recovery.
But this time we started at 1 and progressed to 6.
At 6 we were able to able to start working.
So for our recovery procedure w
;> What is the version of MYSQL you are using currently ?
>>
>> On Tue, Apr 19, 2011 at 3:46 PM, Brent Clark
>> wrote:
>>
>>> Ive added
>>>
>>> innodb_force_recovery=4
>>>
>>> Still no go.
>>>
>>>
Ive added
innodb_force_recovery=4
Still no go.
Original Message
Subject:Mysql issue / crashing
Date: Tue, 19 Apr 2011 12:15:30 +0200
From: Brent Clark mailto:brentgclarkl...@gmail.com>>
To: mys
rently ?
>
> On Tue, Apr 19, 2011 at 3:46 PM, Brent Clark wrote:
>
>> Ive added
>>
>> innodb_force_recovery=4
>>
>> Still no go.
>>
>>
>> Original Message
>> Subject:Mysql issue / crashing
>> Dat
no go.
Original Message
Subject:Mysql issue / crashing
Date: Tue, 19 Apr 2011 12:15:30 +0200
From: Brent Clark mailto:brentgclarkl...@gmail.com>>
To: mysql@lists.mysql.com <mailto:mysql@lists.mysql.com>
Hiya
Im getting the following
I ran
What is the version of MYSQL you are using currently ?
On Tue, Apr 19, 2011 at 3:46 PM, Brent Clark wrote:
> Ive added
>
> innodb_force_recovery=4
>
> Still no go.
>
>
> Original Message
> Subject: Mysql issue / crashing
> Date: Tue, 19
Ive added
innodb_force_recovery=4
Still no go.
Original Message
Subject:Mysql issue / crashing
Date: Tue, 19 Apr 2011 12:15:30 +0200
From: Brent Clark
To: mysql@lists.mysql.com
Hiya
Im getting the following
I ran myisamchk --silent --force */*.MYI
But
Hiya
Im getting the following
I ran myisamchk --silent --force */*.MYI
But still I get the following.
I cant see how I can bring Mysql up.
# mysqld
110419 12:13:22 [Warning] 'for replication startup options' is
deprecated and will be removed in a future release. Please use ''CHANGE
MASTER''
No idea on the cause, but sitting with the exact same issue on 1 specific
MyISAM table on mysql-5.1.50
Since the table was created it never had any change in data structure, the
table is almost exclusively INSERTs and it is quite big in my instance
however. Table crashes on average every 2 to 3 d
Hi,
I have a very strange problem whereby one particular table in our
database is repeatedly (on average, every couple of days) generating
errors stating that the table is crashed and needs to be repaired.
Running a repair fixes it.
What makes it strange (and something that I've never encoun
On Fri, Aug 13, 2010 at 11:54:02AM -0700, Rob Wultsch wrote:
> # file /usr/local/mysql/bin/mysqld
> /usr/local/mysql/bin/mysqld: ELF 64-bit LSB executable, AMD x86-64,
> version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared
> libs), for GNU/Linux 2.4.0, not stripped
>
it is 64bit
On Fri, Aug 13, 2010 at 11:47 AM, Krishna Chandra Prajapati
wrote:
> Hi Yectli,
>
> I am talking about mysql server. Is it 32bit or 64bit.
>
> Provide some additional information. mysql configuration file, show
> variables, Error log file details etc.
>
> Kirshna
>
> On Fri, Aug 13, 2010 at 8:36 P
On Sat, Aug 14, 2010 at 12:17:20AM +0530, Krishna Chandra Prajapati wrote:
> Hi Yectli,
>
> I am talking about mysql server. Is it 32bit or 64bit.
>
> Provide some additional information. mysql configuration file, show
> variables, Error log file details etc.
>
> Kirshna
>
i provided the trace
Hi Yectli,
I am talking about mysql server. Is it 32bit or 64bit.
Provide some additional information. mysql configuration file, show
variables, Error log file details etc.
Kirshna
On Fri, Aug 13, 2010 at 8:36 PM, Yectli Huerta wrote:
> On Fri, Aug 13, 2010 at 04:33:38PM +0530, Krishna Chandr
On Fri, Aug 13, 2010 at 04:33:38PM +0530, Krishna Chandra Prajapati wrote:
> Hi Yectli,
>
> In mysql configuration file (my.cnf) you have given
>
> key_buffer_size = 5G
>
> For 32bit OS it should be less than or equal to 4GB and for 64bit it can be
> greater than 4GB.
> Reduce the key_buffer_siz
Hi Yectli,
In mysql configuration file (my.cnf) you have given
key_buffer_size = 5G
For 32bit OS it should be less than or equal to 4GB and for 64bit it can be
greater than 4GB.
Reduce the key_buffer_size to 3GB and try.
_Kirshna
On Fri, Aug 13, 2010 at 3:02 AM, Yectli Huerta wrote:
> Hello,
Hello,
I compiled a version of mysql 5.1.49 and it crashed a couple of times already.
I recompiled it with debug enabled and this is the error I got. Do any of
you guys/gals have any suggestions?
thanks,
this is from the trace file:
do_select: info: select cond 0xb7e088
do_select: info: select
Hi All,Sorry forgot to
mention subject in earlier message.I am running normal mysql and I
am trying to insert one entry in one database table.The logs
I am getting are as follows:-Version:
'5.1.38-community' socket: '/var/lib/mysql/mysql.sock' port: 3306
MySQL Community Server (GPL)091218 5:26:
I'm sorry for the delay in thanking those that offered help, I have not been
able to look at this problem for a day or so, but thank you. And Thank you
Martin for your note.
I have not backed up anything on this, however it was really just a practice
run, so I will not really lose anything, but
BTW, this is the error message that windows wanted to send to MS
C:\DOCUME~1\GARYPA~1\LOCALS~1\Temp\WERd238.dir00\mysqld.exe.mdmp
C:\DOCUME~1\GARYPA~1\LOCALS~1\Temp\WERd238.dir00\appcompat.txt
"Carlos Proal" wrote in message
news:4a58cb7c.4090...@gmail.com...
>
> Take a look on the my.ini to s
I dont see anything wrong, but then again I may not know wht to look for,
this is the my.ini file
# Example MySQL config file for small systems.
#
# This is for a system with little memory (<= 64M) where MySQL is only used
# from time to time and it's important that the mysqld daemon
# doesn't us
Take a look on the my.ini to see if there is something wrong (maybe a
path pointing to a missing place or memory setting bigger than your
actual RAM)
Carlos
On 7/11/2009 12:17 PM, Gary wrote:
Not sure if this is it, it was the only .err file that I have. Also this
seems to be the latest en
Not sure if this is it, it was the only .err file that I have. Also this
seems to be the latest entry that has a date.
Thanks for your help.
Gary
090617 21:50:45 - mysqld got exception 0xc005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the librarie
You have to take a look on the error log, a file named hostname.err
(hostname=your machine name) and should be located inside
the mysql dir on the xammp dir.
That file will give an insight about the problem, or you can post the
error here to get help.
Carlos
On 7/11/2009 11:52 AM, Gary wr
I have an issue that Mysql will not start on my local machine. I noticed a
few days ago on a restart that I got an error saying that Mysqld had
encountered a problem and had to close. I did not pay any attention to it
because I was not working in it for a bit.
I then tried to start it today and go
On Sun, Feb 15, 2009 at 1:43 PM, Martin Gainty wrote:
> Jason-
>
> can we see the schema and a few data rows for
> `soapware_charts_xmldocumentitems`
> says something about invalid pointers?
>
> Martin
>
Ok, I hope this is what you are wanting, I'm a newb.
schema: http://papernapkin.org/pas
>From what I read it is indeed a bug that was so far only found on 64
bits amd platform. Maybe it is not what is causing your problem, but
it is worth looking into :)
Walter
PS. Sorry for just posting a link in my last message. I was tired and
din't have much time :)
OlinData: Professional servi
On Sun, Feb 15, 2009 at 4:07 PM, Walter Heck wrote:
> http://bugs.mysql.com/bug.php?id=26081
>
Walter,
Thanks for replying. I read the bug and the comments. This seems to be a
problem on 64bit AMD hardware. Is this a correct assessment?
I'm using 2x Xeon quad core 64bit.
Thanks,
jd
of a confidential nature and Sender
> does not endorse distribution to any party other than intended recipient.
> Sender does not necessarily endorse content contained within this
> transmission.
>
>
>
>
>> Date: Sun, 15 Feb 2009 11:59:00 -0700
>> Subject:
business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
> Date: Sun, 15 Feb 2009 11:59:00 -0700
> Subject: DB cr
Hello,
I have been trying mysqldump with different switches to get my DB to dump.
All give me the same error (after dumping 218gigs) :
http://papernapkin.org/pastebin/view/4447/
Here is the command I'm currently trying..
mysqldump -A -q -v --lock-all-tables -u root -p --skip-extended-insert
--
intended
recipient. Sender does not necessarily endorse content contained
within this transmission.
> Date: Sun, 28 Dec 2008 19:27:45 -0600
> From: jrst...@barntowire.com
> To: mysql@lists.mysql.com
> Subject: mysqld-nt.exe crashing
>
> This is on my WinXP Media Center lapt
econd time.
Went back to my Drupal install, hit back and then saved my configuration
again. It couldn't connect to the server. I rebooted the computer, and
got a popup about mysqld-nt.exe crashing and did I want to report it to
Windows.
What do I do next? I still don't have a my.c
Hello,
our mysql 5.0.67 on a AMD Opteron 2218 with 2 GB RAM is crashing from
time to time.
This what is in the log:
081028 6:37:30 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt
ket: '/var/run/mysqld/mysqld.sock'
port: 3306 Debian etch distribution
As far as I understand, this means, that the MySQL Server crashed
and mysqld_safe noticed that and restarted it.
I also see much database corruption, but I somewhat run into a
chicken & egg problem here. I
e corruption, but I somewhat run into a
chicken & egg problem here. I don't know if the databases corruption
appeared first and led into the crashes or if the crashes led to the
corruption.
How can I investigate further into the problem? I don't think that a
perticular query
; egg problem here. I don't know if the databases corruption appeared
first and led into the crashes or if the crashes led to the corruption.
How can I investigate further into the problem? I don't think that a
perticular query is crashing the system, since all of our users just
run well
#x27;t know if the databases corruption appeared
first and led into the crashes or if the crashes led to the corruption.
How can I investigate further into the problem? I don't think that a
perticular query is crashing the system, since all of our users just run
well known apps like phpBB
We have MySQL 5.0.27 running on about 10 different RedHat EL4 boxes,
all from the same RPMs. Every night we run mysqladmin flush-logs from
crontab (as well as some other things) on most of these servers.
One on server, mysqld is dying with signal 11 every single night right
during the mysqladmin
:)
- Message d'origine
De : David Griffiths <[EMAIL PROTECTED]>
À : Julien Marchand <[EMAIL PROTECTED]>
Cc : mysql@lists.mysql.com
Envoyé le : Vendredi, 22 Juin 2007, 23h31mn 27s
Objet : RE: Re : InnoDB: Assertion failure - MySQL keeps crashing
It doesn't look like a
ust making informed guesses...
Let me know how it goes.
David
-Original Message-
From: Julien Marchand [mailto:[EMAIL PROTECTED]
Sent: June 22, 2007 12:43 PM
To: David Griffiths
Cc: mysql@lists.mysql.com
Subject: Re : InnoDB: Assertion failure - MySQL keeps crashing
Yes, and
I
d'origine
De : David Griffiths <[EMAIL PROTECTED]>
À : Julien Marchand <[EMAIL PROTECTED]>; mysql@lists.mysql.com
Envoyé le : Vendredi, 22 Juin 2007, 21h18mn 01s
Objet : RE: InnoDB: Assertion failure - MySQL keeps crashing
Did you see this part of the stack trace?
"I
InnoDB) are you allocating to the database?
Do you have enough memory on the machine?
David
-Original Message-
From: Julien Marchand [mailto:[EMAIL PROTECTED]
Sent: June 22, 2007 4:33 AM
To: mysql@lists.mysql.com
Subject: InnoDB: Assertion failure - MySQL keeps crashing
Hello,
L PROTECTED]>
Cc : mysql@lists.mysql.com
Envoyé le : Vendredi, 22 Juin 2007, 16h31mn 15s
Objet : Re: Re : InnoDB: Assertion failure - MySQL keeps crashing
I had this issue, so just wanted to know, even if you have the same error
message.
regards
anandkl
On 6/22/07, Julien Marchand <[EMAIL
EMAIL PROTECTED]>
À : Julien Marchand <[EMAIL PROTECTED]>
Cc : mysql@lists.mysql.com
Envoyé le : Vendredi, 22 Juin 2007, 13h45mn 12s
Objet : Re: InnoDB: Assertion failure - MySQL keeps crashing
Hi Julien,
Do you see any "InnoDB: using the same InnoDB data or log files.
>>
ertion failure - MySQL keeps crashing
Hi Julien,
Do you see any "InnoDB: using the same InnoDB data or log files.
>> InnoDB: Unable to lock /var/lib/mysql/ibdata1, error: 11
>> InnoDB: Check that you do not already have another mysqld process
>> InnoDB: using the same Inno
r log file. Was there any file system full issue.
On 6/22/07, Julien Marchand <[EMAIL PROTECTED]> wrote:
Hello,
My MySQL keeps crashing and restarting, and I get this log, which
repeats indefinitely:
Number of processes running now: 0
070622 13:01:46 mysqld restarted
Hello,
My MySQL keeps crashing and restarting, and I get this log, which repeats
indefinitely:
Number of processes running now: 0
070622 13:01:46 mysqld restarted
070622 13:01:46 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start
Tables frequently crashing on my site. Here is the message I'm seeing
*
Warning*: Table './mydb/sessions' is marked as crashed and should be
repaired query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid=
s.uid WHERE s.sid = '854c6474111de174abbddf77f74b9d99
Tables frequently crashing on my site. Here is the message I'm seeing
*
Warning*: Table './mydb/sessions' is marked as crashed and should be
repaired query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid=
s.uid WHERE s.sid = '854c6474111de174abbddf77f74b9d99
map.conf as per many FreeBSD/MySQL
advisories.
[mysqld]
libpthread.so.2 libthr.so.2
libpthread.so libthr.so
innodb engine status, never shows more then 10gb with change allocated.
The database keeps crashing, but does come back on line after rolling
back some transactions. I did a full databa
to InnoDB. We can't
> do that however on another server, which we turned debugging on
> instead. It appears to be an assertion failure, the error message from
> the MySQL debugging code is:
>
> Assertion failed: fixed == 1, file item.h, line 1601
>
>
> Any help is greatly
ixed == 1, file item.h, line 1601
Any help is greatly appreciated. Should we report this as a bug?
Any crashing is most certainly a bug, so if you could gather as much
information on this as possible and report a bug that would be great.
Please include:
o The full section of the error log
Hello,
We've been getting random crashes on our MySQL servers running MyISAM
tables for the last month, its gotten very bad in the last two weeks.
This has occurred on both 5.0.27, 5.1.11 and 5.1.15-nightly20070103.
It crashes the tables with high queries per second. We've fixed the
issue on one
I see several values set to '18446744073709551615', which is an
insanely large number for any memory setting (16.7 million terabytes
unless my math is wrong; huge in any case).
There was another person on the list earlier this year who had a
similar problem with large numbers, IIRC. I'd adjust t
Kevin Old wrote:
On 12/8/06, Philip Mather <[EMAIL PROTECTED]> wrote:
So something like 15G, that's not that bad. I'd run mtop as someone
suggested and see if some query is hammering it, maybe some other
process on the machine is hogging or going IO bound?
Thanks. We are watching the querie
On 12/8/06, Philip Mather <[EMAIL PROTECTED]> wrote:
So something like 15G, that's not that bad. I'd run mtop as someone suggested
and see if some query is hammering it, maybe some other process on the machine
is hogging or going IO bound?
Thanks. We are watching the queries. The pattern we
We have 16GB total, but are only using 8GB (according to mysql and our dbadmin).
Kevin
On 12/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
Thanks,
Jocelyn Fournier
www.me
[EMAIL PROTECTED] wrote:
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
min_memory_needed = global_buffers + (thread_buffers * max_connections)
thread_buffers
---+-
sort_buffer_size
Hi,
How much memory do you have on your system ? (the current setting in your
my.cnf could eat *a lot* of memory)
Thanks,
Jocelyn Fournier
www.mesdiscussions.net
> On 12/7/06, David Sparks <[EMAIL PROTECTED]> wrote:
>> Kevin Old wrote:
>> > Hello everyone,
>> >
>> > We have a 4 CPU master se
On 12/7/06, David Sparks <[EMAIL PROTECTED]> wrote:
Kevin Old wrote:
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 queries/per second and lately, the server will
> all of a s
Kevin Old wrote:
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 queries/per second and lately, the server will
> all of a sudden lock up and we are forced to restart mysql.
T
No backups (like innodb-backup) running during these times.
We have 16GB of RAM and are currently using about 8GB of it.
We think we might have narrowed it down to a few hellish queries that
are hitting a few tables that we recently converted to InnoDB from
MyISAM. We're gonna convert them back
RAM too, how are you on RAM?
Obviously 100GB+ probably isn't going to fit in cache, but the usage pattern
during slower periods might be causing killer thrashing.
On Thu, Dec 07, 2006 at 12:43:17PM -0600, Dan Buettner wrote:
> Another thought is - do you have backups running during this time?
> S
Another thought is - do you have backups running during this time?
Something that might be attempting to backup live the InnoDB files?
We had similar problems with MySQL and backup software a while ago,
though we used all-MyISAM.
Dan
On 12/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
Hi,
Do you use MySQL with a NPTL or a linuxthread glibc configuration ?
Regards,
Jocelyn Fournier
www.mesdiscussions.net
> Hello everyone,
>
> We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
> MySQL with a mix of InnoDB and MyISAM tables.
>
> We normally run at 1500 qu
Hello everyone,
We have a 4 CPU master server running the 5.0.27 RPM x86_64 version of
MySQL with a mix of InnoDB and MyISAM tables.
We normally run at 1500 queries/per second and lately, the server will
all of a sudden lock up and we are forced to restart mysql.
This is not related to higher l
has been crashing once every hour. Memory is not the issue. This is
how I start the mysql:
nohup /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql
--datadir=/usr/
local/mysql/var --user=mysql
--pid-file=/usr/local/mysql/var/admin.scholasticfun
dinggroup.com.pid --skip-locking
Looks like I have too many connections to the database. I made sure all the
connections are closed after use. Hope this is the fix. Anyone please confirm.
Thanks
murthy gandikota <[EMAIL PROTECTED]> wrote:
Can someone please help me figure out what's in this mysqld output befor
Can someone please help me figure out what's in this mysqld output before
crashing:
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can
Hi
Can someone tell me where in the file system to look for the logs?
Mysql has been crashing once every hour. Memory is not the issue. This is
how I start the mysql:
nohup /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql
--datadir=/usr/
local/mysql/var --user=mysql
--pid
Hi,
My mysql is crashing. Below table has the values it logs in the .err file
before restarting. I am using the large.cnf file.
The parameters I have changed are below. Rest are default values.
#for performance SSR
log=/var/log/mysql-queries.log
join_buffer_size=1M
max_connections=300
Quoting Mohammed Abdul Azeem ([EMAIL PROTECTED]):
> Then it hit a mysql bug with signal 6. The mysql db was throwing the
> following errors on the shell prompt ie the OS shell prompt.
I had exactly the same behaviour on MySQL 5.0.19 running on AMD64.
What helped in my case was re-creating all the
Hi,
Iam having a mysql version 5.0.15-standard-log installed on redhat es4.
It is configured as slave server. It was running fine till yesterday.
Then it hit a mysql bug with signal 6. The mysql db was throwing the
following errors on the shell prompt ie the OS shell prompt.
*** glibc detected **
Quoting Pete Harlan ([EMAIL PROTECTED]):
> > MySQL version 5.0.18
> > | Mar 14 00:32:59 zwart mysqld[29820]: *** glibc detected *** double
> > | free or corruption (!prev): 0x012b1ab0 ***
> You don't say which versions of glibc or the kernel you're running,
> but if you're r
On Tue, Mar 28, 2006 at 10:12:58AM +0200, Sander Smeenk wrote:
> Hello!
>
> I have a dual Opteron 250 system with 4GB memory running Debian with
> MySQL version 5.0.18 and unfortunately it keeps crashing at (somewhat)
> random intervals with messages like:
>
> | Mar 14
Hello!
I have a dual Opteron 250 system with 4GB memory running Debian with
MySQL version 5.0.18 and unfortunately it keeps crashing at (somewhat)
random intervals with messages like:
| Mar 14 00:32:59 zwart mysqld[29820]: *** glibc detected *** double
| free or corruption (!prev
I'm running a dual G5 xserve with OSXS 10.3.9. Mysql version 4.0.24
(the version that ships with the OS). For many months now mysql has
been stopping/crashing about twice a week. It's primary purpose in life
is to provide the database for a minimally used Horde webmail setup.
I
the problem still exists on the official binaries of the latest
>
> release. Have a look here as well:
>
> http://bugs.mysql.com/bug.php?id=15868
>
>
>
>
>
> sheeri kritzer wrote:
>
> > We're running MySQL version 4.1.12 on Fedora Core 3 64-bit. we&#
sheeri kritzer wrote:
> We're running MySQL version 4.1.12 on Fedora Core 3 64-bit. we've
> been crashing; here is a mysqld.err file from one crash:
>
> mysqld got signal 11;
> This could be because you hit a bug. It is also possible that this binary
> or one of
we've
been crashing; here is a mysqld.err file from one crash:
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly
built,
or misconfigured. This error can also be caused by malfunctionin
We're running MySQL version 4.1.12 on Fedora Core 3 64-bit. we've
been crashing; here is a mysqld.err file from one crash:
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improp
-linux-gnu-i686 (statically
linked version) to which I upgraded to just today from 4.0.2 because 4.0.2
seemed to be crashing randomly during some queries. The problem, however,
was not fixed with the update.
I'm running MySQL on a virtual server running Xen with 2.6.10-kernel. When
using for exa
Hmmm, I downloaded source and compiled, and had an instant segfault.
Rolled back to 4.1.11. I assumed it was something funky w/ my compile,
but after reading all the above posts ... ???
Mark Matthews wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donny Simonton wrote:
I'm not sure but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donny Simonton wrote:
> I'm not sure but I know when I installed it yesterday via RPM it kept core
> dumping and restarting. Glad I still had 4.1.11 available.
>
> Donny
Donny, Douglas,
Something goofy went on with the production of those RPMs for
l@lists.mysql.com
> Subject: Re: 4.1.12 Crashing on Mandrake 10.1
>
> Mark Hughes wrote:
>
> >
> >A lot of the RPM's for 4.1.12 seems to have been removed from the
> >download page so I presume there's a known problem:
> >
> >http://dev.mysql.com/
Mark Hughes wrote:
A lot of the RPM's for 4.1.12 seems to have been removed from the
download page so I presume there's a known problem:
http://dev.mysql.com/downloads/mysql/4.1.html
I noticed this when I just went to download 4.1.12. What's going on? Is
4.1.12 unstable or is this strictly a bu
On 5/18/05, Gleb Paharenko <[EMAIL PROTECTED]> wrote:
> Hello.
>
>
>
>
>
> > As a footnote to this the 4.1.12 build is significantly smaller, is
>
> > this expected?
>
>
>
> Check the md5 signature of your packages to be sure in its' origin.
>
> Search in the other rpm's for Linux x86. If
Hello.
> As a footnote to this the 4.1.12 build is significantly smaller, is
> this expected?
Check the md5 signature of your packages to be sure in its' origin.
Search in the other rpm's for Linux x86. If you'll be unable to find
mysqld.sym.gz for you distribution - switch to the debug
On 5/18/05, Mark Hughes <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I just upgraded from 4.1.11 (which worked fine, and stil does if I
> downgrade) to 4.1.12 and the first query crashes the server. This
> query is executed via DBD::mysql, when run via the mysql client it
> works OK though. I presume this
Hi,
I just upgraded from 4.1.11 (which worked fine, and stil does if I
downgrade) to 4.1.12 and the first query crashes the server. This
query is executed via DBD::mysql, when run via the mysql client it
works OK though. I presume this must be some library conflict but has
anyone got any idea what
1 - 100 of 265 matches
Mail list logo
