KNEL/PFVCluster
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

more prompt work...

Browse Source
This commit is contained in:
mrcharles
2026-08-01 16:41:13 -05:00
parent 4d86012762
commit 959c3a5bb9
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
nextprompt
+7 -1
View File
@@ -61,7 +61,8 @@ As far as the servers/data center itself, I have made many changes to :
Unfortuantely during my storage moves, I accidently wiped out pfv-netinfra-02 . Can you turn it back into a redundant node? Its setup with the ssh pub key/passwordless sudo like before Unfortuantely during my storage moves, I accidently wiped out pfv-netinfra-02 . Can you turn it back into a redundant node? Its setup with the ssh pub key/passwordless sudo like before
Also, the default /dev/shm allocated to pihole was too small, i fixed that in compose live on the server, as it was a production outage. Can you fold that fix in? Also can you add a docker compose healthcheck for gravity.db issues? I had to manually fix gravitydb (move it out of way, bounce container, pihole auto recreates it). Also, the default /dev/shm allocated to pihole was too small, i fixed that in compose live on the server, as it was a production outage. Can you fold that fix in? Also can you add a docker compose healthcheck for gravity.db issues? I had to manually fix gravitydb (move it out of way, bounce container, pihole auto recreates it). (actualy look at the bash history for root on pfv-netinfra-01 , youll see other fixes i had todo). and/or look at the docker compose config and poke around in the container. basically i had to prune volumes and bounce the container. i dont ever want to have dns fail again. this is enterprise IT , has to work.
In general, re-orient yourself to this repo, to the servers/viritual machines (via lldp/snmpwalk/ssh/nmap) In general, re-orient yourself to this repo, to the servers/viritual machines (via lldp/snmpwalk/ssh/nmap)
@@ -85,6 +86,7 @@ utilize snmpwalk/nmap/lldp and your api access to :
- uptime kuma - uptime kuma
- librenms - librenms
- beszel - beszel
- technitum
- home assistant - home assistant
to get as much together as possible. let me know if anything isn't working/broke since last time. i made a bunch of changes. to get as much together as possible. let me know if anything isn't working/broke since last time. i made a bunch of changes.
@@ -93,3 +95,7 @@ I want to get you connected into promethus/promethus alert manager/grafana and h
I want home assistant to handle all environmental monitoring and reporting for the site. I want home assistant to handle all environmental monitoring and reporting for the site.
Also, any api keys must be moved into hashicorp vault as soon as possible. Track that as a very high priority todo. vault is deployed and out of box setup but nothing configured. its at https://vault.knownelement.com
Also, any work we do here, that perhaps should also be replicated in the KNELIAC repository/project, track it in a STATUS.md file in that project. We are doing a bit of fast/loose here at this time with bash scripts, in the interest of time. For the mid/long term, the work should be captured as ansible roles/playbooks.