Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-07-07 10:14:04 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated Troubleshooting (markdown)

Michael Stanclift 2022-04-11 17:04:20 -05:00
parent 6e0c8dd66f
commit 650bf64812
1 changed files with 6 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Troubleshooting.md

@ -1,19 +1,12 @@
In addition to any known issues outlined here, please review the [GitHub Issues](https://github.com/vmstan/gravity-sync/issues) page for real time user submitted bugs, enhancements or active/past discussions.
In addition to any known issues outlined here, please review the [GitHub Issues](https://github.com/vmstan/gravity-sync/issues) page for real time user submitted bugs, enhancements or past issue discussions not documented here.
### Updater Issues
If the built in updater doesn't function as expected, you can manually run the git commands that operate under the covers.
```bash
git fetch --all
git reset --hard origin/master
```
If your code is still not updating after this, reinstallation is suggested rather than spending all your time troubleshooting `git` commands.
If the built in updater doesn't function as expected, you can reinstall Gravity Sync using the single line installer. This will make sure you have the latest copy. Your existing configuration file will not be impacted.
### sudo: no tty present
If you get the error `sudo: a terminal is required to read the password` or `sudo: no tty present and no askpass program specified` during your execution, make sure you have [implemented passwordless sudo](https://linuxize.com/post/how-to-run-sudo-command-without-password/), as defined in the system requirements, for the user accounts on both the local and remote systems.
If you get the error `sudo: a terminal is required to read the password` or `sudo: no tty present and no askpass program specified` during your execution, make sure you have [implemented password-less sudo](https://linuxize.com/post/how-to-run-sudo-command-without-password/), as defined in the system requirements, for the user accounts on both the local and remote systems.
### unrecognized option: preserve-status
@ -21,8 +14,8 @@ Some minimalist Linux distributions (such as Alpine Linux) use an older version
### Database disk image is 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.
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 Gravity Database takes longer than expected (or never finishes) and thus when Gravity Sync replicates that copy to the peer, 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.
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 Gravity 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).
The suggested workaround is to move your Pi-hole installations to storage devices with more available IOPS.