-
-
Notifications
You must be signed in to change notification settings - Fork 130
Troubleshooting
In addition to any known issues outlined here, please review the GitHub Issues page for real time user submitted bugs, enhancements or past issue discussions not documented here.
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.
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 installed Gravity Sync on both systems. This will have implemented password-less sudo, as defined in the system requirements, for the user accounts on both the local and remote systems.
Some minimalist Linux distributions (such as Alpine Linux) use an older version of Busybox, which misses the --preserve-status option on the timeout command. You can either update to a newer version of Busybox, or you can install the coreutils package in Alpine Linux, which includes a version of timeout which has --preserve-status implemented.
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.
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 your Pi-hole installations to storage devices with more available IOPS.