nm that didn't fix it

talking out loud ...

getting lots of page not found errors in the log, can't believe that would be enough to kill it.  maybe it's getting indexed?

found this:

When using Drupal’s “pretty URLs” which uses Apache’s mod_rewrite to, well, make URLs pretty, all requests that the web server does not process (including errors) will go through Drupal. Going through Drupal means a long boot-strapping process to initialize Drupal and load all its modules, and at least one database request to find out a URL does not exist and to return an error 404. Too many requests for a non-existent file can basically become aDoS attack.


Ryan LeTulle, Web Developer

blog:  bayousoft.com
twitter: @bayousoft





On Thu, Jan 6, 2011 at 2:43 PM, Ryan LeTulle <bayousoft@gmail.com> wrote:
I increased the max mysql connections to 200 & restarted mysql but was still getting the site offline page almost immediately after.

Settings > performance > caching mode was set to disabled.  I set it to normal.  Can this setting cause a site offline error?  So far it appears to have stopped and the pages seem snappier (which I would expect).

Ryan LeTulle, Web Developer

blog:  bayousoft.com
twitter: @bayousoft





On Thu, Jan 6, 2011 at 1:18 PM, Ryan Letulle <bayousoft@gmail.com> wrote:
Thx

Ryan

i4

On Jan 6, 2011, at 12:34 PM, Jamie Holly <hovercrafter@earthlink.net> wrote:

Most of the time it's PHP unable to connect to the database. Check your PHP error logs and see if it gives you a hint.
Jamie Holly
http://www.intoxination.net 
http://www.hollyit.net

On 1/6/2011 1:14 PM, Ryan LeTulle wrote:
Training users on a new Drupal site today and getting lots of site offline errors.  Can someone tell me what triggers this?  PHP memory setting?


Ryan LeTulle, Web Developer

blog:  bayousoft.com
twitter: @bayousoft



--
[ Drupal support list | http://lists.drupal.org/ ]