I've been digging through the mailing archive, but haven't been able to find any thread on the problem we are experiencing.<br><br>We've been running the config setup, shown at the bottom, for months on windows server 2003 using spread version 3.17.4. I've used <font size="-1">spsend and<span style="font-weight: bold;"></span> sprecv with -a </font>172.25.30.255 with final results of:<br> sprecv - Report: total packets 10000, total missed 8001, total corrupted 0<br> spsend - sent 10000 packets of 1024 bytes<br>So, it seems the Spread_Segments are setup correctly and the network is not an issue.<br><br>however, the daemon will suddenly become unresponsive after it's been running fine for a few days. The longest any daemon has been up without issue was around 3 or 5 weeks; the shortest would be around 4 days. Once we restart the spread daemon, everything is fine again until the next relapse.<br><br>Any
help or insight into resolving this issue will greatly be appreciated.<br> <br> DebugFlags = { EXIT PRINT DEBUG EVENTS CONFIGURATION STATUS }<br> EventLogFile = C:\logs\spreadlog.log<br> EventTimeStamp = "[%a %d %b %Y %H:%M:%S]"<br> <br> SocketPortReuse = ON<br> DangerousMonitor = true<br> <br> Spread_Segment 172.25.30.255:8006 {<br> as-ny-cbapps2 172.25.30.27<br> as-ny-cbsql3 172.25.30.35<br> }<br> <br> Spread_Segment 172.25.5.255:8006 {<br> as-phl-cbiis1 172.25.5.61<br> as-phl-cbiis4 172.25.5.62<br> }<p> 
<hr size=1>Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. <a href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ "> Try it now.</a>