Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Apache Takes A Long Time To Start |
|
| Author |
|
apishdad
Joined: 01 Jul 2019
Posts: 59
Location: Canada, Toronto
|
 Posted: Mon 28 Sep '26 19:22 Post subject: Apache Takes A Long Time To Start |
 |
|
We had a older version of Apache 2.4.45 for a number of years and we decided to upgrade to Apache 2.4.68 recently. In the old version when I did
httpd -t -f ./conf/httpd-MAIN.conf
it came back very quickly and the service itself did not take a long time to start. Only 1-2 seconds.
I use the mod_proxy_balancer module and the size of our server pool has grown by 25%
Most of the configuration for our new config file is pretty much like before, but now when I login to the virtual machine at work and try to run the above command it takes 5 minutes to do that and then the service restart takes about 3-5 minute.
Is there a parameter in the new apache start that bypasses some checks when starting the service.
I asked CoPilot and it said that its taking time to verify DNS entries. I dont know whether that is right or wrong, but it must have done the same thing in previous versions too.
So how come in 2.4.68 its taking longer to start? |
|
| Back to top |
|
tangent
Moderator
Joined: 16 Aug 2020
Posts: 466
Location: UK
|
| Posted: Tue 29 Sep '26 11:40 Post subject: |
|
|
I doubt the later version of Apache is to blame.
You mention it takes some 5 minutes to log in to the virtual machine (VM), which to me rather confirms what CoPilot is saying; namely that name resolution services on your VM are timing out on various queries. Is your VM in a DMZ, in which case is it able to fully resolve AD related logon services and queries, as much as normal DNS queries?
In your Apache configuration, are your various host, vhost and balancer members referenced by hostname or IP address? If by hostname, how long does it take for the system to resolve those entries?
In your VM, you can time DNS queries from the command line, e.g.
| Code: | C:\>powershell -NoProfile -Command "(Measure-Command { Resolve-DnsName example.com -DnsOnly > $null }).TotalMilliseconds"
321.2559 |
If it were me, I'd make sure all the proxied hosts mentioned in your Apache configuration are defined in the local hosts file, and see if that helps with the start up delay.
Is the Apache service running under a domain account, which might be timing out on DNS and related AD/DC queries?
Beyond that, I'd probably go back to your Windows server administrators and ask them to look in to the server configuration, suspecting there might be a firewall issue somewhere. |
|
| Back to top |
|
|
|
|
|
|
