Package: libapache-mod-ssl
Version: 2.8.22-1sarge1
Severity: important


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libapache-mod-ssl depends on:
ii  apache-common         1.3.33-6sarge3     support files for all Apache webse
ii  libc6                 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii  libdb4.2              4.2.52-18          Berkeley v4.2 Database Libraries [
ii  libexpat1             1.95.8-3           XML parsing C library - runtime li
ii  libssl0.9.7           0.9.7e-3sarge4     SSL shared libraries
ii  openssl               0.9.7e-3sarge4     Secure Socket Layer (SSL) binary a

-- no debconf information

Hi, 

Ignore my previous bugreport if you got it, I got the
strace: 

Hi, 

The past week I have seen apache lockup on four
different servers.  Upon "apachectl restart" it comes back up
without any errors... but the webserver is still not
responding. 

I look in /var/log/apache and there are about a
bazillion ssl.mutex* files in there.  Restart a few more
times... still nothing.  Attach a strace to it and we
see: 

open("/var/cache/apache/__db.ssl_cache.db",O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 
0600) = -1 EEXIST (File exists)
stat64("/var/cache/apache/ssl_cache.db", 0xbffff130) = -1 ENOENT (No such file 
or directory)
open("/var/cache/apache/__db.ssl_cache.db",O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 
0600) = -1 EEXIST (File exists)
open("/var/cache/apache/__db.ssl_cache.db",O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE,0600)
 = -1 EEXIST (File exists)
open("/var/cache/apache/__db.ssl_cache.db",O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE,0600)
 = -1 EEXIST (File exists)
stat64("/var/cache/apache/ssl_cache.db", 0xbffff130) = -1 ENOENT (No such file 
or directory)
open("/var/cache/apache/__db.ssl_cache.db",O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE,0600)
 = -1 EEXIST (File exists)
Process 32538 detached

...rm that ssl_cache.db file up there, restart, and it
is back. 

These are debian sarge machines, although I'm wondering
if there isn't a new DoS exploit in the wild right now?
The machines are fully patched.  Anyone else seen this?

Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to