apache running at 100% indefinitely
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache2 (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Binary package hint: apache2
Description: Ubuntu 9.10
Release: 9.10
Arch: amd64
This apache2 process has been running for days at 100% CPU. There were actually ~6 or 7 of them - I killed all but one, to get my load down from 12+ to something usable. I've seen this several times in the last 2 months since I migrated from 8.04 i386 to 9.10 amd64.
top - 09:00:31 up 20 days, 12:45, 4 users, load average: 1.49, 1.39, 3.67
Tasks: 258 total, 3 running, 254 sleeping, 1 stopped, 0 zombie
Cpu(s): 23.1%us, 0.2%sy, 0.0%ni, 74.4%id, 2.2%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 2025104k total, 1845848k used, 179256k free, 266588k buffers
Swap: 2056248k total, 56472k used, 1999776k free, 641952k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7966 www-data 20 0 326m 21m 1888 R 100 1.1 3144:35 apache2
root@ns:
apache2:
Installed: 2.2.12-1ubuntu2.2
Candidate: 2.2.12-1ubuntu2.2
Version table:
*** 2.2.12-1ubuntu2.2 0
500 http://
500 http://
100 /var/lib/
2.
500 http://
root@ns:
php5:
Installed: 5.2.10.
Candidate: 5.2.10.
Version table:
*** 5.2.10.
500 http://
500 http://
100 /var/lib/
5.
500 http://
root@ns:
zend-framework:
Installed: (none)
Candidate: 1.9.4-0ubuntu2.1
Version table:
1.
500 http://
500 http://
1.9.4-0ubuntu2 0
500 http://
root@ns:
libzend-
Installed: (none)
Candidate: 1.9.4-0ubuntu2.1
Version table:
1.
500 http://
500 http://
1.9.4-0ubuntu2 0
500 http://
strace and ltrace yield nothing. Attaching gdb to the running process shows:
0x00007f749e47fff1 in _zval_ptr_dtor (zval_ptr=
at /build/
413 /build/
(gdb) bt
#0 0x00007f749e47fff1 in _zval_ptr_dtor (zval_ptr=
at /build/
#1 0x00007f749e4cd9bd in ZEND_ASSIGN_
execute_
at /build/
#2 0x00007f749e4b075c in execute (op_array=
at /build/
#3 0x00007f749e4b43aa in zend_do_
execute_
at /build/
#4 0x00007f749e4b075c in execute (op_array=
at /build/
#5 0x00007f749e48c5f6 in zend_execute_
file_count=3) at /build/
#6 0x00007f749e447673 in php_execute_script (primary_
at /build/
#7 0x00007f749e4fe5ed in php_handler (r=0x7f749e4fe5ed)
at /build/
#8 0x00007f74a311f0d0 in ap_run_handler ()
from /usr/lib/
#9 0x00007f74a3122a18 in ap_invoke_handler ()
from /usr/lib/
#10 0x00007f74a3130578 in ap_process_request ()
from /usr/lib/
#11 0x00007f74a312d458 in ?? () from /usr/lib/
#12 0x00007f74a3126c68 in ap_run_
from /usr/lib/
#13 0x00007f74a3134fcb in ?? () from /usr/lib/
#14 0x00007f74a313529a in ?? () from /usr/lib/
#15 0x00007f74a31355cb in ap_mpm_run ()
from /usr/lib/
#16 0x00007f74a310b350 in main () from /usr/lib/
ProblemType: Bug
Architecture: amd64
Date: Tue May 4 08:55:39 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: apache2.2-bin 2.2.12-1ubuntu2.2
ProcEnviron:
PATH=(custom, no user)
LANG=C
ProcVersionSign
SourcePackage: apache2
Uname: Linux 2.6.31-20-generic x86_64
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!
When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.