📚 Improved documentation and log file maintenance 🚀
This commit is contained in:
parent
b6e53463a1
commit
8b663aa7f4
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -145,3 +145,4 @@
|
||||
2025-06-04 00:50:42 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-04 00:56:10 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-04 00:56:22 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-04 07:21:03 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
|
||||
@ -3846,3 +3846,25 @@ WHERE jobs.status = ?) AS anon_1]
|
||||
2025-06-04 01:00:01 - [app] app - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
|
||||
2025-06-04 01:00:31 - [app] app - [INFO] INFO - Admin-Check für Funktion api_admin_error_recovery_status: User authenticated: True, User ID: 1, Is Admin: True
|
||||
2025-06-04 01:00:31 - [app] app - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
|
||||
2025-06-04 07:21:03 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: /mnt/database/myp.db
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ Timeout Force-Quit Manager geladen
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - 📋 Standard-Konfiguration verwendet
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ Zentraler Shutdown-Manager initialisiert
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ Error-Recovery-Monitoring gestartet
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ System-Control-Manager initialisiert
|
||||
2025-06-04 07:21:04 - [app] app - [WARNING] WARNING - ⚠️ Kiosk-Service nicht gefunden - Kiosk-Funktionen eventuell eingeschränkt
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - 🔄 Starte Datenbank-Setup und Migrationen...
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ JobOrder-Tabelle bereits vorhanden
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ Datenbank-Setup und Migrationen erfolgreich abgeschlossen
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - 📋 Standard-Konfiguration aktiv (keine Optimierungen)
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - 🖨️ Starte automatische Steckdosen-Initialisierung...
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ℹ️ Keine Drucker zur Initialisierung gefunden
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ Printer Queue Manager erfolgreich gestartet
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - Job-Scheduler gestartet
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - 🚀 Starte Production Server (Waitress) auf 127.0.0.1:5000
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - 💡 Kiosk-Browser sollte http://127.0.0.1:5000 verwenden
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ IPv6-Probleme behoben durch IPv4-only Binding
|
||||
2025-06-04 07:21:04 - [app] app - [INFO] INFO - ✅ Performance optimiert für Kiosk-Betrieb
|
||||
|
||||
@ -150,3 +150,4 @@
|
||||
2025-06-04 00:50:42 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-04 00:56:09 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-04 00:56:22 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-04 07:21:03 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
|
||||
@ -614,3 +614,7 @@
|
||||
2025-06-04 00:56:23 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-04 00:56:23 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback)
|
||||
2025-06-04 00:56:23 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading)
|
||||
2025-06-04 07:21:04 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-04 07:21:04 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-04 07:21:04 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit eventlet initialisiert
|
||||
2025-06-04 07:21:04 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: eventlet)
|
||||
|
||||
@ -146,3 +146,4 @@
|
||||
2025-06-04 00:50:42 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-04 00:56:09 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-04 00:56:22 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-04 07:21:03 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
|
||||
@ -94,3 +94,6 @@
|
||||
2025-06-04 00:56:23 - [database_cleanup] database_cleanup - [INFO] INFO - 🧹 Starte umfassendes Datenbank-Cleanup...
|
||||
2025-06-04 00:56:23 - [database_cleanup] database_cleanup - [INFO] INFO - 📝 Schritt 1: Schließe alle Datenbankverbindungen...
|
||||
2025-06-04 00:56:23 - [database_cleanup] database_cleanup - [INFO] INFO - 🔄 Schließe alle aktiven Datenbankverbindungen...
|
||||
2025-06-04 07:21:04 - [database_cleanup] database_cleanup - [INFO] INFO - 🧹 Starte umfassendes Datenbank-Cleanup...
|
||||
2025-06-04 07:21:04 - [database_cleanup] database_cleanup - [INFO] INFO - 📝 Schritt 1: Schließe alle Datenbankverbindungen...
|
||||
2025-06-04 07:21:04 - [database_cleanup] database_cleanup - [INFO] INFO - 🔄 Schließe alle aktiven Datenbankverbindungen...
|
||||
|
||||
@ -1,32 +1,32 @@
|
||||
=================================================================
|
||||
MYP Installation DEBUG Log - 2025-06-04 07:18:35
|
||||
MYP Installation DEBUG Log - 2025-06-04 07:22:23
|
||||
=================================================================
|
||||
|
||||
[2025-06-04 07:18:35] DEBUG von setup.sh:464
|
||||
[2025-06-04 07:22:23] DEBUG von setup.sh:464
|
||||
Debian erkannt über /etc/debian_version: 12.11
|
||||
---
|
||||
|
||||
[2025-06-04 07:18:35] DEBUG von setup.sh:532
|
||||
[2025-06-04 07:22:23] DEBUG von setup.sh:532
|
||||
Kein Raspberry Pi erkannt. Hardware-Info:
|
||||
---
|
||||
|
||||
[2025-06-04 07:18:35] DEBUG von setup.sh:533
|
||||
[2025-06-04 07:22:23] DEBUG von setup.sh:533
|
||||
- Device Tree: nicht verfügbar
|
||||
---
|
||||
|
||||
[2025-06-04 07:18:35] DEBUG von setup.sh:534
|
||||
[2025-06-04 07:22:23] DEBUG von setup.sh:534
|
||||
- CPU Hardware: nicht verfügbar
|
||||
---
|
||||
|
||||
[2025-06-04 07:18:35] DEBUG von setup.sh:574
|
||||
[2025-06-04 07:22:23] DEBUG von setup.sh:574
|
||||
Vollständige Kernel-Info: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux
|
||||
---
|
||||
|
||||
[2025-06-04 07:18:35] DEBUG von setup.sh:630
|
||||
[2025-06-04 07:22:23] DEBUG von setup.sh:630
|
||||
DNS-Test Details: Teste DNS für 8.8.8.8: Erfolg mit nslookup.
|
||||
---
|
||||
|
||||
[2025-06-04 07:18:35] DEBUG von setup.sh:731
|
||||
[2025-06-04 07:22:23] DEBUG von setup.sh:731
|
||||
Externe IP ermittelt über ifconfig.me: 163.116.178.114
|
||||
---
|
||||
|
||||
|
||||
@ -142,3 +142,4 @@
|
||||
2025-06-04 00:50:43 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-04 00:56:10 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-04 00:56:23 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-04 07:21:04 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
|
||||
@ -107,3 +107,7 @@
|
||||
2025-06-04 00:56:23 - [error_recovery] error_recovery - [INFO] INFO - 🔍 Error-Monitoring gestartet
|
||||
2025-06-04 00:56:23 - [error_recovery] error_recovery - [WARNING] WARNING - 🚨 Fehler erkannt: database_lock - 2025-06-01 00:29:13 - myp.app - ERROR - ❌ Fehler beim Datenbank-Cleanup: (sqlite3.OperationalError) database is locked
|
||||
2025-06-04 00:56:23 - [error_recovery] error_recovery - [INFO] INFO - 🔧 Führe Recovery-Aktion aus: reset_database
|
||||
2025-06-04 07:21:04 - [error_recovery] error_recovery - [INFO] INFO - 🛡️ Error-Recovery-Manager initialisiert
|
||||
2025-06-04 07:21:04 - [error_recovery] error_recovery - [INFO] INFO - 🔍 Error-Monitoring gestartet
|
||||
2025-06-04 07:21:04 - [error_recovery] error_recovery - [WARNING] WARNING - 🚨 Fehler erkannt: database_lock - 2025-06-01 00:29:13 - myp.app - ERROR - ❌ Fehler beim Datenbank-Cleanup: (sqlite3.OperationalError) database is locked
|
||||
2025-06-04 07:21:04 - [error_recovery] error_recovery - [INFO] INFO - 🔧 Führe Recovery-Aktion aus: reset_database
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
=================================================================
|
||||
MYP Installation FEHLER Log - 2025-06-04 07:18:35
|
||||
MYP Installation FEHLER Log - 2025-06-04 07:22:23
|
||||
=================================================================
|
||||
|
||||
|
||||
@ -1,27 +1,27 @@
|
||||
=================================================================
|
||||
MYP Installation Log - 2025-06-04 07:18:35
|
||||
MYP Installation Log - 2025-06-04 07:22:23
|
||||
Script Version: 4.1.0
|
||||
System: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux
|
||||
Arbeitsverzeichnis: /mnt
|
||||
Log-Verzeichnis: /mnt/logs
|
||||
=================================================================
|
||||
|
||||
[0;32m[2025-06-04 07:18:35] === MODUS: ROBUSTE ABHÄNGIGKEITEN-INSTALLATION FÜR MANUELLES TESTEN ===[0m
|
||||
[0;32m[2025-06-04 07:18:35] ✅ Root-Berechtigung bestätigt[0m
|
||||
[0;32m[2025-06-04 07:18:35] === SYSTEM-RESSOURCEN PRÜFUNG ===[0m
|
||||
[0;32m[2025-06-04 07:22:23] === MODUS: VOLLSTÄNDIGE ROBUSTE KIOSK-INSTALLATION MIT REMOTE-ZUGANG ===[0m
|
||||
[0;32m[2025-06-04 07:22:23] ✅ Root-Berechtigung bestätigt[0m
|
||||
[0;32m[2025-06-04 07:22:23] === SYSTEM-RESSOURCEN PRÜFUNG ===[0m
|
||||
[0;35m[FORTSCHRITT] Prüfe RAM...[0m
|
||||
[0;35m[FORTSCHRITT] Verfügbarer RAM: 3914MB[0m
|
||||
[0;36m[ERFOLG] ✅ Ausreichend RAM verfügbar (3914MB)[0m
|
||||
[0;35m[FORTSCHRITT] Prüfe Festplattenplatz...[0m
|
||||
[0;35m[FORTSCHRITT] Verfügbarer Festplattenplatz: 12,0GB (12324MB)[0m
|
||||
[0;35m[FORTSCHRITT] Verfügbarer Festplattenplatz: 12,0GB (12322MB)[0m
|
||||
[0;36m[ERFOLG] ✅ Ausreichend Festplattenplatz verfügbar (12,0GB)[0m
|
||||
[0;35m[FORTSCHRITT] Prüfe CPU...[0m
|
||||
[0;35m[FORTSCHRITT] CPU: 4 Kern(e) - 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz[0m
|
||||
[0;36m[ERFOLG] ✅ CPU-Information erfolgreich ermittelt[0m
|
||||
[0;32m[2025-06-04 07:18:35] ✅ System-Ressourcen-Prüfung abgeschlossen[0m
|
||||
[0;32m[2025-06-04 07:22:23] ✅ System-Ressourcen-Prüfung abgeschlossen[0m
|
||||
[0;35m[FORTSCHRITT] Prüfe Debian/Raspbian-System...[0m
|
||||
[0;34m[DEBUG] Debian erkannt über /etc/debian_version: 12.11[0m
|
||||
[0;32m[2025-06-04 07:18:35] ✅ Debian/Raspbian-basiertes System erkannt (Version: 12.11)[0m
|
||||
[0;32m[2025-06-04 07:22:23] ✅ Debian/Raspbian-basiertes System erkannt (Version: 12.11)[0m
|
||||
[0;35m[FORTSCHRITT] Prüfe Raspberry Pi Hardware...[0m
|
||||
[0;34m[INFO] 💻 Standard-PC/Server System (kein Raspberry Pi)[0m
|
||||
[0;34m[DEBUG] Kein Raspberry Pi erkannt. Hardware-Info:[0m
|
||||
@ -33,7 +33,7 @@ Log-Verzeichnis: /mnt/logs
|
||||
[0;35m[FORTSCHRITT] Prüfe Kernel-Version...[0m
|
||||
[0;34m[INFO] 🐧 Kernel-Version: 6.1.0-37-amd64[0m
|
||||
[0;34m[DEBUG] Vollständige Kernel-Info: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux[0m
|
||||
[0;32m[2025-06-04 07:18:35] ✅ System-Analyse abgeschlossen[0m
|
||||
[0;32m[2025-06-04 07:22:23] ✅ System-Analyse abgeschlossen[0m
|
||||
[0;35m[FORTSCHRITT] Prüfe Internetverbindung (erweiterte Methoden)...[0m
|
||||
[0;35m[FORTSCHRITT] Teste DNS-Auflösung...[0m
|
||||
[0;34m[DEBUG] DNS-Test Details: Teste DNS für 8.8.8.8: Erfolg mit nslookup. [0m
|
||||
@ -42,11 +42,107 @@ Log-Verzeichnis: /mnt/logs
|
||||
[0;35m[FORTSCHRITT] Ermittle externe IP-Adresse...[0m
|
||||
[0;34m[INFO] 🌐 Externe IP: 163.116.178.114[0m
|
||||
[0;34m[DEBUG] Externe IP ermittelt über ifconfig.me: 163.116.178.114[0m
|
||||
[0;32m[2025-06-04 07:18:35] === KONFIGURIERE HOSTNAME ===[0m
|
||||
[0;32m[2025-06-04 07:18:35] ✅ Hostname bereits korrekt: 'raspberrypi'[0m
|
||||
[0;32m[2025-06-04 07:18:36] ✅ Hostname-Auflösung funktioniert: raspberrypi -> 127.0.1.1[0m
|
||||
[0;32m[2025-06-04 07:18:36] === ANTI-HÄNGE SYSTEM-UPDATE MIT TIMEOUTS ===[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere APT für bessere Zuverlässigkeit (timeout-gesichert)...[0m
|
||||
[0;35m[FORTSCHRITT] Validiere APT-Repositories (timeout-gesichert)...[0m
|
||||
[0;35m[FORTSCHRITT] Bereinige APT-Lock-Dateien...[0m
|
||||
[0;35m[FORTSCHRITT] Aktualisiere Paketlisten (max 60s timeout)...[0m
|
||||
[0;32m[2025-06-04 07:22:23] === KONFIGURIERE HOSTNAME ===[0m
|
||||
[0;32m[2025-06-04 07:22:23] ✅ Hostname bereits korrekt: 'raspberrypi'[0m
|
||||
[0;32m[2025-06-04 07:22:23] ✅ Hostname-Auflösung funktioniert: raspberrypi -> 127.0.1.1[0m
|
||||
[0;34m[INFO] Anwendung bereits deployed - überspringe Basis-Installation[0m
|
||||
[0;32m[2025-06-04 07:22:23] === SIMPLE NETZWERK-SICHERHEIT (ANTI-HÄNGE VERSION) ===[0m
|
||||
[0;34m[INFO] 🚀 Netzwerk-Sicherheit übersprungen für schnellere Installation[0m
|
||||
[0;34m[INFO] 📝 Kann später manuell aktiviert werden mit: SKIP_NETWORK_SECURITY=0[0m
|
||||
[0;32m[2025-06-04 07:22:23] === ENTFERNE DESKTOP ENVIRONMENTS FÜR KIOSK-MODUS ===[0m
|
||||
[0;35m[FORTSCHRITT] Stoppe alle Desktop-Services...[0m
|
||||
[0;35m[FORTSCHRITT] Entferne Desktop-Pakete vollständig...[0m
|
||||
[0;32m[2025-06-04 07:22:48] ✅ Desktop Environments vollständig entfernt[0m
|
||||
[0;32m[2025-06-04 07:22:48] === INSTALLIERE MINIMALE X11-UMGEBUNG FÜR KIOSK ===[0m
|
||||
[0;35m[FORTSCHRITT] Installiere minimale X11-Pakete...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Browser für Kiosk-Modus...[0m
|
||||
[0;32m[2025-06-04 07:23:05] ✅ Chromium erfolgreich installiert[0m
|
||||
[0;32m[2025-06-04 07:23:05] ✅ Minimale X11-Umgebung installiert[0m
|
||||
[0;32m[2025-06-04 07:23:05] === WEBAPP PERFORMANCE-OPTIMIERUNG FÜR RASPBERRY PI ===[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere Python-Performance-Optimierungen...[0m
|
||||
[0;35m[FORTSCHRITT] Optimiere Systemd-Services für bessere Performance...[0m
|
||||
[0;32m[2025-06-04 07:23:05] ✅ Service deaktiviert: bluetooth.service[0m
|
||||
[0;32m[2025-06-04 07:23:06] ✅ Service deaktiviert: avahi-daemon.service[0m
|
||||
[0;32m[2025-06-04 07:23:06] ✅ Service deaktiviert: cups.service[0m
|
||||
[0;32m[2025-06-04 07:23:06] ✅ Service deaktiviert: cups-browsed.service[0m
|
||||
[0;32m[2025-06-04 07:23:07] ✅ Service deaktiviert: wpa_supplicant.service[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere tmpfs für bessere I/O Performance...[0m
|
||||
[0;35m[FORTSCHRITT] Optimiere systemd Journal für bessere Performance...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere automatische Cache-Bereinigung...[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere System-Limits...[0m
|
||||
[0;35m[FORTSCHRITT] Entferne konfliktbehaftete Webserver...[0m
|
||||
[0;32m[2025-06-04 07:23:07] ✅ Webapp Performance-Optimierung abgeschlossen:[0m
|
||||
[0;32m[2025-06-04 07:23:07] 🚀 Python Bytecode-Optimierung aktiviert[0m
|
||||
[0;32m[2025-06-04 07:23:07] 💾 tmpfs für temporäre Dateien konfiguriert[0m
|
||||
[0;32m[2025-06-04 07:23:07] 📝 Journal-Logging optimiert[0m
|
||||
[0;32m[2025-06-04 07:23:07] 🧹 Automatische Cache-Bereinigung installiert[0m
|
||||
[0;32m[2025-06-04 07:23:07] ⚡ Unnötige Services deaktiviert[0m
|
||||
[0;32m[2025-06-04 07:23:07] 📊 System-Limits für bessere Performance gesetzt[0m
|
||||
[0;32m[2025-06-04 07:23:07] === STATISCHE DATEIEN OPTIMIERUNG ===[0m
|
||||
[0;35m[FORTSCHRITT] Analysiere und optimiere CSS/JS Dateien...[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle optimierte CSS-Kombination...[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle optimierten JavaScript-Loader...[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle optimierten Service Worker...[0m
|
||||
[0;35m[FORTSCHRITT] Komprimiere statische Dateien...[0m
|
||||
[0;32m[2025-06-04 07:23:07] ✅ Statische Dateien optimiert:[0m
|
||||
[0;32m[2025-06-04 07:23:07] 📦 Kritische CSS-Styles kombiniert[0m
|
||||
[0;32m[2025-06-04 07:23:07] ⚡ Asynchroner Asset-Loader erstellt[0m
|
||||
[0;32m[2025-06-04 07:23:07] 🗜️ Gzip-Kompression angewendet[0m
|
||||
[0;32m[2025-06-04 07:23:07] 🔄 Service Worker für Caching installiert[0m
|
||||
[0;32m[2025-06-04 07:23:07] === INSTALLIERE REMOTE-ZUGANG (RDP & SSH) ===[0m
|
||||
[0;35m[FORTSCHRITT] Installiere und konfiguriere SSH-Server...[0m
|
||||
[0;34m[INFO] SSH-Benutzer 'user' existiert bereits[0m
|
||||
[0;35m[FORTSCHRITT] Installiere RDP-Server (xrdp) - vereinfachte Installation...[0m
|
||||
[0;35m[FORTSCHRITT] Entferne vorherige xrdp-Installationen...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere minimale XFCE-Umgebung...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere xrdp neu...[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle minimale xrdp-Konfiguration...[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere XFCE-Sessions...[0m
|
||||
[0;35m[FORTSCHRITT] Setze Root-Passwort für RDP...[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle Log-Verzeichnisse...[0m
|
||||
[0;35m[FORTSCHRITT] Starte xrdp-Services...[0m
|
||||
[0;36m[ERFOLG] ✅ xrdp-sesman erfolgreich gestartet[0m
|
||||
[0;36m[ERFOLG] ✅ xrdp erfolgreich gestartet[0m
|
||||
[0;32m[2025-06-04 07:23:37] ✅ Remote-Zugang vollständig konfiguriert:[0m
|
||||
[0;32m[2025-06-04 07:23:37] 📡 SSH: user:raspberry (Port 22)[0m
|
||||
[0;32m[2025-06-04 07:23:37] 🖥️ RDP: root:744563017196A (Port 3389)[0m
|
||||
[0;32m[2025-06-04 07:23:37] 🖥️ RDP: user:raspberry (Port 3389)[0m
|
||||
[0;32m[2025-06-04 07:23:37] === KONFIGURIERE FIREWALL (firewalld) ===[0m
|
||||
[0;35m[FORTSCHRITT] Installiere firewalld...[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere firewalld-Zonen und -Regeln...[0m
|
||||
[0;35m[FORTSCHRITT] Entferne bestehende myp-backend Zone falls vorhanden...[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle neue myp-backend Zone...[0m
|
||||
[0;35m[FORTSCHRITT] Füge Netzwerk-Quellen hinzu...[0m
|
||||
[0;35m[FORTSCHRITT] Füge lokalen Hostname hinzu: raspberrypi[0m
|
||||
[0;32m[2025-06-04 07:23:52] ✅ Lokaler Hostname raspberrypi hinzugefügt: 127.0.1.1[0m
|
||||
[0;35m[FORTSCHRITT] Füge Frontend-Server hinzu: m040tbaraspi001[0m
|
||||
[0;32m[2025-06-04 07:23:52] ✅ Frontend-Server m040tbaraspi001 hinzugefügt: 53.37.211.254[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere Ports und Services...[0m
|
||||
[0;35m[FORTSCHRITT] Deaktiviere IPv6 in firewalld...[0m
|
||||
[0;35m[FORTSCHRITT] Setze Default-Zone...[0m
|
||||
[0;35m[FORTSCHRITT] Lade Firewall-Konfiguration neu...[0m
|
||||
[0;35m[FORTSCHRITT] Firewall-Konfiguration:[0m
|
||||
[0;32m[2025-06-04 07:23:57] ✅ Firewall-Konfiguration erfolgreich angezeigt[0m
|
||||
[0;35m[FORTSCHRITT] Validiere Firewall-Konfiguration...[0m
|
||||
[0;32m[2025-06-04 07:23:58] ✅ Firewall konfiguriert und validiert:[0m
|
||||
[0;32m[2025-06-04 07:23:58] 🔒 Zone: myp-backend (als Default gesetzt)[0m
|
||||
[0;32m[2025-06-04 07:23:58] 🌐 Netzwerk: 192.168.0.0/16 (nur IPv4)[0m
|
||||
[0;32m[2025-06-04 07:23:58] 🏠 Localhost: 127.0.0.1[0m
|
||||
[0;32m[2025-06-04 07:23:58] 🖥️ Lokaler Host: raspberrypi[0m
|
||||
[0;32m[2025-06-04 07:23:58] 📡 Frontend-Server: m040tbaraspi001[0m
|
||||
[0;32m[2025-06-04 07:23:58] 🔌 Ports: 443/tcp (HTTPS), 22/tcp (SSH), 3389/tcp (RDP)[0m
|
||||
[0;32m[2025-06-04 07:23:58] 🚫 IPv6 vollständig blockiert[0m
|
||||
[0;32m[2025-06-04 07:23:58] === KIOSK-BENUTZER SETUP ===[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle Kiosk-Benutzer: kiosk[0m
|
||||
[0;32m[2025-06-04 07:23:58] ✅ Kiosk-Benutzer konfiguriert: kiosk[0m
|
||||
[0;32m[2025-06-04 07:23:58] === KONFIGURIERE AUTOLOGIN FÜR KIOSK-BENUTZER ===[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere automatischen Login auf tty1...[0m
|
||||
[0;32m[2025-06-04 07:23:59] ✅ Autologin für kiosk konfiguriert[0m
|
||||
[0;32m[2025-06-04 07:23:59] === KONFIGURIERE AUTOMATISCHEN KIOSK-START ===[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere automatischen Kiosk-Start für kiosk...[0m
|
||||
[0;32m[2025-06-04 07:23:59] ✅ Automatischer Kiosk-Start konfiguriert[0m
|
||||
[0;34m[INFO] Der Kiosk-Modus startet automatisch beim Login des kiosk[0m
|
||||
[0;32m[2025-06-04 07:23:59] === ROBUSTE SYSTEMD-SERVICES INSTALLATION ===[0m
|
||||
[0;35m[FORTSCHRITT] Validiere und kopiere Service-Dateien...[0m
|
||||
[0;35m[FORTSCHRITT] Kopiere essenziellen Service: myp-https.service[0m
|
||||
[0;36m[ERFOLG] ✅ myp-https.service erfolgreich installiert[0m
|
||||
|
||||
@ -290,3 +290,5 @@
|
||||
2025-06-04 00:56:10 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-04 00:56:23 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-04 00:56:23 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-04 07:21:04 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-04 07:21:04 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
|
||||
@ -288,3 +288,5 @@
|
||||
2025-06-04 00:56:10 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-04 00:56:23 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-04 00:56:23 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-04 07:21:04 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-04 07:21:04 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
|
||||
@ -144,3 +144,4 @@
|
||||
2025-06-04 00:50:43 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-04 00:56:10 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-04 00:56:23 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-04 07:21:04 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
|
||||
@ -3921,3 +3921,16 @@
|
||||
2025-06-04 01:00:45 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
2025-06-04 01:00:45 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-04 01:00:45 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
2025-06-04 07:21:03 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-04 07:21:03 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-04 07:21:04 - [printer_monitor] printer_monitor - [INFO] INFO - 🚀 Starte Steckdosen-Initialisierung beim Programmstart...
|
||||
2025-06-04 07:21:04 - [printer_monitor] printer_monitor - [WARNING] WARNING - ⚠️ Keine aktiven Drucker zur Initialisierung gefunden
|
||||
2025-06-04 07:21:05 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Starte automatische Tapo-Steckdosenerkennung...
|
||||
2025-06-04 07:21:05 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Teste 6 Standard-IPs aus der Konfiguration
|
||||
2025-06-04 07:21:05 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 1/6: 192.168.0.103
|
||||
2025-06-04 07:21:12 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 2/6: 192.168.0.104
|
||||
2025-06-04 07:21:21 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 3/6: 192.168.0.100
|
||||
2025-06-04 07:21:29 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 4/6: 192.168.0.101
|
||||
2025-06-04 07:21:35 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 5/6: 192.168.0.102
|
||||
2025-06-04 07:21:41 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 6/6: 192.168.0.105
|
||||
2025-06-04 07:21:47 - [printer_monitor] printer_monitor - [INFO] INFO - ✅ Steckdosen-Erkennung abgeschlossen: 0/6 Steckdosen gefunden in 42.2s
|
||||
|
||||
@ -227,3 +227,17 @@
|
||||
(Background on this error at: https://sqlalche.me/e/20/f405)
|
||||
2025-06-04 00:36:05 - [queue_manager] queue_manager - [INFO] INFO - 🛑 Shutdown-Signal empfangen - beende Monitor-Loop
|
||||
2025-06-04 00:36:05 - [queue_manager] queue_manager - [INFO] INFO - 🔚 Monitor-Loop beendet
|
||||
2025-06-04 07:21:04 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Initialisiere neuen Queue-Manager...
|
||||
2025-06-04 07:21:04 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Zentrale Shutdown-Verwaltung erkannt - deaktiviere lokale Signal-Handler
|
||||
2025-06-04 07:21:04 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Starte Printer Queue Manager...
|
||||
2025-06-04 07:21:04 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Queue-Überwachung gestartet (Intervall: 120 Sekunden)
|
||||
2025-06-04 07:21:04 - [queue_manager] queue_manager - [INFO] INFO - ✅ Printer Queue Manager gestartet
|
||||
2025-06-04 07:21:04 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestartet
|
||||
2025-06-04 07:21:04 - [queue_manager] queue_manager - [INFO] INFO - 🔍 Überprüfe 8 wartende Jobs...
|
||||
2025-06-04 07:21:11 - [queue_manager] queue_manager - [WARNING] WARNING - ⏱️ Ping-Timeout für Drucker 192.168.0.104 nach 5 Sekunden
|
||||
2025-06-04 07:21:32 - [queue_manager] queue_manager - [WARNING] WARNING - ⏱️ Ping-Timeout für Drucker 192.168.0.103 nach 5 Sekunden
|
||||
2025-06-04 07:21:56 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Stoppe Queue-Manager...
|
||||
2025-06-04 07:21:56 - [queue_manager] queue_manager - [INFO] INFO - ⏳ Warte auf Monitor-Thread...
|
||||
2025-06-04 07:21:56 - [queue_manager] queue_manager - [INFO] INFO - 🛑 Shutdown-Signal empfangen - beende Monitor-Loop
|
||||
2025-06-04 07:21:56 - [queue_manager] queue_manager - [INFO] INFO - 🔚 Monitor-Loop beendet
|
||||
2025-06-04 07:21:56 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestoppt
|
||||
|
||||
@ -40197,3 +40197,70 @@
|
||||
2025-06-04 01:01:19 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x000001C16BB58AF0>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 01:01:19 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 6 nicht einschalten
|
||||
2025-06-04 01:01:19 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 9: zi
|
||||
2025-06-04 07:21:03 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-04 07:21:04 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
|
||||
2025-06-04 07:21:04 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
|
||||
2025-06-04 07:21:04 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 7: test
|
||||
2025-06-04 07:21:07 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978504ed0>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:07 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 7 nicht einschalten
|
||||
2025-06-04 07:21:07 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 8: test
|
||||
2025-06-04 07:21:09 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978514410>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:09 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 8 nicht einschalten
|
||||
2025-06-04 07:21:09 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: test
|
||||
2025-06-04 07:21:11 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978516c90>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:11 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 1 nicht einschalten
|
||||
2025-06-04 07:21:11 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 2: test
|
||||
2025-06-04 07:21:13 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978519710>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:13 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 2 nicht einschalten
|
||||
2025-06-04 07:21:13 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 3: test
|
||||
2025-06-04 07:21:15 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978515450>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:15 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 3 nicht einschalten
|
||||
2025-06-04 07:21:15 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 4: test
|
||||
2025-06-04 07:21:17 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd9785075d0>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:17 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 4 nicht einschalten
|
||||
2025-06-04 07:21:17 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 5: test
|
||||
2025-06-04 07:21:19 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978518790>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:19 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 5 nicht einschalten
|
||||
2025-06-04 07:21:19 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 6: test
|
||||
2025-06-04 07:21:21 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97851c910>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:21 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 6 nicht einschalten
|
||||
2025-06-04 07:21:21 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 9: zi
|
||||
2025-06-04 07:21:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.104: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97b7c4090>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:25 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 9 nicht einschalten
|
||||
2025-06-04 07:21:25 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 10: zi
|
||||
2025-06-04 07:21:27 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.104: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97ae53590>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:27 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 10 nicht einschalten
|
||||
2025-06-04 07:21:27 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 11: fee
|
||||
2025-06-04 07:21:29 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.104: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97851dbd0>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:29 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 11 nicht einschalten
|
||||
2025-06-04 07:21:29 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 12: fee
|
||||
2025-06-04 07:21:31 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.104: HTTPConnectionPool(host='192.168.0.104', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97851eb10>, 'Connection to 192.168.0.104 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:31 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 12 nicht einschalten
|
||||
2025-06-04 07:21:31 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 13: e2
|
||||
2025-06-04 07:21:33 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd9785157d0>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:33 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 13 nicht einschalten
|
||||
2025-06-04 07:21:33 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 14: e2
|
||||
2025-06-04 07:21:35 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978505b50>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:35 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 14 nicht einschalten
|
||||
2025-06-04 07:21:35 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 15: test
|
||||
2025-06-04 07:21:37 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97851ef90>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:37 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 15 nicht einschalten
|
||||
2025-06-04 07:21:37 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 16: test
|
||||
2025-06-04 07:21:40 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97851d490>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:40 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Sofort-Job 16 nicht einschalten
|
||||
2025-06-04 07:21:41 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 7: test
|
||||
2025-06-04 07:21:43 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97b7c5c50>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:43 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 7 nicht einschalten
|
||||
2025-06-04 07:21:43 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 8: test
|
||||
2025-06-04 07:21:46 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd978514410>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:46 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 8 nicht einschalten
|
||||
2025-06-04 07:21:46 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: test
|
||||
2025-06-04 07:21:48 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97852c110>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:48 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 1 nicht einschalten
|
||||
2025-06-04 07:21:48 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 2: test
|
||||
2025-06-04 07:21:52 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97852d9d0>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:52 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 2 nicht einschalten
|
||||
2025-06-04 07:21:52 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 3: test
|
||||
2025-06-04 07:21:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Fehler beim einschalten der Tapo-Steckdose 192.168.0.103: HTTPConnectionPool(host='192.168.0.103', port=80): Max retries exceeded with url: /app (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fd97852fa90>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-04 07:21:54 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 3 nicht einschalten
|
||||
2025-06-04 07:21:54 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 4: test
|
||||
|
||||
@ -144,3 +144,4 @@
|
||||
2025-06-04 00:50:43 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-04 00:56:10 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-04 00:56:23 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-04 07:21:04 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
|
||||
@ -245,3 +245,4 @@
|
||||
2025-06-04 00:50:43 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
2025-06-04 00:56:10 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
2025-06-04 00:56:23 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
2025-06-04 07:21:04 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
|
||||
@ -1294,3 +1294,10 @@
|
||||
2025-06-04 00:56:23 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-04 00:56:23 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-04 00:56:23 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-04 07:21:04 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-04 07:21:04 - [startup] startup - [INFO] INFO - 🚀 MYP Platform Backend wird gestartet...
|
||||
2025-06-04 07:21:04 - [startup] startup - [INFO] INFO - 🐍 Python Version: 3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0]
|
||||
2025-06-04 07:21:04 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: posix (linux)
|
||||
2025-06-04 07:21:04 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: /mnt
|
||||
2025-06-04 07:21:04 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-04T07:21:04.322209
|
||||
2025-06-04 07:21:04 - [startup] startup - [INFO] INFO - ==================================================
|
||||
|
||||
@ -25,3 +25,4 @@
|
||||
2025-06-04 00:50:43 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
2025-06-04 00:56:11 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
2025-06-04 00:56:23 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
2025-06-04 07:21:04 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
=================================================================
|
||||
MYP Installation WARNUNGEN Log - 2025-06-04 07:18:35
|
||||
MYP Installation WARNUNGEN Log - 2025-06-04 07:22:23
|
||||
=================================================================
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user