[KLUG Members] Apache hung up at semop

Adam Tauno Williams members@kalamazoolinux.org
Thu, 06 Sep 2001 09:59:41 -0400 (EDT)


I have IMP 2.2.1 on our interal web server.  Prior to a recent upgrade of the
systsem software (OS, apache, etc...) this product was 100% stable.  Since the
upgrade it (IMP) has been getting hung every few hours performing a semop.  All
other server functions and web pages continue normally, but IMP stops working
for all users.  Using strace and ipcs I can see an httpd sitting at semop on
IMP's semaphore id.  Doing a "/etc/rc.d/init.d/httpd stop" stops all put one
httpd,  and a strace -p {pid} of that http shows it sitting in semop.  I have
recompiled PHP just to make sure it was all happy,  but the problem seems to
still exists.  Has anyone seen this before?

Currently running....

kernel-smp-2.2.19-7.0.8
glibc-2.2-12
apache-1.3.14-3
imap-devel-4.7c2-12
php 4.0.6 (compiled as a module)

 './configure' '--with-apxs' '--with-ldap' '--with-pgsql' '--with-informix'
'--enable-sysvsem' '--enable-sysvshm' '--with-imap' '--enable-sockets'
'--with-gd' '--with-ttf' '--with-jpeg' '--with-png' '--enable-ftp'
'--disable-mysql'

Hardware: Dual Pentium III (Katmai) 498.699MHz Netfinity 5000

Looked around and haven't seen anything that appears obviously relevent to this
problem.  Anyone heard of any such problems with the mentioned
apache/php/kernel.  I'm entirely sure it is not IMP itself as this is the EXACT
same set of PHP files as before the upgrade.

Systems and Network Administrator
Morrison Industries
1825 Monroe Ave NW.
Grand Rapids, MI. 49505