Auto-Sync: 2026-06-22 20:39
This commit is contained in:
Auto-Sync
parent
4f61172468
commit
eb7450677f
3 changed files with 27 additions and 167 deletions
|
|
@ -1,5 +1,5 @@
|
|||
# Arakava News — Live State
|
||||
> Auto-generiert: 2026-04-17 22:00
|
||||
> Auto-generiert: 2026-06-22 20:39
|
||||
|
||||
## Service Status
|
||||
| Service | CT | Status |
|
||||
|
|
@ -8,11 +8,11 @@
|
|||
| WordPress Docker | 101 | running |
|
||||
|
||||
## Letzte Feed-Aktivität (Top 5)
|
||||
Dr. Bines Substack: 2026-04-17 20:00:00
|
||||
Photon.info (KI-Analyse): 2026-04-17 19:41:19
|
||||
Golem.de: 2026-04-17 19:41:05
|
||||
Heise Online: 2026-04-17 19:41:05
|
||||
Rubikon.news: 2026-04-17 19:40:53
|
||||
Photon.info (KI-Analyse): 2026-06-22 17:55:49
|
||||
Heise Security: 2026-06-22 17:55:00
|
||||
Golem.de: 2026-06-22 17:54:59
|
||||
Heise Online: 2026-06-22 17:54:59
|
||||
Norbert Häring: 2026-06-22 17:54:48
|
||||
|
||||
## Fehler (letzte 24h)
|
||||
- Fehler gesamt: 0
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
# Infrastruktur — Live State
|
||||
> Auto-generiert: 2026-04-17 22:00
|
||||
> Auto-generiert: 2026-06-22 20:39
|
||||
|
||||
## pve-hetzner Disk
|
||||
| Mount | Belegt |
|
||||
|---|---|
|
||||
| / (root) | 59G 38% |
|
||||
| /var/lib/vz (VMs/CTs) | 1.8T 37% |
|
||||
| / (root) | 36G 63% |
|
||||
| /var/lib/vz (VMs/CTs) | 2.7T 5% |
|
||||
|
||||
## Aktive Container auf pve-hetzner
|
||||
| CT | Name | Tailscale IP | Dienste |
|
||||
|
|
@ -48,110 +48,3 @@
|
|||
|---|---|
|
||||
| @MutterbotAI_bot | Watchdog-Alerts |
|
||||
| @Orbitalo_Hausmeister_bot | Homelab AI-Bot |
|
||||
|
||||
## Hermes CT151 Monitoring und Backup
|
||||
|
||||
Stand: 2026-05-16
|
||||
|
||||
Hermes (`hermes-mu`, CT151) ist als kritischer Dienst eingestuft und wird separat abgesichert.
|
||||
|
||||
### Proxmox / PBS Backup
|
||||
|
||||
Backup-Job auf `pve3` / `pve-mu-3`:
|
||||
|
||||
| Feld | Wert |
|
||||
|------|------|
|
||||
| Job-ID | `hermes-mu-backup` |
|
||||
| VMID | `151` |
|
||||
| Container | `hermes-mu` |
|
||||
| Node | `pve3` |
|
||||
| Ziel | `pbs-nvme` / Muldenstein PBS (`100.99.139.22:nvme-pool`) |
|
||||
| Modus | `snapshot` |
|
||||
| Kompression | `zstd` |
|
||||
| Zeitplan | täglich `03:20` |
|
||||
| Nachholen | `repeat-missed=1` |
|
||||
| Prune | `keep-daily=7`, `keep-weekly=4`, `keep-monthly=3` |
|
||||
|
||||
Manuelles Safety-Backup wurde am 2026-05-16 erfolgreich erstellt:
|
||||
|
||||
```text
|
||||
ct/151/2026-05-16T10:51:53Z
|
||||
Dauer: 56s
|
||||
Gesichert: ca. 6.15 GiB
|
||||
Komprimiert übertragen: ca. 3.98 GiB
|
||||
Ergebnis: Backup job finished successfully
|
||||
```
|
||||
|
||||
PBS-Auslastung danach:
|
||||
|
||||
```text
|
||||
pbs-nvme active, ca. 5.63% belegt
|
||||
```
|
||||
|
||||
Schnelltest:
|
||||
|
||||
```bash
|
||||
# Auf pve3 / pve-mu-3
|
||||
pvesh get /cluster/backup/hermes-mu-backup --output-format json
|
||||
pvesm status --storage pbs-nvme
|
||||
```
|
||||
|
||||
### Prometheus / node_exporter
|
||||
|
||||
Auf CT151 ist `prometheus-node-exporter` installiert und aktiv.
|
||||
|
||||
```bash
|
||||
systemctl is-active prometheus-node-exporter
|
||||
curl -sS http://127.0.0.1:9100/metrics | grep -m1 '^node_uname_info'
|
||||
```
|
||||
|
||||
Von CT116 / Hausmeister erreichbar über:
|
||||
|
||||
```bash
|
||||
curl -sS http://100.109.174.120:9100/metrics
|
||||
```
|
||||
|
||||
### Loki / Promtail
|
||||
|
||||
Auf CT151 läuft `promtail` und schickt Logs mit Host-Label `hermes-mu` an Loki.
|
||||
|
||||
Wichtige Checks:
|
||||
|
||||
```bash
|
||||
systemctl is-active promtail
|
||||
curl -sS http://100.109.174.120:9080/ready
|
||||
```
|
||||
|
||||
### Hermes-Service-Checks
|
||||
|
||||
Aktive Dienste auf CT151:
|
||||
|
||||
```bash
|
||||
systemctl is-active hermes-gateway beellama-tunnel promtail prometheus-node-exporter
|
||||
curl -sS http://127.0.0.1:11435/v1/models
|
||||
```
|
||||
|
||||
Der lokale BeeLlama/OpenAI-kompatible Tunnel lauscht in CT151 auf `127.0.0.1:11435`; er ist deshalb von CT116 nicht direkt per HTTP erreichbar. Der Health-Check erfolgt lokal auf CT151 bzw. indirekt über Hermes/Hausmeister.
|
||||
|
||||
### Hausmeister-Integration
|
||||
|
||||
Hausmeister (`CT116`) enthält in `/opt/homelab-ai-bot/monitor.py` einen `check_hermes()`.
|
||||
|
||||
Der Check prüft:
|
||||
|
||||
- Hermes Promtail: `http://100.109.174.120:9080/ready`
|
||||
- Hermes node_exporter: `http://100.109.174.120:9100/metrics`
|
||||
- Websuche/SearXNG CT121: `http://100.74.196.29:8080/search?...`
|
||||
- Loki: `http://100.109.206.43:3100/ready`
|
||||
- PBS Muldenstein: `https://100.99.139.22:8007`
|
||||
- Loki-Health für Host `hermes-mu`
|
||||
- auffällige Hermes-Logs der letzten 30 Minuten
|
||||
|
||||
Harmloser `node_exporter`-Diskstats-Logspam (`diskstats_linux.go`, `disabling udev device properties`) wird gefiltert.
|
||||
|
||||
Finaler Test am 2026-05-16:
|
||||
|
||||
```text
|
||||
monitor.check_hermes() -> OK
|
||||
hausmeister-bot.service -> active
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,57 +1,24 @@
|
|||
# Smart Home Muldenstein — Live State
|
||||
|
||||
> **Alles läuft in CT 143 auf pve-mu-3.** Es gibt keinen Raspberry Pi mehr.
|
||||
> Für die Heizung & Brennererkennung: siehe **[HEIZUNG.md](HEIZUNG.md)**.
|
||||
|
||||
## Container CT 143 — smart-home
|
||||
|
||||
| Attribut | Wert |
|
||||
|---|---|
|
||||
| Host | `pve-mu-3` (Tailscale `100.109.101.12`) |
|
||||
| Tailscale IP | `100.66.78.56` |
|
||||
| LAN IP | `192.168.178.36` |
|
||||
| OS | Debian LXC |
|
||||
|
||||
### Dienste im Container (ein Container, drei Dienste)
|
||||
|
||||
| Dienst | Port | URL public | URL intern | Login |
|
||||
|---|---|---|---|---|
|
||||
| **Grafana** | 3000 | https://grafana.orbitalo.net (Cloudflare Tunnel) | http://100.66.78.56:3000 | `admin` / `astral66` |
|
||||
| **ioBroker** | 8081 | — | http://100.66.78.56:8081 · http://192.168.178.36:8081 | `admin` / `astral66` |
|
||||
| **InfluxDB 1.x** | 8086 | — | http://100.66.78.56:8086 | keine Auth, DB `iobroker` |
|
||||
|
||||
**Alle Passwörter = `PW_DEFAULT` = `astral66`** (siehe `homelab.conf`).
|
||||
|
||||
## Zugang
|
||||
|
||||
```bash
|
||||
# aus dem monitoring-bot (CT 116 auf pve-mu-2, wo Cursor läuft):
|
||||
ssh pve-mu-3 # Host
|
||||
ssh pve-mu-3 'pct exec 143 -- <cmd>' # im Container
|
||||
ssh pve-mu-3 'pct exec 143 -- bash' # interaktive Shell
|
||||
|
||||
# Grafana-Dashboard als PNG (Puppeteer-Login mit admin/astral66):
|
||||
node /tmp/grafana_shot.js "https://grafana.orbitalo.net/d/heizung/f09f94a5-heizung-and-puffer?kiosk" /tmp/out.png
|
||||
```
|
||||
|
||||
## Wichtige Python-Services in CT 143
|
||||
|
||||
| Service | Datei | Zweck |
|
||||
|---|---|---|
|
||||
| `brennerstarts.service` | `/root/brennerstarts.py` | Ölbrenner-Erkennung per Vorlauftemperatur → InfluxDB |
|
||||
|
||||
Backup der Originalskripte vor Anpassungen: `/root/*.bak-YYYYMMDD-HHMM` direkt im Container.
|
||||
> Auto-generiert: 2026-06-22 20:39
|
||||
|
||||
## Backup-Status
|
||||
- Letztes Backup: 696 MB, 2026-04-17 04:43
|
||||
- Backups gesamt: 34
|
||||
- Ziel: `/home/backup-muldenstein/backups/` auf CT 144 (muldenstein-backup)
|
||||
- Cronjob: täglich 04:00 → `/root/backup-to-hetzner.sh` (auf `pve-mu-3`)
|
||||
- Retention: 30 d täglich, 90 d wöchentlich, monatlich unbegrenzt
|
||||
- Letztes Backup: 991MB, 2026-06-22 04:01
|
||||
- Backups gesamt: 41
|
||||
- Ziel: /home/backup-muldenstein/backups/ (CT 144)
|
||||
|
||||
## Grafana Alerts → Telegram (Chat `674951792`)
|
||||
## Services (CT 143)
|
||||
| Dienst | URL |
|
||||
|---|---|
|
||||
| Grafana | https://grafana.orbitalo.net |
|
||||
| ioBroker | http://192.168.178.36:8081 |
|
||||
| InfluxDB | http://192.168.178.36:8086 |
|
||||
|
||||
## Grafana Alerts → Telegram 674951792
|
||||
- Promtail DOWN (> 5 Min keine Daten)
|
||||
- CPU > 70 %
|
||||
- Memory > 80 %
|
||||
- Disk > 90 %
|
||||
- CPU > 70%
|
||||
- Memory > 80%
|
||||
- Disk > 90%
|
||||
|
||||
## Backup-Zeitplan
|
||||
- täglich 04:00 → /root/backup-to-hetzner.sh (auf pve3)
|
||||
- Retention: 30d tägl, 90d wöchl, unbegrenzt monatl
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue