Blank Screen (WSOD)
I am configuring a new Drupal 6.x (6.1 for now) on a GoDaddy dedicated server. The set up will be and exact copy of an installation currently running with no error on a GoDaddy shared server. My intention is to move it to a dedicated server to increase the DB performance thereby increasing the speed of page loads.
I've tried several ways to copy the site but kept running into WSOD problems on the modules list page when enabling modules, so I decided to just use the Plesk Control Panel installation of v 6.1 to later upgrade to v 6.10.
I've been happily humming along adding then enabling modules in an orderly fashion with no issues. I uploaded the addresses module folder which adds the "Addresses", "Addresses-CCK", Addresses-Phone/Fax", Addresses-Users" modules to the list.
As soon as I enable the "Addresses" module and the modules page refreshes, I get the WSOD.
I then enabled error reporting in index.php and it displays these errors:
Notice: unserialize() [function.unserialize]: Error at offset 2 of 20 bytes in /var/www/vhosts/mysonora.net/httpdocs/includes/bootstrap.inc on line 425
Notice: unserialize() [function.unserialize]: Error at offset 21 of 31 bytes in /var/www/vhosts/mysonora.net/httpdocs/includes/bootstrap.inc on line 425
I checked the variables table in the DB and can't determine what could be causing these errors, however when I disable the "Addresses" table using phpMyAdmin, I then get my list of modules however I still get the unserialize errors and I get these no matter what page I'm on. I suspect these errors existed from the beginning and may not be related to my WSOD issues.
Additionally, I installed various OG modules but when I enable the "Organic groups Views integration" module the same thing happens with the WSOD and when I disable the module I get my modules list back.
When I get the WSOD it seems to only happen with the modules page "/admin/build/modules". All other pages display.
I have searched and searched the forums and issues and I have reviewed the WSOD troubleshooting page to no avail.
At this point I'm stuck with no where else to go. If I can't resolve this issue I'll be forced to cancel the dedicated server account and stay with a poorly performing site on a shared server.
Any _SPECIFIC_ help with this problem would be greatly appreciated.
Thanks.
=-=
6.1 isn't a version to use. If I remember correctly there were issues that weren't cleared up API wise until Drupal 6.2 or 6.3
whether or not that is the cause of the problem you are experiencing I can't say but if you were going to upgrade from 6.1 to 6.10 I'd of done that before throwing contrib modules at my install that have grown past the previous releases of drupal 6.x
using the error as as search term I found: http://drupal.org/node/167764
have you gone through and made sure you are using the lastest pathauto.module? if in use at all?
They also mention OG in that thread.
WSOD is usually related to not enough memory for PHP to process. have you checked your apache error logs?
what is your memory limit set to in php.ini?
These error messages are not
These error messages are not errors, they are just PHP "notices" for the developers about some bad practice. On a live server they should be disabled in PHP's error_reporting settings.
Drupal 6 is E_ALL compliant (doesn't have any php notices) but most modules are not (Drupal 5 was not either). There are several ways to fix the problem.
In php.ini (system-wide setting, the best way if you are not doing PHP development):
error_reporting = E_ALL & ~E_NOTICEOr, in .htaccess (per directory setting, overrides the previous one):
php_value error_reporting 6135Or, in sites/default/settings.php (setting within a running script, overrides the previous ones):
ini_set('error_reporting', E_ALL & ~E_NOTICE);If you still see errors (not notices), you may get another idea about what is causing the WSODs. If not, it may be the memory_limit (http://drupal.org/node/207036) or some timeout.
Blank Screen (WSOD)
I guess I should have been clearer. I am fully aware that these are notice messages but I will continue to refer to them as errors since, in essence, they are reporting something bad. Anyway, as I mentioned, I'm not sure if this is related to my issue.
To further detail what I have done. I started this out by first, installing the instance by 1) copying the code from the shared account; 2) importing the database that was exported from the shared account; 3) making appropriate changes to the settings.php for the database and making sure the .htaccess file was correct.
Then I tried to open the site and got NOTHING BUT WSOD on ALL pages. I couldn't fine anything here that would help.
Then I completely removed and started over. I used the default GoDaddy (v6.1) application in Plesk and then upgraded to v6.10 then uploaded all my modules and themes from the shared site, then dropped all the tables that were created from the Plesk install and imported the DB from my shared account. Then I got a bunch of permissions issues that I believe I resolved. Then started getting these stupid WSOD issues all over again.
So I figured I try to go back to the v6.1 Plesk install, add the modules and themes and then when the file structure was matched to my shared account, wipe the DB and import from my shared account.
Unfortunately I couldn't get that far because I started to get these Freakin stupid WSOD issues as I was enabling the modules which prompted this post in the first place.
I appreciate being told "6.1 isn't a version to use" and asking "what is your memory limit set to in php.ini?".
What I really need are some hard numbers as to what the memory should be so I can make sure that is what I have and some hard samples from others experiencing WSOD when enabling modules. Also, if someone reading this has successfully set up an installation on a GoDaddy dedicated server running Fedora 8, please send along their server configuration details as well as their Drupal configuration, that would go a long way to putting me in the right direction.
As I said, I have read nearly ALL the posts and issues that come close to this and the troubleshooting document (not very concise in my opinion) and am getting absolutely no where. I might just have to cancel the dedicated hosting account and tell my HOA board that their stuck with a crappy performing site or go out and hire a professional company that specializes in HOA portal sites.
Blank Screen (WSOD)
Incidentally, the memory limit is set to 32MB so that can't be the issue.
=-=
There is no set standard on memory. Each module consumes a different amount of memory. Thus a combination of modules = X
Core recommends 16MB of memory alone. use the imageapi? it recommends 96M of memory. Some modules may not be optimized and so on...
either way, WSOD are recorded to an error log somewhere. Locating these logs may prove fruitful.
Since this is a site being moved, did you clear the cache database tables? to ensure no cache was left behind?
Even if I endanger myself to
Even if I endanger myself to get some of your frustation but 32M might not alway be enough.....
e.g. http://drupal.org/node/310150 ; http://drupal.org/node/326411 (also a comment on imageapi)
a quick search memory+og on google got also results but mostly at drupalnorge.
edit: telephone and commenting-> don't mix because it makes you slow....
Oh, no danger :)
In fact, before reading your reply I Shelled in to the server, edited php.ini increasing the max memory to 64M and lo and behold, the issue disappeared. I need to be better at reading. :)
Thanks!!