I can't reach the Pi-hole v6 web interface

DL6ER · February 8, 2025, 2:04pm

This was more a precaution command, as these files might have the restart from working.

Glad it worked for you. The Tricorder logs shows quite many successful restarts of pihole-FTL after the migration, it happened later. I am now able to reproduce this.

The problem is that FTL detects any other FTL instances from running - as designed. However, this may also be a long-lived interactive process like

pihole-FTL sqlite3

As long as this is open, any further restarts are not possible. We'll get this fixed!

DL6ER · February 8, 2025, 6:36pm

github.com/pi-hole/FTL

Allow parallel FTL processes

development ← tweak/process_parallelism

opened 06:24PM - 08 Feb 25 UTC

DL6ER

+108 -42

# What does this implement/fix? So far, FTL tried to prevent multiple process…es from being started on the same machine. However, as the `pihole-FTL` binary became kind of a Swiss-army-knife offering integrated features such as `sqlite3`, `sqlite3_rsync`, `sha256sum`, `gzip`, `lua`, `dhcp-discover`, and others (like a small TLS certificate managing toolset), it becomes more and more likely that there are long-lived interactive `pihole-FTL` instances on the machine. They may coexist without any issues, however, once such an interactive process is running, restarting the original `pihole-FTL` may be prevented under certain circumstances. Hence, I propose going a different, much easier path: Allow parallel processes to coexist peacefully much like most other daemons do. Duplicate processes will in the end not be able to fully start up as they cannot acquire the DNS and webserver ports. However, the currently possible situation of not being able to restart the *main* DNS-providing process is resolved hereby. We allow the new parallelism by ensuring uniqueness of the shard memory objects by changing their name to include the main PID of each FTL process, e.g., `FTL-34532-clients` instead of (right now) the shorter `FTL-clients`. No change to the `post-stop` command is needed as the deletion glob still matches the tweaked names: ![Screenshot from 2025-02-08 18-39-40](https://github.com/user-attachments/assets/1fbdd38c-b1c0-42c5-b4f9-74f9ededcbd4) --- **Related issue or feature (if applicable):** N/A **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.

nero355 · February 9, 2025, 12:25am

COOL!!!

Thank you for helping out!
I will make sure to remember the command for future use in case something similar happens and report back to you guys ofcourse!

Pi-Hole is my favorite piece of software for quite some time now : I am guessing between 6 and 8 years or so

Big THANK YOU to all the Developers involved who made that possible and I hope the development will continue for many years to come !!!

I can't live without this beautiful project anymore!

yubiuser · February 18, 2025, 9:16pm

A post was split to a new topic: Web interface not accessible after v6 upgrade

yubiuser · February 20, 2025, 10:44pm

A post was split to a new topic: Web interface not accessible after v6 upgrade

yubiuser · February 22, 2025, 9:51pm

A post was split to a new topic: V6 web interface not reachable