Guys,

Issues.apache.org, which is running trunk or something very close to it to debug the JIRA issues, has some child processes sucking extreme quantities of CPU. For instance:

nobody 8515 8411 75 Feb25 ? 1-01:17:28 /usr/local/apache2- install/iss
                                       ^^^^^^^^^^

Isn't this cumulative CPU time in ps -fC httpd? And doesn't that reflect over a day's worth?

Here's a backtrace of the above:

(gdb) bt
#0 allocator_free (allocator=0x6000000000167ad0, node=0x6000000000186e80)
    at ../../../apr/memory/unix/apr_pools.c:343
#1  0x20000000003b6540 in apr_pool_destroy (pool=0x6000000000186ea8)
    at ../../../apr/memory/unix/apr_pools.c:769
#2  0x400000000004ae20 in eor_bucket_destroy (data=0x6000000000186f18)
    at /home/jerenkrantz/work/httpd-trunk/server/eor_bucket.c:52
#3  0x20000000000eef90 in apr_brigade_cleanup (data=0x600000000016aae8)
    at ../../../apr-util/buckets/apr_brigade.c:44
#4  0x20000000000eeec0 in brigade_cleanup (data=0x600000000016aae8)
    at ../../../apr-util/buckets/apr_brigade.c:34
#5  0x20000000003b77a0 in run_cleanups (cref=0x6000000000169be8)
    at ../../../apr/memory/unix/apr_pools.c:2044
#6  0x20000000003b62e0 in apr_pool_clear (pool=0x6000000000169bc8)
    at ../../../apr/memory/unix/apr_pools.c:689
#7  0x40000000000746d0 in child_main (child_num_arg=118704)
at /home/jerenkrantz/work/httpd-trunk/server/mpm/prefork/ prefork.c:467
#8  0x4000000000074de0 in make_child (s=0x6000000000023790, slot=100)
at /home/jerenkrantz/work/httpd-trunk/server/mpm/prefork/ prefork.c:736
#9  0x4000000000074fc0 in startup_children (number_to_start=49)
at /home/jerenkrantz/work/httpd-trunk/server/mpm/prefork/ prefork.c:747 #10 0x4000000000076740 in ap_mpm_run (_pconf=0x0, plog=0x600000000004e2a8,
    s=0x6000000000023790)
at /home/jerenkrantz/work/httpd-trunk/server/mpm/prefork/ prefork.c:975
#11 0x4000000000025ad0 in main (argc=2, argv=0x60000fffffffaf68)
    at /home/jerenkrantz/work/httpd-trunk/server/main.c:712

I don't see a request record anywhere, so I can't really tell if any of these CPU hogs have a reproducible history. However, I have seen this before on this codebase on this CPU and it looks like they're stuck in a tight loop in apr/memory/unix/apr_pools.c...

Perhaps this merits a closer look.

Maybe we should run this instance niced?

S.

--
[EMAIL PROTECTED]              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to