Yes, I have the same problem. I have a monitor watching for the "Log: UDP <span class="nfakPe">recvfrom</span> error: 111 () from <a href="http://0.0.0.0:0/" target="_blank">0.0.0.0:0</a>" error in the log file, which will then cause the server to be restarted.
<br><br>But alas, the log file is buffered, so it often does not show up, the server becomes unusable, but still shows up in gametracker and game-moniter.<br><br>They should unbuffer the logfile, or at the very least flush it every few seconds.
<br><br><div class="gmail_quote">On Jan 12, 2008 9:12 PM, Rick Page <<a href="mailto:mpcacrucesalus@gmail.com">mpcacrucesalus@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have been trying to track this down so I can give Ryan something to work with, but nothing is showing up in the log files. Server appears to be running fine from <a href="http://gametracker.com" target="_blank">gametracker.com
</a>, <a href="http://game-monitor.com" target="_blank">
game-monitor.com</a> and shows up in the Server Browser. After server has been running for awhile, nobody can connect. This is a dedicated server. I then go into the server and execute the script to stop it and look in DedicatedServer.log
file to see if I see anything and it shows that it shutsdown fine. I did see a NetComeGo: Close TcpipConnection_20 xx.xx.xx.xx:3237 followed by Exit: closesocket error (5), during one of the times I shutdown. Anyways, I start the server running again and everything seems to be fine again for awhile. I have replaced the ut3-bin file with the most recent one I could find from this list. It is frustrating because the script I use to check to see if ut3 has crashed and needs to be restarted doesn't restart it, because it doesn't think ut3 has crashed. Is there something else I should have in the command line to log more info?
<br>Thanks,<br><font color="#888888">Rick<br>
</font></blockquote></div><br>