Re^3: Weird IO::Socket problem

Perhaps the switch/router/net device between computers is timing out the connection and not telling you?

You might try putting ethereal on both segments and have it log the traffic between the two computers so you can catch it when it stops working. Then you might be able to determine if it's a client problem, server problem or network problem.

...roboticus

Comment on Re^3: Weird IO::Socket problem

Replies are listed 'Best First'.
Re^4: Weird IO::Socket problem by hallikpapa (Scribe) on Jan 14, 2008 at 17:24 UTC
I SUPPOSE that is a possibility, but we just got done moving the boxes to a new switch because there was a problem with the other one. This is a brand new switch and traffic is flying thru this thing now.	[reply]
Re^5: Weird IO::Socket problem by roboticus (Chancellor) on Jan 14, 2008 at 17:31 UTC
Did the weird behaviour start at about the time of the network change? Could the new switch may be misconfigured? ...roboticus	[reply]
Re^6: Weird IO::Socket problem by hallikpapa (Scribe) on Jan 14, 2008 at 17:35 UTC
No the change was because of the weird behavior we are seeing. There is 5 other boxes on this switch that have this process happening, and this is the only one randomly "timing out" or just stops reading the data.	[reply]