Quantcast
Channel: Symantec Connect - Backup and Recovery
Viewing all articles
Browse latest Browse all 6339

NB 7.6.0.1 - socket writer faile (24)/file read failed(13)

$
0
0
I need a solution

Hi,

I'm testing backups for two Win32 bit servers and am getting either socket write failed (24) or file read failed (13). This testing is to make sure that the various servers that we have will work with 7.6.0.1 before we upgrade the remaining 2 NBU domains.

 

Environment:

Master: RHEL5 x64 running NB 7.6.0.1

Media: Win 2008, x64 SP1 NB 7.6.0.1

Clients: 1) Win 2003, x86 and 2) Win 2008 x86

Below is the excerpt from the bpkar log on client (full log attached as zip):

13:50:08.785 [6764.6984] <2> TransporterRemote::write[2](): DBG -  | An Exception of type [SocketWriteException] has occured at: |   Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.55 $ , Function: TransporterRemote::write[2](), Line: 338 |   Local Address: [::]:0 |   Remote Address: [::]:0 |   OS Error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

) |   Expected bytes: 262144 |  (../TransporterRemote.cpp:338)

13:50:08.821 [6764.6984] <16> tar_tfi::processException:

An Exception of type [SocketWriteException] has occured at:

  Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.55 $ , Function: TransporterRemote::write[2](), Line: 338

  Module: @(#) $Source: src/ncf/tfi/lib/Packer.cpp,v $ $Revision: 1.91 $ , Function: Packer::getBuffer(), Line: 652

  Module: tar_tfi::getBuffer, Function: D:\NB\NB_7.6.0.1\src\cl\clientpc\util\tar_tfi.cpp, Line: 311

  Local Address: [::]:0

  Remote Address: [::]:0

  OS Error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

)

  Expected bytes: 262144

13:50:08.837 [6764.6984] <4> tar_base::V_vTarMsgW: INF - tar message received from tar_backup_tfi::processException
13:50:08.837 [6764.6984] <2> tar_base::V_vTarMsgW: FTL - socket write failed
13:50:08.844 [6764.6984] <16> dtcp_write: TCP - failure: send socket (384) (TCP 10053: Software caused connection abort)
13:50:08.844 [6764.6984] <16> dtcp_write: TCP - failure: attempted to send 26 bytes
13:50:08.844 [6764.6984] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
13:50:08.844 [6764.6984] <4> tar_backup::backup_done_state: INF -     number of file directives found: 1
13:50:08.844 [6764.6984] <2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup

 

This has happened before I upgraded the client on both the x86 servers from 7.5.0.5 to the latest one. Error happens after random duration (e.g. 5minutes, 2hrs, etc) But somehow didn't show up last week and I thought that a couple of changes that I had done on the media server might have fixed the issue. Other servers e.g. Win x64 and especially Linux servers have not had this error during my testing i.e. only Win x86 servers are showing this erratic behaviour.

Has anyone seen this earlier? or during the upgrade to 7.6.0.1? Any suggestions will be appreciated.


Viewing all articles
Browse latest Browse all 6339

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>