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 HTTPD 2.4.39 Hangs |
|
| Author |
|
harishankar
Joined: 02 Aug 2019
Posts: 2
Location: India
|
 Posted: Fri 02 Aug '19 9:39 Post subject: Apache HTTPD 2.4.39 Hangs |
 |
|
We are using Apache HTTPD 2.4.39 in Windows Server 2012. It is working fine most of the times, but, some times it is getting hanged. Due to which the web page is not getting browsed throwing Service Unavailable error. Once we restart the Apache it comes back to normal. This is a production environment and downtime matters. What is causing this problem?
We tried setting up the following config,
| Code: | <IfModule mpm_winnt_module>
ThreadsPerChild 1920
MaxConnectionsPerChild 20000
AcceptFilter http none
AcceptFilter https none
</IfModule> |
But no grace. Still facing this issue.
Current settings in httpd.conf as follows,
Admin note:
See forum rules, httpd.conf moved to
https://apaste.info/h1mp
Error log as follows,
| Code: | [Mon Jul 29 13:29:15.635531 2019] [mpm_winnt:notice] [pid 8576:tid 368] AH00363: Child: Terminating 1013 threads that failed to exit.
[Mon Jul 29 13:29:15.635531 2019] [mpm_winnt:notice] [pid 8576:tid 368] AH00364: Child: All worker threads have exited.
[Mon Jul 29 13:29:15.635531 2019] [http2:warn] [pid 8576:tid 368] [client 105.210.70.50:13034] AH10020: h2_session(1869,WAIT,1): session cleanup triggered by pool cleanup. this should have happened earlier already.
[Mon Jul 29 13:29:15.635531 2019] [http2:warn] [pid 8576:tid 368] [client 105.210.70.50:13034] AH03199: h2_session(1869,WAIT,1): connection disappeared without proper goodbye, clients will be confused, should not happen |
|
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Fri 02 Aug '19 21:38 Post subject: |
|
|
I think I'd leave MaxConnectionsPerChild at 0. mpm_winnt only has one child by default and every 20,000 connections is going to trigger a cleanup which could take some time depending on your config.
More importantly however, per: http://httpd.apache.org/docs/2.4/mod/mpm_common.html#maxconnectionsperchild
| Quote: | | Setting MaxConnectionsPerChild to a non-zero value limits the amount of memory that process can consume by (accidental) memory leakage. |
Which may be causing the hanging when memory is exhausted. |
|
| Back to top |
|
harishankar
Joined: 02 Aug 2019
Posts: 2
Location: India
|
| Posted: Wed 07 Aug '19 9:03 Post subject: |
|
|
Hi glsmith,
Thank you for your response. We'll check updating it to 0. Meanwhile I have a doubt.
| Quote: | <IfModule mpm_winnt_module>
ThreadsPerChild 1920
MaxConnectionsPerChild 0
AcceptFilter http none
AcceptFilter https none
</IfModule> |
What if we remove the above section from httpd.conf? Will this cause any other issue? |
|
| Back to top |
|
|
|
|
|
|
