CNAME syncing not pushing properly, pull works

[blysik]

trafficstars

version 4.0.4, everything running properly, but DNS CNAMEs don't push:

∞ Initializing Gravity Sync (4.0.4)
✓ Loading gravity-sync.conf
✓ Detecting local Pi-hole installation
✓ Detecting remote Pi-hole installation
✓ Gravity Sync remote peer is configured
✓ Evaluating arguments: PUSH
» Remote target user@ip
✓ Validating pathways to Pi-hole
✓ Validating pathways to DNSMASQ
✓ Hashing the remote Gravity Database
✓ Comparing to the local Gravity Database
✓ Hashing the remote DNS Records
✓ Comparing to the local DNS Records
! DNS CNAMEs not detected on the remote Pi-hole
! Static DHCP Addresses not detected on the local Pi-hole
! No replication is required at this time
∞ Gravity Sync PUSH exited after 2 seconds

I manually added INCLUDE_CNAME to the conf:

# grep CNAME /etc/gravity-sync/gravity-sync.conf
INCLUDE_CNAME='1'

Everything else seems to sync fine. Ideas? Thanks.

[blysik]

On a whim, I tried a pull from the other host, and that actually worked:

# gravity-sync pull
∞ Initializing Gravity Sync (4.0.4)
✓ Loading gravity-sync.conf
✓ Detecting local Pi-hole installation
✓ Detecting remote Pi-hole installation
✓ Gravity Sync remote peer is configured
✓ Evaluating arguments: PULL
» Remote target user@ip
✓ Validating pathways to Pi-hole
✓ Validating pathways to DNSMASQ
✓ Hashing the remote Gravity Database
✓ Comparing to the local Gravity Database
✓ Hashing the remote DNS Records
✓ Comparing to the local DNS Records
! DNS CNAMEs has been detected on the remote Pi-hole
! DNS CNAMEs not detected on the local Pi-hole
! Static DHCP Addresses not detected on the local Pi-hole
! Replication of Pi-hole settings is required
✓ Performing backup of local Gravity Database
✓ Performing backup of remote Gravity Database
✓ Checking Gravity Database copy integrity
✓ Pulling the remote Gravity Database
✓ Replacing the local Gravity Database
✓ Setting file ownership on Gravity Database
✓ Setting file permissions on Gravity Database
✓ Performing backup of local DNS Records
✓ Performing backup of remote DNS Records
✓ Pulling the remote DNS Records
✓ Replacing the local DNS Records
✓ Setting file ownership on DNS Records
✓ Setting file permissions on DNS Records
! No local 05-pihole-custom-cname.conf detected
✓ Performing backup of remote DNS CNAMEs
✓ Pulling the remote DNS CNAMEs
✓ Replacing the local DNS CNAMEs
✓ Setting file ownership on DNS CNAMEs
✓ Setting file permissions on DNS CNAMEs
✓ Updating local FTLDNS configuration
✓ Reloading local FTLDNS services
› Performing replicator diagnostics
✓ Rehashing the remote Gravity Database
✓ Recomparing to local Gravity Database
✓ Rehashing the remote DNS Records
✓ Recomparing to local DNS Records
✓ Rehashing the remote DNS CNAMEs
✓ Recomparing to local DNS CNAMEs
! Static DHCP Addresses not detected on the local Pi-hole
✓ Saving updated data hashes
✓ Sending hashes to Gravity Sync peer
✓ Setting permissions on remote hashing files
✓ Logging successful PULL
∞ Gravity Sync PULL completed after 22 seconds

[brianroberg]

I observed the same behavior with static DHCP addresses: sync didn't work, but pull did. (I too am running version 4.0.4.)

[zAAmpie]

Can confirm on 4.0.4. Push host sees that CNAME is not in sync, but ignores it. Pull works fine. Quite a few possibilities, will take a stab a bit later - could be rsync, permissions, backup file etc.

[wblew]

This PR might contain a fix for this issue. https://github.com/vmstan/gravity-sync/pull/384

I haven't checked any further than reading its description.

[zAAmpie]

Ah, you're right. Missed it because the PR has multiple independent changes. That said, if it only happens on initial push, it should work eventually using smart sync.

[vmstan]

Effective July 26, 2024, this project has been retired. Thank you for your use and enthusiasm for a project that began as a few lines of bash in a Slack channel and envolved into something far more complex, and used by many thousands of Pi-hole enthusiasts over the last four years.