Re: [Veritas-bu] EXIT STATUS 24: socket write failed
Hi, I will look into this. Justin. On Thu, 27 Jan 2011, Saran Brar wrote: > 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 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@mailman.eng.auburn.edu >> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >> > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] EXIT STATUS 24: socket write failed
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 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@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] EXIT STATUS 24: socket write failed
Hi Simon, Looks close if not the one he is talking about, will give it a try, thanks! Justin. On Mon, 24 Jan 2011, WEAVER, Simon (external) wrote: > Not this one by chance? > http://www.symantec.com/business/support/index?page=content&id=TECH73159 > > > > From: veritas-bu-boun...@mailman.eng.auburn.edu > [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wayne T > Smith > Sent: Monday, January 24, 2011 6:16 PM > To: veritas-bu@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] EXIT STATUS 24: socket write failed > > > Maybe some new version of NetBackup will use robust, programmed > connections rather than the current hodge-podge that leads to untold > customer frustrations and lost time. So many versions, so little gain. > Wayne > > P.S. I think a Symantec note admits problems with larger buffers and > some versions of Windows; sorry I don't recall its ID. > > > This email (including any attachments) may contain confidential > and/or privileged information or information otherwise protected > from disclosure. If you are not the intended recipient, please > notify the sender immediately, do not copy this message or any > attachments and do not use it for any purpose or disclose its > content to any person, but delete this message and any attachments > from your system. Astrium disclaims any and all liability if this > email transmission was virus corrupted, altered or falsified. > -o- > Astrium Limited, Registered in England and Wales No. 2449259 > Registered Office: > Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] EXIT STATUS 24: socket write failed
Not this one by chance? http://www.symantec.com/business/support/index?page=content&id=TECH73159 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wayne T Smith Sent: Monday, January 24, 2011 6:16 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] EXIT STATUS 24: socket write failed Maybe some new version of NetBackup will use robust, programmed connections rather than the current hodge-podge that leads to untold customer frustrations and lost time. So many versions, so little gain. Wayne P.S. I think a Symantec note admits problems with larger buffers and some versions of Windows; sorry I don't recall its ID. This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. -o- Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] EXIT STATUS 24: socket write failed
Maybe some new version of NetBackup will use robust, programmed connections rather than the current hodge-podge that leads to untold customer frustrations and lost time. So many versions, so little gain.Wayne P.S. I think a Symantec note admits problems with larger buffers and some versions of Windows; sorry I don't recall its ID. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] EXIT STATUS 24: socket write failed
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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
