Sorry
Would you be so kind as to explain your thinking.
How would upgrading Mysql fix the issue?
Regards
Brent Clark
On 20/04/2011 06:23, Suresh Kuna wrote:
Install the latest version of mysql on top of the current version and
start the database.
On Tue, Apr 19, 2011 at 9:34 PM, Brent
It will, try it out.
On Wed, Apr 20, 2011 at 1:11 PM, Brent Clark brentgclarkl...@gmail.comwrote:
Sorry
Would you be so kind as to explain your thinking.
How would upgrading Mysql fix the issue?
Regards
Brent Clark
On 20/04/2011 06:23, Suresh Kuna wrote:
Install the latest version
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
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
Thanks for replying
5.1.55
On 19/04/2011 13:55, Suresh Kuna wrote:
What is the version of MYSQL you are using currently ?
On Tue, Apr 19, 2011 at 3:46 PM, Brent Clark
brentgclarkl...@gmail.com mailto:brentgclarkl...@gmail.com wrote:
Ive added
innodb_force_recovery=4
Still no
Install the latest version of mysql on top of the current version and start
the database.
On Tue, Apr 19, 2011 at 9:34 PM, Brent Clark brentgclarkl...@gmail.comwrote:
Thanks for replying
5.1.55
On 19/04/2011 13:55, Suresh Kuna wrote:
What is the version of MYSQL you are using currently
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.
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
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
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 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]: ***
Heikki Tuuri wrote:
Baba,
an undo log seems to be corrupt. He should restart mysqld with:
innodb_force_recovery=4
dump all tables, and recreate the whole InnoDB installation.
This was roughly my assessment and recommended procedure as well. The
customer decided to restore the system from a full
Baba,
an undo log seems to be corrupt. He should restart mysqld with:
innodb_force_recovery=4
dump all tables, and recreate the whole InnoDB installation.
Did the .err log contain any hint what could be behind the corruption?
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and
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
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
This doesn't make much sense to me. By host server you mean your ISP?
If so how are you able to view the logs? Are you DB admin or something? By
the looks, someone is able to get in and shut it down. This can only happen
with admin rights or mysql server wasn't set up correctly in the first
26 matches
Mail list logo
