Invalid configuration dnsmasq: syntax check OK.

erotikbaer · January 3, 2025, 6:28pm

I have problems with my PiHole v6. I try to start the DHCP server (after moving from an RPi to Proxmox) and always get the message: “ Invalid configuration
dnsmasq: syntax check OK.”. also importing the configuration via teleporter gave the same error.
I have taken over the pihole.toml from the old Pihole. the DHCP starts without problems on the old Pi, but not on the new Proxmox Pihole. Of course I deactivated the old Pi beforehand.

I see the following messages in the ftl.log:

“2025-01-03 17:55:34.688 ERROR Error NTP client: Failed to adjust time during NTP sync: Insufficient permissions
2025-01-03 17:56:22.732 ERROR Cannot wait for dnsmasq test: No child process
2025-01-03 17:56:22.732 ERROR dnsmasq test failed with signal 4
2025-01-03 17:56:22.733 WARNING New dnsmasq configuration is not valid (dnsmasq: syntax check OK.), config remains unchanged
2025-01-03 17:56:22.733 WARNING API: Invalid configuration (dnsmasq: syntax check OK.)”

Translated with DeepL.com (free version)```

yubiuser · January 3, 2025, 6:30pm

This might be a bug that has been fixed 12 hours ago.

github.com/pi-hole/FTL

Harden dnsmasq syntax checking against signals

pi-hole:development ← pi-hole:fix/dnsmasq_test_signal

opened 06:45PM - 02 Jan 25 UTC

DL6ER

+18 -3

# What does this implement/fix? Retry to wait for result of dnsmasq syntax te…st if interrupted by a signal --- **Related issue or feature (if applicable):** #2149 **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.

Please run pihole -up and see if the issue persists.

erotikbaer · January 3, 2025, 6:49pm

` [i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date

[✓] Everything is up to date!`

the error persits

yubiuser · January 3, 2025, 7:04pm

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