: Wednesday, July 11, 2012 7:11 AM
To: MySql
Subject: Re: MySQL crashed..
sorry.. im using 5.1
On Wed, Jul 11, 2012 at 10:09 AM, J M jerom...@gmail.com wrote:
hi all,
our DB crashed for some reason... any inputs would be greatly
appreciated..
120711 8:12:21 - mysqld got signal 11
hi all,
our DB crashed for some reason... any inputs would be greatly appreciated..
120711 8:12:21 - 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.
sorry.. im using 5.1
On Wed, Jul 11, 2012 at 10:09 AM, J M jerom...@gmail.com wrote:
hi all,
our DB crashed for some reason... any inputs would be greatly appreciated..
120711 8:12:21 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or
I have an environment where upon boot of a machine I need to know if
mysql shutdown nicely or if it crashed.
How can I know for sure which was the case so that I can take action if
needed?
I notice that issuing a reboot or shutdown -r now command, (in Linux)
that the 'service mysql stop' is
Signal 15 is pretty much equal to a regular shutdown, except that if your
shutdown script doesn't run, you may be left with lockfiles, pidfiles and
the like.
A crash would most likely be visible in the logfile, and even if it isn't
(machine loses power), your log should show innodb running a
On Tue, Oct 27, 2009 at 7:51 AM, Bryan Cantwell bcantw...@firescope.com wrote:
I notice that issuing a reboot or shutdown -r now command, (in Linux) that
the 'service mysql stop' is never run... it just seems to catch the sig 15
and does its own shutdown...
I have scripted in the stop section
Hi,
MySQL 4.0.16 running on Red Hat Linux release 8.0
with 4 Intel XEON 2.40 GHz with InnoDB tables.
This is the stack trace :
0x81077c6 handle_segfault + 474
0x4002a929 _end + 935891041
0x8272ff8 sync_array_print_long_waits + 580
0x81a7328 srv_error_monitor_thread + 96
0x40024ada _end +
mysql 4.0.5a binary crashed with following error messages.
What's the problem? :(
021128 11:06:23 Slave I/O thread: connected to master
'austin@atis1:3306', replication started in log 'FIRST' at position 4
021128 17:35:52 Slave: received 0 length packet from server, apparent
master
Hi there,
during a wrong select query on a table containing over 2 mill. records
(involving other tables) mysql and the whole linux server crashed.
After rebooting I did run myisamchk and this reported that some tables are
damaged but still can be read. So I did shut down the server und run
]
To: [EMAIL PROTECTED]
Sent: Sunday, May 19, 2002 6:28 PM
Subject: mysql crashed and created huge .MYI files. All data lost?
Hi there,
during a wrong select query on a table containing over 2 mill. records
(involving other tables) mysql and the whole linux server crashed.
After rebooting I
Dear All,
While running our application, mysql suddenly started
giving an error as MYD file not found for our
database.
On restoring the database through backup which was
taken withthe help of mysqldump, it now converts all
the tables to MyIsam and not Innodb even after
specifying the the
Hi.
Could it be that your MySQL server was upgraded to a version compiled
without InnoDB support?
If you used InnoDB it should have never complained about MYD files, as
they belong to MyISAM table format.
Bye,
Benjamin.
On Mon, Apr 29, 2002 at 01:54:28AM -0700, [EMAIL PROTECTED]
Hi,
Mysql ran for 6 days.. It is a website
with heavy traffic.
/usr/libexec/ld-elf.so.1: /usr/local/libexec/mysqld: Undefined symbol
strtoull
010423 23:18:08 mysqld restarted
/usr/local/libexec/mysqld: ready for connections
What is this function
13 matches
Mail list logo
