You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed gravity-sync v4 on my pihole container and on my pihole on Raspberry Pi. Install is working. manual sync is working flawlessly. gravity-sync auto works fine when I run it on the Pi, but errors out when I run it on the pihole container. Here are the errors:
root@pihole-nas:~# gravity-sync auto
∞ Initializing Gravity Sync (4.0.5)
✓ Loading gravity-sync.conf
✓ Detecting local Pi-hole installation
✓ Detecting remote Pi-hole installation
✓ Gravity Sync remote peer is configured
✓ Evaluating arguments: AUTOMATE
✓ Customizing service file username
✓ Customizing service file executable path
✓ Randomizing service timers
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
✓ Moving systemd timer into place
✓ Moving systemd service into place
∞ Reloading systemd daemonSystem has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
✗ Reloading systemd daemon
The text was updated successfully, but these errors were encountered:
I have installed gravity-sync v4 on my pihole container and on my pihole on Raspberry Pi. Install is working. manual sync is working flawlessly. gravity-sync auto works fine when I run it on the Pi, but errors out when I run it on the pihole container. Here are the errors:
root@pihole-nas:~# gravity-sync auto
∞ Initializing Gravity Sync (4.0.5)
✓ Loading gravity-sync.conf
✓ Detecting local Pi-hole installation
✓ Detecting remote Pi-hole installation
✓ Gravity Sync remote peer is configured
✓ Evaluating arguments: AUTOMATE
✓ Customizing service file username
✓ Customizing service file executable path
✓ Randomizing service timers
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
✓ Moving systemd timer into place
✓ Moving systemd service into place
∞ Reloading systemd daemonSystem has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
✗ Reloading systemd daemon
The text was updated successfully, but these errors were encountered: