Replies: 3 comments
-
Sorry, wanted to at least respond to show I looked at this but I did a little looking around and was unable to figure out what may be causing this. It seems to be a Pi-hole issue, but I have no idea why using the teleporter would trigger it. I would try replicating it yourself by using the teleporter (perform backup in the admin UI on the primary and restore in the admin UI on the secondary) and if you experience the same issue, try creating an issue with Pi-hole. |
Beta Was this translation helpful? Give feedback.
-
Yeah, I think you may have been right. I tried what you suggested (restoring backup from the primary on the secondary via teleporter) and I got this error:
Which also caused the pihole-FTL.service to fail with the same error message. I will reach out to the folks at Pi-hole directly then to see what may be causing this issue. Thanks! |
Beta Was this translation helpful? Give feedback.
-
simple set SYNC_LOCALDNSRECORDS and SYNC_LOCALCNAMERECORDS to false. |
Beta Was this translation helpful? Give feedback.
-
Hi.
So today I installed orbital-sync in docker, but ran into an issue when trying to run the service. Well, the first time it ran, it worked fine, but subsequent runs always fail. It fails at updating gravity on the secondary pi-hole instance. I enabled verbose mode, and here's what I get:
It does this every time it runs now. When this happens it makes the pihole-FTL.service in the secondary pihole fail with these messages:
After this happens, I have to manually restart the pihole-FTL service for it to work again. Unfortunately I can't make use of orbital-sync with this issue. Any ideas what could be causing this?
Beta Was this translation helpful? Give feedback.
All reactions