server_loop: accept: Software caused connecti

[Anonymous]

Freebsd 8.0 x86
udpxy 1.0-Chipmunk (build 19)

Запускаю демон такой командой
udpxy -a ip -m em0 -p 8888 -S -v -l /var/log/udpxy.log -B 2048K -c 1000 -R 1 -T -M 120 -H 120

Периодически демон вылетает через 20-30 мин, в логе следующее:

Feb 13 20:33:31 stream3 udpxy: read_buf: read: Resource temporarily unavailable
Feb 13 20:33:35 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:33:36 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:33:36 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:33:44 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:33:55 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:33:57 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:34:06 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:34:10 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:34:11 stream3 udpxy: read_command - recv: Connection reset by peer
Feb 13 20:34:11 stream3 udpxy: get_src_info: getpeername: Socket is not connected
Feb 13 20:34:11 stream3 udpxy: send_http_response - send: Broken pipe
Feb 13 20:34:11 stream3 udpxy: send_http_response - send: Broken pipe
Feb 13 20:34:12 stream3 udpxy: read_buf: read: Resource temporarily unavailable
Feb 13 20:34:13 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:34:15 stream3 udpxy: read_command - recv: Connection reset by peer
Feb 13 20:34:15 stream3 udpxy: get_src_info: getpeername: Socket is not connected
Feb 13 20:34:15 stream3 udpxy: send_http_response - send: Broken pipe
Feb 13 20:34:15 stream3 udpxy: send_http_response - send: Broken pipe
Feb 13 20:34:16 stream3 udpxy: server_loop: accept: Software caused connection abort
Feb 13 20:34:16 stream3 udpxy: udpxy 1.0-Chipmunk (build 19) standard is exiting with rc=
Feb 13 20:34:16 stream3 udpxy: write_buf: write: Broken pipe
Feb 13 20:34:16 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:16 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:16 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:16 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:16 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:17 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:17 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:17 stream3 udpxy: tpstat_update: write: Broken pipe
Feb 13 20:34:18 stream3 udpxy: tpstat_update: write: Broken pipe

Хелп! :)

[Anonymous]

В логе udpxy:

2011-02-11 20:34:29.752343 EET  1560    Received TSTAT={ sender=, bytes=, seconds= }
2011-02-11 20:34:29.752362 EET  1560    Updated context for pid=;  Kb/sec
2011-02-11 20:34:29.752374 EET  1560    Server is waiting for input: socket=, pipe=
2011-02-11 20:34:30.000431 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:31.003981 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:32.001282 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:33.005329 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:34.001256 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:34.066986 EET  1560    Received TSTAT={ sender=, bytes=, seconds= }
2011-02-11 20:34:34.067005 EET  1560    Updated context for pid=;  Kb/sec
2011-02-11 20:34:34.067017 EET  1560    Server is waiting for input: socket=, pipe=
2011-02-11 20:34:35.009303 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:36.003481 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:37.004032 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:38.003331 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:38.310810 EET  1560    Received TSTAT={ sender=, bytes=, seconds= }
2011-02-11 20:34:38.310828 EET  1560    Updated context for pid=;  Kb/sec
2011-02-11 20:34:38.310840 EET  1560    Server is waiting for input: socket=, pipe=
2011-02-11 20:34:39.000259 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:40.002183 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:41.004731 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:41.598028 EET  1560    Received TSTAT={ sender=, bytes=, seconds= }
2011-02-11 20:34:41.598043 EET  1560    Updated context for pid=;  Kb/sec
2011-02-11 20:34:41.598051 EET  1560    Server is waiting for input: socket=, pipe=
2011-02-11 20:34:42.002907 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:43.000209 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:44.003016 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:45.000934 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:45.137621 EET  1560    Received TSTAT={ sender=, bytes=, seconds= }
2011-02-11 20:34:45.137639 EET  1560    Updated context for pid=;  Kb/sec
2011-02-11 20:34:45.137650 EET  1560    Server is waiting for input: socket=, pipe=
2011-02-11 20:34:46.008855 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:47.000421 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:48.003834 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:48.946060 EET  1560    Received TSTAT={ sender=, bytes=, seconds= }
2011-02-11 20:34:48.946080 EET  1560    Updated context for pid=;  Kb/sec
2011-02-11 20:34:48.946091 EET  1560    Server is waiting for input: socket=, pipe=
2011-02-11 20:34:49.002135 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:50.003808 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:51.001236 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:52.019150 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:53.008082 EET  1594    read_data: Buffer timed out after  seconds
2011-02-11 20:34:53.559783 EET  1560    Received TSTAT={ sender=, bytes=, seconds= }
2011-02-11 20:34:53.559801 EET  1560    Updated context for pid=;  Kb/sec