Re: Socket Listener died.

Abhay Mannur wrote: > Here is the onstat -m output : > > 19:06:25 mt.c, line 5977, thread 19, proc id 14876, Invalid Mutex Type.> > 19:06:25 > Thread(19, soctcplst, 0, 1) > 19:06:25 oninit pid 14876 waiting for debugger I'm afraid I have no idea what is going on, but I have a couple of comments anyway. 1. There should also be a message saying it had written to a file named something like /tmp/af.83744512 (generally, af.xxxxxxx...) This file would be much more useful than your onconfig file (not that the onconfig is completely useless -- I can tell that your system is configured for both shared memory and sockets connections, and the sockets threads are running on the CPU VP). 2. The "oninit pid 14876 waiting for debugger" message means that someone has turned on AFDEBUG, which is done to make the system hang instead of crash, so that Tech Support can look at the conditions on the system when the error occurred. My suggestion is that you take all this information -- the af file, if it exists, your onconfig file, and your hung system (best to do this immediately after the error occurs) to your local Tech Support office (I mean, call them -- don't put it in a truck and visit them). Hopefully, you have a modem on the machine, or something on the network, so they can dial up and look at it. Or maybe you should try upgrading -- I think someone else has complained about 7.23 on this newsgroup recently. June -- june_t@hotmail.com Lost in the wilds of Palo Alto, living on Peanut M&M's