Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: R1-E-Failed to transfer files

  1. #1
    bwelker is offline Junior Member
    Join Date
    Oct 2015
    Posts
    8
    Rep Power
    0

    R1-E-Failed to transfer files

    I've been using Repliweb for about 8 months with decent success. Most uploads and downloads to/from S3 buckets work well. Every once in a while my job fails without a clear reason in the logs. I am attempting an upload of about 1.5TB worth of files and the last 200GB are giving me problems. When I resubmit the job after failing, lists are created and the transfer begins but only does about 20 files per transfer and then fails. I've resubmitted the job a few times and it slowly chips away at the file count but never gets very far.

    Here are the last few log entries from the General Log, full log available upon request:

    13:29:07 Continuing replication of "saic"

    13:29:11 Recovering previous transfer to target operation
    13:47:16 LFA-E-MTRSFD, An error occurred during transfer. Transferred 20 out of 81 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <9170999>, bytes_sent <0>, curr_bytes_sent <-1>
    -SYS-E-SYSMSG, W_10053 An established connection was aborted by the software in your host machine.
    13:47:16 R1-E-Failed to transfer files
    ================================================

    13:52:25 Continuing replication of "saic"

    13:52:28 Comparative snapshot has expired and is no longer valid - going back to Comparative snapshot generation stage
    13:52:29 Starting Controller and Satellite snapshot generation
    Controller snapshot generation time was 267 seconds
    Satellite snapshot generation time was 39 seconds
    13:56:56 Finished Controller and Satellite snapshot generation

    13:56:56 Starting Comparative snapshot generation
    13:56:58 Finished Comparative snapshot generation

    78021 file(s) (~198785 Mbytes) will be copied from the source to the target

    13:56:58 No files to delete on target before transfer

    13:57:00 No directories to create on target


    13:57:03 Starting file transfer
    Using Large File Accelerator
    Using SSL authentication and encryption
    Using 3 concurrent transfer(s)
    Set to abort on file access errors
    Set to use maximum 3 concurrent sessions per file

    14:12:56 LFA-E-MTRSFD, An error occurred during transfer. Transferred 120 out of 141 file(s) scanned. First file error was:
    14:12:56 R1-E-Failed to transfer files
    ================================================

    14:18:04 Continuing replication of "saic"

    14:18:07 Recovering previous transfer to target operation
    14:20:22 LFA-E-MTRSFD, An error occurred during transfer. Transferred 40 out of 181 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <8981275>, bytes_sent <0>, curr_bytes_sent <-1>
    -SYS-E-SYSMSG, W_10053 An established connection was aborted by the software in your host machine.
    14:20:22 R1-E-Failed to transfer files

  2. #2
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    234
    Rep Power
    4
    Quote Originally Posted by bwelker View Post
    I've been using Repliweb for about 8 months with decent success. Most uploads and downloads to/from S3 buckets work well. Every once in a while my job fails without a clear reason in the logs. I am attempting an upload of about 1.5TB worth of files and the last 200GB are giving me problems. When I resubmit the job after failing, lists are created and the transfer begins but only does about 20 files per transfer and then fails. I've resubmitted the job a few times and it slowly chips away at the file count but never gets very far.

    Here are the last few log entries from the General Log, full log available upon request:

    13:29:07 Continuing replication of "saic"

    13:29:11 Recovering previous transfer to target operation
    13:47:16 LFA-E-MTRSFD, An error occurred during transfer. Transferred 20 out of 81 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <9170999>, bytes_sent <0>, curr_bytes_sent <-1>
    -SYS-E-SYSMSG, W_10053 An established connection was aborted by the software in your host machine.
    13:47:16 R1-E-Failed to transfer files
    ================================================

    13:52:25 Continuing replication of "saic"

    13:52:28 Comparative snapshot has expired and is no longer valid - going back to Comparative snapshot generation stage
    13:52:29 Starting Controller and Satellite snapshot generation
    Controller snapshot generation time was 267 seconds
    Satellite snapshot generation time was 39 seconds
    13:56:56 Finished Controller and Satellite snapshot generation

    13:56:56 Starting Comparative snapshot generation
    13:56:58 Finished Comparative snapshot generation

    78021 file(s) (~198785 Mbytes) will be copied from the source to the target

    13:56:58 No files to delete on target before transfer

    13:57:00 No directories to create on target


    13:57:03 Starting file transfer
    Using Large File Accelerator
    Using SSL authentication and encryption
    Using 3 concurrent transfer(s)
    Set to abort on file access errors
    Set to use maximum 3 concurrent sessions per file

    14:12:56 LFA-E-MTRSFD, An error occurred during transfer. Transferred 120 out of 141 file(s) scanned. First file error was:
    14:12:56 R1-E-Failed to transfer files
    ================================================

    14:18:04 Continuing replication of "saic"

    14:18:07 Recovering previous transfer to target operation
    14:20:22 LFA-E-MTRSFD, An error occurred during transfer. Transferred 40 out of 181 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <8981275>, bytes_sent <0>, curr_bytes_sent <-1>
    -SYS-E-SYSMSG, W_10053 An established connection was aborted by the software in your host machine.
    14:20:22 R1-E-Failed to transfer files

    Hello bwelker,

    We have since LFA transfer issue on previous version of R1.

    Please download the latest version of R1 6.2 below and upgrade your R1 center and R1 on your EC2 server.

    Then, try to resubmit the job to see if this resolve the issue.

    https://attunity-patch.s3.amazonaws....068.150216.exe

    Thanks,
    Steve

  3. #3
    bwelker is offline Junior Member
    Join Date
    Oct 2015
    Posts
    8
    Rep Power
    0
    Quote Originally Posted by stevenguyen View Post
    Hello bwelker,

    We have since LFA transfer issue on previous version of R1.

    Please download the latest version of R1 6.2 below and upgrade your R1 center and R1 on your EC2 server.

    Then, try to resubmit the job to see if this resolve the issue.

    https://attunity-patch.s3.amazonaws....068.150216.exe

    Thanks,
    Steve
    Updated both but now I receive "R1-E-Failed to get remote Edge information" message.

  4. #4
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    234
    Rep Power
    4
    The error "Updated both but now I receive "R1-E-Failed to get remote Edge information" message."

    it mean that the center could not reach the edge altogether.

    1. on the edge server, verify that our services is running.
    - on the edge server, try to telnet localhost 2837 ,,, you should get a blank screen.

    2. on the center server, try to telnet the edge.
    telnet edgeserver_or_ipaddressofedge 2837 ,, you should get a blank screen.

    3. Verify that your firewall is set correctly for your center and edge.

    Thanks,
    Steve

  5. #5
    bwelker is offline Junior Member
    Join Date
    Oct 2015
    Posts
    8
    Rep Power
    0
    Quote Originally Posted by stevenguyen View Post
    The error "Updated both but now I receive "R1-E-Failed to get remote Edge information" message."

    it mean that the center could not reach the edge altogether.

    1. on the edge server, verify that our services is running.
    - on the edge server, try to telnet localhost 2837 ,,, you should get a blank screen.

    2. on the center server, try to telnet the edge.
    telnet edgeserver_or_ipaddressofedge 2837 ,, you should get a blank screen.

    3. Verify that your firewall is set correctly for your center and edge.

    Thanks,
    Steve
    Blank screens for both. Firewall hasn't changed.

  6. #6
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    234
    Rep Power
    4
    Quote Originally Posted by bwelker View Post
    Blank screens for both. Firewall hasn't changed.
    Pretty sure you have connection issue.

    1. try to restart the Attunity Cloudbeam server from AWS.

    2. Try to Restart the R1 server locally.

    3. Instead of replicating to S3 bucket. try to setup a test job to replicate a small folder from your the R1 center to the Edge server (Attunity Cloudbeam server), does this job fail as well or success?

    Thanks,
    Steve

  7. #7
    bwelker is offline Junior Member
    Join Date
    Oct 2015
    Posts
    8
    Rep Power
    0
    Quote Originally Posted by stevenguyen View Post
    The error "Updated both but now I receive "R1-E-Failed to get remote Edge information" message."

    it mean that the center could not reach the edge altogether.

    1. on the edge server, verify that our services is running.
    - on the edge server, try to telnet localhost 2837 ,,, you should get a blank screen.

    2. on the center server, try to telnet the edge.
    telnet edgeserver_or_ipaddressofedge 2837 ,, you should get a blank screen.

    3. Verify that your firewall is set correctly for your center and edge.

    Thanks,
    Steve
    1. Blank screen
    2. Blank screen
    3. No firewall rules were changed

    Here is info from the general log:

    15:20:03 Starting Satellite <23.21.128.222> information retrieval
    Satellite access credentials: User: <administrator>

    Error during Satellite information retrieval,
    Failed to establish edge session
    -RDSSVR-E-SSLINIT, Error initializing SSL
    -CRP-E-SSLINIT, failed to initialize ssl context
    -CRP-E-PKEY, failed to load private key from file C:\Program Files\RepliWeb\RDS\config\SSL\rds_server_key.pem
    -CRP-E-INTMSG, bad decrypt
    -CRP-E-CONN, client failed to establish secured connection
    -CRP-E-INTMSG, (null)

  8. #8
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    234
    Rep Power
    4
    Quote Originally Posted by bwelker View Post
    1. Blank screen
    2. Blank screen
    3. No firewall rules were changed

    Here is info from the general log:
    Much better error message, it mean that the certificate between the server could have gone bad.

    please do the follow steps : Stage 3: Configure the 'Attunity CloudBeam for Amazon S3' EC2 Instance

    and follow the guide again.

    Quick Start Guide: Attunity CloudBeam for Amazon S3 | Attunity

    Thanks,
    Steve

  9. #9
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    234
    Rep Power
    4
    Hello bwelker,

    From further investigation:


    The updated R1 6.2.xx is only to be install on the local R1 server / On premise server. and Not to install on the Amazon Attunity S3 Cloudbeam server.

    So if you already install 6.2xx on your Amazon Attunity S3 Cloudbeam server, you would have to terminate this server and spin up a new Attunity S3 Cloudbeam server from the Marketplace to reverse back the version.

    Thanks,
    Steve

  10. #10
    bwelker is offline Junior Member
    Join Date
    Oct 2015
    Posts
    8
    Rep Power
    0
    Quote Originally Posted by stevenguyen View Post
    Hello bwelker,

    From further investigation:


    The updated R1 6.2.xx is only to be install on the local R1 server / On premise server. and Not to install on the Amazon Attunity S3 Cloudbeam server.

    So if you already install 6.2xx on your Amazon Attunity S3 Cloudbeam server, you would have to terminate this server and spin up a new Attunity S3 Cloudbeam server from the Marketplace to reverse back the version.

    Thanks,
    Steve
    I reverted back o the Marketplace version and it worked for a few weeks. I've had an upload fail on me over and over for the past week and a half now. It will move 20, 40, 60 files and then fail.

    General Report

    12:03:43 Starting file transfer
    Using Large File Accelerator
    Using SSL authentication and encryption
    Using 3 concurrent transfer(s)
    Set to abort on file access errors
    Set to use maximum 3 concurrent sessions per file

    12:27:57 LFA-E-MTRSFD, An error occurred during transfer. Transferred 20 out of 23 file(s) scanned. First file error was: LFA-E-INSLNK, TCP Link object must support SFO_ID_SET_NUMBER/SFLC_SEND_SIZE/SFLC_BUFFER_SIZE/SFLC_[SEND|RECV]_TIMEOUT_SEC
    12:27:57 R1-E-Failed to transfer files
    ================================================

    12:30:07 Continuing replication of "kelleyiu"

    12:30:11 Recovering previous transfer to target operation
    12:51:58 LFA-E-MTRSFD, An error occurred during transfer. Transferred 20 out of 30 file(s) scanned. First file error was: LFA-E-INSLNK, TCP Link object must support SFO_ID_SET_NUMBER/SFLC_SEND_SIZE/SFLC_BUFFER_SIZE/SFLC_[SEND|RECV]_TIMEOUT_SEC
    12:51:58 R1-E-Failed to transfer files
    ================================================

    12:54:40 Continuing replication of "kelleyiu"

    12:54:44 Recovering previous transfer to target operation
    13:17:30 LFA-E-MTRSFD, An error occurred during transfer. Transferred 20 out of 41 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <9492668>, bytes_sent <0>, curr_bytes_sent <-1>
    -CRP-E-INTMSG, (null)
    13:17:30 R1-E-Failed to transfer files
    ================================================

    13:20:58 Continuing replication of "kelleyiu"

    13:21:01 Comparative snapshot has expired and is no longer valid - going back to Comparative snapshot generation stage
    13:21:02 Starting Controller and Satellite snapshot generation
    Controller snapshot generation time was 48 seconds
    Satellite snapshot generation time was 13 seconds
    13:21:50 Finished Controller and Satellite snapshot generation

    13:21:50 Starting Comparative snapshot generation
    13:21:51 Finished Comparative snapshot generation

    13001 file(s) (~68363 Mbytes) will be copied from the source to the target

    13:21:51 No files to delete on target before transfer

    13:21:52 No directories to create on target


    13:21:53 Starting file transfer
    Using Large File Accelerator
    Using SSL authentication and encryption
    Using 3 concurrent transfer(s)
    Set to abort on file access errors
    Set to use maximum 3 concurrent sessions per file

    13:25:35 LFA-E-MTRSFD, An error occurred during transfer. Transferred 0 out of 21 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <9492586>, bytes_sent <0>, curr_bytes_sent <-1>
    -CRP-E-INTMSG, (null)
    13:25:35 R1-E-Failed to transfer files
    ================================================

    13:30:04 Continuing replication of "kelleyiu"

    13:30:08 Starting file transfer
    Using Large File Accelerator
    Using SSL authentication and encryption
    Using 3 concurrent transfer(s)
    Set to abort on file access errors
    Set to use maximum 3 concurrent sessions per file

    13:50:43 LFA-E-MTRSFD, An error occurred during transfer. Transferred 20 out of 27 file(s) scanned. First file error was: LFA-E-INSLNK, TCP Link object must support SFO_ID_SET_NUMBER/SFLC_SEND_SIZE/SFLC_BUFFER_SIZE/SFLC_[SEND|RECV]_TIMEOUT_SEC
    13:50:43 R1-E-Failed to transfer files
    ================================================

    13:55:52 Continuing replication of "kelleyiu"

    13:55:56 Recovering previous transfer to target operation
    13:59:30 LFA-E-MTRSFD, An error occurred during transfer. Transferred 0 out of 15 file(s) scanned. First file error was: LFA-E-INSLNK, TCP Link object must support SFO_ID_SET_NUMBER/SFLC_SEND_SIZE/SFLC_BUFFER_SIZE/SFLC_[SEND|RECV]_TIMEOUT_SEC
    13:59:30 R1-E-Failed to transfer files
    ================================================

    14:04:38 Continuing replication of "kelleyiu"

    14:04:42 Recovering previous transfer to target operation
    14:26:18 LFA-E-MTRSFD, An error occurred during transfer. Transferred 20 out of 41 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <9492446>, bytes_sent <0>, curr_bytes_sent <-1>
    -CRP-E-INTMSG, (null)
    14:26:18 R1-E-Failed to transfer files
    ================================================

    14:31:26 Continuing replication of "kelleyiu"

    14:31:29 Comparative snapshot has expired and is no longer valid - going back to Comparative snapshot generation stage
    14:31:30 Starting Controller and Satellite snapshot generation
    Controller snapshot generation time was 53 seconds
    Satellite snapshot generation time was 10 seconds
    14:32:23 Finished Controller and Satellite snapshot generation

    14:32:23 Starting Comparative snapshot generation
    14:32:24 Finished Comparative snapshot generation

    12915 file(s) (~67584 Mbytes) will be copied from the source to the target

    14:32:24 No files to delete on target before transfer

    14:32:25 No directories to create on target


    14:32:26 Starting file transfer
    Using Large File Accelerator
    Using SSL authentication and encryption
    Using 3 concurrent transfer(s)
    Set to abort on file access errors
    Set to use maximum 3 concurrent sessions per file

    14:40:59 LFA-E-MTRSFD, An error occurred during transfer. Transferred 0 out of 21 file(s) scanned. First file error was: LFA-E-LNKERR, Link error: NET-E-SEND, network send error
    -CRP-E-SEND, send operation failed
    -CRP-E-SEND2, buffer size <9492352>, bytes_sent <0>, curr_bytes_sent <-1>
    -CRP-E-INTMSG, (null)
    14:40:59 R1-E-Failed to transfer files

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •