Hello.


Very often similar symptoms causes various lock problems. Do you use

InnoDB? Try log_slow_queries to find hung queries. 



"Paul Smith" <[EMAIL PROTECTED]> wrote:

> Hi all;

> 

> I have a Mysql 3.2.58 server running on Solaris 8 (the latest 3.2

> version downloaded from Mysql.com).  The system is a Ultra-250 server

> with multiple CPUs and 2G RAM.  There are many databases but they're not

> large and the load on the system is not high at all.  We're using this

> older version because we developed the database with the 3.2.x release,

> years ago, and don't have the manpower to check to see if the newer

> version will work or fix issues we might run into--although we may have

> to find a way.

> 

> 

> This version worked without problems for over a year.  But, for the last

> 4-6 weeks we've seen a problem once every 8-10 days where the server

> hangs and will not come back.  Attempts to attach "normally" hang;

> current operations hang; etc.  Using processlist shows some processes

> which have existed for a long time; that may or may not be correct, I'm

> not sure.  Almost all our queries are coming in through the Perl DBI/DBD

> interface.

> 

> When I try to use mysqladmin kill they don't die; they do go to a state

> of "killed" though.

> 

> When I try to myqladmin flush-tables, that hangs.  Flush-logs works but

> there is nothing interesting in the logs.

> 

> When I try to run mysqld stop, the server process doesn't stop, although

> most of the hung requests

> 

> When I run strace on the PID, I get this:

> 

>  lwp_sema_wait(0x1bfe50

> 

> then it hangs until I ^C.

> 

> I have to kill -9 the server PID to bring it down.  Then I check my

> tables but so far (cross fingers) they've all been fine except they are

> not shut properly, so I fix that with myisamchk.

> 

> 

> Since I have not changed anything I suspect that the IS folks have

> installed some new patch on the Solaris system which is causing this

> problem to appear, but I have no proof of that.

> 

> 

> Does anyone have any advice or information for me: places to look,

> things to do, etc. etc.?  While so far we haven't lost any data this is

> a problem since it seems like it will continue to happen.

> 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to