Pihole v6 update seems to break my install

Rudig · February 16, 2024, 6:19pm

As suggested in other topic after breaking my v6 install I tried to run

/usr/bin/pihole-FTL —teleporter

Expect a backup to be created, which is indeed created as a zip file

But also receive the error

dns.revServer DOES NOT EXIST

What does it mean and how can I correct this?

rdwebdesign · February 16, 2024, 6:33pm

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

Rudig · February 17, 2024, 12:39pm

https://tricorder.pi-hole.net/ScIXnS6a/

DL6ER · February 17, 2024, 3:16pm

Was this really shown as an error to you? This log line might be created during internal config file migration but should only have significance INFO. I will open a PR that moves this into DEBUG realm as there is no issue at all with this message. It simply means your config wasn't old - meaning it didn't need migration.

Indeed, dns,revServer (one setting) became dns.revServers (an array) to support multiple conditional forwarding servers.

DL6ER · February 17, 2024, 3:28pm

github.com/pi-hole/FTL

Improve config migration logging

pi-hole:development-v6 ← pi-hole:fix/migration_message

opened 03:27PM - 17 Feb 24 UTC

DL6ER

+35 -6

# What does this implement/fix? **No functional change** This PR addresses a …message which unnecessarily concerned a user in [the related Discourse thread](https://discourse.pi-hole.net/t/pihole-v6-update-seems-to-break-my-install/68376). We solve this by not logging this message unless `debug.config = true` is explicitly set. There is no issue at all when this message appears. It simply means the config wasn't old - as the old item wasn't there, it didn't need migration. While I was at it, I expanded the comments around this code to make clear what the code does and why it may reach one or the other place. --- **Related issue or feature (if applicable):** see link above **Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) ## Checklist: - [x] The code change is tested and works locally. - [x] I based my code and PRs against the repositories `developmental` branch. - [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions - [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship - [x] I have read the above and my PR is ready for review.

Rudig · February 17, 2024, 3:47pm

Yep this line was shown and after that the line that backup was created

And the script which was run has the following command

DL6ER · February 17, 2024, 4:28pm

Yeah, that's fine. There's absolutely no issue here, the PR I linked above will silence this.

system · March 9, 2024, 4:28pm

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.