Operating system call recv failed (error no. 10054)

alexivara

Кто-нибудь сталкивался с такой руганью в логах? При этом все продолжает работать. 100% появляются такие ошибки когда останавливаю инстанцию. И периодически когда работают в системе. Вот пример лога:

Code:

Wed Nov 26 11:01:06 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 5 / sock 332
    (SI_ECONN_BROKEN/10054; I4; ST; 172.16.3.26:2788) [nixxi.cpp    4424]

Wed Nov 26 11:01:21 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 3 / sock 356
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2368) [nixxi.cpp    4424]
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 8 / sock 280
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2404) [nixxi.cpp    4424]
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 2 / sock 368
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2367) [nixxi.cpp    4424]

Wed Nov 26 11:01:22 2008
***LOG S30=> GwStopGateway, gateway stopped () [gwxxrd.c     14655]

И пример лога с другого сервера(идентичное железо) во время работы:

Code:

Tue Nov 25 14:45:43 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 13 / sock 1212
    (SI_ECONN_BROKEN/10054; I4; ST; 172.16.0.103:3364) [nixxi.cpp    4424]
Network error of client T23, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Client address of T23 is 172.16.0.103(hostname)
***LOG Q04=> DpRTmPrep, NiBufReceive (2028 USERNAME 23 hostname ) [dpxxdisp.c   11532]
RM-T23, U2028, 200   USERNAME, hostname, 11:22:16, M0, W1,     , 2/0

Сеть проверял, ни одного пакета не теряется.
Ноты которые уже прошерстил:
Note 155147 - WinNT: Connection reset by peer
Note 545177 - FAQ: Preliminary steps in analyzing RFC connections
Note 500235 - Network Diagnosis with NIPING

alexivara

такс, про первый пример суппорт уже ответил:

Цитата:

"Dear Customer,

The work processes have a TCP connection to the local gateway. This
connection always uses the local host connection via the IP address
127.0.0.1. When the system shuts down the work processes simply close
that connection which leads to the error messages in the gateway.
If the gateway recognizes those disconnect depends on if the gateway
shuts down faster than the work processes or not. So this is a race
condition if the messages occur or not.

Anyway when the messages appear during the stopping of the system they
do not indicate a problem at all and can be ignored.

Thanks and kind regards,"

Правила форума

Operating system call recv failed (error no. 10054)

Кто сейчас на конференции