By tdc_sunrise on

Live Drupal 5.2.8 site is working well on ISP host. Have recently volunteered to support the site for my church. The site looks and works well on the host but has not been upgraded in quite some time. It needs needs several module security updates. I was hoping to get the site up to major version 6 if possible. I was attempting to get a local test site running so I can safely and efficiently test the minor and major updates before deploying to the live site.

I'm fairly new to Drupal. I am a senior level ASP.NET & SQL Server developer by profession. I have spent a great deal of time reading Sams textbook and tutorials on Drupal. Needless to say, I'm nearly ready to rewrite this site but I would much rather support and build on what they already have. The site looks great and works fairly well!

I would appreciate any help. Here is where I'm at...
--------------------------------------------------
Drupal on Production site reports following specs:
Server Apache
Drupal 5.1.8
PHP 5.2.13
MySQL 5.0.81
--------------------------------------------------
Local Test Environment being created:
Windows 7
XMAPP 1.7.1 (Apache 2.0, PHP 5.2.9, MySQL 5.0.51a)

**** Please note that all XMAP sample applications work correctly! ****

Launching Drupal Site on test box processes for 20-30 seconds then gives the following error:
--------------------------------------------------
Firefox 3.6.3:

ERROR MESSAGE: The connection to the server was reset while the page was loading.
--------------------------------------------------
Windows Error Log;

Faulting application name: httpd.exe, version: 2.2.11.0, time stamp: 0x493f5d44
Faulting module name: php5ts.dll, version: 5.2.9.9, time stamp: 0x49a56925
Exception code: 0xc00000fd
Fault offset: 0x00151eff
Faulting process id: 0x163c
Faulting application start time: 0x01cae672d460d2b3
Faulting application path: C:\xampp\apache\bin\httpd.exe
Faulting module path: C:\xampp\apache\bin\php5ts.dll
Report Id: 31f229a0-5266-11df-ad89-0016414b7fcb
--------------------------------------------------
Have searched Drupal community and Googled extensively. Have taken following suggestions:

-Have copied libmysql.dll file from PHP folder to Win32 folder and deleted other copies in Apache and MySQL.

-Environment Path = %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\QuickTime\QTSystem\;C:\xampp\php;C:\xampp\mysql\bin;

-Ran Process Monitor looking for clues.

Also installed and uninstalled newer versions of XAMPP, WAMP and even separate installs of Apache, PHP, etc. in failed attempts.

I would appreciate any help. I feel like it's something quite easy to fix once found but isn't that always the case?

Thanks,
Sunrise

⋅ Categories: Drupal 5.x

Comments

dnuss’s picture

dnuss commented

I have experience testing various 5.xx versions of Drupal in a XAMPP stack environment on Windows ( XP not Windows 7), so I would be willing to see if I can get you going....

Here is my XAMPP / Windows info:

  • Windows XP Build 2600 Service Pack 3
  • XAMPP for Windows Version 1.7.1
  • Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i PHP/5.2.9
  • PHP Version 5.2.9
  • MySQL Server version: 5.1.33-community
  • MySQL client version: 5.0.51a

So that I can best answer your questions, please let me know the following:

From the .\modules\system\system.info file on your local machine, what is value of the [version = "5.xx"] variable?

Are you getting your errors while trying to run the install.php script of a clean version of 5.xx Drupal?

If not, exactly what were you trying to do when you get those errors, as you describe "Launching Drupal Site"?

Dave

tdc_sunrise’s picture

tdc_sunrise commented

Dave,

Thanks so much for helping me!

My system.info file contains the following:

; $Id: system.info,v 1.3 2006/11/21 20:55:35 dries Exp $
name = System
description = Handles general site configuration for administrators.
package = Core - required
version = VERSION

; Information added by drupal.org packaging script on 2009-05-13
version = "5.18"
project = "drupal"
datestamp = "1242244862"

I haven't ran a clean version of 5.xx Drupal in this test environment but will do so and let you know.

Tony

tdc_sunrise’s picture

tdc_sunrise commented

Dave,

The live site is running Drupal 5.18 on the host. I downloaded and installed a clean Drupal 5.18 site on my laptop without issue. The new clean site comes right up and seems to function ok! What do you recommend as my next step?

Thanks,
Tony

dnuss’s picture

dnuss commented

Now that you have a successful install of baseline 5.18 on your test machine, the next step is to go through the “host vs. test - what is different” process. Your production 5.18 runs fine on the host server, but fails when installed on your test machine. There are several areas that would be suspect:

  • .htaccess file content
  • settings.php content
  • core features turned on in the host, but not turned on in the baseline Drupal test environment
  • contributed modules installed on the host, but not installed in the baseline Drupal test

While you will find in the Drupal forum many different suggestions on how to setup a test environment, I will offer to you how I setup and use my environment. On my test machine, I have XAMPP installed on drive “G”, so all my Drupal installs are relative to the “G:\xampp\htdocs” folder. I then create a folder for the Drupal version I am testing, in this case it is “G:\xampp\htdocs\drupal-5.18-drupal” which is my naming convention for the “fresh install of Drupal 5.18” (naming is also applied to the database names in MySQL). I can then “clone” this baseline installation at anytime to “seed” other testing scenarios, for example “G:\xampp\htdocs\drupal-5.18-test1”.

When I want to download and test my current hosted Drupal installation, I would create another folder “G:\xampp\htdocs\drupal-5.18-host” and either use FTP to download into that folder or download a zipped file containing the entire contents of my hosted site into that folder. Then of course I would import the hosted database into its local MySQL counterpart. Now here is what I consider an important part (others might consider it to be “old school”), I always “clone” that host installation into another test version, leaving the original for research and comparison purposes. In this scenario I would end up with the following folders:

  • G:\xampp\htdocs\drupal-5.18-drupal
  • G:\xampp\htdocs\drupal-5.18-test1
  • G:\xampp\htdocs\drupal-5.18-host
  • G:\xampp\htdocs\drupal-5.18-hosttest1

Using appropriate MySQL exports at key testing points, I can “rollback” or create other test “freeze points” for research and compare purposes.

Whatever testing structure you setup, you can now start looking for the differences that make your host system break when installed locally. I would immediately look at the .htaccess and settings.php files to make sure they have the appropriate values for the local setup. Using a compare program will also show what changes were made by the persons who originally installed your host system (and even detect changes made by your hosting service or hackers).

Once you establish that .htaccess and settings.php or OK, then start turning off contributor modules, and note that you may have to do that using a SQL script if you can’t log in as administrator in the Drupal install.

I hope this gets you started. I will keep monitoring this issue and get more specific as needed.

tdc_sunrise’s picture

tdc_sunrise commented

Awesome Dave! Solid advice. Some may consider your approach "old school" but rather I consider it prudence based on hard earned experience! I'll look at the .htaccess and settings.php files and follow up with a file compare as you instructed.

tdc_sunrise’s picture

tdc_sunrise commented

Dave,

I'm running Windows 7 Professional, 32-bit.

Uninstalled previous XAMPP.
Reinstalled XAMPP for Windows Version 1.7.1 onto newly created virtual hard drive (G:).
Created folders following your naming convention:
G:\xampp\htdocs\drupal-5.18-drupal
G:\xampp\htdocs\drupal-5.18-host

On host site copy...
Copied host files into G:\xampp\htdocs\drupal-5.18-drupal folder.
Imported copy of host database.

On clean Drupal site...
Copied Drupal 5.18 files into G:\xampp\htdocs\drupal-5.18-drupal folder.
Ran localhost/install.php, configured and tested..
http://localhost/drupal-5.18-Drupal is functioning correctly!

On host site copy...
Changed database server name to localhost in host settings.php file. Otherwise, file was nearly identical to clean Drupal settings.php file.
Granted database user configured above with full privileges in host database.

On host site copy...
.htaccess file differs from Drupal file on several lines. However, regardless of how the host .htaccess file is
configured, the following error is received when bringing up http://localhost/drupal-5.18-host. It doesn't seem to matter
how the .htaccess is configured. (Please note that I restarted the Apache server after each configuration change.)

Error Received:
Apache HTTP Server has stopped working,.,.,
Problem signature:
Problem Event Name: APPCRASH
Application Name: httpd.exe
Application Version: 2.2.11.0
Application Timestamp: 493f5d44
Fault Module Name: php5ts.dll
Fault Module Version: 5.2.9.9
Fault Module Timestamp: 49a56925
Exception Code: c00000fd
Exception Offset: 00151eff
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: d4eb
Additional Information 2: d4eb7cf28a4f910486e91a11f70d294f
Additional Information 3: 4233
Additional Information 4: 4233afa7e7d65ff69414cd8b30317f4a

What do you suggest as a next step? You suggested turning off the contributors modules.
I see where they are listed in the system table having a type = module and a status flag.
Will these only be the modules located at G:\xampp\htdocs\drupal-5.18-host\sites\all\modules?
If so, how do I decide which modules to disable in the database? Are some more likely to be troublesome or do I disable the whole smash?
I assume I'll have to run update.php between each change and restart Apache.

Thanks,
Tony

dnuss’s picture

dnuss commented

Tony,

Next step, lets check PHP memory…

From XAMPP Control Panel, click the "Admin" button for Apache and when the XAMPP page comes up in the browser, click "phpinfo()" menu item. Then on next page look for the "memory_limit" parameter value down in the PHP Core section. A value of 32M is baseline and Drupal will run with bare bones options, but it really needs to be 64M or even 96M if there are a lot of contributor modules installed. Not having enough PHP memory allocation causes all kinds of unpredictable errors and since your error is occurring in the php5ts.dll (PHP Script Interpreter ) under the Apache process, this could be the cause. Here is a link for how to change PHP memory allocation ( http://drupal.org/node/29268 ).

If PHP memory doesn't need to be changed, or if after changing to the larger values you still get the same error, then I would definitely disable ALL the contributed modules using a SQL script (see http://drupal.org/node/574880 or http://drupal.org/node/51216 ).

If after you disable all the contributor modules you still get the error, then we can continue to go farther.

Note that if you want to take this thread “offline”, you can contact me via the Drupal contact feature and I can give you a temporary email address that you can contact me at. This would be better if we want to exchange PDF documents of screen prints or file dumps, etc. I assume you can create a temporary email address on your end also. Once we solve the problem, then we can post the result back into this thread so that others can benefit from what we found.

Dave

tdc_sunrise’s picture

tdc_sunrise commented

Dave,

I sent you an email via your Drupal contact with a temporary address you can use to email me.

We have made some progress!!!!

I increased the PHP memory to 96M without any effect.

I disabled all of the contributor modules via a MySQL script.

The test site home page now loads "error free" showing the background theme and a very sparse number of basic html controls. Clicking on any of the navigation links on the bottom of the home page take me back to the xamapp page (http://localhost/xampp/).

What strategy do you recommend in re-enabling the contributor modules?

Thank you!