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.

I recently updated to nginx 1.0.8 and tried to benchmark performance for cached dynamic pages (initially served by a Django app via proxy_pass) and for static pages. In both cases, nginx will not serve more than 3 or 4 requests (even without concurrent connections), so ab almost immediately reports:

apr_socket_recv: Connection reset by peer (54)

It is only when choosing a maximum of 4 (or fewer) requests that ab finishes successfully.

Why is that? I tried increasing the number of worker processes (no luck), but I assume that nginx should be capable of serving more than 4 requests without tweaking any configuration variable. Could it be that I accidentally triggered some sort of DOS protection mechanism?

share|improve this question
    
are you connecting to nginx locally or via a network? Is there anything in the nginx error log? –  Shish Nov 18 '11 at 12:52
    
I connect locally, and the regular nginx error log is empty. Switching to log level 'info', it shows a couple of SIGIO und SIGCHLD signals, as well as exiting cache manager and worker processes exiting. –  janeden Nov 18 '11 at 13:31

Your Answer

 
discard

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

Browse other questions tagged or ask your own question.