Re: Apache 1.3 dies on signal 11

From: Michael (cadaver_at_tucu.net)
Date: 04/20/05

  • Next message: Odhiambo Washington: "Re: [OBORONA-SPAM] Updating FreeBSD" 
    Date: Wed, 20 Apr 2005 03:13:46 -0700
To: freebsd-isp@freebsd.org

    On Apr 19, 2005, at 3:04 PM, Michael wrote:

    >
    > Hi,
    >
    > I have a system running FreeBSD 4.11-RELEASE-p3 and Apache 1.3.33 with
    > mod_ssl 2.8.22. Up until recently everything was working fine. Then as
    > of last week, Apache would die unexpectedly, usually around 3:30 AM
    > and 5:00 AM exiting with signal 11. Also, once it has died I can't
    > start it up with mod_ssl. I checked my crontab and newsyslog for any
    > clues what might be triggering this but I couldn't find anything that
    > seemed to be triggering the Apache processes to exit.
    >
    > Looking at the archives, other folks suggested that this could be a
    > hardware problem. I can't run memtest86 since the machine is located
    > in a hosting facilty, but I did run two make buildworlds to see if gcc
    > would die. Gcc didn't die.
    >
    > I can share the output of truss or gdb if anyone can help me figure
    > out what is going on. If you have any tips or clues, I would greatly
    > appreciate any suggestions.
    >
    > Thanks in advance,
    >
    > Michael
    >

    I had a suspicion that mod_php might have something to do with my
    problems judging from other posts I saw in the mailing list archives. I
    disabled my php extensions in /usr/local/etc/php/extension.ini one by
    one until Apache would start up with mod_ssl and not die.

    If I disable the openssl php extension, things work fine as far as I
    can tell. With the openssl extension enabled, Apache dies and this is
    what I get from the backtrace in gdb:
    (gdb) where
    #0 0x283f0fcc in RSA_new () from /usr/lib/libcrypto.so.3
    #1 0x2840b70e in RSAPrivateKey_asn1_meth () from
    /usr/lib/libcrypto.so.3
    #2 0x28417d20 in ASN1_item_ex_new () from /usr/lib/libcrypto.so.3
    #3 0x28417b4c in ASN1_item_ex_new () from /usr/lib/libcrypto.so.3
    #4 0x28413801 in ASN1_item_ex_d2i () from /usr/lib/libcrypto.so.3
    #5 0x2841329e in ASN1_item_d2i () from /usr/lib/libcrypto.so.3
    #6 0x2840b773 in d2i_RSAPrivateKey () from /usr/lib/libcrypto.so.3
    #7 0x2830c3f0 in ssl_init_TmpKeysHandle (action=1, s=0x809b038,
    p=0x809b010)
         at ssl_engine_init.c:443
    #8 0x2830bfa6 in ssl_init_Module (s=0x809b038, p=0x809b010)
         at ssl_engine_init.c:282
    #9 0x8055a88 in ap_init_modules (p=0x809b010, s=0x809b038)
         at http_config.c:1664
    #10 0x805df76 in standalone_main (argc=3, argv=0xbfbffb54) at
    http_main.c:5379
    #11 0x805e6ff in main (argc=3, argv=0xbfbffb54) at http_main.c:5767

    Does anyone know why this is happening?

    Michael

    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"

  • Next message: Odhiambo Washington: "Re: [OBORONA-SPAM] Updating FreeBSD"