Re: Repeated 100% CPU problem in FreeBSD

2004-01-20 Thread Arnaud Pignard
0x0 in ?? () If you see that, get rid of DNS lookups. - Original Message - From: "Arnaud Pignard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 16, 2004 7:06 PM Subject: Re: Repeated 100% CPU problem in FreeBSD > Hi ! > > Anyone find a s

Re: Repeated 100% CPU problem in FreeBSD

2004-01-20 Thread Ken Menzel
- Original Message - From: "Arnaud Pignard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 16, 2004 7:06 PM Subject: Re: Repeated 100% CPU problem in FreeBSD > Hi ! > > Anyone find a solution for this problem ? > > We have 2 m

Re: Repeated 100% CPU problem in FreeBSD

2004-01-16 Thread Arnaud Pignard
Hi ! Anyone find a solution for this problem ? We have 2 mysql server with same problem. Happen like every 1-2 months. Regards, -- Arnaud Pignard ([EMAIL PROTECTED]) Frontier Online - Opérateur Internet -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscri

Re: Repeated 100% CPU problem in FreeBSD

2003-11-28 Thread Andrey Kotrekhov
SQL I have the same situation. I set skip-name-resolve in my.cnf. But sometimes mysqld get all CPU. I can't notice strong dependences between name resoving and mysqld stuped. > Hello, > > Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9 > system. However, today, unexplicably

Re: Repeated 100% CPU problem in FreeBSD

2003-11-27 Thread Jeremy Zawodny
On Thu, Nov 27, 2003 at 06:25:38PM -0600, Dan Nelson wrote: > In the last episode (Nov 27), Chris Elsworth said: > > Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9 > > system. However, today, unexplicably, it's run into the same problem > > 3 times now; a couple of the thread

Re: Repeated 100% CPU problem in FreeBSD

2003-11-27 Thread Dan Nelson
In the last episode (Nov 27), Chris Elsworth said: > Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9 > system. However, today, unexplicably, it's run into the same problem > 3 times now; a couple of the threads suddenly start eating 100% CPU > for no good reason while doing a