AK01 Posted October 21, 2009 Share Posted October 21, 2009 Hi There, I've been developing a site locally for a few weeks using Apache2.2 with PHP5.3.0 I am running Windows Vista. Everything has been working fine until I changed the 'SMTP = locahost' config item in php.ini to SMTP = 'smtp.mysmtp.com' I also changed log_errors to 'On' After this whenever I hit localhost in my browser I get a connection interrupted error. At which point I also get a windows information popup that says 'Apache HTTP Server stopped working and was closed' I reset these values to there defaults but this has made no difference. I have manually stopped and restarted Apache several times and rebooted my machine. Still I get the same issue, I can no longer hit my site, I instead receive this message about Apache stopping working. I have checked logs and there is nothing informing me of any errors. Here's what I get [Wed Oct 21 17:46:23 2009] [notice] Apache/2.2.13 (Win32) PHP/5.2.10 configured -- resuming normal operations [Wed Oct 21 17:46:23 2009] [notice] Server built: Aug 6 2009 15:50:50 [Wed Oct 21 17:46:23 2009] [notice] Parent: Created child process 4224 [Wed Oct 21 17:46:24 2009] [notice] Child 4224: Child process is running [Wed Oct 21 17:46:24 2009] [notice] Child 4224: Acquired the start mutex. [Wed Oct 21 17:46:24 2009] [notice] Child 4224: Starting 64 worker threads. [Wed Oct 21 17:46:24 2009] [notice] Child 5964: Released the start mutex [Wed Oct 21 17:46:25 2009] [notice] Child 5964: All worker threads have exited. [Wed Oct 21 17:46:25 2009] [notice] Child 4224: Starting thread to listen on port 80. [Wed Oct 21 17:46:25 2009] [notice] Child 5964: Child process is exiting [Wed Oct 21 17:47:09 2009] [notice] Parent: child process exited with status 255 -- Restarting. [Wed Oct 21 17:47:10 2009] [notice] Apache/2.2.13 (Win32) PHP/5.2.10 configured -- resuming normal operations [Wed Oct 21 17:47:10 2009] [notice] Server built: Aug 6 2009 15:50:50 [Wed Oct 21 17:47:10 2009] [notice] Parent: Created child process 5260 [Wed Oct 21 17:47:10 2009] [notice] Child 5260: Child process is running [Wed Oct 21 17:47:10 2009] [notice] Child 5260: Acquired the start mutex. [Wed Oct 21 17:47:10 2009] [notice] Child 5260: Starting 64 worker threads. [Wed Oct 21 17:47:10 2009] [notice] Child 5260: Starting thread to listen on port 80. The access logs are giving no output at all which would imply to me that Apache is not even geting chance to service the request before exploding. My php.ini is fairly standard, I would paste it in but it's rather large. This is getting rather annoying. Any help with this would be greatly appreciated. Cheers, ak Quote Link to comment Share on other sites More sharing options...
cags Posted October 21, 2009 Share Posted October 21, 2009 It's a long shot, but have you tried checking your hosts file (c:\windows\system32\drivers\etc by default) to make sure localhost is redirecting to the loopback address. The only reason I say this is potentially if you had a virus or malware it could be redirecting you and the error message isn't actually from your apache it's javascript from a remote machine... Like I said, long shot. Quote Link to comment Share on other sites More sharing options...
AK01 Posted October 21, 2009 Author Share Posted October 21, 2009 Cags, Thanks for replying. I had a look at my hosts file and the only entries I have are for localhost; 127.0.0.1 localhost ::1 localhost I assume the second entry '::1' is a reference to the first localhost IP and not an issue? Cheers Quote Link to comment Share on other sites More sharing options...
cags Posted October 21, 2009 Share Posted October 21, 2009 I have no idea what that second line does, I've never seen one like that before. Try commenting it out (in the same manner as the comments at the top of the page) then trying http://localhost/ and see if you get the same problem. If you do then uncomment and continue the quest. Quote Link to comment Share on other sites More sharing options...
AK01 Posted October 21, 2009 Author Share Posted October 21, 2009 Removed the ::1 localhost entry from hosts file. Still the same problem. Apache just seems to blow up. However the apache process is still running on port 80 and the monitor indicates the server is running. As previously mentioned nothing in the apache logs implies any form of error or shutdown. What is interesting is when I type http://localhost/ into URL bar as I get the Page Load Error the address diverts to http://www.localhost.com/ Is this just a firefox default setting that attempts to find the address on the net if it can't be hit locally? Quote Link to comment Share on other sites More sharing options...
cags Posted October 21, 2009 Share Posted October 21, 2009 Try typing http://127.0.0.1/ in your address bar instead, see what happens. Quote Link to comment Share on other sites More sharing options...
AK01 Posted October 21, 2009 Author Share Posted October 21, 2009 Same problem but no redirect to www.localhost.com Quote Link to comment Share on other sites More sharing options...
corbin Posted October 21, 2009 Share Posted October 21, 2009 The ::1 is the IPv6 address for localhost. It looks like something is causing a fault in Apache. (Could be a memory error or just an extension is exiting on an error.) I would guess it's PHP related since that's all that you've changed. Try changing the settings back and see if that fixes it. If it does fix it, then I would guess that something is wrong with the PHP install in regards to the SMTP stuff. Quote Link to comment Share on other sites More sharing options...
AK01 Posted October 23, 2009 Author Share Posted October 23, 2009 I have managed to get Apache running OK again. All I did was comment out the line 'error_log = php_errors.log' in php.ini It seems Apache didn't want to create this log file in this way. Maybe I should have explicitly set the path for the file? Either way its all good now. Cheers, AK Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.