WSOD nightmare
I ran cron in a 5.5 drupal site (cron hadn't run for almost a year:( ) and I came up with wsod problem. Every page is blank.
I have tried:
a) I increased the memory in settings.php file up to 96M as mentioned in http://drupal.org/node/207036
b) entered this part of code in index.php file as mentioned here http://drupal.org/node/158043
<?php
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);
without the "<?php" part ...
c) Installed the dtools module to diagnose the problem but it threw an error about an undefined function :S
d)tried to clean and re-write the watchdog table as a link from this site mentioned (sry I can't find the link)
e)cleaned the cache table
f) Looked to the various logs I found and I came up only with "file not found errors" except the apache conf where there is a
" caught SIGWINCH, shutting down gracefully" (don't know what that is)...
g) Also I observed that there is not a /sites/all/modules folder, instead all modules are places where the core modules are in /modules :S
but I dont' think tha could cause a proble except tha the module should not be working... would it? (I saw some modules like: avatar_selection, chatroom which I think are third-party... that's why I mention it...)
Obviously nothing from them worked, and I restored to default after every change. The site is a public one(that means not mine) and I
really need to restore as soon as possible. I have full(I think so:P) access to server via ssh.
The server hosts other 2 running sites so I
haven't found the courage to try anything extreme like droping the database and re-importing it(phpmyadmin),(there is an 1 year or so backup) beacuse when I tried that to my localhost for expirement, I came up with "error in your SQL query" (and html code following...). Someone gave me the idea of creating a new db on server and try to import the backup without dropping the running one and then
configure the settings.php file with teh new db .... (that seems a good idea but is it safe?)
And a last note if this gives any clues... Some of the site's submenus were also threwing blank pages before the accident.
Thank you for your time, sry for the big story but it was an adventure drama one week now ...
=-=
you can certainly use a new db to import into. The fact that your site is still running 5.5 and you didn't keep your core updated, tells me you likely didn't keep your modules updated. That said, the reality is, a pletohra of things can be wrong with your site. 5.5 is 13 bug and security releases behind.
I'd try the new DB angle. I'd try updating the installation and contrib modules. I'd work on getting the folder struture correct. moving contrib to sites/all/modules
depending on the amount of content and how important it is to you, it may just be easier to scrub the site and start new with a 5.18 installation or better yet a 6.12 installation.
Thanks VeryMisunderstood. i
Thanks VeryMisunderstood. i will try a new database and if it fails, maybe I will built it from beginning(that ideas goes around my mind maybe more time than I would need to built the site :)
recover
I managed to somehow get the site back by re-arranging some contrib modules to the right folder /sites/all/modules and re-running cron...
Now I come up with more internal blank pages than before and there is generally a problem with uploading/creating paths because I can't
even post anything. All it displays is just the theme of the post and when I click it : blank page.
I noticed that the files foldes was also in top path and I copied it to /sites/all/files but nothing changed...
Are there any common modules which are know to cause WSOD?
Here is the site : www.ftuc.sealabs.net. You can notice the problem by exploring the top right sidebar menu, when you click to download something.
=-=
you shouldn't have moved the files folder. There was no cause to do that at all. Uploaded files aren't a module. By moving that folder everything you previously uploaded is likely broken based on what you had the administer -> file system settings set at when they were uploaded.
There is no single or combo of modules that cause a WSOD. Typically it's a memory issue.
Have you checked you apache error logs?
How did you increase memory? did you run a phpinfo() to make sure that memory is actually being increased?
In your original post you state that you tried to report errors to the screen. What happened? what error was/is being thrown?
I didn't move the files. I
I didn't move the files. I copied them and afterwards I deleted the /sites/all/files as I understood it was meaningless. Some files are displayed
so I don't think anything broke.
I have putted the
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);
in index.php but nothing comes up.
OOh, and here it comes. You are right, in phpinfo it displayes memory limit = 20M in core section!!
Well after a "deep search" ;) I found in /etc/php5/apache2/php.ini a line :
memory limit = 20M ; Maximum amount of memory a script may consume (16MB)
Is this the line I have to edit? That will affect also the other sites (2 of them) hosted (as I get it). Will it be safe?
=-=
There may be multiple php.ini files on your system. I'd copy one to my drupal root of the site that I want affected and change the memory_limit. then I"d run a phpinfo() on that single site. I wouldn't change the master (if that is the master) unless you want every site set to the same memory limit.
I copied one of the php.ini
I copied one of the php.ini files to site's main directory changed the memory_limit parameter, restarted apache, but phpinfo still displayes the
20M value :(
Also by editing .htaccess
Also by editing .htaccess file I finally managed to get 96M mem but the problem remains. Anyway I suppose this site needs re-building ...
To Anyone Who Had this problem
I disabled the PEAR Wiki filter module and everything fixed!