Drupal kills localhost XAMPP

By litwol on 26 Mar 2007 at 06:53 UTC

For the life of me i cant figure out what is going on. it used to work just fine (allbeit slow). but now whenever i launch my xampp server it works, but the moment i try to access drupal it kills my server instantly and i cant bring it back up unless i restart the server.

i tried installing xampp on other location (followed the proper install procedure) and drupal kills xampp there too.

i tried installing wamp and drupal is lightning fast on wamp as i'ver never seen drupal so fast before.

can some one with experience or interest in this explain what is going on?

Comments

More Details

rokr commented 26 March 2007 at 09:33

Which version of XAMPP are you using? When i used a pre 1.6.0 version i had a similar behaviour. Now i'm using 1.6.0a. Yesterday i installed devel module. Whenever i accessed drupal apache crached an restarted.

apache access_log:
[notice] Parent: child process exited with status 3221225477 -- Restarting.

I did not find out yet if apache or php causes this error.

What's in your access.log?

Ronald

Logs are vital to this

dman commented 26 March 2007 at 09:58

So go google the problem

this post hints it may be a problem with characters in the database.

It cetainly seems to be linked with the DB access by most of the other versions of this problem. Limited to Windows too, it would seem.

Most of the times I've killed Apache have been endless recursion loops (when developing) but that would be hard to get with stable Drupal code.

The boring response from php.net is update to a stable pairing of Apache+PHP - although I would have expected that the XAMMP bundle would be one :)

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

_{.dan. is the New Zealand Drupal Developer working on Government Web Standards}

Hard to debug

rokr commented 26 March 2007 at 23:07

Since i'm not too deep into server architecture it is hard to debug for me. Last time a similar error occured when i used an earlier version of XAMPP as mentioned above and installed openID module. Updating XAMPP resolved my problem but returned with devel module. Interesting: Even removing devel module from drupal module path doesn't help. So it can't be active anymore but apache still crashes. I have to clean several database entries containing %devel% and %dev_% strings. Maybe it's really the database. If there is time i'm trying to debug which database entry makes the difference.

thanks, Ronald

This is the error that i am

litwol commented 26 March 2007 at 16:06

I am using xampp 1.6.0a
2 gigs of ram and fast CPU.
xampp installed in top root of ipod which i formated yesterday just to make sure nothing else interferes... still no luck.

This is the error that i am receiving. i have quite a few entries of exactly this text:

[Sun Mar 25 18:02:41 2007] [notice] Server built: Jan 30 2007 12:11:56
[Sun Mar 25 18:02:41 2007] [notice] Parent: Created child process 4540
[Sun Mar 25 18:02:45 2007] [notice] Child 4540: Child process is running
[Sun Mar 25 18:02:45 2007] [notice] Child 4540: Acquired the start mutex.
[Sun Mar 25 18:02:45 2007] [notice] Child 4540: Starting 250 worker threads.
[Sun Mar 25 18:02:45 2007] [notice] Child 4540: Starting thread to listen on port 443.
[Sun Mar 25 18:02:45 2007] [notice] Child 4540: Starting thread to listen on port 80.
[Sun Mar 25 18:02:49 2007] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Sun Mar 25 18:02:51 2007] [crit] (22)Invalid argument: unable to replace stderr with error_log
[Sun Mar 25 18:02:51 2007] [crit] (2)No such file or directory: unable to replace stderr with /dev/null
[Sun Mar 25 18:03:04 2007] [crit] (22)Invalid argument: unable to replace stderr with error_log
[Sun Mar 25 18:03:04 2007] [crit] (2)No such file or directory: unable to replace stderr with /dev/null
[Sun Mar 25 18:03:05 2007] [crit] (22)Invalid argument: unable to replace stderr with error_log
[Sun Mar 25 18:03:05 2007] [crit] (2)No such file or directory: unable to replace stderr with /dev/null
[Sun Mar 25 18:03:06 2007] [notice] Apache/2.2.4 (Win32) DAV/2 mod_ssl/2.2.4 OpenSSL/0.9.8d mod_autoindex_color PHP/5.2.1 configured -- resuming normal operations

what should i do?

Sometimes something interesting appears on http://litwol.com

What happened. What I did to fix it.

MichaelCole commented 7 September 2007 at 16:26

What happened:

I installed XAMPP 1.6.3a
I ran drupal for awhile and built a site.
I installed the devel module and started flippin switches. I don't know which ones. You know how it is ;-)
Apache started crashing in zendOptimizer.dll
I took the drupal modules out of the sites folder and Apache kept crashing.

I read this thread.
I installed the new Zend Core 2.0.3 (installer here: http://www.zend.com/products/zend_core
I got my site working again.

Then I had trouble with phpMyAdmin
So I uninstalled ZendCore, and XAMPP and installed WAMP.
Seems to work now.
The End.

Mike

same problem

bdpq commented 2 April 2007 at 22:55

I am also experiencing the same problem using XAMPP 1.6.0a on a wintel platform. Looking at the windows XP error report, it seems like the error is coming from the zend engine in PHP.

I am not too familiar with the zend engine (I sorta take it for granted) so the best thing I could do to circumvent this problem is by disabling the zend engine and Apache no longer crashes anymore. The devel module works fine so far without a glitch.

I believe most of us already know that you can disable the zend engine by editing the php.ini file, so until someone magically solve this problem, I will just have to live without the zend engine on my local machine.

bdpq

New ZendOptimizer worked for me...

bjvetter commented 25 April 2007 at 23:30

I tried updating to the latest XAMPP and I still get a crash (it was crashing in ZendOptimizer.dll). I found that the latest XAMPP does not include the latest ZendOptimizer (it has 3.2.4 vs. 3.2.6).

I downloaded and installed 3.2.6 of ZendOptimizer and things are working again for me.

XAMPP on WIN needs Apache2.2 binaries?

ichibby commented 18 April 2007 at 21:30

I found a thread on the svnforum site. The idea is that XAMPP is using 2.0 WIN binaries instead of 2.2.

http://www.svnforum.org/2017/viewtopic.php?t=3364

JRSofty says:

"After doing some checking. Apparently the people who package the windows installer have only compiled Subversion for use with Apache 2.0 and have not done so with Apache 2.2"

kama points to:

http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=8100&...

I downloaded the zip (svn-win32-1.4.3.zip) and copied the /bin and /iconv directory contents over my local XAMPP apache folder (iconv is inside bin). I rebooted apache and posted to my localhost Drupal. It didn't crash right away, but I don't know if it really works because it takes some time before it crashes again.

--ch

PS.

The XAMPP 1.6.1 (for Windows) is available!

http://www.apachefriends.org/en/xampp-windows.html

I have tried with tried with

Sharique commented 19 April 2007 at 04:44

I have tried with tried with XAMPP 1.6.1 (for Windows),but it still crashing. I don't understand why?
-----------
Sharique uddin Ahmed Farooqui
IT head, Managefolio.com

Sharique Ahmed Farooqui
http://www.openahmed.com

There's always WAMP! here

elgreg commented 19 April 2007 at 15:43

There's always WAMP! here

Apache on Win perhaps not ideal

halfer commented 29 April 2007 at 23:08

Well, it may in the end come down to running on Windows. This is not idle Win bashing - I've recently deployed a complex symfony application (i.e. PHP5) on Apache2 on Windows 2000 Server and it requires regularly scheduled soft restarts to keep the server up - not good! There's a number of things we are intending to try to improve the reliability of the stack, including deploying FastCGI (I believe it does process recycling automatically, thus covering any possible memory leak sins) but if I had my way we'd move to a Linux platform quickly.

Thanks for your advice, but...

MichaelCole commented 6 September 2007 at 23:20

Somehow, I think switching to Linux isn't the quickest way to get Drupal working again on my system.

Thanks for taking the time to write a response though.

Mike

Me too

greg.harvey

English

commented 2 January 2008 at 16:12

I got this issue when I enabled the devel module and while I haven't gotten as far as upgrading Zend, commenting it out in my php.ini has done the trick! :-)

--
https://www.codeenigma.com/

XAMMP too slow for drupal solved by Manisekaran

source4india commented 12 February 2008 at 18:09

Hi Most people are using xammp for drupal development

clear /tmp folder for better performance

change apache configuration for fast process

Regards
Manisekaran
http://www.internetconsultantonline.com

same problem after installing dev module

ajayg commented 24 February 2008 at 00:48

I am seeing the same problem and it started happening only after enabling devel module (as others have noticed). REmoving devl module from directory (and from the database) has not helped. It seems to have made some change in the database that seems to be causing this.

THis is not a php proble. I have other versions of drupal installed and those are working fine. Only the version where devel module installed has this problem

Comment out Zend Optimiser

greg.harvey

English

commented 5 March 2008 at 17:51

Comment out Zend Optimiser in php.ini and you should be able to use your faulty Drupal installation again. You can either uninstall Devel gracefully or continue in your dev environment without the Zend Optimiser running. Since it's just your dev environment, I'd be inclined to just leave Zend switched off, as the devel module is extremely useful! =)

--
https://www.codeenigma.com/