t;> Subject: Re: How can I drop a table that is named “logs/#sql-ib203” and
>> appeared after MySQL crash?
>>
>> i know what happened but how get rid of these two bullshit files after
>> *three years* not touched and used by mysqld
>>
>> Am 20.06.2013 21:28,
amed “logs/#sql-ib203” and
> appeared after MySQL crash?
>
> i know what happened but how get rid of these two bullshit files after
> *three years* not touched and used by mysqld
>
> Am 20.06.2013 21:28, schrieb Rick James:
> > #sql files are temp tables that vanish when the
Hi Frank,
On 20/06/2013 05:00, Franck Dernoncourt wrote:
Hi all,
A table `logs/#sql-ib203` appeared after a MySQL crash due to disk space
shortage while deleting some attributes in a table in the `logs` database
and adding an index.
`USE logs; SHOW TABLES;` does not list the table `logs/#sql
12:19 PM
> To: mysql@lists.mysql.com
> Subject: Re: How can I drop a table that is named “logs/#sql-ib203” and
> appeared after MySQL crash?
>
>
>
> Am 19.06.2013 21:00, schrieb Franck Dernoncourt:
> > `USE logs; SHOW TABLES;` does not list the table `logs/#sql-ib203`
crash happened in the
> middle of the ALTER.
>
>> -Original Message-
>> From: Reindl Harald [mailto:h.rei...@thelounge.net]
>> Sent: Wednesday, June 19, 2013 12:19 PM
>> To: mysql@lists.mysql.com
>> Subject: Re: How can I drop a table that is named “lo
sql-ib203`
appeared after a MySQL crash due to disk space shortage while executing the
following query:
ALTER TABLE `logs`.`srv_logs` DROP COLUMN `filenum` , DROP COLUMN `agent` ,
DROP COLUMN `ip` , DROP COLUMN `event_source`
, ADD INDEX `username_event_type_idx` (`username` ASC, `event_
On Thu, Jun 20, 2013 at 7:13 AM, Denis Jedig wrote:
>
> If you already tried enclosing the table name in backticks (DROP TABLE
> `#sql-ib203`) and using the DROP TEMPORARY TABLE syntax without success,
Yep, no success with:
DROP TEMPORARY TABLE `logs/#sql-ib203`;
DROP TEMPORARY TABLE `/#sql-ib20
This may be a naive question, but I'm not sure I can see you've covered
this: Have you tried "USE logs" before DROP TABLE `#sql-ib203` (without
the "logs/" bit)?
/ Carsten
On 19-06-2013 21:00, Franck Dernoncourt wrote:
Hi all,
A table `logs/#sql-ib203` appea
Franck,
Am 19.06.2013 21:00, schrieb Franck Dernoncourt:
A table `logs/#sql-ib203` appeared after a MySQL crash
the #sql-ib tables are temporarily created during an
ALTER TABLE operation for recovery purposes. Apparently these
temporary tables might stay in certain circumstances even after
Am 19.06.2013 21:00, schrieb Franck Dernoncourt:
> `USE logs; SHOW TABLES;` does not list the table `logs/#sql-ib203`, but
> when trying to `ALTER` the table that was being changed during the crash
> MySQL complains about the existence of the table `logs/#sql-ib203`:
>
>> ERROR 1050: Table 'logs
Hi all,
A table `logs/#sql-ib203` appeared after a MySQL crash due to disk space
shortage while deleting some attributes in a table in the `logs` database
and adding an index.
`USE logs; SHOW TABLES;` does not list the table `logs/#sql-ib203`, but
when trying to `ALTER` the table that was being
On Wed, May 2, 2012 at 4:58 AM, vishesh kumar wrote:
> I am getting following in error log
>
>
> 120502 07:52:05 mysqld started
> 120502
> Cc: mysql@lists.mysql.com
> Subject: Re: MySQL Crash when Open_files reach 128
>
> I am getting following in error log
>
> ---
> ---
>
e .
> >>
> >> I didn't set any open_files limit in my.cnf .
> >>
> >> For testing i set open_files_limit to 300 but still MySQL crashing after
> >> 128.
> >>
> >> ~Vishesh
> >>
> >> On Wed, May 2, 2012 at 4:28 PM
idn't set any open_files limit in my.cnf .
>>
>> For testing i set open_files_limit to 300 but still MySQL crashing after
>> 128.
>>
>> ~Vishesh
>>
>> On Wed, May 2, 2012 at 4:28 PM, Reindl Harald wrote:
>>
>>>
>>>
>>>
in my.cnf .
>
> For testing i set open_files_limit to 300 but still MySQL crashing after
> 128.
>
> ~Vishesh
>
> On Wed, May 2, 2012 at 4:28 PM, Reindl Harald wrote:
>
>>
>>
>> Am 02.05.2012 12:52, schrieb vishesh kumar:
>> > Hi Members,
>> >
>&g
,
> >
> > I am using MySQL 5.0.67 . I am facing the problem of MySQL crashing
> > problem . MySQL Crash after every a few minutes . On investigation i
> > noticed that when the Open_files status variable reach 128 MySQL C
Am 02.05.2012 12:52, schrieb vishesh kumar:
> Hi Members,
>
> I am using MySQL 5.0.67 . I am facing the problem of MySQL crashing
> problem . MySQL Crash after every a few minutes . On investigation i
> noticed that when the Open_files status variable reach 128 MySQL Cr
mysqldump. There are other users, but the behavior recurs even if the
database is only being used by mysqldump.
Thanks,
LA
Michael Dykman wrote:
How are you performing the backup? What tools are involved? Are
there any ther users of the database while you are doing this?
- michael dykm
How are you performing the backup? What tools are involved? Are
there any ther users of the database while you are doing this?
- michael dykman
On Wed, Sep 3, 2008 at 4:43 PM, L'argent <[EMAIL PROTECTED]> wrote:
>
> I've been trying to backdown a production database for some time and can't
>
I've been trying to backdown a production database for some time and
can't seem to get around MySQL crashing at about 1GB of backup data.
(the database is about 400GB).
I have a page corruption, but it isn't found when I do a CHECK TABLE on
*any* of the tables. InnoDB is running in super-saf
Hi all,
I woke up this morning to find that our main database had stopped
responding so I jumped on to see what was going on. MySQL was no
longer running and the error log contained lots of...
<---
InnoDB: Warning: a long semaphore wait:
--Thread 39439068816 has waited at trx0trx.c line 715
Am Donnerstag, den 22.11.2007, 09:31 -0800 schrieb Frank Niedermann:
> Nov 22 15:32:16 localhost mysqld[12720]: InnoDB: Last MySQL binlog file
> position 0 1991372, file name /var/log/mysql/mysql-bin.000580
>
> Is there a way to find out why MySQL crashed?
You have the binlog and the position wher
s there a way to find out why MySQL crashed?
Regards,
Frank
--
View this message in context:
http://www.nabble.com/MySQL-crash-on-Debian-Etch-system-tf4857583.html#a13900443
Sent from the MySQL - General mailing list archive at Nabble.com.
--
MySQL General Mailing List
For list archives: htt
A message in the MySQL log file asserts that someone at this e-mail
address may be able to assist in troubleshooting/diagnosing a chronic
error we encounter during our nightly database dumps.
Here is an excerpt of the log file (near the reference to your e-mail
address):
InnoDB: Error: semaphore
Marten,
Yeah, my experience has been that InnoDB is great when it's working
but a complete nightmare when it stops working. I have scripts to deal
with this which I'm actually hoping to release to the public in the
near future. Essentially, what you need to do is edit your my.cnf to
bring MySQL up
Hello,
today I got this in my logs and mysql stopped working.
InnoDB: http://dev.mysql.com/doc/mysql/en/InnoDB_troubleshooting_datadict.html
InnoDB: how to resolve the issue.
071107 8:46:26 InnoDB: Flushing modified pages from the buffer pool...
071107 8:46:26 InnoDB: Started; log sequence nu
; Heikki Tuuri; mysql@lists.mysql.com; Logan, David (SST
- Adelaide)
Subject: Re: Surviving MySQL crash
>>15 * * * * /usr/local/mysql/bin/mysql -u root -pxx -e 'FLUSH
TABLES'
>>
>>This would run a FLUSH TABLES once every hour at 15 minutes past. If
you
>>are
15 * * * * /usr/local/mysql/bin/mysql -u root -pxx -e 'FLUSH TABLES'
This would run a FLUSH TABLES once every hour at 15 minutes past. If you
are using Windows, sorry I'm not sure how to do it there.
Easier to just set flush_time=900 in my.cnf :)
Thanks guys. Will give it a shot
In the last episode (Feb 10), David Logan said:
> Foo Ji-Haw wrote:
> >Heikki Tuuri wrote:
> >>if the OS crashes do not corrupt files, then InnoDB tables would
> >>survive an OS crash without a problem.
> >
> >Thanks for the reply Heikki. Let me rephrase my problem: the data
> >remains intact, but
Foo Ji-Haw wrote:
Heikki Tuuri wrote:
Ji-Haw,
if the OS crashes do not corrupt files, then InnoDB tables would
survive an OS crash without a problem.
Thanks for the reply Heikki. Let me rephrase my problem: the data
remains intact, but I suspect the indexes are corrupted. Basically I
h
Heikki Tuuri wrote:
Ji-Haw,
if the OS crashes do not corrupt files, then InnoDB tables would
survive an OS crash without a problem.
Thanks for the reply Heikki. Let me rephrase my problem: the data
remains intact, but I suspect the indexes are corrupted. Basically I
have to run myisamchec
backs up MyISAM
tables
http://www.innodb.com/order.php
- Original Message -
From: "Foo Ji-Haw" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, February 10, 2006 7:05 AM
Subject: Surviving MySQL crash
Hi all,
I have a MySQL server servng low-l
---
-Original Message-
From: Foo Ji-Haw [mailto:[EMAIL PROTECTED]
Sent: Friday, 10 February 2006 3:45 PM
To: mysql@lists.mysql.com
Subject: Surviving MySQL crash
Hi all,
I have a MySQL server servng low-load applications. Problem is, the
environment is sometimes unstable, leading the entire OS to
Hi all,
I have a MySQL server servng low-load applications. Problem is, the
environment is sometimes unstable, leading the entire OS to crash. I
notice that even in low-load situations the MySQL tables can be
corrupted during crashes.
My question is: is there a way for MySQL to flush when id
Please upgrade to the newest 4.0 mysql binaries.
Anil wrote:
Hi,
We are using mysql 4.0.20 on RHEL3.0 with circular replication setup A ->B
->C ->A . A is the master and all operations will be happening on A. We are
facing frequent mysql crash on Master with page corruption error
Hi,
We are using mysql 4.0.20 on RHEL3.0 with circular replication setup A ->B
->C ->A . A is the master and all operations will be happening on A. We are
facing frequent mysql crash on Master with page corruption errors. How to
identify which process is causing this page corrupti
Hello.
Really, there is not enough information. I suggest you to upgrade
to the latest release (4.1.11 now). If the problem remains, our
next step will be finding a possible query which crashes the
server.
Jason Johnson <[EMAIL PROTECTED]> wrote:
> [-- text/plain, encoding 7bit, chars
Doesn't seem like this is going to be much help, but this is what I
could pull together. The highlighted lines seem to be the only
indication as to something going wrong. No real error.
Any thoughts?
050414 8:30:24 InnoDB: Started; log sequence number 0 996013795
D:\MySQL Server 4.1\bin\mysqld
Hello.
What is in error log? See:
http://dev.mysql.com/doc/mysql/en/error-log.html
http://dev.mysql.com/doc/mysql/en/windows-troubleshooting.html
Jason Johnson <[EMAIL PROTECTED]> wrote:
> I am running MySQL 4.1.8 on Windows 2000. Sporadically, the service
> will stop. It does no
I am running MySQL 4.1.8 on Windows 2000. Sporadically, the service
will stop. It does not seem to be in relationship with load on the
service itself, or the box. At seemingly random intervals, the service
will go kaput for no readily apparent reason.
My question to you isn't "hey, what's wrong
Mel,
- Alkuperäinen viesti -
Lähettäjä: "mel list_php" <[EMAIL PROTECTED]>
Vastaanottaja: <[EMAIL PROTECTED]>;
Lähetetty: Friday, March 04, 2005 4:13 PM
Aihe: Re: mysql crash - innodb not starting
Hi Heikki,
Still only one process with ps -fA. And mysql doesn
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: "mel list_php" <[EMAIL PROTECTED]>,
Subject: Re: mysql crash - innodb not starting
Date: Fri, 4 Mar 2005 15:50:26 +0200
Mel,
do
ps -fA
Do you see more mysqld processes?
If the ibdata1 file stays locked even though there is
anottaja:
Kopio: <[EMAIL PROTECTED]>
Lähetetty: Friday, March 04, 2005 12:00 PM
Aihe: Re: mysql crash - innodb not starting
I did ps -aux
I see one mysqld running (mine, launched with --skip-innodb).
I shut it down.
ps -aux: nothing
I tried to start it again, doesn't work.
As it is running
your time.
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To:
Subject: Re: mysql crash - innodb not starting
Date: Thu, 3 Mar 2005 23:20:56 +0200
Hi!
Error 11 means that you already have a mysqld process running on the same
files.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, t
base.myodbc
Sent: Thursday, March 03, 2005 2:25 PM
Subject: mysql crash - innodb not starting
Hi,
I just have a crash of my mysql 4.1.5 .(the machine where it was running
just shutdown)
Tried to restart it, and problem with innodb:
050303 11:58:46 [WARNING] Asked for 196608 thread stack, but go
Hi,
I just have a crash of my mysql 4.1.5 .(the machine where it was running
just shutdown)
Tried to restart it, and problem with innodb:
050303 11:58:46 [WARNING] Asked for 196608 thread stack, but got 126976
InnoDB: Unable to lock ./ibdata1, error: 11InnoDB: Error in opening
./ibdata1
050303
affected (0.00 sec)
mysql>
mysql>
mysql> insert into Leads(LeadNo) values (1);
Query OK, 1 row affected (0.00 sec)
mysql> insert into Leads(LeadNo) values (2);
Query OK, 1 row affected (0.00 sec)
mysql> insert into Leads(LeadNo) values (3);
Query OK, 1 row affected (0.00 sec
Hi all.
I just tried adding a foreign key constraint, and crashed MySQL ( 4.0.18 ).
I tried it again and crashed it again :(
The SQL I'm using is:
---
alter table Leads
add foreign key fk_LeadNo ( LeadNo ) references Prospects ( LeadNo );
---
The tables involved:
`Prospects` (
`LeadNo` mediumint(8
Hi,
I have installed mysql 4.0.18 on my debian box. I am
quite new to linux. mysql works fine with the command
line (mysql) and with apache/phpmyadmin too. But when
i try to connect from Windows or if i telnet from
Debian, i got:
Number of processes running now: 0
040622 21:27:33 mysqld restarte
Hi!
On Dec 29, Derek J wrote:
> Hello,
>First, Yes I can create repeatable test case, I still have live
> server with the same problem. and another Dual opteron server, which i
> created the same database there as a test to make sure there are no
> hardware faliures casuing this probles, but i
Hello,
First, Yes I can create repeatable test case, I still have live
server with the same problem. and another Dual opteron server, which i
created the same database there as a test to make sure there are no
hardware faliures casuing this probles, but i still had the same problem
there too. I
Hi!
On Dec 28, Derek J wrote:
> Hello Every Body ,
> I have been facing a strange problem, that i assume its a mysql bug of
> some sort.
>
> In my datadabase there are 2 tables, if i tried to add any index to them
> ,any INSERT INTO request status will be - in show processlist- update
> and will
I have enough disk space for indexes, the problem doesn't happen during
adding an index. it happens after the index is added.
On Sun, 2003-12-28 at 21:33, mos wrote:
> At 06:28 PM 12/28/2003, you wrote:
> >Hello Every Body ,
> >I have been facing a strange problem, that i assume its a mysql bug of
At 06:28 PM 12/28/2003, you wrote:
Hello Every Body ,
I have been facing a strange problem, that i assume its a mysql bug of
some sort.
In my datadabase there are 2 tables, if i tried to add any index to them
,any INSERT INTO request status will be - in show processlist- update
and will freeze like
Hello Every Body ,
I have been facing a strange problem, that i assume its a mysql bug of
some sort.
In my datadabase there are 2 tables, if i tried to add any index to them
,any INSERT INTO request status will be - in show processlist- update
and will freeze like this forever , and consequently
ursday, October 30, 2003 5:25 AM
Subject: mySQL crash
> --=_NextPart_000_007E_01C39ECE.F3C28910
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> Dear,
>
> We encountered mysql (innodb) crash, and we can't rec
Dear,
We encountered mysql (innodb) crash, and we can't recover the database
after the crash. Could you please help use to investigate the problem.
Thanks in advance for your help.
The following is copied from the mysql error log:
031027 17:16:12 mysqld started
031027 17:16:12 Warning: se
Hi folks,
I just set up a slave server and it seemed to be working alright,
catching up with the new data, and then the server suddenly went away.
Looking at the slave's data directory, there are approximately 2
relay-bin files. I can't even restart the server now, because it gets a
sig
AIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Sunday, September 28, 2003 12:00 PM
Subject: MySQL Crash
> OK I had a big MySQL crash last night on a very busy system I can't
> understand the InnoDB errors can anybody help before I post a bug report?
>
> resolve_stack_dum
Hello, mysql,
Yesterday,mysql process disappear sliently.
After I check the err-log,no clues found.
But the PID file still exising.I think the mysql terminate by some reason.But
I still not found why.
The error-log mysqld.log wouldn't provide any valueable msg.It j
>Description:
When i using default-character-set tis620 (Thai sort order) mysql server
has been crash and then I test to use latin1 can work fine but can't
sort order in thai language.
>How-To-Repeat:
>Fix:
>Submitter-Id:
>Originator:apples
>Organization:
>MySQL
CTED]>
Sent: Friday, January 17, 2003 6:28 PM
Subject: FreeBSD: MySQL crash when importing 148 MB dumpfile
> Problem: I am migrating servers, from a dual PIII-866 Mhz with 384
MB of
> RAM running Linux to the following server configuration:
>
> Dual Athlon 1.5 Ghz
> 1 GB RAM
&g
Problem: I am migrating servers, from a dual PIII-866 Mhz with 384 MB of
RAM running Linux to the following server configuration:
Dual Athlon 1.5 Ghz
1 GB RAM
2 x 18 GIG SCSI drives.
FreeBSD 4.7-Stable
MySQL-Max-3.23.54a (ELF) i.e. without linuxthreads - runs on only 1 process.
I am trying to i
I'm developing a site using MySQL and JSP (with Resin).
Everything seems to be jolly the first few times I load a page, but then MySQL just
crashes.
My system is:
- Hardware: Celeron 500, 128MB RAM
- Mandrake 9.0 vanilla
- Resin 2.1.5 (installed as per resin documentation, configured with Apach
Hello,
I've just had a MySQL crash on a very simple operation. I have the
following table:
***
+---+---+--+-+-++
| Field | Type | Null | Key | Default |
apples,
Wednesday, June 26, 2002, 2:39:25 PM, you wrote:
a> I got problem on my machine running with mysql 3.23.51, some field use
a> varchar
a> (40) if query from this field mysql got hanging
a> Trying to get some variables.
a> Some pointers may be invalid and cause the dump to abort...
a
I got problem on my machine running with mysql 3.23.51, some field use
varchar
(40) if query from this field mysql got hanging
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd-query at 0x82c3318 = SELECT * FROM `COURSE` ORDER BY
`SUBJNAME` ASC
Hi all,
I have a problem with MySQL under Windows NT/2000 where it crashes every time I issue
an ALTER TABLE command while the table is being written to under high load. I've
tried several versions of MySQL on a few different machines/OS and still the problem
remains. I'm hoping someone might
below is a resolve stack .
I use tis620 charset (thai) all query of my program with php is normaly command
such as 'select' 'select count(*)' 'insert' 'update' 'delete' I didn't know why mysqld
crash help meplease
root@academic:/tmp# resolve_stack_dump -s /tmp/mysqld.sym -n
mysqld.stack
0x80
> which version of MySQL you are running?
3.23.39 :-(... sorry for not including this earlier. I will try and
move to .47
Thanks!
>
> >From http://www.innodb.com/bugfixes.html :
>
> November 17, 2001:
> The insert buffer tree can get into an inconsistent state, causing a cr
Johannes,
which version of MySQL you are running?
>From http://www.innodb.com/bugfixes.html :
November 17, 2001:
The insert buffer tree can get into an inconsistent state, causing a crash,
and also crashing the recovery. This bug may appear especially in large
table imports or a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just started using innodb tables to help with some locking
problems.
The table I am trying to convert is large (100 Million rows, 23 GigByte).
I setup 20 2Gig ibdata files. (I choose a size of 2 Gig as this is the
maximum size I can easily trans
Thanks Mr. Sinisa, but Mr. Miguel Angel could reproduce it, maybe you may ask him
about details, since he is a mysql developer he can tell you about the problem.
I am sure there are more mysql (3.23.39) bugs specially related to the wrapper support.
Any away i am really curious about the facts
e
> user comunity too)
>
> >Submitter-Id:
> >Originator:Gustavo Vieira Gonçalves Coelho Rios
> >Organization:
> Ifour Sistemas.
> >MySQL support: none
> >Synopsis: MySQL Crash with "show logs" queries
> >Severity: crit
Gustavo Vieira Gonçalves Coelho Rios writes:
> >Description:
> MySQL Daemon crashes when a user with the necessary privileges issue a query
>"show logs"
> >How-To-Repeat:
> Start your daemon with the option --skip-bdb:
> your-shell> safe_mysqld --skip-bdb
>
> Then, issue
feedback (Not only developer but the user comunity
too)
>Submitter-Id:
>Originator:Gustavo Vieira Gonçalves Coelho Rios
>Organization:
Ifour Sistemas.
>MySQL support: none
>Synopsis: MySQL Crash with "show logs" queries
>Severity: critical
>
Hello,
I am running MySQL (3.23.xx) on Linux RedHat 6.2 and plan to
increase volume of data in the near future. So, I would like to know some
db schema , total row and your SQL you used to protect my database.
Sommai Fongnamthip
At 20:56 21/5/2001 +0300, Sinisa Milivojevic wrote:
>Ru
Rui Barreiros writes:
>
> hi,
>
> i've upgraded mysql server with 3.23.38 from mysql, and i have the same
> behaviour sinisa if you have some time i could give you access to one of the
> machines. :/
>
> --
> WEBSOLUT - Soluções Internet
> Emailto: [EMAIL PROTECTED]
> Personal Info: http://
hi,
i've upgraded mysql server with 3.23.38 from mysql, and i have the same
behaviour sinisa if you have some time i could give you access to one of the
machines. :/
--
WEBSOLUT - Soluções Internet
Emailto: [EMAIL PROTECTED]
Personal Info: http://websolut.net/people/rui.html
As informações
Rui Barreiros writes:
>
> hi there, from one day to another, my mysql in 2 machines with 2 different
> mysql version crashed after a quite long query,
>
> i've run mysql server with the log option, here are the details:
>
> in hostname.err:
>
> mysqld got signal 11;
> it's quite strange, i'm
hi there, from one day to another, my mysql in 2 machines with 2 different
mysql version crashed after a quite long query,
i've run mysql server with the log option, here are the details:
in hostname.err:
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use
Meyer, Patrick writes:
> Running 3.23.33 on Windows 2000 Server.
>
> I have noticed that executing an ALTER TABLE works... but the next query on
> the alter table crashes MySQL and corrupts the table.
>
> If I FLUSH TABLES after an ALTER TABLE, it seems to reduce the occurance,
> but sh
Running 3.23.33 on Windows 2000 Server.
I have noticed that executing an ALTER TABLE works... but the next query on
the alter table crashes MySQL and corrupts the table.
If I FLUSH TABLES after an ALTER TABLE, it seems to reduce the occurance,
but should this be required?
[EMAIL PROTECTED]
Na
84 matches
Mail list logo
