Possible reasons for apache failure to start and countermeasures
- 2020-05-06 12:11:00
- OfStack
If apache fails to start, you can analyze the problem according to the following possible reasons.
Reason 1: port 80 occupies
IIS, for example, and thunderbolt. My apache server was disabled by thunderbolt!
reason # 2: software conflicts
Installing some software will prevent apache from starting, such as Dr.com you open the network connection -> - > TcpIp attribute Advanced - > The WINS tag removes the lmhosts pair of netbios and disables netbios of tcp/ip.
reason 3: httpd.conf misconfigured
If the apache configuration file httpd.conf makes a mistake, launch it in windows and it will prompt the requested operation has failed.
In fact, you can use the command line mode to launch apache, and take parameters, apache will prompt you which sentence is wrong, and then you can be targeted to solve, command as follows: httpd. Es57en-w-n "Apache2" -k start
another case:
Even if one startup succeeds, the next startup may fail. What can be done?
In the run, enter: netsh winsock reset
cmd will tell 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 is helpful to solve the problem that apache cannot start.
Reason 1: port 80 occupies
IIS, for example, and thunderbolt. My apache server was disabled by thunderbolt!
reason # 2: software conflicts
Installing some software will prevent apache from starting, such as Dr.com you open the network connection -> - > TcpIp attribute Advanced - > The WINS tag removes the lmhosts pair of netbios and disables netbios of tcp/ip.
reason 3: httpd.conf misconfigured
If the apache configuration file httpd.conf makes a mistake, launch it in windows and it will prompt the requested operation has failed.
In fact, you can use the command line mode to launch apache, and take parameters, apache will prompt you which sentence is wrong, and then you can be targeted to solve, command as follows: httpd. Es57en-w-n "Apache2" -k start
another case:
Even if one startup succeeds, the next startup may fail. What can be done?
In the run, enter: netsh winsock reset
cmd will tell 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 is helpful to solve the problem that apache cannot start.