1. BSDI 2.1 Apache 1.1.1 Zombie "D" Status Processes
We are running BSDI 2.1 with all of the patches and running
Apache 1.1.1.
It appears that, after going to BSDI 2.1, Apache (even the 1.00
that I was using previously) would slowly build up some kind
of baggage that would eventually cause web connections to hang.
We are running 500,000 hits on some days and this "hang" might
take 1/2 to 2 days to come to.
When I got to Apache 1.1.1 I ran up the scoreboard and found
processes that would go into "D" status and then stay there
until they were killed.
Well, yes, I'm a slimy blind-curve-passing hack and I put in
an alarm(120) just as apache began to lookup the DNS, and put
another alarm(0) just as it finished. Hehehehehe... I'm still\
a little nervous, but the dagone httpd "D" zombies seem to
kill themselves off at just exactly 120 seconds as the scoreboard
says.
I may have my problem licked but I'm not sure and I'm nervouse
about my "whacko" solution. Has anyone else seen this problem and
does anyone have any suggestions or comments?
Cheers!
--
Jobs - Graphic Arts - Commercial Production -> http://studio.vni.net/jobs/
Indianapolis Indianapolis Indianapolis Metro http://www.vnii.net/
Indiana Indiana Indiana
Washington DC Washington DC Washington DC Metro http://www.vni.net/
Virtual Networks Incorporated Virtual Networks of Indiana, Incorporated
Jobs - Graphic Arts - Commercial Production -> http://studio.vni.net/jobs/
2. Monitor type not recognized ...
3. WU-FTPDm BSDI 2.1, recompiling problems
4. High-Speed/Volume Database
5. BSDI compatibility in 2.1-stable ?
6. How to find wdc1?
7. Getting MacPPP to work with BSDI 2.1
8. Logging in on Linux 0.99p6 with poeigl-1.9a's login
9. How configure Linux 1.2.13, BSDI 2.1, and Windows NT on the same PC?
10. Apache 1.03, BSDI 2.1 and CPU Overload
11. Microsoft: BSDI 2.1 + Apache Where do you want to go today?
12. ARGUS 1.5 compile blows up on BSDI 2.1