summaryrefslogtreecommitdiffstats
path: root/health/guides/pihole
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-05-05 11:19:16 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-05-05 12:07:37 +0000
commitb485aab7e71c1625cfc27e0f92c9509f42378458 (patch)
treeae9abe108601079d1679194de237c9a435ae5b55 /health/guides/pihole
parentAdding upstream version 1.44.3. (diff)
downloadnetdata-b485aab7e71c1625cfc27e0f92c9509f42378458.tar.xz
netdata-b485aab7e71c1625cfc27e0f92c9509f42378458.zip
Adding upstream version 1.45.3+dfsg.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'health/guides/pihole')
-rw-r--r--health/guides/pihole/pihole_blocklist_last_update.md55
-rw-r--r--health/guides/pihole/pihole_status.md54
2 files changed, 0 insertions, 109 deletions
diff --git a/health/guides/pihole/pihole_blocklist_last_update.md b/health/guides/pihole/pihole_blocklist_last_update.md
deleted file mode 100644
index d358e04ce..000000000
--- a/health/guides/pihole/pihole_blocklist_last_update.md
+++ /dev/null
@@ -1,55 +0,0 @@
-### Understand the alert
-
-This alert indicates that the Pi-hole blocklist (Gravity) file hasn't been updated for an extended period of time. The blocklist file contains domains that have been processed by Pi-hole to filter ads and malicious content. An outdated blocklist may leave your system more vulnerable to unwanted content and threats.
-
-### Troubleshoot the alert
-
-1. **Check the current blocklist update status**
-
- To see how long it has been since the last update, you can use the following command:
-
- ```
- root@netdata~ # pihole -q -adlist
- ```
-
- This will display the timestamp of the last update.
-
-2. **Rebuild the blocklist**
-
- If the alert indicates that your blocklist file is outdated, it's essential to update it by running:
-
- ```
- root@netdata~ # pihole -g
- ```
-
- This command will download the necessary files and rebuild the blocklist.
-
-3. **Check for errors during the update**
-
- If you encounter any issues during the update, check the `/var/log/pihole.log` file for errors. You can also check the `/var/log/pihole-FTL.log` file for more detailed information on the update process.
-
-4. **Verify the blocklist update interval**
-
- To ensure that your blocklist file is updated regularly, make sure you configure a regular update interval. You can do this by editing the `cron` job for Pi-hole:
-
- ```
- root@netdata~ # crontab -e
- ```
-
- This will open an editor. Look for the line containing the `pihole -g` command and adjust the schedule accordingly. For example, to update the blocklist daily, add the following line:
-
- ```
- 0 0 * * * /usr/local/bin/pihole -g
- ```
-
- Save the file and exit the editor to apply the changes.
-
-5. **Monitor the blocklist update status**
-
- After performing the necessary troubleshooting steps, keep an eye on the `pihole_blocklist_last_update` alert to ensure that your blocklist file is updated as expected.
-
-### Useful resources
-
-1. [Pi-hole Blocklists](https://docs.pi-hole.net/database/gravity/)
-2. [Rebuilding the Blocklist](https://docs.pi-hole.net/ftldns/blockingmode/)
-3. [Pi-hole Documentation](https://docs.pi-hole.net/) \ No newline at end of file
diff --git a/health/guides/pihole/pihole_status.md b/health/guides/pihole/pihole_status.md
deleted file mode 100644
index 57dd203f4..000000000
--- a/health/guides/pihole/pihole_status.md
+++ /dev/null
@@ -1,54 +0,0 @@
-### Understand the alert
-
-This alert monitors if Pi-hole's ability of blocking unwanted domains is active. If you receive this alert, it means that your Pi-hole's ad filtering is currently disabled.
-
-### Troubleshoot the alert
-
-1. Check the status of Pi-hole
-
-To check the current status of Pi-hole, run the following command:
-```
-pihole status
-```
-This command will show if Pi-hole is active or disabled.
-
-2. Re-enable Pi-hole
-
-If Pi-hole is disabled as per the status, you can re-enable it by running the following command:
-
-```
-pihole enable
-```
-
-3. Confirm Pi-hole is enabled
-
-After running the previous command, run `pihole status` again to confirm that Pi-hole is now enabled and blocking unwanted domains.
-
-4. Check for errors or warnings
-
-If Pi-hole is still not enabled, take a look at the logs for any errors or warnings:
-
-```
-cat /var/log/pihole.log | grep -i error
-cat /var/log/pihole.log | grep -i warning
-```
-
-5. Rebuild the blocklist
-
-If you still face issues, you can try rebuilding the blocklist by running:
-
-```
-pihole -g
-```
-
-6. Update Pi-hole
-
-If the problem persists, consider updating Pi-hole to the latest version:
-
-```
-pihole -up
-```
-
-### Useful resources
-
-1. [Pi-hole Official Documentation](https://docs.pi-hole.net/)