Possible reasons for failure of apache startup and countermeasures
- 2020-05-09 19:42:41
- OfStack
In case apache fails to start, you can analyze the problem according to the following possible reasons.
Reason: port 1:80 is occupied
IIS, for example, and thunderbolt. My apache server was disabled by thunderbolt!
Reason 2: software conflicts
Installing some software will disable the launch of apache such as Dr.com when you open the network connection - > TcpIp properties - > Advanced - > The WINS TAB checks lmhosts for netbios and disables tcp/ip for netbios. Then it should start again.
Reason 3: httpd.conf is misconfigured
If the apache configuration file httpd.conf is mistaken, launch it in windows and it will prompt the requested operation has failed.
In fact, you can launch apache in command line mode with parameters. apache will prompt you for any errors, and then you can fix them accordingly. The command is as follows: httpd.exe-w-n "Apache2" -k start
Another one:
Even if one startup succeeds, the next startup may fail. How to fix it?
Input: netsh winsock reset
1. cmd will prompt you to restart in a moment, but ignore it. Now APACHE is ready to start.
The above is actually the completion of an winsock fix.
I hope the above method will help you solve the problem that apache cannot start.
Reason: port 1:80 is occupied
IIS, for example, and thunderbolt. My apache server was disabled by thunderbolt!
Reason 2: software conflicts
Installing some software will disable the launch of apache such as Dr.com when you open the network connection - > TcpIp properties - > Advanced - > The WINS TAB checks lmhosts for netbios and disables tcp/ip for netbios. Then it should start again.
Reason 3: httpd.conf is misconfigured
If the apache configuration file httpd.conf is mistaken, launch it in windows and it will prompt the requested operation has failed.
In fact, you can launch apache in command line mode with parameters. apache will prompt you for any errors, and then you can fix them accordingly. The command is as follows: httpd.exe-w-n "Apache2" -k start
Another one:
Even if one startup succeeds, the next startup may fail. How to fix it?
Input: netsh winsock reset
1. cmd will prompt you to restart in a moment, but ignore it. Now APACHE is ready to start.
The above is actually the completion of an winsock fix.
I hope the above method will help you solve the problem that apache cannot start.