Updated Troubleshooting (markdown)

Michael Stanclift 2021-04-05 17:25:04 -05:00
parent bc7a2246bb
commit d17e35324e

@ -23,4 +23,4 @@ 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. 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.
The suggested workaround is to move at least 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). 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).