settings file copied, database created, datbase name and user entered, and then apache stops working any ideas please, this is my first D7 installation :(

Comments

q8doc’s picture

q8doc commented

when i checked the database it appear it builds the tables and every thing,
am running apache on a xampp test server if this helps
thank you

ctmattice1’s picture

ctmattice1 commented

More info please!

Are you using the htdocs folder or a different root directory. If your using a different root directory, do you have the required logfiles in it. What windows version are you running?

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

See if the apache error.log contains something..

If a childprocess of Apache dies, there is usually a warning/error message in error.log.

Also, in case you haven't already up to date versions, update Apache and PHP...

q8doc’s picture

q8doc commented

oh so it should be the latest php 5 and apache, am running xampp v1.7
IE
Apache 2.2.11
+ MySQL 5.1.30
+ PHP 5.2.8 + PEAR
Besides, drupal instalation agreed to xampp meeting theh requirements, so i dont think its the versions, i will re run it on a real server and see what happens

q8doc’s picture

q8doc commented

am using it directly under the htdocs

agir’s picture

agir commented

Hi I am having same problem. XAMPP on Windows.
Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.8
In error.log is nothing. In access.log is:
127.0.0.1 - - [23/Nov/2009:21:11:00 +0100] "GET /drupal7 HTTP/1.1" 301 365
127.0.0.1 - - [23/Nov/2009:21:11:01 +0100] "GET /drupal7/ HTTP/1.1" 302 110
127.0.0.1 - - [23/Nov/2009:21:11:01 +0100] "GET /drupal7/install.php HTTP/1.1" 200 3340
127.0.0.1 - - [23/Nov/2009:21:11:04 +0100] "POST /drupal7/install.php HTTP/1.1" 302 -
127.0.0.1 - - [23/Nov/2009:21:11:04 +0100] "GET /drupal7/install.php?profile=default HTTP/1.1" 200 2448
127.0.0.1 - - [23/Nov/2009:21:11:06 +0100] "GET /drupal7/install.php?profile=default&locale=en HTTP/1.1" 200 6540

tobiasb’s picture

tobiasb
Primary language German
Location Berlin
commented
Category: bug » support
agir’s picture

agir commented

Yesterday I tried update to Apache 2.2.14 and php 5.2.11 and the error is the same :-(

s.daniel’s picture

s.daniel commented

At what point does the installation break excacly? What do you see? Any error message / white screen / etc?

q8doc’s picture

q8doc commented

After looking more into it, i think this is because of php 5.3.3 , i mean the old versions of xampp, works perfectly, while the new one . doesn't...
this could either be of xampp it self while they setup php and apache, or drupal, to which we can only test by setting up drupal under the latest apache and php 5.3.3, any one please

David_Rothstein’s picture

David_Rothstein commented

If you are running xampp, it's possible you have an old version of eAccelerator or some other buggy PHP optimizer turned on (I think eAccelerator ships with xampp, but I don't know what version).

If so, this could be #914742: Add hook_requirements() for buggy versions of eAccelerator

kars-t’s picture

kars-t commented
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not pose the problem comprehensible.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order this issue no longer remains, I put this issue to "fixed".

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.