Woo hoo segfault!
At one point I installed an new theme, actually a duplicate of an existing one I planned to modify. Just a directory copy within 'themes'.
Next I enabled it as default without previewing it or anything.
The entire drupal system crashed
Attempting to view anything returned a "Cannot Find Server" error (not any broken page sort of thing)
Turns out it was causing Apache to segfault!
Repair (lucky I had low-level DB access) was only possible by undoing my mistake by reverting the theme by hand;
INSERT INTO `variable` VALUES ('theme_default','s:6:\"asianz\";');
and manually purging the cache
DELETE FROM cache;
... It appears the trigger is having a theme of the same name as a module!
I was doing this because I was customizing a site for a client, and naming both the theme and the extension module I was making after the same project name ... which they are. But Ouch.
This error would have been impossible for an average user to fix without purging the database completely (if they could even do that) and the error returned (Cannot Find Server) naturally looks like your network has just fallen over!
Just FYI ... :-)
.dan.
