Restoring to a recent db backup (restored successfully, no improvement) Running cron via drush (cron success, no improvementĬlearing a large watchdog table via drush (cleared, but no improvement)Ĭlearing cache (cleared, anon users could still see the site but slower) On the shared hosting sites, there is no correlation between amount of users/content and the headers. On the PS, the largest site (most users and content) works ok for cached/anon usage, but logged in users get 500 errors, so I can't even log in as admin to up performance. I have 3 sites on a PS and 3 personal site on shared 2 of the PS sites are fine, 1 of the shared is working. Memory_limit = 80M Maximum amount of memory a script may consume (8MB) Max_input_time = 1600 Maximum amount of time each script may spend parsing request data
Max_execution_time = 1600 Maximum execution time of each script, in seconds
I was able to eliminate these errors by doing the following:ġ) created a custom php.ini following these directionsĢ) edited the new php.ini to increase values for resources and change post_max_size : I believe that it was those users with slower internet connections that were having the problem, but I couldn't prove that beyond an educated guess. For example, posting content or submitting a contact form was problematic. The site worked fine for many things, but some users would get 'page not found' (internal_error.html in watchdog 'premature end of script headers' in error.log) errors doing things on the site that I never had problems doing. I moved a site from shared hosting to dreamhost_ps last weekend. Although this is closed, I'd like to add a note for Dreamhost users in case they are struggling with "Premature end of script headers" (a server error found in user/logs/http./error.og) and 'page not found' / internal_error.html (found in Drupal's log).
0 kommentar(er)
