Updated Troubleshooting (markdown)

Michael Stanclift 2021-04-23 15:58:17 -05:00
parent b7dfd2d9d7
commit e0c53ed6ec

@ -23,4 +23,6 @@ Some minimalist Linux distributions (such as Alpine Linux) use an older version
This error has been observed mostly when Gravity Sync is running on slower SD Cards or older Raspberry Pi systems, and where the backup of the running Domain Database takes longer than expected (or never finishes) and thus when Gravity Sync replicates that copy to the secondary, it's malformed.
Starting in version 3.4.2, Gravity Sync will perform an integrity check after replication that attempt to detect this problem before completing the replication. If you see the error `Integrity check has failed for the Domain Database` this is typically why.
The suggested workaround is to move the primary (or both) of the Pi-hole installations to a storage device with more available IOPS, the alternative is to increase the timeout of the backup process from the default (60 seconds) as documented in [Hidden Figures](https://github.com/vmstan/gravity-sync/wiki/Hidden-Figures#backup_timeout).