List:General Discussion« Previous MessageNext Message »
From:Jeremy Zawodny Date:August 4 2002 11:03am
Subject:Re: SIGPROF problem in FreeBSD 4.6 (REPOST)
View as plain text  
On Sat, Aug 03, 2002 at 11:59:56PM -0400, mysql@stripped wrote:
> 
> Symptoms:
> 
> mysqld locks itself in a tight loop, consuming all available CPU cycles.
> a simple "kill" sometimes kills the daemon, other times a -9 is required.
> While in this state, any access to the daemon stops - mysql queries simply
> hang.

Hmm.  Looks like a problem we solve recently, but yours is a bit
different.  We found that FreeBSD's not-so-thread-safe gethostbyname_r()
causes problems for MySQL.  So it's best to use --skip-name-resolve when
starting it up.  Maybe the same bug is somehow triggering this?  Seems
unlikely, but ya never know...

Jeremy
-- 
Jeremy D. Zawodny     |  Perl, Web, MySQL, Linux Magazine, Yahoo!
<Jeremy@stripped>  |  http://jeremy.zawodny.com/

MySQL 3.23.51: up 66 days, processed 1,370,770,519 queries (238/sec. avg)
Thread
SIGPROF problem in FreeBSD 4.6 (REPOST)mysql4 Aug
  • Re: SIGPROF problem in FreeBSD 4.6 (REPOST)Jeremy Zawodny4 Aug
    • Re: SIGPROF problem in FreeBSD 4.6 (REPOST)David Miller10 Aug
      • Re: SIGPROF problem in FreeBSD 4.6 (REPOST)Dan Nelson10 Aug
        • Re: SIGPROF problem in FreeBSD 4.6 (REPOST)Jeremy Zawodny10 Aug
      • Re: SIGPROF problem in FreeBSD 4.6 (REPOST)Jeremy Zawodny18 Aug