jcorso1313
asked on
Apache 2.4 https ssl hanging. Port 80 stays open...
Any ideas on direction to look. set it on debug logging and generated 150mb in 4 hrs. Set back to error, doesn't show much...
Traffic doesn't just stop. Port 443 stops accepting after about 5-7 minutes of spikes and stops. Very sporadic. Restart service seems to fix it for about 2-4 hrs...
It's win 2012 64 sp2.
Thanks,
Traffic doesn't just stop. Port 443 stops accepting after about 5-7 minutes of spikes and stops. Very sporadic. Restart service seems to fix it for about 2-4 hrs...
It's win 2012 64 sp2.
Thanks,
ASKER
The spikes are long response times so far, followed by complete drops, for about 5 minutes before the stop, which is basically just turning off 443. Port 80 stays open...
doesn't seem reproducible yet.
CPU and memory use were very low, and never seemed to get over 50% leading to the issue. Didn't check while the service was hung, but will next time.
For now, I can add this error messages until it happens again...
[mpm_winnt:warn] [pid 4924:tid 1920] (OS 121)The semaphore timeout period has expired. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
doesn't seem reproducible yet.
CPU and memory use were very low, and never seemed to get over 50% leading to the issue. Didn't check while the service was hung, but will next time.
For now, I can add this error messages until it happens again...
[mpm_winnt:warn] [pid 4924:tid 1920] (OS 121)The semaphore timeout period has expired. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
I can see from the error messages that you are running Apache under Windows.
From the little information you have provided, it would look like you have some issues with C runtime libraries ( have you installed the correct C runtime libraries for Apache/Open SSL executables?) or conflicts with another service attempting to use port 443 on your server.
To be able to better assist you can you provide some additional information:
From the little information you have provided, it would look like you have some issues with C runtime libraries ( have you installed the correct C runtime libraries for Apache/Open SSL executables?) or conflicts with another service attempting to use port 443 on your server.
To be able to better assist you can you provide some additional information:
Which version of Windows Server are you running?
Is it 64bit install, and if so did you install Apache 64bit?
Which version of Apache 2.4 and where did you download/obtain it from?
Additionally, can you check which version of OpenSSL is running?
Also make sure that the libeay.dll and ssleay.dll that came with your Apache are in your windows root folders.
Is it 64bit install, and if so did you install Apache 64bit?
Which version of Apache 2.4 and where did you download/obtain it from?
Additionally, can you check which version of OpenSSL is running?
Also make sure that the libeay.dll and ssleay.dll that came with your Apache are in your windows root folders.
ASKER
windows 2012 x64
Apache 64 v.2.4.12 (apachehaus)
OpenSSL/1.0.1
libeay32 and ssleay32.dll are there. I presume those are 32 bit?
Apache 64 v.2.4.12 (apachehaus)
OpenSSL/1.0.1
libeay32 and ssleay32.dll are there. I presume those are 32 bit?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried a different 64 bit install, OpenSSL 1.0.1j.
I'm not sure why these 32 bit files are there.
Can you point me to a 64 bit build of 2.4.12 with the 64 bit Vers. Of these files.
I have downloaded a couple, and all seem to use the 32 bit ones.
Thank you.
I'm not sure why these 32 bit files are there.
Can you point me to a 64 bit build of 2.4.12 with the 64 bit Vers. Of these files.
I have downloaded a couple, and all seem to use the 32 bit ones.
Thank you.
Did you try WAMPServer - http://www.wampserver.com/en/ although the problem with their downloads is that they are installers. We normally take the binaries from Apache Lounge.
But as I mentioned, you may have another application installed that is running a 32bit version of SSL which would account for why they are there.
I am assuming you tried the changes to the httpd.conf and that they did not help?
But as I mentioned, you may have another application installed that is running a 32bit version of SSL which would account for why they are there.
I am assuming you tried the changes to the httpd.conf and that they did not help?
Does the debug logging indicate the CPU utilization? If not, I would see check the CPU health. Can you set up System Monitor to collect the CPU utilization over the 5 to 7 minutes? Do you have Cacti or a network monitoring service? Do you know mow many connections are going to the server? (e.g., 10,000)