[✗] Updating FTLDNS Configuration

[nicedevil007]

As shown in the last Issue where the pihole wasn't deleting old backups I told that the FTLDNS seems to be broken on my site.

So both piholes run in a docker environment. The main one is a docker-compose.yml and the 2nd one is docker swarm.
So I used this for installation of your script:

[>] Starting Gravity Sync Configuration
========================================================
[∞] Gravity Sync 3.2.6 Executing
[✓] Evaluating Arguments: CONFIGURE Requested
[✓] Creating New gravity-sync.conf from Template
[i] Advanced Configuration Required
[?] Local Pi-hole in Docker Container? (Leave blank for default 'No'): yes
[✓] Saving Local Docker Setting to gravity-sync.conf
[?] Local Docker Container Name? (Leave blank for default 'pihole'): $(docker ps -qf name=pihole)
[✓] Saving Local Container Name to gravity-sync.conf
[?] Local Pi-hole 'etc' Volume Path? (Required, no trailing slash): /var/lib/docker/volumes/pihole_etc/_data
[✓] Saving Local Pi-hole Volume to gravity-sync.conf
[?] Local DNSMASQ 'etc' Volume Path? (Required, no trailing slash): /var/lib/docker/volumes/pihole_dnsmasq/_data
[✓] Saving Local DNSMASQ Volume to gravity-sync.conf
[✓] Saving Local Volume Ownership to gravity-sync.conf
[?] Remote Pi-hole in Docker Container? (Leave blank for default 'No'): yes
[✓] Saving Remote Docker Setting to gravity-sync.conf
[?] Remote Docker Container Name? (Leave blank for default 'pihole'): $(docker ps -qf name=pihole)
[✓] Saving Remote Container Name to gravity-sync.conf
[?] Remote Pi-hole 'etc' Volume Path? (Required, no trailing slash): /var/lib/docker/volumes/pihole_etc/_data
[✓] Saving Remote Pi-hole Volume to gravity-sync.conf
[?] Remote DNSMASQ 'etc' Volume Path? (Required, no trailing slash): /var/lib/docker/volumes/pihole_dnsmasq/_data
[✓] Saving Remote DNSMASQ Volume to gravity-sync.conf
[✓] Saving Remote Volume Ownership to gravity-sync.conf
[?] Use Custom SSH Port? (Leave blank for default '22'):
[?] Enable ICMP Check? (Leave blank for default 'Yes'):
[?] Use Custom SSH PKIF Location? (Leave blank for default '.ssh/id_rsa'):
[?] Enable Replicate 'Local DNS Records' Feature? (Leave blank for default 'Yes'):
[?] Enable Replicate 'Local CNAME Records' Feature? (Leave blank for default 'Yes'):
[✓] Saving Local CNAME Preference to gravity-sync.conf
[?] Change Backup Retention in Days? (Leave blank for default '7'): 1
[✓] Saving Backup Retention to gravity-sync.conf
[i] Standard Settings
[?] Primary Pi-hole Address (IP or DNS): 192.168.188.254
[✓] Testing Network Connection (ICMP)
[?] SSH User for 192.168.188.254: root
[✓] Saving Host to gravity-sync.conf
[✓] Saving User to gravity-sync.conf
[i] Using Existing ~/.ssh/id_rsa
[✓] Importing New gravity-sync.conf
[i] Registering Key-Pair on 192.168.188.254
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh -p '22' 'root@192.168.188.254'"
and check to make sure that only the key(s) you wanted were added.

Maybe I did something wrong here?

The initial compare command returns this:

[root@cloud-03 gravity-sync]# ./gravity-sync.sh compare
[∞] Gravity Sync 3.2.6 Executing
[✓] Importing gravity-sync.conf Settings
[✓] Evaluating Arguments: COMPARE Requested
[i] Targeting root@192.168.188.254
[✓] Validating SSH Client on cloud-03 (OpenSSH)
[✓] Validating RSYNC Installed on cloud-03
[✓] Validating Gravity Sync Folders on cloud-03
[✓] Validating Pi-hole Configuration
[✓] Validating DNSMASQ Configuration
[✓] Validating Connection to 192.168.188.254
[✓] Analyzing gravity.db on 192.168.188.254
[✓] Analyzing gravity.db on cloud-03
[!] Differenced gravity.db Detected
[✓] Analyzing custom.list on 192.168.188.254
[✓] Analyzing custom.list on cloud-03
[!] Differenced custom.list Detected
[i] No 05-pihole-custom-cname.conf Detected on cloud-03
[!] Replication Required
[e] Scrubbing 1 Redundant Antimatter Containment Podsfind: ‘/root/gravity-sync/backup/2021*.backup’: No such file or directory
[✗] Scrubbing 1 Redundant Antimatter Containment Pods

And then I tested a pull command again with this result:

[root@cloud-03 gravity-sync]# ./gravity-sync.sh pull
[∞] Gravity Sync 3.2.6 Executing
[✓] Importing gravity-sync.conf Settings
[✓] Evaluating Arguments: PULL Requested
[i] Targeting root@192.168.188.254
[✓] Validating SSH Client on cloud-03 (OpenSSH)
[✓] Validating RSYNC Installed on cloud-03
[✓] Validating Gravity Sync Folders on cloud-03
[✓] Validating Pi-hole Configuration
[✓] Validating DNSMASQ Configuration
[✓] Validating SQLITE Installed on cloud-03
[✓] Validating Connection to 192.168.188.254
[✓] Analyzing gravity.db on 192.168.188.254
[✓] Analyzing gravity.db on cloud-03
[!] Differenced gravity.db Detected
[✓] Analyzing custom.list on 192.168.188.254
[✓] Analyzing custom.list on cloud-03
[!] Differenced custom.list Detected
[i] No 05-pihole-custom-cname.conf Detected on cloud-03
[!] Replication Required
[✓] Performing Backup of Local gravity.db
[✓] Performing Backup of Remote gravity.db
[✓] Pulling gravity.db from 192.168.188.254
[✓] Replacing gravity.db on cloud-03
[✗] Validating Ownership on gravity.db
[!] Attempting to Compensate
[✓] Setting Ownership on gravity.db
[✓] Continuing Validation of gravity.db
[✓] Performing Backup Up Local custom.list
[✓] Performing Backup of Remote custom.list
[✓] Pulling custom.list from 192.168.188.254
[✓] Replacing custom.list on cloud-03
[✓] Validating Settings on custom.list
[i] Isolating Regeneration Pathways
[✗] Updating FTLDNS Configuration