[omniORB] Troubleshooting a server that is becoming inaccessible during the night.

Mike Bendickson Mike.Bendickson@spanlink.com
Tue, 7 Nov 2000 11:22:59 -0600


I have a server on one system that becomes inaccessible every night.  Both
network and local clients are unable to send messages to it.  If I restart
the server, the clients are able to connect again.

Looking at the trace output, the only thing that sticks out to me is:

	tcpSocketMTfactory real_shutdown: fd no. 324

I haven't seen this message on our other (working) systems.

I believe that tcpSocketStrand::real_shutdown() is the function that is
printing this message.

I'm using 2.8.0 on NT 4.0.

Here's the trace output:

gateKeeper is not installed. All incoming are accepted.
strand Rope::incrRefCount: old value = 0
strand Ripper: start.
scavenger : start.
tcpSocketMTfactory Rendezvouser: start.
tcpSocketMTfactory Rendezvouser: block on accept()
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
.
.
.
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
tcpSocketMTfactory Rendezvouser: unblock from accept()
tcpSocketMTfactory Rendezvouser: accept new strand.
tcpSocketMTfactory Rendezvouser: block on accept()
tcpSocketMTfactory Worker: start.
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
tcpSocketMTfactory Rendezvouser: unblock from accept()
tcpSocketMTfactory Rendezvouser: accept new strand.
tcpSocketMTfactory Rendezvouser: block on accept()
tcpSocketMTfactory Worker: start.
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
.
.
.
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
tcpSocketMTfactory Worker: #### Communication failure. Connection closed.
tcpSocketMTfactory Worker: exit.
tcpSocketMTfactory ~tcpScoketStrand: close socket no. 300
tcpSocketMTfactory Rendezvouser: unblock from accept()
tcpSocketMTfactory Rendezvouser: accept new strand.
tcpSocketMTfactory Rendezvouser: block on accept()
tcpSocketMTfactory Worker: start.
tcpSocketMTfactory Worker: #### Communication failure. Connection closed.
tcpSocketMTfactory Worker: exit.
tcpSocketMTfactory ~tcpScoketStrand: close socket no. 352
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
.
.
.
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
tcpSocketMTfactory real_shutdown: fd no. 324
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
.
.
.
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
tcpSocketMTfactory Worker: #### Communication failure. Connection closed.
tcpSocketMTfactory Worker: exit.
tcpSocketMTfactory ~tcpScoketStrand: close socket no. 324
scavenger : scanning connections
scavenger : scanning connections
scavenger : scanning connections
.
.
.

Nothing but "scavenger : scanning connections" after this, even when a
client tries to make a request.

Troubleshooting tips are very welcome.

Thanks,
-Mike