Don't get ansible installed

[soharddbwarez]

This is what I see when I want to install ansible on my Raspberry Pi 3, and yes I commented out and uncommented the right file and changed the ip address to my pi and still nothing.
I'm also logged in over SSL and have it installed but it tells me that the module in python isn't available, I don't get what's going wrong.

pip3 install ansible

Defaulting to user installation because normal site-packages is not writeable
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
Could not fetch URL https://pypi.org/simple/ansible/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/ansible/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ansible/
Could not fetch URL https://www.piwheels.org/simple/ansible/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='www.piwheels.org', port=443): Max retries exceeded with url: /simple/ansible/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
ERROR: Could not find a version that satisfies the requirement ansible (from versions: none)
ERROR: No matching distribution found for ansible
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
Could not fetch URL https://www.piwheels.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='www.piwheels.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping

[geerlingguy]

This seems to be an issue where the Python version you have installed on your Pi might not be set up correctly or may be missing something. Did you install Python 3 using sudo apt-get install -y python3-pip or did you install some other way? Can you do which python3 and python3 --version? And is this a fresh new install of Raspberry Pi OS or something else?

[soharddbwarez]

which pyton3 gives me - /usr/local/bin/python3
python3 --version gives me 3.9.0
I'm not sure how I installed python3 onto my raspberry pi, what I can tell you is that I had it already installed before you could install it the usual way using apt, I downloaded it from the website and installed it from within the downloaded python directory.
What do you suggest? I'm not even sure if I can uninstall python3 without breaking the Raspberry Pi OS and if I can prevent doing a complete fresh system install I rather do that. I have a lot of customizations running that would take me a lot of time if I have to do all that again.

[yxchiwork]

It's probably issue with your SSL certificate. The connection from your pi to piwheels/pypi/.etc is broken because of that. You need to fix that first before retrying. You should also have issue installing other stuff using pip.

[soharddbwarez]

Guess what happened... I figured if it's a python issue just try to reinstall python right? Well, I shouldn't have done that because when I did purge python3 it broke my whole system, it's kinda funny now, I can laugh about it so I'm ok.
I'm giving it another try right now to see how far I come with a fresh clean install of the latest Raspberry Pi OS, I hope it will work but I'm not sure so I'll come back to you if I'm getting stuck again.

[yxchiwork]

Hahahah, you don’t have to reinstall, you can just install another version and link the python3 command to it.

[soharddbwarez]

So, I have some news... Here's what happened, I did step 1, python tells me I already have the latest version installed, then I did the "Everywhere" step to install ansible which was successful and then I did step 3 and got the following error:

Installing collected packages: packaging, resolvelib, ansible-core, ansible
Successfully installed ansible-4.2.0 ansible-core-2.11.2 packaging-20.9 resolvelib-0.5.5
pi@raspberrypi:~ $ ansible-galaxy collection install -r requirements.yml
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with
Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature
will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
ERROR! The requirements file '/home/pi/requirements.yml' does not exist.
pi@raspberrypi:~ $ ansible-galaxy collection install -r requirements.yml
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with
Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature
will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
Starting galaxy collection install process
Process install dependency map
Starting collection install process
Downloading https://galaxy.ansible.com/download/ansible-posix-1.2.0.tar.gz to /home/pi/.ansible/tmp/ansible-local-299338d5mhgwv/tmpgrldn5fc/ansible-posix-1.2.0-20au9qq2
Installing 'ansible.posix:1.2.0' to '/home/pi/.ansible/collections/ansible_collections/ansible/posix'
Downloading https://galaxy.ansible.com/download/community-docker-1.8.0.tar.gz to /home/pi/.ansible/tmp/ansible-local-299338d5mhgwv/tmpgrldn5fc/community-docker-1.8.0-iyt2770r
ansible.posix:1.2.0 was installed successfully
Installing 'community.docker:1.8.0' to '/home/pi/.ansible/collections/ansible_collections/community/docker'
community.docker:1.8.0 was installed successfully

Then I tried to do the playbook and this happened:

pi@raspberrypi:~ $ ansible-playbook main.yml
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with
Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature
will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
ERROR! the playbook: main.yml could not be found

So, now I don't know where it is installed, I can't find the main.yml file anywhere in the directories provided in the error messages. So I'm stuck again.

[yxchiwork]

You need to git clone this repository, and there will be a folder called internet-pi, main.yml is in it. Follow the steps on this repo. Ricardo ***@***.***>于2021年7月1日 周四下午6:21写道：

So, I have some news... Here's what happened, I did step 1, python tells me I already have the latest version installed, then I did the "Everywhere" step to install ansible which was successful and then I did step 3 and got the following error: Installing collected packages: packaging, resolvelib, ansible-core, ansible Successfully installed ansible-4.2.0 ansible-core-2.11.2 packaging-20.9 resolvelib-0.5.5 ***@***.***:~ $ ansible-galaxy collection install -r requirements.yml [DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. ERROR! The requirements file '/home/pi/requirements.yml' does not exist. ***@***.***:~ $ ansible-galaxy collection install -r requirements.yml [DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. Starting galaxy collection install process Process install dependency map Starting collection install process Downloading https://galaxy.ansible.com/download/ansible-posix-1.2.0.tar.gz to /home/pi/.ansible/tmp/ansible-local-299338d5mhgwv/tmpgrldn5fc/ansible-posix-1.2.0-20au9qq2 Installing 'ansible.posix:1.2.0' to '/home/pi/.ansible/collections/ansible_collections/ansible/posix' Downloading https://galaxy.ansible.com/download/community-docker-1.8.0.tar.gz to /home/pi/.ansible/tmp/ansible-local-299338d5mhgwv/tmpgrldn5fc/community-docker-1.8.0-iyt2770r ansible.posix:1.2.0 was installed successfully Installing 'community.docker:1.8.0' to '/home/pi/.ansible/collections/ansible_collections/community/docker' community.docker:1.8.0 was installed successfully Then I tried to do the playbook and this happened: ***@***.***:~ $ ansible-playbook main.yml [DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. ERROR! the playbook: main.yml could not be found So, now I don't know where it is installed, I can't find the main.yml file anywhere in the directories provided in the error messages. So I'm stuck again. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#100 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANJJ4VDLCSIPI2GYN5VZO73TVTZ53ANCNFSM47SKWPBA> .

-- Regards Yuxiang Chi

[soharddbwarez]

You need to git clone this repository, and there will be a folder called internet-pi, main.yml is in it. Follow the steps on this repo. Ricardo @.>于2021年7月1日 周四下午6:21写道：
So, I have some news... Here's what happened, I did step 1, python tells me I already have the latest version installed, then I did the "Everywhere" step to install ansible which was successful and then I did step 3 and got the following error: Installing collected packages: packaging, resolvelib, ansible-core, ansible Successfully installed ansible-4.2.0 ansible-core-2.11.2 packaging-20.9 resolvelib-0.5.5 @.:~ $ ansible-galaxy collection install -r requirements.yml [DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. ERROR! The requirements file '/home/pi/requirements.yml' does not exist. @.:~ $ ansible-galaxy collection install -r requirements.yml [DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. Starting galaxy collection install process Process install dependency map Starting collection install process Downloading https://galaxy.ansible.com/download/ansible-posix-1.2.0.tar.gz to /home/pi/.ansible/tmp/ansible-local-299338d5mhgwv/tmpgrldn5fc/ansible-posix-1.2.0-20au9qq2 Installing 'ansible.posix:1.2.0' to '/home/pi/.ansible/collections/ansible_collections/ansible/posix' Downloading https://galaxy.ansible.com/download/community-docker-1.8.0.tar.gz to /home/pi/.ansible/tmp/ansible-local-299338d5mhgwv/tmpgrldn5fc/community-docker-1.8.0-iyt2770r ansible.posix:1.2.0 was installed successfully Installing 'community.docker:1.8.0' to '/home/pi/.ansible/collections/ansible_collections/community/docker' community.docker:1.8.0 was installed successfully Then I tried to do the playbook and this happened: @.:~ $ ansible-playbook main.yml [DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. ERROR! the playbook: main.yml could not be found So, now I don't know where it is installed, I can't find the main.yml file anywhere in the directories provided in the error messages. So I'm stuck again. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#100 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANJJ4VDLCSIPI2GYN5VZO73TVTZ53ANCNFSM47SKWPBA .
-- Regards Yuxiang Chi

Thank you very much, I copied the directory to my pi and started the command again from within the directory and now it is installing.

I do get the python 3.8 requirement warning still, is there a way to get the latest python version installed in an easy way?

I'll see how far I come now and when I have more questions I'll come back here.

[yxchiwork]

The warning is fine. You can follow some instructions to download the source code and make install it. But it is not something you are looking for. In short, Python 3.7 is good enough for now. Or you can try to install something like Anaconda, it comes with python 3.8.

[soharddbwarez]

It's Working!

The warning is fine. You can follow some instructions to download the source code and make install it. But it is not something you are looking for. In short, Python 3.7 is good enough for now. Or you can try to install something like Anaconda, it comes with python 3.8.

Okay thanks, I'll leave it be and keep using Python 3.7

Good news by the way, I already had the zip file downloaded to my main pc so I copied it to my Pi, then I tried the playbook again and got the expected error which is mentioned in the readme so I did a reboot and started over new and this time everything got installed the right way and it is working.

Now when I open my internet browser on my main computer and go to the Pi's IP address I see the Pi-Hole page and I can login with the password that I changed in the config.yml file so that is working alright, however I made a booboo by forgetting to change the internet monitoring configuration password, is there a way to change that afterwards?

I'm pretty happy that I got it installed and it's now working at least.

[yxchiwork]

you should be able to change it any time.

[geerlingguy]

@soharddbwarez - For Grafana (the monitoring UI), the password in config.yml only affects first install. If you want to change that password, log into Grafana with the default (admin/admin) then go into the account password update in the UI and change it there.

[soharddbwarez]

So Grafana stopped working and it was hogging all the resources from my Pi, it was so bad that I had to disable pi-hole and return back to my router for the DNS server to be able to get online.

I don't know what happened but I can't get the grafana page to open up anymore and I don't know how to get it restarted or whatever I need to do to get it working again, I've tried to run the playbook again to reinstall the whole thing but I get a warning that I already have an instance of grafana running and I don't know how to shut it down and the installation basically failed on that part so now I can't use anything anymore, I don't trust to set pi-hole as the DNS server as long as grafana isn't running as it should.

What should I do now to fix it?

[soharddbwarez]

Never mind for the last post, it's working again.

Even though I got the warning I got it fixed, I found the readme file in the internet monitoring folder and I did the Quick start command: docker-compose up -d
That removed grafana-1 and made me a new one and now I can login from my main computer again with the internet browser using the IP address and port.

I also changed the Raspberry Pi config to use less graphic memory since I don't do anything that needs a lot of graphical memory anyway. Changed it from 256MB to 96MB.

[soharddbwarez]

One question remains: How do I get the latest version of grafana installed?
At the bottom of the grafana login page it says "There's a new version available"
Can I simply follow the instructions on the grafana website or do I need to do something completely different?
Well, that's two questions but it's about the same thing.
Best regards,
Ricardo Penders

[soharddbwarez]

I need help!

Man, I can't get a break...

I figured out how to get grafana and also all the other stuff that comes installed when running your ansible playbook updated to the latest versions, turns out that it updates everything at once with just one simple command I just need to be located in the right directory... Duh...

Also in the meanwhile I was tinkering with overclocking my Pi and I now found the right settings to keep running it stable and it never throttles down, not even when running a benchmark, temperatures do not get higher than about 51.5 degree Celsius.
Here's a chart with results of running stressberry with the overclocked settings:

Because of that and some other maintenance I had to reboot my Pi a bunch of times and every time that I reboot grafana just stops working... When I try to load the grafana dashboard in my browser, either on my main computer or on the Pi itself I get the message that the connection is refused and can't load the page anymore.

The problem has gotten worse now because all the tricks that I used before, including running the playbook again and docker-compose up -d, I just can't get that stupid page to load anymore and I know that grafana and all that is running fine in the background because I can see the processes in Htop.

So I can't get it figured out from this point, I'm out of tricks that I know and worked before so I can really use some guidance to resolve the issue that I'm having only with grafana but it's persistent and annoying that I don't know what to do about it.

[geerlingguy]

Can you run docker ps -a and confirm Grafana's container is running well? And docker stats to see how much memory/CPU it's using? And docker logs [grafana container ID here] using the container ID listed with docker ps to see the logs?

[soharddbwarez]

docker ps -a revealed that the Grafana container is running ok

docker stats revealed that it's using less than 1% CPU and 0% memory but the latter is showing for everything so I don't know what's up with that.
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
cd0a2362f965 internet-monitoring_grafana_1 12.81% 0B / 0B 0.00% 6.39kB / 3.12kB 0B / 0B 9
fd4b7ddf82d2 internet-monitoring_prometheus_1 3.41% 0B / 0B 0.00% 220MB / 36.8MB 0B / 0B 12
8b7990f471de internet-monitoring_speedtest_1 0.02% 0B / 0B 0.00% 15.3MB / 257kB 0B / 0B 5
786c9c6e60a1 internet-monitoring_nodeexp_1 0.00% 0B / 0B 0.00% 21.4MB / 138MB 0B / 0B 15
27809a42494c pihole 0.18% 0B / 0B 0.00% 46.7MB / 55.4MB 0B / 0B 21
1e5f3729b921 internet-monitoring_ping_1 0.83% 0B / 0B 0.00% 59.2MB / 94.4MB 0B / 0B 12

And last docker logs [container ID] shows the following:
Error: ✗ Get "https://grafana.com/api/plugins/repo/flant-statusmap-panel": dial tcp: lookup grafana.com on 127.0.0.11:53: read udp 127.0.0.1:58162->127.0.0.11:53: i/o timeout (Client.Timeout exceeded while awaiting headers)
Error: ✗ Get "https://grafana.com/api/plugins/repo/flant-statusmap-panel": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Ow yes, turns out that I still don't know how to get the latest version of Grafana installed, the instructions on the website using docker turned out to install a complete new version next to the one already running so I removed that container again so that I'm only running the one version of yours.

Back to square one.

It would be great if you can tell me how to update Grafana after I get it running again that would be appreciated very much.

[soharddbwarez]

UPDATE

First

I tried to get Grafana fixed today again because I found that Pi-hole had an update so that was a great way for me to see if I'm doing this the right way now.

This is what I did, on my Pi I opened the terminal, then navigated to the pi-hole directory, checked if the docker-compose.yml file exists which it did, also checked what's in the file and if that data is correct and it was.

Then I run the command docker-compose pull which started to download and extract the new pi-hole version.
And last command I run was docker-compose up -d which did update pi-hole to the latest version and recreated the container.

So, when that finished I checked on my main computer if I'm running the latest version of pi-hole now, and I do so it seems to me that I'm doing this updating the right way now using docker-compose because everything did go to plan, at least for pi-hole.

Next

I navigated to the "internet-monitoring" directory to see if the docker-compose.yml file exists, and it did. I skipped to look inside the file assuming everything is as it should.

Then I did the same as before with pi-hole using the command docker-compose pull which started to download and extract the latest versions of Grafana, Prometheus, nodeexp, ping, and speedtest... That's great, it worked the same way as pi-hole up to here.
Then I used the command docker-compose up -d and to my surprise it updated Grafana and two other parts, recreating the containers just as with pi-hole so at this point I was almost convinced that Grafana should be working again since everything seemed to work and I didn't get any warnings or errors, nothing.

Last

Well, everything worked and got updated the right way but Grafana still doesn't work and gives me the same errors as before the update which you can see below, I made 2 screenshots after doing the first two commands that you asked me to do and the last command I copied and pasted the error messages so it's a bit easier for you to read. If I just copy and paste the text it shows up as gobbledygook.

docker ps -a

docker stats

docker logs 83b1d5d706d4

Error: ✗ Get "https://grafana.com/api/plugins/repo/flant-statusmap-panel": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Error: ✗ Get "https://grafana.com/api/plugins/repo/flant-statusmap-panel": dial tcp: lookup grafana.com on 127.0.0.11:53: read udp 127.0.0.1:56152->127.0.0.11:53: i/o timeout (Client.Timeout exceeded while awaiting headers)

I don't know what these errors mean or how to fix it so I really need some help with this please.

[soharddbwarez]

FIXED THE ISSUE MYSELF

So after some digging in the issues from other people regarding the same issue I found the solution for the problem.

I don't know why this is happening but I've read that I'm not the only one with the exact same issue and you commented something regarding #8 and to fix the issue I should find the following file: "etc/resolvconf.conf" and uncomment the following: "name_servers=127.0.0.1" and after doing a reboot Grafana came back to life for me so it totally worked.

But why does Grafana work normally at first when it's just installed and after a couple of days without me doing anything, not even a reboot and something that I'm unaware of must have changed the file and commented out that one specific line that needs to be uncommented again manually.

I hope this isn't something persistent, I don't mind when it happens after an update or something now that I know what I need to do to fix it again but if it keeps changing after a couple of days without me doing anything or the Pi not being rebooted in the meanwhile that's really strange and unacceptable.

If it happens again I'll let you know when it happened and the reason what caused the issue to return if you want otherwise you can close this issue.

Best regards,
Ricardo Penders.

[soharddbwarez]

Grafana is still working after a couple of days

Hi @geerlingguy
As you can see below from my screenshot Grafana is still running, the issue doesn't seem to return after I manually changed the file "etc/resolvconf.conf" by uncommenting the "name_servers=127.0.0.1" part.

What I don't understand is that I got the same issue as those people regarding #8 but I'm glad that the fix that you suggested to them is working for me and it seems that it fixed it permanently for now, I have to see what happens after an update but as long as the *.conf file isn't changed I think it's going to be okay.
Another thing I don't get is why Grafana works fine just after the initial installation using your playbook for pi-hole and then it suddenly stops working for some reason that I'm not aware of, maybe you already know what that is and if you'd be so kind to explain that to me if you have the time for it, I would appreciate it very much.

And last thing I want to mention is that Grafana does give me a new warning every time when I load the main page of internet-connection which is the following:

Do you know how to fix that?
Or point me in the right direction so I can figure it out on my own that's cool too, I'm quite capable to fix things myself but I'm new to everything that came installed with your playbook and at this point I just don't have a clue where I should start to look so it would be very helpful if you at least point me to the right direction, thanks.

Best regards,
Ricardo Penders
@soharddbwarez

PS. I read your latest update of the README file but the part where you discus updating you only mention Pi-hole, I think you should add instructions for updating the other parts of software from your playbook which is Grafana, nodeexp, Ping, Speedtest and Prometheus need to be added, I'm new to it all and one of the first things that I wanted to do is getting everything updated to the latest version especially Grafana, you know why...
But I found out that updating the other parts of software is exactly the same as you do with Pi-hole but you don't mention that at all, I think you're missing out having a complete README with instructions to get all parts of your playbook updated.

[802compute]

The "Annotation Query Failed" error is actually being tracked in #192; For that issue, there is a workaround by copying the updated lines referenced here:

#192 (comment)

There is an issue with that latest version of Grafana that'll have to be fixed by the Grafana Developers.

[soharddbwarez]

@802compute Thanks for clearing that up... I'll keep running the latest version of Grafana because it's not something crucial for the software to work I think and it doesn't bother me that much.

Also it took me too much time and effort to get it all running correctly except the little message that keeps popping up and if others are already complaining about it and the Grafana developers are aware of the problem I think they would have a solution for it soon enough.

And last thing I wanted to show is that Pi-hole and Grafana are still running after all the above issues, made a couple screenshots to show you below:

Although you recommend a Raspberry Pi 4 to run your internet-monitoring, I've got it running on my Raspberry Pi 3B+ without any problems and I don't have to worry about the Pi slowing down my internet connection because as you can see on the Grafana Dashboard Screenshot my internet connection is only around the 20Mbps download and around 2Mbps upload which is the maximum that the ISP can deliver here at home via ADSL, I don't watch any 4K videos and I don't have many different devices that need the internet at the same time so I haven't run into the issues that come with that.

I do have my Raspberry Pi 3B+ overclocked pretty high and very specifically using settings that turned out to be very stable for me and I've allocated less memory to the graphics on the Pi since I'm not doing anything with that except every once in a while I'm managing the Pi remotely via the VNC server which is the only graphic thing I'll ever run on my Pi.
I have the graphic memory set to 96MB at the moment just to show the desktop and maybe I don't even need to have that much memory allocated to the GPU.
If you have any idea how much graphical memory is the absolute minimum to be able to run the GUI Desktop let me know so I can change that setting to give the not used memory to the system which is more important to me.

Last thing I wanted to mention is that you @geerlingguy are the first person that I started to sponsor here on GitHub since I'm using the internet-monitoring software from you and I appreciate the work that you've put into this project.

[geerlingguy]

Last thing I wanted to mention is that you @geerlingguy are the first person that I started to sponsor here on GitHub since I'm using the internet-monitoring software from you and I appreciate the work that you've put into this project.

@soharddbwarez - Thank you SO much! I love to see other people benefit from the work I do, and the support means a ton to me.

[soharddbwarez]

The message in Grafana that I mention in an earlier post went away for me, I haven't done anything and didn't do an update.
I can't tell you why I don't get that message anymore, I can do a guess but that would be pure speculation and I don't want to go into that rabbit hole so if you know more than I do about that please let me know.

[stale]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[stale]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.