Project

General

Profile

Bug #17836

Replication Tasks Broken after update from 9.10.1 to 9.10.1-U1

Added by DENNY VANDEMAELE about 4 years ago. Updated about 4 years ago.

Status:
Closed: Duplicate
Priority:
Critical
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

For several months I've had successful replication from the same source dataset to multiple target datasets and they began failing after update from 9.10.1 to 9.10.1-U1.

We also have a TrueNAS that wasn't updated and is replicating fine to the 9.10.1-U1 FreeNAS servers.

Steps to reproduce:
1) Replication Task must reside on a machine with 9.10.1-U1.
2) Setup replication task on SERVER A to SERVER B from dataset named "TEST"
3) Setup another replication task on SERVER A to SERVER C from dataset named "TEST" (or to SERVER B on a different volume)
4) The second replication will go very slow and then start reporting failures. Then after a while the first replication will start reporting failures as well.

I tried a reboot of the source server and replication errors persisted.

Steps to fix.... after 16 hours of failures, I booted the source machine back to 9.10.1, it came up and resolved the replication errors in about 10 minutes.

autorepl.py (25 KB) autorepl.py William Grzybowski, 09/28/2016 01:45 PM

Related issues

Has duplicate FreeNAS - Bug #17826: Errors reported during replicationResolved2016-09-28

History

#1 Updated by Heather Ownby about 4 years ago

  • Assignee set to William Grzybowski

#2 Updated by William Grzybowski about 4 years ago

  • File autorepl.py autorepl.py added
  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Critical
  • Target version set to 9.10.1-U2

Can you try booting again 9.10.1-U1 replacing attached file in /usr/local/www/freenasUI/tools/autorepl.py , reboot and check of it is back to normal again?

#3 Updated by William Grzybowski about 4 years ago

  • Status changed from Screened to Closed: Duplicate

#4 Updated by William Grzybowski about 4 years ago

  • Has duplicate Bug #17826: Errors reported during replication added

#5 Updated by DENNY VANDEMAELE about 4 years ago

The autorepl.py fixed both servers. Thanks!

Also available in: Atom PDF