HTTPD and AppleFileServer processes maxing out CPU at 100%
Hello.
I have a G5 Xserve (2Ghz PPC with 8GB RAM running 10.5.8 on a 1TB HD [RAID1 via HD bays 1&2] — networked via gigabit ethernet averaging 70–80+ MB/s) — the services the server is handling are:
- AFP
- DNS (slave — Primary DNS is an Intel Xserve)
- MySQL
- Open Directory (connected to an OD Master — OD Master is an Intel Xserve)
- Software Update
- Web
AFP is only connectable by 3 users in total.
SUS serves a maximum 35 machines (after hours only).
Web hosts sites internally only — not accessible from outside the LAN. At max, it's only serving 10-15 connections to internal requests.
Over the last few weeks I've noticed the server responding very, very slow. Working on it via ARD is painful (click, wait, response sorta thing), and web hosting is terrible (when viewing sites hosted on this server, I feel like it's 1995 and I just got a speedy 56k modem! <G>).
So, I've been looking into various things and today I had Activity Monitor open while I was working on the server. I then noticed the machine starting to chug and I looked at Activity Monitor and the CPU was maxed out at 100% — it was two HTTPD processes hogging the CPU. So, I've done some preliminary testing and every time I hit a page hosted by the server, no matter how big or small (one is just a simple, static HTML page with a few lines of code), every hit results in the HTTPD process(es) maxing out the CPU at 100%.
So, I shut down Web to do some further testing and noticed the chugging starting again. So, I looked at Activity Monitor again and this time the CPU was maxed out by the AppleFileServer process — a quick look into AFP showed one user connected. So, some further testing of AFP reveals the same sorta thing — any time there's an active file transfer, no matter how big or small, the CPU is maxed out at 100% by the AppleFileServer process.
I've not noticed any other processes even coming close to maxing out the CPU, so right now these two processes seem to be my main culprits. But, I have absolutely no idea why they're be hogging all the CPU resources like this.
Has anyone else ever experienced this?
Any suggestions on what I can do to fix this?
Thanks,
Kristin.
I have a G5 Xserve (2Ghz PPC with 8GB RAM running 10.5.8 on a 1TB HD [RAID1 via HD bays 1&2] — networked via gigabit ethernet averaging 70–80+ MB/s) — the services the server is handling are:
- AFP
- DNS (slave — Primary DNS is an Intel Xserve)
- MySQL
- Open Directory (connected to an OD Master — OD Master is an Intel Xserve)
- Software Update
- Web
AFP is only connectable by 3 users in total.
SUS serves a maximum 35 machines (after hours only).
Web hosts sites internally only — not accessible from outside the LAN. At max, it's only serving 10-15 connections to internal requests.
Over the last few weeks I've noticed the server responding very, very slow. Working on it via ARD is painful (click, wait, response sorta thing), and web hosting is terrible (when viewing sites hosted on this server, I feel like it's 1995 and I just got a speedy 56k modem! <G>).
So, I've been looking into various things and today I had Activity Monitor open while I was working on the server. I then noticed the machine starting to chug and I looked at Activity Monitor and the CPU was maxed out at 100% — it was two HTTPD processes hogging the CPU. So, I've done some preliminary testing and every time I hit a page hosted by the server, no matter how big or small (one is just a simple, static HTML page with a few lines of code), every hit results in the HTTPD process(es) maxing out the CPU at 100%.
So, I shut down Web to do some further testing and noticed the chugging starting again. So, I looked at Activity Monitor again and this time the CPU was maxed out by the AppleFileServer process — a quick look into AFP showed one user connected. So, some further testing of AFP reveals the same sorta thing — any time there's an active file transfer, no matter how big or small, the CPU is maxed out at 100% by the AppleFileServer process.
I've not noticed any other processes even coming close to maxing out the CPU, so right now these two processes seem to be my main culprits. But, I have absolutely no idea why they're be hogging all the CPU resources like this.
Has anyone else ever experienced this?
Any suggestions on what I can do to fix this?
Thanks,
Kristin.
20" Intel iMac 2.16 Ghz, Macintosh SE/30, Mac OS X (10.6.2), Xserves (Early 2009, Early 2008, G5), Mac Pro