can't run update.php on localhost

By Mokey on 8 Mar 2013 at 19:39 UTC

I just managed to get a copy of my site running on localhost with wampserver. When I tried to upgrade to the latest version of from Drupal 6.x to latest 6.x (I think it's 6.22 to 6.28 and can look it up if that's relevant), running update.php seems to be timing out after 30 seconds. The message I get is "This page can't be displayed" My apache log shows:
::1 - - [08/Mar/2013:14:12:15 -0500] "GET /coop/update.php HTTP/1.1" 302 -

I don't really know what I'm doing. I've googled to the best of my ability, but don't really know what to look for. In order to get my site running locally at all, I increased a lot of timeouts in the apache php.ini file:
max_execution_time = 5000
max_input_time = 5000
I tried setting these values in the php directory php.ini file as well. I don't see anything set to 30 seconds which is how long the browser tries before giving up.

Windows 8
Wampserver 2.2
Apache 2.2.22
PHP 5.3.13
MySQL 5.5.24

Comments

Provided you have good

John_B commented 9 March 2013 at 20:27

Provided you have good internet connection, the first thing I would check is whether the request is being blocked by Windows Firewall.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

WSOD

Mokey commented 13 March 2013 at 19:25

So, apparently, this is called the white screen of death, or WSOD. There are several pages that are helpful with diagnosing the WSOD. None of them really helped me, though I did read somewhere that modules can sometimes cause issues. I finally figured out my problem. A clean Drupal install worked, but not my complex site (which works fine on my host, just not locally). So, I started adding my modules to the clean install until it stopped working. Turns out there's some problem with Mass Contact (that I don't know enough to diagnose).

Ensure you are using the most

John_B commented 14 March 2013 at 10:54

Ensure you are using the most recent release of this module. Next steps are to check that Drupal core plus the problem module (with nothing else enabled) still causes the problem. (It could be interaction of Mass Contact with some other contributed module). Then, check Drupal Recent Log Messages, and the server log for errors. This should give some information. Check the issue queue for the module and if you have found an issue which has not yet been reported, you can than raise an issue and hope that the maintainers will help with fixing it.

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

[deleted duplicate post]

John_B commented 14 March 2013 at 10:55

[deleted duplicate post]

Digit Professionals specialising in Drupal, WordPress & CiviCRM support for publishers in non-profit and related sectors

adding new modules

mahayh commented 26 May 2017 at 13:48

I added one new module after that i started facing a similar issue..many links couldn't open in drupal 7. after removing the module , all worked fine!