"Update Status" Proyect gives "White Screen of Death" on Windows Server 2003 error, event: 1030, 1053

+1 I have the same problem
Drupal 5.10 (on 5.3 the same)
MySQL 5.0.54
PHP 5.2.6
Apache/1.3.41 (nix)

I resolve this issue by disabling all modules, and enable first only Update Status module. After that i re-enabling all modules.

No, it looks like problem remain. When I enable all my modules WSOD return. I try memory_limit 75M and max_execution_time 120. But it didn't help.
This problem appear after moving to the new hosting service. Main differents beetwin them is PHP4 -> PHP5.

drupal 5.10, update-status 5.x-2.3

to me it looks as if the update status server (wherever that is) isn't responding. i don't get a 'white screen of death,' but page generation hangs at /admin/build/modules after enabling a new module, i.e., when drupal tries to check the update status. the same thing happens when going to /admin/logs/updates manually.

i'm going to find out from the module code the URL where drupal get's it's update status from, and see if that's available manually, but for now my drupal site, and apparently others, aren't able to collect the upd-status...

i noticed this happening today only but suspect it's been going on for the last few days.

Same here but on CentOS server. Never happened to me before.

I'm getting this in 5.2 and 5.3 after upgrading to MySQL 5.0.67 and PHP 5.2.6. Before, when running PHP 4 and MySQL 4 everything was fine. Now it runs until it times out.

Running Drupal 5.10 and Apache/2.0.52 (Red Hat)

strange, now everything works fine again. the main update source at http://updates.drupal.org/release-history didn't seem to have any problem, but when i wasn't able to get the update report, i had a new module enabled, trackback.

after disabling trackback update_status was working ok. when i now enabled trackback again, everything is still ok, so i assume that at that time trackback module wasn't able to connect to it's update status source.

in any case, since everything works fine again, i won't be able to figure out what went wrong...

where is the track back thing. IS this in drupal or in windows 2003 server?
I'm having problems with the update status module on all my installs of drupal.

Thanks.

Antonio

I still thinking that windows 2003 server is my problem.

I was just submitting a bug error over at workflow-ng:

"enabling the workflow-ng UI 5.x-2.1 caused a WSOD with the browser location stalling at admin/build/modules/list/confirm. Further investigation found this to be Dependant on whether Update Status 2.3 module was enabled or not."

for me this is on a live linux based server. I have updated everything on an Ubercart enabled site to drupal 5.11. All modules were added one by one with update status being the first, and updates being checked for between every module I enabled, and update.php being run for each one if required. any further information requests are welcome.

I have the same problem with Drupal 5.12 and 5.3
Apache/1.3.39 (Unix) mod_fastcgi/2.4.2 mod_gzip/1.3.26.1a mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.30 OpenSSL/0.9.7a PHP-CGI/0.1b
MySQL 4.1.22, CentOS

Same problem here,
Only on Drupal 5.13 not on Drupal 5.12 core

#222073: Update Status causing Drupal to run very slowly