Date: Wed, 29 Oct 2003 11:37:56 +0100 From: =?ISO-8859-2?Q?=22Branko_F=2E_Gra=E8nar=22?= <bfg@noviforum.si> To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: FreeBSD 5.1-p10 reproducible crash with Apache2 Message-ID: <3F9F9884.3020309@noviforum.si>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. FreeBSD 5.1-p10 (and also possible other 5.1-pX version) can be remotely locked up if the following criteria is met: + apache2 has mod_ssl loaded and enabled + apache2 has the following configuration directives set to the following values: SSLMutex sem SSLSessionCache shm:/some/file(1048576) + client connects via SSL/TLS to apache fast enough. If all conditions above are satisfied except the last one, then lockup doesn't happen. I tested on three 5.1-p10 machines (SMP, uniprocessor, uniprocessor with hypterthreading) with JMeter 1.9.1. It is possible lockup machine with 100 requests (1 concurrent request) in 1-3 seconds. If SSLMutex is set to file:/path/somewhere and SSLSessionCache is set to dbm:/some/dbm lockup does not accour. Linux 2.4.22 is not affected by this issue. Details: apache: 2.0.47 php: 4.3.3 + turck mmcache 2.4.2 web application: horde imp webmail Best regards, Brane -----BEGIN PGP SIGNATURE----- iD8DBQE/n5iEfiC/E+t8hPcRAu9kAJ4lpD5CJf7HwYxphipHin0gUFaORACfV6ei Wxi5PvScjACrKmCxCEbt0l0= =UVfz -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F9F9884.3020309>