FW: mysqld in hung mode

FW: mysqld in hung mode

am 05.06.2006 21:53:19 von Ilavajuthy Palanisamy

------_=_NextPart_001_01C688D9.C0862D5C
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have enabled debug by executing the command 'mysqladmin debug'.

Now on the .err file I can see lots of prints like 'lock: 0xfa0b8d0:'.

=20

Ila.

=20

=20

________________________________

From: Ilavajuthy Palanisamy=20
Sent: Monday, June 05, 2006 12:49 PM
To: MySQL Win32 List
Subject: mysqld in hung mode

=20

Hi,

=20

Today our mysqld process is in hung mode. I'm able to connect to mysqld
thru mysql client, but none of the commands are going thru.

I tried 'show processlist' and 'select 1' from mysql client, the command
just hangs.

In the task manager I can see mysqld in running and its cpu usage as 0.

Any idea why mysqld is in this state?

=20

Is there any command that I can use to see the state of the mysqld?=20

=20

Ila.

=20


------_=_NextPart_001_01C688D9.C0862D5C--

Re: FW: mysqld in hung mode

am 05.06.2006 22:30:19 von Daniel da Veiga

On 6/5/06, Ilavajuthy Palanisamy wrote:
> I have enabled debug by executing the command 'mysqladmin debug'.
>
> Now on the .err file I can see lots of prints like 'lock: 0xfa0b8d0:'.
>
>
>
> Ila.
>

Ok, this is just a guess, but have you checked your OS state? I mean
memory, filesystem, disk space and resources in general. After that,
try restarting MySQL and see how it behaves. It doesn't look good, so,
back it up and I hope you have previous backups also.

Post back when you finish please.

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: FW: mysqld in hung mode

am 05.06.2006 22:45:37 von Ilavajuthy Palanisamy

I have already verified the machine state.
I have ample amount of disk space and memory. Looks like all the system
resources are in good condition.

Surely if I restart mysql, it will start working fine.
But, I need to find out how to recover from this state or what this
state is so that I can avoid getting into this state.

Through mysqladmin kill command I have killed all the pending queries
(these queries are executed due to mysqldump command and they were stuck
up in 'Opening tables' state). After killing all the queries are in
Killed state and they are not going away.=20

Any idea under which circumstances mysql will go into this kind of
state?

Ila.


-----Original Message-----
From: Daniel da Veiga [mailto:danieldaveiga@gmail.com]=20
Sent: Monday, June 05, 2006 1:30 PM
To: MySQL Win32 List
Subject: Re: FW: mysqld in hung mode

On 6/5/06, Ilavajuthy Palanisamy wrote:
> I have enabled debug by executing the command 'mysqladmin debug'.
>
> Now on the .err file I can see lots of prints like 'lock: 0xfa0b8d0:'.
>
>
>
> Ila.
>

Ok, this is just a guess, but have you checked your OS state? I mean
memory, filesystem, disk space and resources in general. After that,
try restarting MySQL and see how it behaves. It doesn't look good, so,
back it up and I hope you have previous backups also.

Post back when you finish please.

--=20
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--=20
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dipalanisamy@consentry.c om


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: FW: mysqld in hung mode

am 05.06.2006 23:03:52 von Daniel da Veiga

On 6/5/06, Ilavajuthy Palanisamy wrote:
> I have already verified the machine state.
> I have ample amount of disk space and memory. Looks like all the system
> resources are in good condition.
>
> Surely if I restart mysql, it will start working fine.
> But, I need to find out how to recover from this state or what this
> state is so that I can avoid getting into this state.
>
> Through mysqladmin kill command I have killed all the pending queries
> (these queries are executed due to mysqldump command and they were stuck
> up in 'Opening tables' state). After killing all the queries are in
> Killed state and they are not going away.
>
> Any idea under which circumstances mysql will go into this kind of
> state?
>

I've only seen this kind of behavior when a memory corruption occured
on my machine, and also once in an old version (<4.1.12), if that's
your case, you should upgrade to the latest version of your brand.

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: FW: mysqld in hung mode

am 05.06.2006 23:09:30 von Ilavajuthy Palanisamy

The version that we are using is 'Server version 4.1.15-log'.



-----Original Message-----
From: Daniel da Veiga [mailto:danieldaveiga@gmail.com]=20
Sent: Monday, June 05, 2006 2:04 PM
To: MySQL Win32 List
Subject: Re: FW: mysqld in hung mode

On 6/5/06, Ilavajuthy Palanisamy wrote:
> I have already verified the machine state.
> I have ample amount of disk space and memory. Looks like all the
system
> resources are in good condition.
>
> Surely if I restart mysql, it will start working fine.
> But, I need to find out how to recover from this state or what this
> state is so that I can avoid getting into this state.
>
> Through mysqladmin kill command I have killed all the pending queries
> (these queries are executed due to mysqldump command and they were
stuck
> up in 'Opening tables' state). After killing all the queries are in
> Killed state and they are not going away.
>
> Any idea under which circumstances mysql will go into this kind of
> state?
>

I've only seen this kind of behavior when a memory corruption occured
on my machine, and also once in an old version (<4.1.12), if that's
your case, you should upgrade to the latest version of your brand.

--=20
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--=20
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=3Dipalanisamy@consentry.c om


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: FW: mysqld in hung mode

am 05.06.2006 23:37:53 von Daniel da Veiga

Well my friend, my last shot would be to extend check and repair,
rebuilding indexes from scratch. Windows is used to inconsistencies
like that.

On 6/5/06, Ilavajuthy Palanisamy wrote:
> The version that we are using is 'Server version 4.1.15-log'.
>
>
>
> -----Original Message-----
> From: Daniel da Veiga [mailto:danieldaveiga@gmail.com]
> Sent: Monday, June 05, 2006 2:04 PM
> To: MySQL Win32 List
> Subject: Re: FW: mysqld in hung mode
>
> On 6/5/06, Ilavajuthy Palanisamy wrote:
> > I have already verified the machine state.
> > I have ample amount of disk space and memory. Looks like all the
> system
> > resources are in good condition.
> >
> > Surely if I restart mysql, it will start working fine.
> > But, I need to find out how to recover from this state or what this
> > state is so that I can avoid getting into this state.
> >
> > Through mysqladmin kill command I have killed all the pending queries
> > (these queries are executed due to mysqldump command and they were
> stuck
> > up in 'Opening tables' state). After killing all the queries are in
> > Killed state and they are not going away.
> >
> > Any idea under which circumstances mysql will go into this kind of
> > state?
> >
>
> I've only seen this kind of behavior when a memory corruption occured
> on my machine, and also once in an old version (<4.1.12), if that's
> your case, you should upgrade to the latest version of your brand.
>
> --
> Daniel da Veiga
> Computer Operator - RS - Brazil
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
> PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
> ------END GEEK CODE BLOCK------
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/win32?unsub=ipalanisamy@consentry.com
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: FW: mysqld in hung mode

am 06.06.2006 10:47:18 von Shane Bester

Hi,


> The version that we are using is 'Server version 4.1.15-log'.
>
>

Please see http://bugs.mysql.com/bug.php?id=12071 (Windows hang: 'Opening tables' or 'Waiting for table' lockup)
If you have InnoDB tables and notice SHOW TABLE STATUS in your processlist, then you should Upgrade to
latest version of 4.1.20. You should upgrade, anyway though.


Regards,
Shane

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org