| Author |
|
tuukka
Joined: 08 Jan 2015
Posts: 4
|
 Posted: Thu 08 Jan '15 14:12 Post subject: httpd 2.4 freezes |
 |
|
Dear collective wisdom,
we are making the switch to the 64-bit apachelounge distribution of apache 2.4 (we currently have the 2.2 binary that used to be available at apache web site). Unfortunately, httpd from apachelounge freezes after a couple of hours in the production environment (in test it has been running smoothly). It simply stops processing requests, but no errors are written to logs. CPU load is 0%. Server-status and jkstatus pages are inaccessible. I am at loss on how to debug the issue.
About the environment: we use apache 2.4.9 with SSL and mod_jk. Its role is to be a front end for Tomcat (mounted with mod_jk) and a proxy for JIRA/Confluence. OS is Windows 2008 Server R2. Apache 2.2 (32-bit) with the same configuration (as closely as possible) works perfectly in the same machine.
All advice appreciated,
Tuukka |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3093
Location: Hilversum, NL, EU
|
| Posted: Thu 08 Jan '15 14:31 Post subject: |
|
|
When you have hangs, slow traffic and/or when having in your log entries like Asynchronous AcceptEx failed. You can try the following settings:
AcceptFilter http none
AcceptFilter https none
EnableSendfile off
EnableMMAP off |
|
| Back to top |
|
tuukka
Joined: 08 Jan 2015
Posts: 4
|
| Posted: Thu 08 Jan '15 15:10 Post subject: |
|
|
Traffic is certainly slow. We have some "Asynchronous AcceptEx failed" entries in the log, but not many (I counted 12 in the logs, all from yesterday and the hang happened today).
A change to the default configuration, inherited from our 2.2 installation, is ThreadsPerChild 250.
I will try the settings you mentioned to see if they are of help.
Tuukka |
|
| Back to top |
|
spitzerspace
Joined: 24 Dec 2014
Posts: 6
|
| Posted: Fri 09 Jan '15 7:51 Post subject: |
|
|
I have these directives already set:
EnableSendfile off
EnableMMAP off
Don't know about the other ones.
I also recently made the move from Apache 2.2. Never had any issues like this where the server is entirely unresponsive. |
|
| Back to top |
|
spitzerspace
Joined: 24 Dec 2014
Posts: 6
|
| Posted: Fri 09 Jan '15 18:35 Post subject: |
|
|
I will try adding the additional lines to my conf.
Last edited by spitzerspace on Fri 09 Jan '15 18:38; edited 1 time in total |
|
| Back to top |
|
jimski
Joined: 18 Jan 2014
Posts: 196
Location: USSA
|
| Posted: Mon 12 Jan '15 17:45 Post subject: |
|
|
Few suggestions:
1. Check the tasklist to see if there is anything unusual running and what is memory consumption.
2. Check windows event log.
3. Check your VC versions and make sure they are up to date.
4. Are you using all the modules from the same compilation as the Apache or are you downloading modules from third party websites.
5. Did you check the checksum before installing
6. If the previous apache was installed using .msi installer then you may have some artefacts from a previous version still present in the system. |
|
| Back to top |
|
spitzerspace
Joined: 24 Dec 2014
Posts: 6
|
| Posted: Mon 12 Jan '15 21:20 Post subject: |
|
|
Good suggestions. I'm interested as to what you mean by this:
| jimski wrote: |
6. If the previous apache was installed using .msi installer then you may have some artefacts from a previous version still present in the system. |
I did use an msi installer to install the original copy and then overwrote it with a VC11 build. What artifacts are you referring to? |
|
| Back to top |
|
jimski
Joined: 18 Jan 2014
Posts: 196
Location: USSA
|
| Posted: Tue 13 Jan '15 7:46 Post subject: |
|
|
The automated installs make changes to registry, system path, and copy various files such as dlls to various locations through the system.
If you overwrite the original msi installation without first uninstalling you may end up with a various pieces of old installation still present in your system and conflicting with the new installation. |
|
| Back to top |
|
tuukka
Joined: 08 Jan 2015
Posts: 4
|
| Posted: Wed 21 Jan '15 10:53 Post subject: |
|
|
| Quote: | | 6. If the previous apache was installed using .msi installer then you may have some artefacts from a previous version still present in the system. |
The previous 32-bit 2.2 installation was done with msi-installer. Currently the machine has both the old 32-bit installation and the new 64-bit installation as separate services and I can switch back and forth. Until I can make the new installation run smoothly, this is a necessary arrangement.
As the 32-bit version is installed to C:\Program Files (x86) and the 64-bit version is installed to C:\Program Files the they should be reading correct files. However, I am not sure of how the check all the necessary registry entries.
Tuukka |
|
| Back to top |
|
