My customer is getting pretty upset. Where running Zope 2.2.3 on RH Linux 7 using the Zope bundled python. We're using gvib and have moved the Interbase server onto windows due to the broken pipe error bug in the Linux SS Interbase server. Every few hours the server just "locks up". It accepts TCP connections, but GET / returns nothing. I'm running with -M and -D options. I have up to 10 threads allowed. Using gdb, I can attach to each thread. All the threads are waiting for the global lock: at ../sysdeps/unix/sysv/linux/sigsuspend.c:45 #1 0x400347e9 in __pthread_wait_for_restart_signal (self=0xbf7ffc00) at pthread.c:901 #2 0x40030b8c in pthread_cond_wait (cond=0x8693f1c, mutex=0x8693f28) at restart.h:34 #3 0x80631f2 in PyThread_acquire_lock (lock=0x8693f18, waitflag=1) at thread_pthread.h:318 #4 0x807a63d in lock_PyThread_acquire_lock (self=0x8646338, args=0x0) at ./threadmodule.c:100 Except for one thread which is blocked here: 0x4008de75 in __sigsuspend (set=0x869623c) at ../sysdeps/unix/sysv/linux/sigsuspend.c:45 #1 0x400347e9 in __pthread_wait_for_restart_signal (self=0x4003e360) at pthread.c:901 #2 0x40036ad9 in __pthread_alt_lock (lock=0x40183720, self=0x0) at restart.h:34 #3 0x40032b26 in __pthread_mutex_lock (mutex=0x40183710) at mutex.c:120 #4 0x400dee48 in __libc_free (mem=0x8c09278) at malloc.c:3052 #5 0x4003234b in pthread_exited (pid=11887) at manager.c:707 #6 0x40032709 in pthread_reap_children () at manager.c:787 #7 0x40031a28 in __pthread_manager (arg=0x13) at manager.c:158 I can't find manager.c so I can't see if this code does, or does not have the global lock. Is this the "manager" thread, and is this normal? Perhaps this one is a red herring and there's another cause? -- Anyone have suggestions for how to diagnose this? Customer is getting pretty pissed. He has over 100 users of this site (import export operation) Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com AOL-IM: BKClements