Hello,
Since a few weeks, I encounter a WSOD while trying to access some admin pages, especially :
/admin/config
/admin/modules/update
/admin/reports/status
/admin/reports/updates
However, my website still runs normally when my actions are just about adding or editing pages or articles.
WSOD occurs even if all additional modules are disabled. I managed to follow the WSOD handbook recommendations : my root index.php is modified to display errors, but the WSOD still don't give any message.
With phpmyadmin, I flushed the cache, flushed the sessions, and also flushed the search indexes and results, and no evolution was noticed.
I was so upset I decided to delete all a restart from a Drupal 7.16 fresh installation and, surprise : my "friend" WSOD appears as soon as I try to access to /admin/config
Apache logs don't give any info except the GET request when calling /admin/config is executed with return code 200
Drupal : version 7.16
PHP memory_limit : 512M
PHP max_execution_time : 360
What surprises me is that the website was fully functional with a bunch of additional modules but no manipulation was done when the first WSOD appeared.
Although, I thought there was a filesystem permission issue, but if the WSOD happened with a fresh install from scratch, neither a module or a permission can explain it.
Thanks for your help…
Comments
This is very odd. WSOD
This is very odd. WSOD without any error page does not look like a server permission problem, although I have more than once seen folder ownership change apparently by itself on a Linux server, so that could cause it. If you get this on a new install (of which I have done many without such problems) I suggest you take a hard look at the quality of your server. Setting a high max memory for PHP means nothing unless the memory is really available. In addition Drupal can easily get disk-bound if the database server is not well set up (in terms of hardware and / or mysql settings). If you are on shared hosting and wish to remain on shared hosting, you should certainly move to a Drupal specialist, who will sort this out. if you are running your own server you might need to take a careful look at the setup and resources. When running your own server, one place to look is in the server OS logs (dmesg, messages). Apache seg faults and mysql running out of memory and and so on can show up there.
Digit Professionals
Problem solved
I explained my Drupal problems to my webhoster. I asked him to restart Apache services, in order to see if PHP zombie processus may be the cause. Nothing changed...
Then, he migrated my domain from PHP version 5.3.10 to PHP version 5.3.18 and... everything works fine now !
Analysis are still running, but there is no more WSOD for the moment. Case closed.
Come
//camposm.gps5.com/