5.0.19 on Solaris: hangs after several days

I upgraded from 4.1.12 to 5.0.19 on Solaris (5.8 sun4u). It generally
works, but after a few days (and sometimes a few hours), a sequence
of events seems to take place:

- queries lock (judging from the processlist)
- the connection limit (around 100) is reached
- the server becomes unresponsive and has to be killed hard (kill -
TERM doesn't work)

Besides upgrading the tables, nothing has changed between 4.1.12 and
5.0.19 (same hardware, some OS).

As an additional oddity, the only indication of trouble in the error
log is

060409 21:10:17 [Note] /proj/signal/mysql-5.0.19/bin/mysqld: ready
for connections.
Version: '5.0.19-standard-log' socket: '/proj/signal/mysql/
mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)
060409 21:40:56 [Warning] Got signal 14 from thread 8
[server unusable shortly thereafter]

I'm only using myISAM tables.

Henning Schulzrinne
Columbia University

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: 5.0.19 on Solaris: hangs after several days

Hi Henning,

>I upgraded from 4.1.12 to 5.0.19 on Solaris (5.8 sun4u). It generally
>works, but after a few days (and sometimes a few hours), a sequence of
>events seems to take place:

First of all, please, describe the exact upgrade procedure. Did you use
mysqldump and then reloaded data in 5.0.19 or simply installed new binaries?

> - queries lock (judging from the processlist)
> - the connection limit (around 100) is reached
> - the server becomes unresponsive and has to be killed hard (kill - TERM
> doesn't work)
>
> Besides upgrading the tables, nothing has changed between 4.1.12 and
> 5.0.19 (same hardware, some OS).

Please, send the SHOW PROCESSLIST result before/during this hang.

Anyway, looks like you have to add a bug report about this at
http://bugs.mysql.com

Best regards,
--
Valeriy Kravchuk, Support Engineer
MySQL AB, Kiev, Ukraine, www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: 5.0.19 on Solaris: hangs after several days

> First of all, please, describe the exact upgrade procedure. Did you
> use
> mysqldump and then reloaded data in 5.0.19 or simply installed new
> binaries?

No, I simply installed the new binaries and ran the --upgrade process.

Would this likely make a difference? I'm more than happy to try this
if this will likely make a difference. (I have run mysqlcheck, with
no interesting results.)

> Please, send the SHOW PROCESSLIST result before/during this hang.
>
> Anyway, looks like you have to add a bug report about this at
> http://bugs.mysql.com

The practical problem is that the database is part of a fairly
critical system and I was only able to get the process list once (but
didn't save it). Unfortunately, it seems to happen mostly in the
middle of the night (and I find hundreds of email messages in my
mailbox complaining the next morning...). Thus, I've had to resort to
restarting the server every three hours for now.

I did notice that some queries have ridiculously long lock times:

# User@Host: x[x] @
# Query_time: 518 Lock_time: 510 Rows_sent: 2 Rows_examined: 14
SET timestamp=1144720272;

When I re-run the query an hour later, on the same system, the query
time is maybe 0.16 seconds. I don't know if these are at all
connected. (The system did not crash at that time.)

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: 5.0.19 on Solaris: hangs after several days

Hi,

> No, I simply installed the new binaries and ran the --upgrade process.

In general, only mysqldump and restore will give you correct results.

> Would this likely make a difference? I'm more than happy to try this if
> this will likely make a difference. (I have run mysqlcheck, with no
> interesting results.)

Please, try. You can also check newer version, 5.0.20, now officially
released. If the problem will appear again in 5.0.20 even after restore,
open a new bug report at http://bugs.mysql.com.

Best regards,
--
Valeriy Kravchuk, Support Engineer
MySQL AB, Kiev, Ukraine, www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org