mailto:brentgclarkl...@gmail.com wrote:
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 brentgclarkl...@gmail.com
at 3:46 PM, Brent Clark
brentgclarkl...@gmail.comwrote:
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 brentgclarkl...@gmail.com
To: mysql
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
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 brentgclarkl...@gmail.comwrote:
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
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
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 brentgclarkl...@gmail.com
To: mysql@lists.mysql.com
Hiya
Im getting the following
I ran myisamchk
What is the version of MYSQL you are using currently ?
On Tue, Apr 19, 2011 at 3:46 PM, Brent Clark brentgclarkl...@gmail.comwrote:
Ive added
innodb_force_recovery=4
Still no go.
Original Message
Subject:Mysql issue / crashing
Date: Tue, 19 Apr 2011 12:15:30
no go.
Original Message
Subject:Mysql issue / crashing
Date: Tue, 19 Apr 2011 12:15:30 +0200
From: Brent Clark brentgclarkl...@gmail.com
mailto:brentgclarkl...@gmail.com
To: mysql@lists.mysql.com mailto:mysql@lists.mysql.com
Hiya
Im
?
On Tue, Apr 19, 2011 at 3:46 PM, Brent Clark brentgclarkl...@gmail.comwrote:
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 brentgclarkl...@gmail.com
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
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_size to 3GB
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 yhue...@msi.umn.edu wrote:
On Fri, Aug 13, 2010 at 04:33:38PM
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 tracefile
On Fri, Aug 13, 2010 at 11:47 AM, Krishna Chandra Prajapati
prajapat...@gmail.com 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,
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.
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:
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:
I tried something different:
This Server was acting as a slave before, so I removed all the Slave
stuff from it. Also mydns DNS Server was running, but i relocated it to
a different server.
Unfortunately I still get the same behavior:
# grep ' mysqld' /var/log/syslog
Oct 10 07:06:29 h1314631
Hey guys,
First of all: I have tried to post this Issue on forums.mysql.com, but
the Topic doesn't appear in the Forum. When I try to post again, it
tells me that it's a duplicate?!?!
Now the real problem:
I have MySQL set up on two Servers with 7000 Users each and about the
same amount of
I did some more research:
I ran xfs_check on the partition and it didn't report any errors at
all, so I'm guessing, that the hard drives are ok.
I also recompiled MySQL with --with-debug.
How would I get some debug output about the crashes now?
Thanks,
Samy
Samuel Vogel schrieb:
Hey guys,
Actually I have an somewhat reproducible test case.
Problem is, it only works on my Server.
When I start MySQL it crashes almost exactly after one minute. This
happens every single time:
Oct 7 21:41:04 h1314631 mysqld_safe[18591]: started
Oct 7 21:41:04 h1314631 mysqld[18594]: 071007
. 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
070622 13:01:46
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
: 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.
InnoDB: Unable to lock /var/lib/mysql/ibdata1, error
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
070622 13
@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 PROTECTED] wrote:
No, I don't have
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,
My MySQL keeps crashing
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?
It is possible that mysqld could use up to key_buffer_size +
(record_buffer
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 also saw InnoDB: Out of memory in additional
:)
- 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 memory issue, but only you
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 sudden
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 server running
[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
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
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
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
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
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
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
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,
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?
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
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.
That
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 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
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 running
on somewhat the same setup, same kernel,
same mysql version, same processors, only less memory (2GB). Is this
problem caused by bad memory? And if so, why does only mysql suffer from
it? I have perl processes running that take about the same amount of
memory as mysql does but yet only mysql keeps
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 00:32:59 zwart mysqld[29820]: ***
Sent: Wednesday, March 02, 2005 6:32 PM
Subject: mysql 4.0.18 crashing on startup
I've got a customer with a mysql that is crashing on startup. MySQL is
4.0.18 with InnoDB tables on a Linux 2.4.26 system. MySQL binaries are
Linux x86 glibc static gcc from mysql.com
Can anyone divine what might have
: mysql 4.0.18 crashing on startup
I've got a customer with a mysql that is crashing on startup. MySQL is
4.0.18 with InnoDB tables on a Linux 2.4.26 system. MySQL binaries are
Linux x86 glibc static gcc from mysql.com
Can anyone divine what might have happened to cause this?
thanks,
baba
I've got a customer with a mysql that is crashing on startup. MySQL is
4.0.18 with InnoDB tables on a Linux 2.4.26 system. MySQL binaries are
Linux x86 glibc static gcc from mysql.com
Can anyone divine what might have happened to cause this?
thanks,
baba
resolve_stack_dump gives:
0x8071f44
Hi All
I have written 2 scripts the first one which will ceate the schema and
second one will insert some rows into it.
The table type is BDB.
Scripts are something like this
SCRIPT 1
DROP TABLE IF EXISTS ROLE;
DROP DATABASE IF EXISTS ERECRUITER;
CREATE DATABASE ERECRUITER;
#Start using
Rajesh,
Wednesday, September 18, 2002, 9:32:29 AM, you wrote:
RK I have written 2 scripts the first one which will ceate the schema and
RK second one will insert some rows into it.
RK The table type is BDB.
RK Scripts are something like this
[skip]
RK If I run these scripts together
Hi all,
I've been trying to install version 4.0.3 of the new MySQL branch 4.0
but got a problem that I cannot seem to solve.
Installing MySQL 4.0.3, both in binary and source compilation, yields
always the following error when I try to visit a website written in PHP:
020912 09:46:19 mysqld
Description:
mysql-server cannot start on netbsd 1.6BETA1
How-To-Repeat:
upgrade to netbsd 1.6; cd /usr/pkgsrc/databases/mysql-server; make install
Fix:
no fix
Submitter-Id: submitter ID
Originator:Charlie
Organization:
MySQL support: [none | licence | email
Sorry for the ambiguity. My application is a gui application written in
Borland C++ Builder 6. It features one form with 4 buttons consisting of
Create, Connect, Disconnect, Destroy. Only the relevant buttons are
availible at certain times. (For instance, you cannot destroy a server
when one is
Hello to all!
I am currently working on a GUI Application in Borland C++ Builder, and
must use an embedded MySQL server in it. I am having difficulties,
however, because whenever I create an instance, and destroy it, then
try to make another instance of an embedded server, the second time it
I'm not sure if this has been reported earlier, but my mysql-server goes
down if I run a query with two 'match against' where one of them
contains/matches the word 'think'...
It terminates after the first query, but when I change the word 'think' to
'excel' or any other word it works flawlessy.
On Mon, Oct 01, 2001 at 04:41:58PM -0600, Spinlock wrote:
I was using gcc not g++
The guts of MySQL are written in C++, and hence the Gnu C++ compiler
will be used:
From the manpage gcc(1):
DESCRIPTION
The C and C++ compilers are integrated. Both process
input files
On Thu, Sep 27, 2001 at 07:19:02PM -0600, Spinlock wrote:
Hello. I am running mySQL 3.23.42 on FreeBSD 4.2.
I have compiled it with InnoDB and full debug to help figure out why it
keeps crashing. I've done a few core dumps and I'll paste 3 of them, it
keeps on crashing in the same function
I was using gcc not g++
---
Spinlock
Creator of EmpireQuest
http://www.empirequest.com
On Mon, 1 Oct 2001, Brian Reichert wrote:
On Thu, Sep 27, 2001 at 07:19:02PM -0600, Spinlock wrote:
Hello. I am running mySQL 3.23.42 on FreeBSD 4.2.
I have compiled it with InnoDB and full
will NOT occur if the database crashes...so
I can go back to him and prove he's lying to me.
Thanx,
Chuck
- Original Message -
From: Rolf Hopkins [EMAIL PROTECTED]
To: Chuck Lucas [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, June 11, 2001 01:55
Subject: Re: MySql keeps crashing
On Mon, Jun 11, 2001 at 02:13:25AM -0400, Chuck Lucas wrote:
Yes, host server means ISP.
I am able to view the logs because he lets me.
I agree with you, I think someone else is shutting down the
database, but he insists that my perl scripts are causing it to
crash. The only proof I
someone with the correct mysql root password could shut it down like
that. Are you able to check what cron jobs are running?
- Original Message -
From: Chuck Lucas [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 11, 2001 14:13
Subject: Re: MySql keeps crashing
Yes, host
Need a little assistance. I've looked through the current MySql manual, but
I can't find any information concerning my questions.
My MySql server keeps crashing, or that's what my host server tells me. He
claims that my scripts are crashing MySql. However, when I look at the
MySql error log
place.
I can't possibly see how SQL scripts could shutdown the server especially if
the server has been properly setup and secured.
- Original Message -
From: Chuck Lucas [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 11, 2001 12:03
Subject: help: MySql keeps crashing
Need
66 matches
Mail list logo