I'm trying to run a WAMP (Windows, Apache, MySQL, PHP) server from my computer for developing a site.

I got Apache up and running and I've successfully installed PHP, but it's not working completely as I expected.

I tried a regular page with just phpinfo() and it works fine in Google Chrome.

My first problem:

Internet Explorer and chrome seem to try to load the page twice for some reason, and after the phpinfo comes up for a brief fraction of a second, it switches to a "could not load" the site error page. Firefox does this as well. What's going on?

I've run this with php files that have no errors and they load up fine. Whenever I'm trying to load a php file I'm developing however, it fails!

In Google chrome I'm told that the connection resets, in IE the webpage cannot be loaded, and I can't remember what Firefox says. Not only does it not show any errors, the error log file I specified remains empty!

Not sure what to do I looked around and I realized I had yet to check my apache log to see what's going on:Here's what I've observed:

Correct me if I'm wrong but I believe the last number in the log entries is the number of bytes that were sent. For whatever reason there is a discrepancy of 378 bytes. I believe that it may be that it flushes the data periodically but as soon as php fails the connection gets reset. The difference in the number of bytes sent I believe can only be attributed to other processes running on my computer making php take longer to complete its operations.

I just checked... I think the last number is just the size of the cache that sent the data or something, because I changed the size of the PHP file (by adding some static text) and it gave the same sizes. So just ignore my guesses above.

You're encountering segmentation faults, which plague the 2.2 line of apache. Something is probably causing this, but the source could be hard to track (for this reason I stayed on 2.0 for a long time). Check the following: - what modules are activated for apache? (especially mod_deflate) - did you make any changes from the default configuration to the document root <directory> directive? perhaps added custom rewrite rules - do you have an .htaccess file setting additional directives to the directory the stores the file causing the faults?You might consider reinstalling apache or even downgrading to the latest 2.0 version.

As I mentioned in my first post, I think these problems are a symptom of a greater problem that's ultimately causing the error messages to fail to be displayed or logged. Without error messages I don't think I'd be able to develop or debug my solutions.

@pytrin

Maybe it's just me but I feel kinda unsafe going back versions. Aren't there lots of security vulnerabilities and performance issues fixed in the newer versions?

However for a development machine I don't think it really matters. I'll try to go back to the last build of Apache 2.0 then. Will I need to get an older version of PHP?

However for a development machine I don't think it really matters. I'll try to go back to the last build of Apache 2.0 then. Will I need to get an older version of PHP?

This does not affect PHP in any way. The 2.0 line is still being supported for security fixes, so that is not a concern either (2.2 has some new features etc). In fact, as surprising as it sounds, many hosting providers are still running apache 1.3 as its considered very stable precisely to avoid the problems you are encountering right now.

Who is online

Users browsing this forum: No registered users and 4 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum