rusty0101
January 12th, 2008, 11:08 PM
I'm running into a bit of a problem with the apache2 server under Mythbuntu. Since I run the same server (I think) under my ubuntu server platform, I think the issue is not specific to the server, but may be related to a configuration issue under Mythbuntu.
I built a dual core platform to run Mythbuntu on and after a recent apt-get update/upgrade cycle, discovered I could no longer see my Mythtweb server from various locations. Any time I log into the server and try kicking off the apache2 server, my system seems to vanish. To try to diagnose the situation, I launched 'top' in one ssh session and in another ssh session I started apache2. The top portion of top gives me:
top - 20:54:17 up 1:36, 3 users, load average: 488.33, 911.75, 33.46
Tasks: 27511 total, 2 running, 27509 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.2%us, 85.4%sy, 0.0%ni, 0.2%id, 13.1%wa, 0.0%hi, 0.2%si, 0.0%st
Mem: 2067504k total, 2018336k used, 49168k free, 668k buffers
Swap: 2000084k total, 2000084k used, 0k free, 1784k cached
Needless to say the system seems a bit sluggish.
I sorted the output of top by pid, (higher pids will be at the top) and I see:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
32767 root 17 0 4384 168 4 S 0 0.0 0:00.00 apport
32766 root 11 -5 0 0 0 S 0 0.0 0:00.00 khelper
32765 root 18 0 4388 168 4 S 0 0.0 0:00.00 apport
32764 root 11 -5 0 0 0 S 0 0.0 0:00.00 khelper
with the aport and khelper processes filling the rest of the listing. And yes, 'ps -ef' presents a screen filled with stuff like:
root 9566 9565 0 20:36 ? 00:00:00 /usr/bin/python /usr/share/appor
root 9567 11 0 20:36 ? 00:00:00 [khelper]
root 9568 9567 0 20:36 ? 00:00:00 /usr/bin/python /usr/share/appor
root 9569 11 0 20:36 ? 00:00:00 [khelper]
Eventually I start seeing messages about no resources available to fork if I try to run a command in a shell.
It looks like either /etc/init.d/apache2 or one of the other apps associated with apache is fork bombing my system. Based upon the output of ps, I'm thinking that the problem is in either /usr/share/apport, or a configuration file for apache.
If the load average at the top of the output of top is confusing, I think it should be. The fact that I got any response at all, including a display out of top, with load averages in any of the timeframes that are in excess of 900 is impressive to me, much less a load that high.
Looking for help on what I should be looking for in that file to fix this.
Thank you.
-Rusty :confused:
I built a dual core platform to run Mythbuntu on and after a recent apt-get update/upgrade cycle, discovered I could no longer see my Mythtweb server from various locations. Any time I log into the server and try kicking off the apache2 server, my system seems to vanish. To try to diagnose the situation, I launched 'top' in one ssh session and in another ssh session I started apache2. The top portion of top gives me:
top - 20:54:17 up 1:36, 3 users, load average: 488.33, 911.75, 33.46
Tasks: 27511 total, 2 running, 27509 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.2%us, 85.4%sy, 0.0%ni, 0.2%id, 13.1%wa, 0.0%hi, 0.2%si, 0.0%st
Mem: 2067504k total, 2018336k used, 49168k free, 668k buffers
Swap: 2000084k total, 2000084k used, 0k free, 1784k cached
Needless to say the system seems a bit sluggish.
I sorted the output of top by pid, (higher pids will be at the top) and I see:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
32767 root 17 0 4384 168 4 S 0 0.0 0:00.00 apport
32766 root 11 -5 0 0 0 S 0 0.0 0:00.00 khelper
32765 root 18 0 4388 168 4 S 0 0.0 0:00.00 apport
32764 root 11 -5 0 0 0 S 0 0.0 0:00.00 khelper
with the aport and khelper processes filling the rest of the listing. And yes, 'ps -ef' presents a screen filled with stuff like:
root 9566 9565 0 20:36 ? 00:00:00 /usr/bin/python /usr/share/appor
root 9567 11 0 20:36 ? 00:00:00 [khelper]
root 9568 9567 0 20:36 ? 00:00:00 /usr/bin/python /usr/share/appor
root 9569 11 0 20:36 ? 00:00:00 [khelper]
Eventually I start seeing messages about no resources available to fork if I try to run a command in a shell.
It looks like either /etc/init.d/apache2 or one of the other apps associated with apache is fork bombing my system. Based upon the output of ps, I'm thinking that the problem is in either /usr/share/apport, or a configuration file for apache.
If the load average at the top of the output of top is confusing, I think it should be. The fact that I got any response at all, including a display out of top, with load averages in any of the timeframes that are in excess of 900 is impressive to me, much less a load that high.
Looking for help on what I should be looking for in that file to fix this.
Thank you.
-Rusty :confused: