> -Original Message-
> From: Halász Sándor [mailto:h...@tbbs.net]
> Sent: Tuesday, October 11, 2011 9:28 PM
> To: mysql@lists.mysql.com
> Subject: Vista crashes
>
> I find that, when under Vista the MySQL daemon has been shut down
There's your first two
so why do you search a list of known bugs instead update your mysql?
5.5.8 is the FIRST ga version of 5.5
currently we have 5.5.16
no, i do not know if 5.5.16 is solving your problem but hwat i know
is that the updates were bot relöeased just for fun
Am 12.10.2011 06:28, schrieb Hal?sz S?ndor:
>
I find that, when under Vista the MySQL daemon has been shut down, by giving
the command
start mysqld -b"%CD%"
in the root directory where MySQL 5.5.8 (the version running on this computer)
has been stored from an instance of command prompt with administrator authority
issued by a user that lack
Hi.
Can you show me some of your critical system logs?
David Yeung, In China, Beijing.
My First Blog:http://yueliangdao0608.cublog.cn
My Second Blog:http://yueliangdao0608.blog.51cto.com
My Msn: yueliangdao0...@gmail.com
2010/12/7 Raj Shekhar
> In infinite wisdom Basil Daoust wrote:
>
> >
In infinite wisdom Basil Daoust wrote:
> Any help greatly appreciated.
>
> Our mysql is restarting a LOT!
> Here is what is in the log, it doesn't seem to give much help.
>
Do you have the coredump from this crash? If yes, can you load the core
dump into gdb and run "bt" (backtrace) and see w
On Fri, December 3, 2010 14:11, Basil Daoust wrote:
> Any help
greatly appreciated.
>
> Our mysql is restarting a
LOT!
> Here is what is in the log, it doesn't seem to give much
help.
>
> --start of log--
> InnoDB: Warning: a
long semaphore wait:
> 101203 15:12:40 - mysqld got signal 11;
> This
Any help greatly appreciated.
Our mysql is restarting a LOT!
Here is what is in the log, it doesn't seem to give much help.
--start of log--
InnoDB: Warning: a long semaphore wait:
101203 15:12:40 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or
Hi
My mysql server suddenly crashed. Not it does not start and dumps the
following stack trace. I suspect some table corruption. Please help me to
start it.
stack_bottom = (nil) thread_stack 0x4
/usr/sbin/mysqld(my_print_stacktrace+0x24) [0x84fd84]
/usr/sbin/mysqld(handle_segfault+0x320) [0x5
you can stop your Mysql server (the program) and delete the file mysql.sock
and the try to start.
2010/6/21 Tyler Poland
> Charlene,
>
> You should check the mysql error log and if there isn't a message about the
> cause there you may want to check /var/log/syslog for mysql being killed by
>
Charlene wrote:
Anybody have any idea why MySQL would start to have this error message
every 4 or so days at midnight:
Do look at the logs, but if the error always occurs at midnight, you
might look for a disk backup or compression program that's scheduled
to run than and accesses the databas
Charlene,
You should check the mysql error log and if there isn't a message about
the cause there you may want to check /var/log/syslog for mysql being
killed by oomkiller.
Tyler
On 6/21/10 11:11 AM, Charlene wrote:
Anybody have any idea why MySQL would start to have this error message
ever
Anybody have any idea why MySQL would start to have this error message
every 4 or so days at midnight:
Connection error: Can't connect to local MySQL server through socket
'/var/lib/mysql/mysql.sock' (2)
This just started happening a little more than 2 weeks ago. The server
has been running
sley Wajon [mailto:wes...@oktober.nl]
Sent: Monday, February 15, 2010 6:30 AM
To: mysql@lists.mysql.com
Subject: Mysql crashes, do not understand backtrace
On one of the servers we maintain mysql recently crashed.
In safe mode (innodb_force_recovery = 4) it runs but then you can't do
any m
On one of the servers we maintain mysql recently crashed.
In safe mode (innodb_force_recovery = 4) it runs but then you can't do
any mutations to the databases.
When we try to start it in normal mode it crashes and we do not really
understand the backtrace.
We eventually ended up in flu
09-12-19 at 10:11 +0530, Kurian Thayil wrote:
> Hi,
>
> Installed compiled mysql-5.1.31 in a centOS 4.4 box. When tried to
> execute an insert query I get Error 2013. In fact mysql server crashes
> and restarts.
>
> mysql> INSERT INTO `sessi
Hi,
Installed compiled mysql-5.1.31 in a centOS 4.4 box. When tried to execute
an insert query I get Error 2013. In fact mysql server crashes and restarts.
*mysql> INSERT INTO `session_table` VALUES
(2,'2',122,'38507720d9d18aede22a2346571a35e7','2009-03-18 10:50:57
ty to Win | Act with Sensitivity | Unyielding
Integrity
From: Amarnath Shivashankar (WI01 - Services)
Sent: Tuesday, October 23, 2007 11:40 AM
To: 'mysql@lists.mysql.com'
Subject: Table crashes
Hi Friends,
I need a document on why tables crash in
edures.
good application + DB design/descent HW sizing and great monitoring
will help reduce the crashes
If you do some more research on this topic you can figure out some
reasons and some pointers to avoid failures.
Regards,
Ranjeet Walunj
>
> Hi Friends,
>
>
>
>
From: Amarnath Shivashankar (WI01 - Services)
Sent: Tuesday, October 23, 2007 11:40 AM
To: 'mysql@lists.mysql.com'
Subject: Table crashes
Hi Friends,
I need a document on why tables crash in MYSQL and what are the repair
methods?
I would also like to know if there are any
Hi Friends,
I need a document on why tables crash in MYSQL and what are the repair
methods?
I would also like to know if there are any preventive measures to avoid
table crashes?
Regards,
Amarnath Shivashankar
SQL Database Management
The information contained in this electronic
am looking for some help on my mysql server crashes.
>
> I run version 5.0.27 on Fedora 6.
>
> However, suddenly mysql server starting crashing. I revised the log
> and it is telling me that is having a input/output operating system
> error on a read operation.
>
>
Hello everybody,
I am looking for some help on my mysql server crashes.
I run version 5.0.27 on Fedora 6.
However, suddenly mysql server starting crashing. I revised the log
and it is telling me that is having a input/output operating system
error on a read operation.
The error shows up like
ntentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev
We've been running mysql 4.1.11 on our sparc solaris 8 (it's a
12 proc Sun 4800) for over a year without problems, but we just
ran into a known innodb bug, so I decided to upgrade to 5.x.
I tried the regular 5.0.24 SPARC 64-bit Solaris 8 package,
the 5.0.24 debug package, the 5.1.11 package, and
On Tue, Jun 13, 2006 at 08:55:59AM +0200, Wouter de Jong wrote:
> The symptoms are that MySQL is constantly (eg. within every 30 minutes)
> getting signal 11's according to the logfile, and is restarting.
Problem finally tracked down and filed bug report.
Regards,
--
WideXS
e
SRPM with --with-debug=full
When running this, I got no crash... but couldn't run it too long, since
the machine became very slow and a lot of clients could no longer connect
after sometime due to timeout.
When running with --skip-safemalloc I got the crashes as well.
I'm running
Hi,
This might be a bug try to create mysql stack trace file and find out
what is causing for mysql
crash, this might be a query hitting mysql and also memory related
issues.Try to upgrade your
mysql and report back.
Daniel da Veiga wrote:
On 6/7/06, Ian Collins <[EMAIL PROTECTED]> wrote:
On 6/7/06, Ian Collins <[EMAIL PROTECTED]> wrote:
I have a site running MySQL 4.1.19.
When I was first given the problem, the site only stayed up for a couple
of days - they then found they had to reboot (as opposed to just
restarting MySQL).
The error message they were getting is below (between
I have a site running MySQL 4.1.19.
When I was first given the problem, the site only stayed up for a couple
of days - they then found they had to reboot (as opposed to just
restarting MySQL).
The error message they were getting is below (between the snip's).
After looking at the site, I alter
On 5/12/06, sheeri kritzer <[EMAIL PROTECTED]> wrote:
So, our MySQL master database crashes about once a week, then
immediately recovers. We are running a Dell 2850 -- 64-bit Fedora Core
3 box with 6G of memory, 4 Intel Xeon processors, at 3.60 GHz speed
each (says /proc/cpuinfo), each cpu
So, our MySQL master database crashes about once a week, then
immediately recovers. We are running a Dell 2850 -- 64-bit Fedora Core
3 box with 6G of memory, 4 Intel Xeon processors, at 3.60 GHz speed
each (says /proc/cpuinfo), each cpu cache size is 2048 Kb. It
replicates to 2 slaves, which have
Hello;
I have tried to build and install MySQL v5.0.18 on FreeBSD v6.0 RELEASE
running on AMD 64 socket 939
w/Gigabyte motherboard.
I have tried this twice and the same message occurs. Premission denied
to creat/write .pid file.
The strange thing is that I did this on another FreeBSD v6.0 runni
On 9/03/2006 9:43 a.m., Kishore Jalleda wrote:
could you tell us if these 6 are in a cluster or in a replication set up,
and u also said the 3 linux bixes all crash at once, did u check the logs,
do they crash under load, what about the OS, is it stable when mysql
crashes
Kishore Jalleda
06 11:38 PM
To: Dave Pullin
Cc: mysql@lists.mysql.com
Subject: Re: Signal 11 crashes on MySQL V5
Dave
What common transaction you have? INSERT? SELECT? UPDATE? DELETE? Are
you using InnoDB?
I have my personal experience with InnoDB and MySQL 5,
with kernel 2.4 (as you use on RedHat 9) MySQL 5 is u
Dave
What common transaction you have? INSERT? SELECT? UPDATE? DELETE? Are
you using InnoDB?
I have my personal experience with InnoDB and MySQL 5,
with kernel 2.4 (as you use on RedHat 9) MySQL 5 is unstable on high
load insert/update/delete
with kernel 2.6 (CentOS, Fedora, ...) you'll get m
we were seeing the same thing with 5.0. We had to roll back to 4.1
the other day, 5.0 was just too unstable.
I haven't reported a bug though because I couldn't narrow down the cause
of the problem. Just seemed to be random crashes, several times per day
(more often when under load).
could you tell us if these 6 are in a cluster or in a replication set up,
and u also said the 3 linux bixes all crash at once, did u check the logs,
do they crash under load, what about the OS, is it stable when mysql
crashes
Kishore Jalleda
On 3/8/06, Dave Pullin <[EMAIL PROTECTED]>
I am running MySQL on 6 servers - 3 Linux and 3 Windows. I recently upgraded
to V5 on all servers. Now MySQL is crashing regularly (several times per
day, some days) with 'got signal 11'.
My 3 Linux servers are very different machines running different software
a uniprocessor Pentium with 512MB ru
I have a problem where i think some of my tables have somehow been
corrupted, if i try to run a check table command against some
tables the
mysql service crashes and i have to restart it. I am not sure
how this
damage has occurred but has anyone got any suggestions of what to
apar
TED]> wrote:
HI
MySQL 5.0 (windows XP)
I have a problem where i think some of my tables have somehow been
corrupted, if i try to run a check table command against some tables the
mysql service crashes and i have to restart it. I am not sure how this
damage has occurred but has anyone g
On 1/31/06, Adrian Bruce <[EMAIL PROTECTED]> wrote:
> HI
>
> MySQL 5.0 (windows XP)
>
> I have a problem where i think some of my tables have somehow been
> corrupted, if i try to run a check table command against some tables the
> mysql service crashes and i have to
rvard
>MySQL 5.0 (windows XP)
>
>I have a problem where i think some of my tables have somehow been corrupted,
>if i try to run a check table command against some tables the mysql service
>crashes and i have to restart it. I am not sure how this damage has occurred
>
HI
MySQL 5.0 (windows XP)
I have a problem where i think some of my tables have somehow been
corrupted, if i try to run a check table command against some tables the
mysql service crashes and i have to restart it. I am not sure how this
damage has occurred but has anyone got any
Original Message-
> From: ESV Media GmbH [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 14, 2006 4:27 PM
> To: mysql@lists.mysql.com
> Subject: Reload Problem -> "Mass-Reload" crashes DB
>
> Thanks for your quick reply.
>
> Thanks a lot for your help
Thanks for your quick reply.
We use PHP.
I´ll try it with mysql_pconnect();
I´ve already thought about it.
What happens, when we´ve several 1000 Users online. Doesn´t it open too
many connections ?
mysql_connect closes every connection after using.
Does mysql_pconnect() the same ?
Thanks a lot
phone: +49 941 / 78 88 7-121
AG Regensburg HRA 6608 USt.183/68311 cellphone: +49 171 / 40 54 777
--
> -Original Message-
> From: ESV Media GmbH [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 14, 2006 12:06 PM
> To: mysql@lists.mysql.com
> Subject: Reload Pro
Hey,
we´ve on 2 website the problem, that if you hit a several times F5 or
hold it down to reload the site,
MySQL opens many connections and breaks down after a while.
How can we prevent this ?
I close every MySQL Session and i do an if-statement ( if there´s any
open connect ) before i open a
.database.myodbc
Sent: Wednesday, January 11, 2006 2:13 PM
Subject: Mysql Server crashes saying Page directory corruption
Hi all,
Server version :4.0.26
OS: FeeBSD-4.10
The mysql server(slave) crashes with the following messages in its error
log, and gets restarted, after which rollbacks and st
Hi all,
Server version :4.0.26
OS: FeeBSD-4.10
The mysql server(slave) crashes with the following messages in its error
log, and gets restarted, after which rollbacks and starts replicating from
master
Page directory corruption: supremum not pointed to
051226 10:02:58 InnoDB: Page
- Original Message - From: "Heikki Tuuri"
<[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, December 16, 2005 3:46 PM
Subject: Re: CPU 100% + crashes ...
Dilipan,
thank you.
I think there indeed is a slight unprotected access in:
> 0x8158a17 inn
day, December 16, 2005 3:46 PM
Subject: Re: CPU 100% + crashes ...
Dilipan,
thank you.
I think there indeed is a slight unprotected access in:
> 0x8158a17 innobase_mysql_print_thd + 471
We will investigate if it has been fixed in 4.1.xx.
Again, SHOW INNODB STATUS\G shows a very light load insid
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up
MyISAM tables
http://www.innodb.com/order.php
Dilipan Sebastiampillai wrote:
can you please post the complete .err log that also contains
information about the c
can you please post the complete .err log that also contains
information about the crashes. If there are stack traces, please
resolve them
iencing some load problems couple with crashes.
>
> The load ( around 5-7 ) is due, according to vmstat, to processes
> waiting for the CPU. And it makes sense because the CPU is used 100%
> most of the time.
> Nearly all tables are Innodb ( 3 tables of 1kb are MyIsam ). Aroun
Dilipan,
can you please post the complete .err log that also contains information
about the crashes. If there are stack traces, please resolve them.
The workload inside InnoDB does not look that big if what you have posted is
a typical SHOW INNODB STATUS\G. Is that the case?
What does
Hi all,
We have a MySQL server used for a queueing system. It worked fine so far
but now we are experiencing some load problems couple with crashes.
The load ( around 5-7 ) is due, according to vmstat, to processes
waiting for the CPU. And it makes sense because the CPU is used 100%
most of
ady there, my client
crashes. Is there an error I can trap for this? The DB does insert the
new record.
Bruce Martin
The Martin Solution
PO Box 644
Delaware Water Gap, PA
(570) 421-0670
[EMAIL PROTECTED]
--
For technical support contracts, goto
https://order.m
hat is identical to a record already there, my client
> crashes. Is there an error I can trap for this? The DB does insert the
> new record.
>
> Bruce Martin
> The Martin Solution
> PO Box 644
> Delaware Water Gap, PA
> (570) 421-0670
> [EMAIL PROTECTED]
&g
OTECTED]>
To:
Sent: Sunday, November 13, 2005 3:58 PM
Subject: Duplicate Insert Crashes Client
Hello again,
Ok new problem. If for some reason, my client tries to INSERT something to
the database that is identical to a record already there, my client
crashes. Is there an error I can trap f
Hello again,
Ok new problem. If for some reason, my client tries to INSERT something
to the database that is identical to a record already there, my client
crashes. Is there an error I can trap for this? The DB does insert the
new record.
Bruce Martin
The Martin Solution
PO Box 644
Delaware
Hello.
> nm: /usr/sbin/mysqld: no symbols
It seems strange because of your version - 4.1.14-debug-log.
Get MySQL which has symbols. See:
http://dev.mysql.com/doc/refman/5.0/en/compiling-for-debugging.html
Don Doumakes wrote:
> Gleb Paharenko wrote:
>
>> Follow links which have
Gleb Paharenko wrote:
Follow links which have been meant in the error log. Resolve the
stack trace and send it to the list. See:
http://dev.mysql.com/doc/refman/5.0/en/crashing.html
I of course attempted to do that before asking for help. Though I
compiled mysql with debug enabled, there
sqld daemon, it crashes and restarts itself, which just doesn't
> seem right. I enter these commands:
>
> cd /usr; /usr/bin/mysqld_safe &
> mysqladmin -u root password 'foobar'
>
> and get this response:
>
> mysqladmin: connect to server at
I'm installing MySQL 4.1.14 on a new Gentoo box. When I try to connect
to the mysqld daemon, it crashes and restarts itself, which just doesn't
seem right. I enter these commands:
cd /usr; /usr/bin/mysqld_safe &
mysqladmin -u root password 'foobar'
and get th
Deva,
hmm... this is mysterious. This might also be an OS bug. If you have the
.err log from other crashes, please send it to [EMAIL PROTECTED]
Best regards,
Heikki Tuuri
Vice President, server technology
Oracle Corp.
- Original Message -
From: "Devananda" <[EM
Heikki Tuuri wrote:
Deva,
it is probably this insert operation that is stuck, and is holding an
S-latch of an index tree in emails_history_30_30:
---TRANSACTION 0 1856588555, ACTIVE 858 sec, process no 1792, OS thread
id 2445845440 inserting, thread declared inside InnoDB 318
mysql tables in
- Original Message -
From: "Devananda" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, October 06, 2005 11:02 PM
Subject: Re: crashes in InnoDB with MySQL 4.1.14 (semaphore wait timeout)
Heikki Tuuri wrote:
Deva,
please post those transactions which have
abase.myodbc
Sent: Thursday, October 06, 2005 10:14 AM
Subject: Re: crashes in InnoDB with MySQL 4.1.14 (semaphore wait timeout)
Heikki Tuuri wrote:
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
Please let me know if there is any
c
Sent: Thursday, October 06, 2005 10:14 AM
Subject: Re: crashes in InnoDB with MySQL 4.1.14 (semaphore wait timeout)
Heikki Tuuri wrote:
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
Please let me know if there is any additional data I can provide to h
Heikki Tuuri wrote:
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
Please let me know if there is any additional data I can provide to help
resolve this.
=
051005 7:18:17 INNODB MONITOR OUTPUT
==
Deva,
please post the complete output except the transaction data.
Regards,
Heikki
- Original Message -
From: "Devananda" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, October 05, 2005 7:05 PM
Subject: Re: crashes in InnoDB with MySQL 4
Devananda wrote:
One of our servers which is configured primarily for InnoDB has crashed
in the same fashion three times in the past 48 hours. I've been going
over the error log, and I would like to know if anyone else has seen
similar errors, or can give me some pointers to work out this probl
e a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/e
Wolfram Stebel wrote:
Am 30.09.2005 16:29 Uhr schrieb "Nuno Pereira" unter
<[EMAIL PROTECTED]>:
in Users/user/Library/Logs/CrashReporter/java.crash.log
one mile of traces
Regards
Wolfram
**
Host Name: Erde
Date/Time: 2005-09-30 15:13:52.351 +0200
OS Version: 10.4.2 (Buil
he problem with single connection and
still crashes randomly.
This is the part of of the source code, not to understand what does every
function, just to illustrate, it is almost self-explanatory
MYCLASS dbmail;
// CONNECT
Hello.
Yes, MySQL 5.0.12 a bit unstable yet. You may want to make a bug
report. See:
http://dev.mysql.com/doc/mysql/en/bug-reports.html
Or send the the list definition of your tables, problematic
queries and a stack trace. It would be great if you include
a test script which generates
MySQL 5.0.12 crashed when I tried to select, backup or left join from
certain table with 431433 rows with Data length of 23.6 MB using InnoDB
engine. Tested on MySQL 4.1.14 with no problem in all aspects. Has this
occured to anyone before?
--
Please avoid sending me Word or PowerPoint attachme
On Mon, 1 Aug 2005, Heikki Tuuri wrote:
> unfortunately, the bug fix was never made to 4.0. It is only in 4.1.12 and
> later.
Hi Heikki,
Thanks for your response. The fix seems to consists only of a few lines:
http://mysql.bkbits.net:8080/mysql-4.1/[EMAIL PROTECTED]|[EMAIL PROTECTED]
It look
;; <[EMAIL PROTECTED]>
Lähetetty: Monday, August 01, 2005 5:08 PM
Aihe: mysql bug 9670 OPTIMIZE TABLE crashes
Hi,
I am experiencing assertion failures described in the following bugreport:
http://bugs.mysql.com/bug.php?id=9670
The bug has been closed, but I'm running the most
On Mon, 1 Aug 2005, Mikhail Entaltsev wrote:
> in the bug report Heikki Tuuri wrote:
> ***
> [13 Apr 20:59] Heikki Tuuri
> The bug was introduced in 4.0.24 and 4.1.10. The fix will be in 4.1.12 and
> 5.0.5.
> ***
Hi Mikhail,
Thank you for your quick response. I had noticed myself that the fix
s
ot;MySQL mailing list"
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, August 01, 2005 4:08 PM
Subject: mysql bug 9670 OPTIMIZE TABLE crashes
> Hi,
>
> I am experiencing assertion failures described in the following bugreport:
>
> http://bugs.mysql.com/b
Hi,
I am experiencing assertion failures described in the following bugreport:
http://bugs.mysql.com/bug.php?id=9670
The bug has been closed, but I'm running the most current 4.0.25 version
of MySQL. The report mentions downgrading to 4.0.23 or upgrading to 4.1.
Is this really neccessary or s
Kasthuri Ilankamban <[EMAIL PROTECTED]> writes:
> Hi, We are running mysql version 4.1.7 with innodb on i686 running
> 2.4.26 linux kernal with 8G memory. Mysql crashes consistently during
> heavy usage with fatal innodb error. We are running a high volume front
> end applica
Kasthuri,
Maybe it's time to re-think your application architecture? A 200-meg
BLOB is quite large for a highly-concurrent system, considering that
MySQL will have to read/save it in its entirety _and_ allocate network
buffers for it, so essentially you're allocating _400_ megs or so
_per_
cl
Matthew has already responded. But I will also add, you must rethink
how your application is coded. I can not possibly imagine a situation
where a user session needs 200meg insert. No matter what database you
use you will have a terrible time trying to scale this application. If
you give more detai
but once in a while application inserts a row for a
user with session data that could exceed 200MG . Since we have lots of
concurrent users and if application inserts few rows with > 200MG data
simultaneously innodb runs out of memory and crashes. Eventhough we
have 8 gig memory, I'm
lication inserts few rows
> with > 200MG data simultaneously innodb runs out of memory and
> crashes. Eventhough we have 8 gig memory, I'm not able to start
> mysql if I allocate more than 2Gig to innodb_buffer_size. Do you know
> how I can allocate more than 2 Gig memory
pplication inserts few rows
with > 200MG data simultaneously innodb runs out of memory and
crashes. Eventhough we have 8 gig memory, I'm not able to start
mysql if I allocate more than 2Gig to innodb_buffer_size. Do you know
how I can allocate more than 2 Gig memory to innodb on 32 b
th innodb on i686 running
> 2.4.26 linux kernal with 8G memory. Mysql crashes consistently
> during heavy usage with fatal innodb error. We are running a high
> volume front end application which inserts > 50M data to a row in
> innodb table often. I don't know whether these
Hi, We are running mysql version 4.1.7 with innodb on i686 running
2.4.26 linux kernal with 8G memory. Mysql crashes consistently
during heavy usage with fatal innodb error. We are running a high
volume front end application which inserts > 50M data to a row in
innodb table often. I do
Hello.
See:
http://dev.mysql.com/doc/mysql/en/crashing.html
"Chris Knipe" <[EMAIL PROTECTED]> wrote:
> We will try our best to scrape up some info that will hopefully help
> diagnose
> the problem, but since we have already crashed, something is definitely
> wrong
> and this may f
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.
key_buffer_size=536870912
read_buffer_size=2093056
max_used_connections=418
max_connections=2048
threads_connected=404
It
There's no real "official" word on the 5.0.2 crashes on win32, although
I believe there were a number of bug reports. A lot of the crashing that
I have come across when using 5.0.2 on win32 has to do with the
"informational" functions - DESCRIBE, SHOW etc.
There were
> Warning, do not install 5.03 it still crashes on win32. This occured
after
> very few minutes of testing. I will send more info as I locate it.
Great... Is there any "official" word on the 5.0.2 crashes? Have there
been fixes regarding this issue?
With regards,
Martijn
Where do I look for the server stopping error. The .err file looks happy with
no error listed after server crashes and stops.
Here is the last entry...
050328 10:34:30 InnoDB: Started; log sequence number 0 43634
050328 10:34:30 InnoDB: Starting recovery for XA transactions...
050328 10:34:30
Warning, do not install 5.03 it still crashes on win32. This occured after
very few minutes of testing. I will send more info as I locate it.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
s.mysql.com>
Sent: Thursday, March 17, 2005 11:47
AM
Subject: RE: 5.0.2 alpha crashes with Query
Browser
When will 5.0.3 come out?Thanks,Lily-Original
Message-From: Peter Brawley [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 10:17 AMTo: Francisco TapiaCc:
mysql@lists.mysq
that pretty much explains why it's been happening ;) Thanks :)
On Thu, 17 Mar 2005 22:34:08 +0100, Martijn Tonies <[EMAIL PROTECTED]> wrote:
> Francisco,
>
> > Maybe it's my setup... but:
> >
> > whenever I try to login to use the mySQL query browser, it instantlly
> > turns off the 5.0.2 alpha
Francisco,
> Maybe it's my setup... but:
>
> whenever I try to login to use the mySQL query browser, it instantlly
> turns off the 5.0.2 alpha mySQL instance (stops running). the error I
> get is:
>
> mysqld-max-nt.exe - Application Error
>
> the instruciton at "0x00538d34" referenced memory at "0
When will 5.0.3 come out?
Thanks,
Lily
-Original Message-
From: Peter Brawley [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 10:17 AM
To: Francisco Tapia
Cc: mysql@lists.mysql.com
Subject: Re: 5.0.2 alpha crashes with Query Browser
Lots of users report such instabilities in
1 - 100 of 383 matches
Mail list logo
