Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Okay. Very strange problem that I'm having here. I just recently updated to Apache 2.4.2 from 2.2.17, mostly to try to get name-based SSL VirtualHosts working (although they should have been working on 2.2.17). Server is Win2008 R2 (so x64 by definition) running with PHP 5.4.3 and MySQL 5.1.40 (outdated, I know).

When I launch the server, it initially works fine. Responds to all requests, VirtualHosts all in order. However, after an uncertain amount of time (appears to only take a few minutes for the most part, but sometimes takes hours), it stops responding to regular HTTP requests (on any VirtualHost). HTTPS continues to work. No errors in the log, and nothing in the access logs when I attempt to connect.

I'm having a hard time finding the source of this error given its intermittent nature. When removing all SSL-based VirtualHosts, it seemingly increased stability (still responding to HTTP requests twelve hours later). This could be mere coincidence, though.

Entirety of SSL VirtualHost is as follows, should there happen to be a problem with it.

<VirtualHost *:443>
   DocumentRoot "C:\Server\www\virtualhosts\mysite.net"
   ErrorLog logs/ssl.mysite.net-error_log
   CustomLog logs/ssl.mysite.net-access_log common env=!dontlog
   SSLEngine on
   SSLProtocol all -SSLv2
   SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM
   SSLCertificateFile C:/Server/bin/apache/apache2.4.2/conf/ssl/server.crt
   SSLCertificateKeyFile C:/Server/bin/apache/apache2.4.2/conf/ssl/server.key
   SSLCertificateChainFile C:/Server/bin/apache/Apache2.4.2/conf/ssl/sub.class1.server.ca.pem
   SSLCACertificateFile C:/Server/bin/apache/Apache2.4.2/conf/ssl/ca.pem
</VirtualHost>

Any ideas what I'm missing?

share|improve this question

migrated from stackoverflow.com Sep 18 '12 at 10:13

This question came from our site for professional and enthusiast programmers.

add comment

1 Answer

Turn Log debug, and look into error log.

http://httpd.apache.org/docs/2.4/mod/core.html#loglevel

If requests don't get served, there must be something, at least some segfault notify.

Also, you can use "ab" utility to regenerate error after serving particular kind of requests

http://httpd.apache.org/docs/2.4/programs/ab.html

As last resort, you can start httpd from command line, and force debug mode / foreground with some switch of apache2 binary. It's impossible that nothing goes to the log about it. What kind of application do you serve on it, is it fastcgi, or some .net bridge ?

More, what exactly do you mean by "stops responding to regular HTTP requests" ? Do you have an 503 error in browser, or just nothing appears / connection fails?

share|improve this answer
    
Set it to debug and will see what I get the next time the issue occurs. This could be anywhere from a few minutes to hours. –  Apropos Sep 17 '12 at 22:02
    
Didn't see the last question. Nothing appears and connection fails, yes. –  Apropos Sep 17 '12 at 22:12
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.