Page MenuHomePhabricator

Unable to install on WAMP server (Windows 7, Apache 2.2.21, PHP 5.3.10): 324 ERR_EMPTY_RESPONSE
Closed, ResolvedPublic

Description

When I click on Set up the wiki it shows error 324 ERR_EMPTY_RESPONSE, I have checked my PHP,APACHE and they are running fine


Version: 1.19.1
Severity: critical
OS: Windows 7

Details

Reference
bz35606

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 12:14 AM
bzimport set Reference to bz35606.
bzimport added a subscriber: Unknown Object (MLST).

What's the version of PHP and Apache? Is there anything relevant in your error log?

APACHE version-2.2.21 PHP version 5.3.10, browser doesn't show anything relevant, any other log files I should check ?

Not the browser error log, apache's error log. Also, which operating system?

Windows 7. Also, worth noting is that I am able to install 1.18 so the problem is probably with MW 1.19. The error log is here

[error] [client 127.0.0.1] File does not exist: C:/wamp/www/favicon.ico
[notice] Parent: child process exited with status 255 -- Restarting.
[notice] Apache/2.2.21 (Win64) PHP/5.3.10 configured -- resuming normal operations
[notice] Server built: Sep 24 2011 19:57:51
[notice] Parent: Created child process 7696
[notice] Child 7696: Child process is running
[notice] Child 7696: Acquired the start mutex.
[notice] Child 7696: Starting 64 worker threads.
[notice] Child 7696: Starting thread to listen on port 80.
[notice] Child 7696: Starting thread to listen on port 80.

Nischay: Does this problem still exist, or did you work it around in the end?

(In reply to comment #5)

Nischay: Does this problem still exist, or did you work it around in the end?

Yes, few days back I tried this again with MW 1.19.1 and it didn't work. Finally I had to switch to Xampp

Without more info this probably will end up rotting...

hashar claimed this task.
hashar added subscribers: Nischayn22, hashar.

I am closing this bug. It is almost four years old and definitely looks like an Apache/PHP config issue on the end user side.

@Nischayn22 is active and hasn't replied. I guess he got the issue at end fixed.

As I said I had switched to XAMPP and have been using that till now. Not sure if its still the same. If nobody is complaining, the bug can be closed though.