[Page 1, 2 Next]

Topic: Apache 2.4 fails to start

[1]

Topic: Apache 2.4 fails to start

[helengeb]

I am using Windows server 2008. I have downloaded apache 24 for 64-win from http://www.apachelounge.com.

I have set the configuration accordingly. I set the server name to localhost:80
I tried also 127.0.0.1 and ::1 for ipv-6.

Now when I try to run httpd –t in command prompt, I get an error saying

AH00558: httpd: Couldn’t reliably determine the servers fully qualified domain name, using fe80:1d1c:848a:3498:5664.
Set the “ServerName ‘ directive globally to suppress this message
Synthax OK.

I am sure my server name is correct, I don’t know why this error is happening.

I tried to ignore it and install apache using
httpd -k install
But it fails with error.

[glsmith]

I do not think that error will make it fail. It's just a warning. once the service is installed it must be started:

httpd -k start

If nothing else, just set the ServerName in httpd.conf to localhost long enough to get the service installed.

[helengeb]

I changed it to 127.0.0.1.

It is still failing when i run httpd -k start.

ERROR:
H00558: httpd: Could not reliably determine the server's fully qualified domai
d1c:848a:3498:56c4. Set the 'ServerName' directive globally to suppress this me
(OS 10048)Only one usage of each socket address (protocol/network address/port)
d. : AH00072: make_sock: could not bind to address [::]:80
(OS 10048)Only one usage of each socket address (protocol/network address/port)
d. : AH00072: make_sock: could not bind to address 0.0.0.0:80
AH00451: no listening sockets available, shutting down
AH00015: Unable to open logs

[tdonovan]

Perhaps you could try setting the server name with just a port number, like this:

[Peter2]

May I use this thread? Or must I open a new thread? It seems to be that helengeb will not return.
And I have similar problems. Apache 2.4 fails to start on my computer. I made already some improvements. Some error messages which were mentioned here did not return after that. But now I have the error message in the DOS prompt:
"AH00369: Failed to open the WinNT service manager, perhaps you forgot to log in as Administrator?"
But I am the only person who works with this computer. And I gave the map C:\Apache\Apache24\bin all the privileges for Administrators and Users. (In this map is the file httpd.exe).

[Steffen]

Sure, when your issue is different we can always split and make a new thread.

Which windows and apache you are using ? And really logged in with an account type Administrator ?

You run Dos prompt(cmd) as Administrator ?

You installed Apache as service ?

Steffen

[Peter2]

That is a fast answer! Thank you!
I am using Windows7 Professional. And I tried to install Apache 2.4 from http://www.apachelounge.com/download/win64/

I think that I am really logged in as an Aministrator. For when I am looking at Control Panel I see that there is only one account. And the name of that account is the name that I gave it for my own use. And directly below that name is written: Administrator. So I suppose that I was running DOS also as Aministrator.
I tried to install Apache as service. But that failed. (I used the command in DOS: httpd.exe -k install).

[glsmith]

well, you have administrator rights but the only true administrator account is hidden and disabled by default.

Run your command prompt (DOS) by right clicking on the icon and choosing "Run as Administrator", when you do this it will say Administrator in the top bar of the DOS window.

Then try httpd -k install

[Peter2]

Yes, it was successful!! Thank you very much!!
You said: "Then try httpd -k install".
Would httpd without .exe be sufficient in DOS?

Maybe later, when installing PHP, MySQL and phpMyAdmin I have more questions about Apache. But on this moment my problem has been solved!

Maybe "helengeb" had the same problem. But it seemed to be that he or she gave it up...
I hope that he or she reads this conversation!

[Peter2]

I have already a new problem. But I shall make a new thread for that, because this is the thread "Apache 2.4 fails to start".

[glsmith]

yes, httpd without the .exe tacked on is fine, it's that way with any executable file

[Peter2]

Thank you!

[Peter2]

I thought that I had installed Apache 2.4 correctly. But many times when I try "localhost" in the browser, then the browser can not find anything. Then the browser is searching during 5 minutes without finding something.

My question is: When I write "localhost" in the browser, and press enter, how does the browser (if possible) finds the location of the Apache-files on my computer?

Until now I did not install PHP and MySQL.

[Steffen]

Localhost goes to 127.0.0.1.

So sometimes it is working ?

Look in the Apache error.log for a clue.

Maybe you are dealing with the AcceptEx issue.

Try in the httpd.conf :

AcceptFilter http none
EnableSendfile Off
EnableMMAP off


Steffen

[glsmith]

On Win >= Vista, localhost is often ::1 (IPv6) and not 127.0.0.1

[Peter2]

I admire the knowledge of you both!
Yes, sometimes "localhost" worked. And sometimes not.
That is very confusing!
I looked at the error logs. But I do not understand what is written there.

glsmith said: On Win >= Vista, localhost is often ::1 (IPv6) and not 127.0.0.1
Yes, in the newspaper I read about IPv6! But my computer works with Windows 7 and not with Vista.

In every case I added the 3 rules of Steffen to my httpd.conf. And then I restarted Apache and tried "localhost" again in the browser. And now many times after each other it was successful! When this continues the problem is solved! I am very grateful!

[Peter2]

As to 127.0.0.1:
Since I added the 3 rules of Steffen this works also correct on my computer with Windows 7.

[glsmith]

Good, so it was the AcceptEx failure.

>= meant windows version greater than or equal to Vista, so Vista, Server 2008, Win7, Home Sever 2011 & the coming Win8 & Server 2012

[Peter2]

OK, Glsmith.
But if you are right, why does 127.0.0.1 work on my computer with Windows 7, 64 bit (and with the Internet Explorer 9.0.8112.16421)?

[glsmith]

because both IPs are valid (dual stack IPv4/IPv6), "localhost" may not point to 127.0.0.1 but ::1 instead ... maybe that did change in Win7, hard to keep all little quirks of the different versions of windows memorized.