Re: [Veritas-bu] EXIT STATUS 24: socket write failed
2011-01-27 11:13:01
Do you see any errors in event viewer. If yes, kindly share the same. I have also faced same issue specially on windows clients.
On Mon, Jan 24, 2011 at 8:54 AM, Justin Piszcz <jpiszcz AT lucidpixels DOT com> wrote:
Hi,
Has anyone seen anything like this before?
I have opened a case with Symantec but was curious what others have done
to delve depeper into socket write errors/timeouts/etc?
Using a 1 MiB buffer size on the media server and the client, only Windows hosts seem to have problems, no problems whatsoever with Linux clients. Before switching over from 1GbE media servers to 1GbE media servers, there
were no problems. Also from 1GbE -> 10GbE came Kernel 2.4 -> Kernel 2.6.
So there were quite a few changes, although the only clients affected seem to be Windows. Any thoughts here?
Also: 1. Already tried disabling TCP/UDP offload/chimney setting/etc.
2. Already tried full duplex/newer NIC driver, etc.
Any other thoughts?
2:55:37.627 AM: [1880.4808] <32> TransporterRemote::write[2](): FTL - SocketWriteException: send() call failed, could not write data to the socket, possible broken connection.
2:55:37.737 AM: [1880.4808] <16> NBUException::traceException(): ( An Exception of type [Symantec::NetBackup::Ncf::OperationFailedException] was thrown. Details about the exception follow...: Error code = (-1008).
Src file = (D:\656\src\cl\clientpc\util\tar_tfi.cpp). Src Line = (276). Description = (%s getBuffer operation failed). Operation type=(). ) 2:55:37.737 AM: [1880.4808] <16> NBUException::traceException(): (
An Exception of type [Symantec::NetBackup::Ncf::SocketWriteException] was thrown. Details about the exception follow...: Error code = (-1027). Src file = (TransporterRemote.cpp). Src Line = (310). Description = (send() call failed, could not write data to the socket, possible broken connection).
Local IP=(). Remote IP=(). Remote Port No.=(0). No. of bytes to write=(1048576) while No. of bytes written=(0). ) 2:55:37.737 AM: [1880.4808] <4> tar_base::V_vTarMsgW: INF - tar message received from tar_backup_tfi::processException
2:55:37.737 AM: [1880.4808] <2> tar_base::V_vTarMsgW: FTL - socket write failed 2:55:37.737 AM: [1880.4808] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0 2:55:37.737 AM: [1880.4808] <4> tar_backup::backup_done_state: INF - number of file directives found: 6
2:55:37.737 AM: [1880.4808] <2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup 2:55:37.737 AM: [1880.4808] <4> tar_base::stopKeepaliveThread: INF - waiting for keepalive thread to exit ...
2:55:37.737 AM: [1880.1712] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0) 2:55:37.737 AM: [1880.4808] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
2:55:37.737 AM: [1880.4808] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 24: socket write failed
Justin.
_______________________________________________ Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|