Brotpilot-921
commented
1 year ago I can repeat the same behavior. I have set up 2 fresh Debian 11 VMs, installed the latest Pihole(Today Pi-hole [v5.14.2], FTL [v5.19.2]and Web Interface [v5.17]) and latest Gravity sync (4.0.4). I have tried push and pull but non of both methods worked for me.
∞ 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 username@ip(of cause replaced) ✓ Validating pathways to Pi-hole ✓ Validating pathways to DNSMASQ ✓ Hashing the remote Gravity Database ✓ Comparing to the local Gravity Database ! Differences detected in the Gravity Database ✓ Hashing the remote DNS Records ✓ Comparing to the local DNS Records ! Differences detected in the DNS Records ! 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 remote Gravity Database ✓ Performing backup of local Gravity Database ✓ Checking Gravity Database copy integrity ✗ Pushing the local Gravity Database
vmstan
Fresh install of Gravity-Sync, first run of gravity-sync push Primary instance is running on a Raspberry Pi Zero running Raspberry Pi OS 11 bullseye secondary instance is running on an x86-64 PC running Debian bookworm I have done gravity-sync purge on both machines and started with a completely fresh install
System just hangs at this point and eventually times out
attempting to run gravity-sync pull on the secondary instance gives similar results
root@thindebian:/var/log/pihole# 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 john@192.168.1.3 ✓ Validating pathways to Pi-hole ✓ Validating pathways to DNSMASQ ✓ Hashing the remote Gravity Database ✓ Comparing to the local Gravity Database ! Differences detected in the Gravity Database ✓ Hashing the remote DNS Records ✓ Comparing to the local DNS Records ! Differences detected in the DNS Records ✓ Hashing the remote DNS CNAMEs ✓ Comparing to the local DNS CNAMEs ! Differences detected in the DNS CNAMEs ! 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
and gravity-sync hangs at this point again, and eventually times out. There doesn't seem to be any logging enabled in gravity-sync, so I can't tell for certain, but I expect rsync is failing somehow
Rsync version info on the secondary instance (Debian Bookworm) is: rsync version 3.2.6 protocol version 31 Copyright (C) 1996-2022 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, symlinks, symtimes, hardlinks, hardlink-specials, hardlink-symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional secluded-args, iconv, prealloc, stop-at, no crtimes Optimizations: SIMD-roll, no asm-roll, openssl-crypto, no asm-MD5 Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none
Rsync version info on the Pi (Raspbian Bullseye) is rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: no SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none