Hrrmph. Second time it's happened -- I go to the site, and Drupal serves an error page saying there are too many mysql processes. Killing and restarting Apache and MySQL fixes the problem temporarily, but I guess something in Drupal is spawning sleeping SQL processes that never get closed out. There's no custom MySQL access in the site, so it's probably a bug in Drupal somewhere, and I don't think I want to spend the time to try to track it down. I may try upgrading to Drupal 6.0, though, in the hope that the problem's been fixed by someone else (we're using 5.7 at the moment).
















