I'm not sure where the best place is to ask this, but this seems like a relatively active forum. Lately my Apache (version 1.3.22 running on Win2k) has been acting up, I use PHP and MySQL and host a few sites for people and so I'm not totally sure what is running on it sometimes. My problem has been that at some point MySQL simply won't make connections, restarting MySQL didn't solve the problem, so I would reboot, but finally I looked into the problem and a netstat found ports 3000-5000 set for listening, first I thought I had a trojan. I found a program called "fport" that reports what process is using a port, apparently apache had all ports that weren't already taken between port 3000 and 5000 set to listen, when I try to connect to them from my lan it is refused, but it still says it is listening. Then I noticed that those ports were being set to listen from a seperate PID (process id) than the normal port 80 listening PID.
So in summary, a seperate PID from the main port 80 is running off of Apache (this might be standard), but it's creating about 2000 dead listening sockets slowly filling those up.
So in summary, a seperate PID from the main port 80 is running off of Apache (this might be standard), but it's creating about 2000 dead listening sockets slowly filling those up.
