Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By IreneKraus on
My site is running Drupal v5.9, and for some strange reason the other day I could not run the update.php script anymore. That is, I click on the link from within the admin/build/modules to run it and the browser window goes blank. I've tried this in both FireFox 3.x and IE7. Spent the past couple of days completely rebuilding my site on my development server, as I thought I somehow screwed something up on the back end. Now I'm having the same thing occur there when I just tried to install an update for one of the modules in use! (Messaging) Really don't want to 'dump' everything and start all over again, as this takes so long to do!
I've made sure the caching under Performance is disabled. (Normally keep that set to 'normal.') Anything else I should look at? Help!
Comments
Blank page is usually a
Blank page is usually a memory error. Check your server error logs to be sure. What is your PHP memory limit set to?
- Corey
Copied from the PHP
Copied from the PHP Configuration section from my hosting service:
Resource Limits max_execution_time Maximum execution time of each script, in seconds 30
Resource Limits max_input_time Maximum amount of time each script may spend parsing request data 60
Resource Limits memory_limit Maximum amount of memory a script may consume (32MB) 32M
The 32MB for memory seems more than generous to me. I'm not sure where to look to find the server error logs with this new hosting company. There are no 300 errors listed at all.
Irene Kraus a.k.a. The Computer Lady
Design COMP - www.design-comp.com
Irene Kraus a.k.a. The Computer Lady
32MB does seem sufficient,
32MB does seem sufficient, depending on what modules you have installed. I would confirm that number, though. Drop a
phpinfo()page in and make sure that PHP is actually getting everything that the configuration says it is. I stress this point, because it happened to me once, and took two weeks for tech support to get it straightened out *after* I found the problem for them.Server error logs can usually be found in your hosting account control panel (ex. cPanel). I would expect to find HTTP 500 errors, not 300.
- Corey
32MB does seem sufficient,
I'm not sure how to drop a phpinfo()page into anything, as I'm far from a PHP expert. (Working on it!) I can download the raw server logs, but I'm not sure what format those really are in, as when I open it up in a text editor I'm seeing all hex codes. As to the hosting web server being possibly wrong, quite possible as this was a new server the company put my account on. At least this company really is providing me with PHP 5 support unlike my former company!
Irene Kraus a.k.a. The Computer Lady
Design COMP - www.design-comp.com
Irene Kraus a.k.a. The Computer Lady
=-=
using a text editor
add the code above to a new file
name the file phpinfo.php
upload it to your public root
call the file in your browser and it will show you all the default php settings (info)
it was almost a tie... -
it was almost a tie...
- Corey
create a file named
create a file named phpinfo.php and put this in the file:
upload it to your server, and access the page (ex. http://www.example.com/phpinfo.php).
- Corey
Wow! Thanks for the idea!
Boy did that create an interesting document! Searching on down thru it, I think these the lines that matter the most under the PHP core info:
max_execution_time 30 30
max_input_nesting_level 64 64
max_input_time 60 60
memory_limit 32M 32M
Took the file off that server as it reveals a mess of info others shouldn't know! So, I guess that looks okay... I'm still stumped as to cause here.
Irene Kraus a.k.a. The Computer Lady
Design COMP - www.design-comp.com
Irene Kraus a.k.a. The Computer Lady
Yes, it is a good idea to
Yes, it is a good idea to remove phpinfo.php from your site.
Just to confirm: the WSOD only happens on update.php?
I would still try to set your memory limit absurdly high (php.ini, perhaps), and use phpinfo to confirm that the setting is in effect, just to rule out the memory issue completely.
Also, your raw logs can often be viewed with a simple text editor. What are you using? (BTW, notepad will choke if the files are large!)
- Corey
Only on running update.php
So far, only on trying to run update.php. Had some memory problems on my local development server (Apache2Triad), which I corrected by altering the settings.php file as mentioned at bottom here:
http://drupal.org/node/66105
Namely, that I added that into the settings.php for the install of Drupal. I'm working on a Windows XP machine, so I had to take the read-only flag on that off first, and then put it back on when done. Trying this idea on that install (not on hosted web server) to see if that corrects problem there.
Nope. Still getting blank page. So, what else should I try to fix? Hoping I can fix this for install on hosted space so I don't have to try to rebuild entire site! Don't get me wrong, I'm learning new stuff by doing that... But, really! ;-)
Irene Kraus a.k.a. The Computer Lady
Design COMP - www.design-comp.com
Irene Kraus a.k.a. The Computer Lady
check out this page for more
check out this page for more ideas: http://drupal.org/node/158043
- Corey