Re: CLOSE_WAIT issues

On Jul 25, 2006, at 11:26 AM, John Pollard wrote:

> I believe we are on WO5.2.4, though not sure how to confirm that  
> 100% these days. We do need to upgrade to 5.3, so will try to bring  
> that process forwards in case it helps.

Hmm... I've never had CLOSE_WAIT problems with 5.2.4 -- and I've  
heard disturbing reports that 5.3 has some problems leaving files in  
CLOSE_WAIT (though not as bad as 5.2.2 and 5.2.1).  Given that you're  
having problems with lsof (and I assume ps too), I'd very strongly  
recommend a re-install of the entire OS.


> You are right, I now think I was mistaken about the multiple  
> wotaskd processes. These are actually our java instances talking to  
> mysqld (at 3306). Not sure if these being in a CLOSE_WAIT state is  
> a problem or not? I suspect not.

Not sure.  I've never noticed CLOSE_WAIT being a problem when  
communicating with a database, so maybe this is something different.   
What I've seen is that both wotaskd and any WO app can get stuck in  
CLOSE_WAIT when talking to each other.


> In our nightly script we do call:
> /sbin/SystemStarter restart 'WebObjects Services'
> but the CLOSE_WAITS do seem to remain afterwards, even with a 5 min  
> sleep after the wo restart, so then we reboot

Do you see wotaskd and your apps restart when you issue this  
command?  Because that is what is required -- and I've had problems  
using SystemStarter in the past.  If this is restarting wotaskd and  
your apps properly and you're still having problems then its even  
more evidence that you need to re-install the OS.  One of my clients  
had similar problems (restarting wotaskd and apps didn't help) and  
_nothing_ we did helped -- short of a reboot, as you are describing  
-- until he re-installed everything.


sacha


-- 
Sacha Michel Mallais             Senior Developer / President
Global Village Consulting Inc.   http://www.global-village.net/
PGP Key ID: 7D757B65             AIM: smallais