🎉 Feature: Backend Performance Optimization 🌟
This commit is contained in:
@ -119,3 +119,4 @@
|
||||
2025-06-03 13:18:50 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-03 13:23:53 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-03 13:27:14 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-03 14:14:07 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
|
||||
@ -3084,3 +3084,24 @@ WHERE jobs.status = ?) AS anon_1]
|
||||
2025-06-03 13:27:14 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\database\myp.db
|
||||
2025-06-03 13:27:15 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
|
||||
2025-06-03 13:27:15 - [app] app - [INFO] INFO - ✅ Timeout Force-Quit Manager geladen
|
||||
2025-06-03 14:14:06 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\database\myp.db
|
||||
2025-06-03 14:14:08 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
|
||||
2025-06-03 14:14:08 - [app] app - [INFO] INFO - ✅ Timeout Force-Quit Manager geladen
|
||||
2025-06-03 14:14:08 - [app] app - [INFO] INFO - ✅ Zentraler Shutdown-Manager initialisiert
|
||||
2025-06-03 14:14:08 - [app] app - [INFO] INFO - ✅ Error-Recovery-Monitoring gestartet
|
||||
2025-06-03 14:14:08 - [app] app - [INFO] INFO - ✅ System-Control-Manager initialisiert
|
||||
2025-06-03 14:14:08 - [app] app - [WARNING] WARNING - ⚠️ Kiosk-Service nicht gefunden - Kiosk-Funktionen eventuell eingeschränkt
|
||||
2025-06-03 14:14:08 - [app] app - [INFO] INFO - 🔄 Starte Datenbank-Setup und Migrationen...
|
||||
2025-06-03 14:14:09 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
|
||||
2025-06-03 14:14:09 - [app] app - [INFO] INFO - ✅ JobOrder-Tabelle bereits vorhanden
|
||||
2025-06-03 14:14:09 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
|
||||
2025-06-03 14:14:09 - [app] app - [INFO] INFO - ✅ Datenbank-Setup und Migrationen erfolgreich abgeschlossen
|
||||
2025-06-03 14:14:09 - [app] app - [INFO] INFO - 🖨️ Starte automatische Steckdosen-Initialisierung...
|
||||
2025-06-03 14:14:11 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 4, Status: disconnected, Quelle: system
|
||||
2025-06-03 14:14:13 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 5, Status: disconnected, Quelle: system
|
||||
2025-06-03 14:14:13 - [app] app - [INFO] INFO - ✅ Steckdosen-Initialisierung: 0/2 Drucker erfolgreich
|
||||
2025-06-03 14:14:13 - [app] app - [WARNING] WARNING - ⚠️ 2 Drucker konnten nicht initialisiert werden
|
||||
2025-06-03 14:14:13 - [app] app - [INFO] INFO - 🔄 Debug-Modus: Queue Manager deaktiviert für Entwicklung
|
||||
2025-06-03 14:14:13 - [app] app - [INFO] INFO - Job-Scheduler gestartet
|
||||
2025-06-03 14:14:13 - [app] app - [INFO] INFO - Starte Debug-Server auf 0.0.0.0:5000 (HTTP)
|
||||
2025-06-03 14:14:13 - [app] app - [INFO] INFO - Windows-Debug-Modus: Auto-Reload deaktiviert
|
||||
|
||||
@ -123,3 +123,4 @@
|
||||
2025-06-03 13:18:50 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-03 13:23:53 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-03 13:27:14 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-03 14:14:07 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
|
||||
@ -478,3 +478,7 @@
|
||||
2025-06-03 13:27:15 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-03 13:27:15 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback)
|
||||
2025-06-03 13:27:15 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading)
|
||||
2025-06-03 14:14:08 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-03 14:14:08 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-03 14:14:08 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback)
|
||||
2025-06-03 14:14:08 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading)
|
||||
|
||||
@ -119,3 +119,4 @@
|
||||
2025-06-03 13:18:50 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-03 13:23:53 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-03 13:27:14 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-03 14:14:07 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
|
||||
@ -22,3 +22,6 @@
|
||||
2025-06-03 13:18:52 - [database_cleanup] database_cleanup - [INFO] INFO - 🧹 Starte umfassendes Datenbank-Cleanup...
|
||||
2025-06-03 13:18:52 - [database_cleanup] database_cleanup - [INFO] INFO - 📝 Schritt 1: Schließe alle Datenbankverbindungen...
|
||||
2025-06-03 13:18:52 - [database_cleanup] database_cleanup - [INFO] INFO - 🔄 Schließe alle aktiven Datenbankverbindungen...
|
||||
2025-06-03 14:14:09 - [database_cleanup] database_cleanup - [INFO] INFO - 🧹 Starte umfassendes Datenbank-Cleanup...
|
||||
2025-06-03 14:14:09 - [database_cleanup] database_cleanup - [INFO] INFO - 📝 Schritt 1: Schließe alle Datenbankverbindungen...
|
||||
2025-06-03 14:14:09 - [database_cleanup] database_cleanup - [INFO] INFO - 🔄 Schließe alle aktiven Datenbankverbindungen...
|
||||
|
||||
@ -116,3 +116,4 @@
|
||||
2025-06-03 13:18:51 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-03 13:23:54 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-03 13:27:15 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-03 14:14:08 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
|
||||
@ -10,3 +10,7 @@
|
||||
2025-06-03 13:18:52 - [error_recovery] error_recovery - [INFO] INFO - 🔍 Error-Monitoring gestartet
|
||||
2025-06-03 13:18:52 - [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-03 13:18:52 - [error_recovery] error_recovery - [INFO] INFO - 🔧 Führe Recovery-Aktion aus: reset_database
|
||||
2025-06-03 14:14:08 - [error_recovery] error_recovery - [INFO] INFO - 🛡️ Error-Recovery-Manager initialisiert
|
||||
2025-06-03 14:14:08 - [error_recovery] error_recovery - [INFO] INFO - 🔍 Error-Monitoring gestartet
|
||||
2025-06-03 14:14:09 - [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-03 14:14:09 - [error_recovery] error_recovery - [INFO] INFO - 🔧 Führe Recovery-Aktion aus: reset_database
|
||||
|
||||
@ -238,3 +238,5 @@
|
||||
2025-06-03 13:23:54 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-03 13:27:15 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-03 13:27:15 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-03 14:14:08 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-03 14:14:08 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
|
||||
@ -236,3 +236,5 @@
|
||||
2025-06-03 13:23:54 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-03 13:27:15 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-03 13:27:15 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-03 14:14:08 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-03 14:14:08 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
|
||||
@ -1,68 +1,76 @@
|
||||
=================================================================
|
||||
MYP Installation DEBUG Log - 2025-06-03 13:52:05
|
||||
MYP Installation DEBUG Log - 2025-06-03 14:11:46
|
||||
=================================================================
|
||||
|
||||
[2025-06-03 13:52:05] DEBUG von setup.sh:449
|
||||
[2025-06-03 14:11:46] DEBUG von setup.sh:449
|
||||
Debian erkannt über /etc/debian_version: 12.11
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:05] DEBUG von setup.sh:517
|
||||
[2025-06-03 14:11:46] DEBUG von setup.sh:517
|
||||
Kein Raspberry Pi erkannt. Hardware-Info:
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:05] DEBUG von setup.sh:518
|
||||
[2025-06-03 14:11:47] DEBUG von setup.sh:518
|
||||
- Device Tree: nicht verfügbar
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:05] DEBUG von setup.sh:519
|
||||
[2025-06-03 14:11:47] DEBUG von setup.sh:519
|
||||
- CPU Hardware: nicht verfügbar
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:06] DEBUG von setup.sh:559
|
||||
[2025-06-03 14:11:47] DEBUG von setup.sh:559
|
||||
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-03 13:52:06] DEBUG von setup.sh:615
|
||||
[2025-06-03 14:11:47] DEBUG von setup.sh:615
|
||||
DNS-Test Details: Teste DNS für 8.8.8.8: Erfolg mit nslookup.
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:06] DEBUG von setup.sh:716
|
||||
[2025-06-03 14:11:47] DEBUG von setup.sh:716
|
||||
Externe IP ermittelt über ifconfig.me: 163.116.178.31
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1221
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1221
|
||||
sysctl-Konfiguration erstellt: /etc/sysctl.d/99-myp-security.conf
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1330
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1330
|
||||
Überspringe system-weites sysctl -p (zu riskant)
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1356
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1356
|
||||
systemd-networkd nicht aktiv - überspringe
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1382
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1382
|
||||
NetworkManager nicht aktiv - überspringe
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1388
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1388
|
||||
IPv6 Einträge in /etc/hosts auskommentiert
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1404
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1404
|
||||
Alternative sysctl-Anwendung:
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1405
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1405
|
||||
- Manuell: sysctl -p /etc/sysctl.d/99-myp-security.conf
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1406
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1406
|
||||
- Automatisch: Beim nächsten Neustart aktiv
|
||||
---
|
||||
|
||||
[2025-06-03 13:52:15] DEBUG von setup.sh:1407
|
||||
[2025-06-03 14:12:01] DEBUG von setup.sh:1407
|
||||
- Verifikation: sysctl net.ipv6.conf.all.disable_ipv6
|
||||
---
|
||||
|
||||
[2025-06-03 14:13:51] DEBUG von setup.sh:1713
|
||||
SSL-Verzeichnis erstellt: /usr/local/share/ca-certificates/myp
|
||||
---
|
||||
|
||||
[2025-06-03 14:13:57] DEBUG von setup.sh:1821
|
||||
SSL-Konfiguration abgeschlossen ohne hängende Prozesse
|
||||
---
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
=================================================================
|
||||
MYP Installation FEHLER Log - 2025-06-03 13:52:05
|
||||
MYP Installation FEHLER Log - 2025-06-03 14:11:46
|
||||
=================================================================
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
=================================================================
|
||||
MYP Installation WARNUNGEN Log - 2025-06-03 13:52:05
|
||||
MYP Installation WARNUNGEN Log - 2025-06-03 14:11:46
|
||||
=================================================================
|
||||
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
=================================================================
|
||||
MYP Installation Log - 2025-06-03 13:52:05
|
||||
MYP Installation Log - 2025-06-03 14:11:46
|
||||
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
|
||||
=================================================================
|
||||
|
||||
[0;32m[2025-06-03 13:52:05] === MODUS: ROBUSTE ABHÄNGIGKEITEN-INSTALLATION FÜR MANUELLES TESTEN ===[0m
|
||||
[0;32m[2025-06-03 13:52:05] ✅ Root-Berechtigung bestätigt[0m
|
||||
[0;32m[2025-06-03 13:52:05] === SYSTEM-RESSOURCEN PRÜFUNG ===[0m
|
||||
[0;32m[2025-06-03 14:11:46] === MODUS: ROBUSTE ABHÄNGIGKEITEN-INSTALLATION FÜR MANUELLES TESTEN ===[0m
|
||||
[0;32m[2025-06-03 14:11:46] ✅ Root-Berechtigung bestätigt[0m
|
||||
[0;32m[2025-06-03 14:11:46] === SYSTEM-RESSOURCEN PRÜFUNG ===[0m
|
||||
[0;35m[FORTSCHRITT] Prüfe RAM...[0m
|
||||
[0;35m[FORTSCHRITT] Verfügbarer RAM: 24031MB[0m
|
||||
[0;36m[ERFOLG] ✅ Ausreichend RAM verfügbar (24031MB)[0m
|
||||
@ -16,10 +16,10 @@ System: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1
|
||||
[0;35m[FORTSCHRITT] Prüfe CPU...[0m
|
||||
[0;35m[FORTSCHRITT] CPU: 8 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-03 13:52:05] ✅ System-Ressourcen-Prüfung abgeschlossen[0m
|
||||
[0;32m[2025-06-03 14:11:46] ✅ 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-03 13:52:05] ✅ Debian/Raspbian-basiertes System erkannt (Version: 12.11)[0m
|
||||
[0;32m[2025-06-03 14:11:46] ✅ 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
|
||||
@ -31,7 +31,7 @@ System: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1
|
||||
[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-03 13:52:06] ✅ System-Analyse abgeschlossen[0m
|
||||
[0;32m[2025-06-03 14:11:47] ✅ 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
|
||||
@ -40,13 +40,13 @@ System: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1
|
||||
[0;35m[FORTSCHRITT] Ermittle externe IP-Adresse...[0m
|
||||
[0;34m[INFO] 🌐 Externe IP: 163.116.178.31[0m
|
||||
[0;34m[DEBUG] Externe IP ermittelt über ifconfig.me: 163.116.178.31[0m
|
||||
[0;32m[2025-06-03 13:52:06] === KONFIGURIERE HOSTNAME ===[0m
|
||||
[0;32m[2025-06-03 13:52:06] ✅ Hostname bereits korrekt: 'raspberrypi'[0m
|
||||
[0;32m[2025-06-03 13:52:06] ✅ Hostname-Auflösung funktioniert: raspberrypi -> 127.0.1.1[0m
|
||||
[0;32m[2025-06-03 13:52:06] === ROBUSTE SYSTEM-UPDATE ===[0m
|
||||
[0;32m[2025-06-03 14:11:47] === KONFIGURIERE HOSTNAME ===[0m
|
||||
[0;32m[2025-06-03 14:11:47] ✅ Hostname bereits korrekt: 'raspberrypi'[0m
|
||||
[0;32m[2025-06-03 14:11:47] ✅ Hostname-Auflösung funktioniert: raspberrypi -> 127.0.1.1[0m
|
||||
[0;32m[2025-06-03 14:11:47] === ROBUSTE SYSTEM-UPDATE ===[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere APT für bessere Zuverlässigkeit...[0m
|
||||
[0;35m[FORTSCHRITT] Validiere APT-Repositories...[0m
|
||||
[0;32m[2025-06-03 13:52:06] ✅ Source-Repositories deaktiviert (nicht benötigt)[0m
|
||||
[0;32m[2025-06-03 14:11:47] ✅ Source-Repositories deaktiviert (nicht benötigt)[0m
|
||||
[0;35m[FORTSCHRITT] Aktualisiere Paketlisten mit Retry...[0m
|
||||
[0;35m[FORTSCHRITT] Führe System-Upgrade durch...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere essenzielle System-Tools...[0m
|
||||
@ -68,8 +68,8 @@ System: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: dbus[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: systemd-timesyncd[0m
|
||||
[0;35m[FORTSCHRITT] Synchronisiere Systemzeit...[0m
|
||||
[0;32m[2025-06-03 13:52:15] ✅ Robustes System-Update abgeschlossen[0m
|
||||
[0;32m[2025-06-03 13:52:15] === KONFIGURIERE ROBUSTE NETZWERK-SICHERHEIT ===[0m
|
||||
[0;32m[2025-06-03 14:12:01] ✅ Robustes System-Update abgeschlossen[0m
|
||||
[0;32m[2025-06-03 14:12:01] === KONFIGURIERE ROBUSTE NETZWERK-SICHERHEIT ===[0m
|
||||
[0;35m[FORTSCHRITT] Deaktiviere IPv6 (robust)...[0m
|
||||
[0;35m[FORTSCHRITT] Deaktiviere IPv6 in GRUB...[0m
|
||||
[0;34m[INFO] IPv6 bereits in GRUB deaktiviert[0m
|
||||
@ -84,18 +84,18 @@ System: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1
|
||||
[0;34m[DEBUG] systemd-networkd nicht aktiv - überspringe[0m
|
||||
[0;34m[DEBUG] NetworkManager nicht aktiv - überspringe[0m
|
||||
[0;34m[DEBUG] IPv6 Einträge in /etc/hosts auskommentiert[0m
|
||||
[0;32m[2025-06-03 13:52:15] ✅ Robuste Netzwerk-Sicherheit konfiguriert:[0m
|
||||
[0;32m[2025-06-03 13:52:15] 🚫 IPv6 Deaktivierung konfiguriert[0m
|
||||
[0;32m[2025-06-03 13:52:15] 🛡️ Netzwerk-Sicherheitsregeln gesetzt[0m
|
||||
[0;32m[2025-06-03 13:52:15] 🔒 Basis-Firewall-Schutz aktiviert[0m
|
||||
[0;32m[2025-06-03 13:52:15] 📝 Sysctl-Konfiguration erstellt: /etc/sysctl.d/99-myp-security.conf[0m
|
||||
[0;32m[2025-06-03 13:52:15] 🔧 Netzwerk-Services entsprechend konfiguriert[0m
|
||||
[0;32m[2025-06-03 13:52:15] ⚙️ Einstellungen werden beim nächsten Boot aktiv[0m
|
||||
[0;32m[2025-06-03 14:12:01] ✅ Robuste Netzwerk-Sicherheit konfiguriert:[0m
|
||||
[0;32m[2025-06-03 14:12:01] 🚫 IPv6 Deaktivierung konfiguriert[0m
|
||||
[0;32m[2025-06-03 14:12:01] 🛡️ Netzwerk-Sicherheitsregeln gesetzt[0m
|
||||
[0;32m[2025-06-03 14:12:01] 🔒 Basis-Firewall-Schutz aktiviert[0m
|
||||
[0;32m[2025-06-03 14:12:01] 📝 Sysctl-Konfiguration erstellt: /etc/sysctl.d/99-myp-security.conf[0m
|
||||
[0;32m[2025-06-03 14:12:01] 🔧 Netzwerk-Services entsprechend konfiguriert[0m
|
||||
[0;32m[2025-06-03 14:12:01] ⚙️ Einstellungen werden beim nächsten Boot aktiv[0m
|
||||
[0;34m[DEBUG] Alternative sysctl-Anwendung:[0m
|
||||
[0;34m[DEBUG] - Manuell: sysctl -p /etc/sysctl.d/99-myp-security.conf[0m
|
||||
[0;34m[DEBUG] - Automatisch: Beim nächsten Neustart aktiv[0m
|
||||
[0;34m[DEBUG] - Verifikation: sysctl net.ipv6.conf.all.disable_ipv6[0m
|
||||
[0;32m[2025-06-03 13:52:15] === ROBUSTE PYTHON-INSTALLATION ===[0m
|
||||
[0;32m[2025-06-03 14:12:01] === ROBUSTE PYTHON-INSTALLATION ===[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Python 3 und Build-Abhängigkeiten...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: python3[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: python3-pip[0m
|
||||
@ -114,27 +114,41 @@ System: Linux raspberrypi 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: zlib1g-dev[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: sqlite3[0m
|
||||
[0;35m[FORTSCHRITT] Validiere Python-Installation...[0m
|
||||
[0;32m[2025-06-03 13:52:22] ✅ Python Version: 3.11.2[0m
|
||||
[0;32m[2025-06-03 14:12:08] ✅ Python Version: 3.11.2[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere pip für bessere Zuverlässigkeit...[0m
|
||||
[0;35m[FORTSCHRITT] Erstelle systemweite pip-Konfiguration...[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere pip für alle Benutzer...[0m
|
||||
[0;32m[2025-06-03 13:52:22] ✅ pip konfiguriert für Benutzer: user[0m
|
||||
[0;32m[2025-06-03 14:12:08] ✅ pip konfiguriert für Benutzer: user[0m
|
||||
[0;35m[FORTSCHRITT] Aktualisiere pip mit Retry...[0m
|
||||
[0;32m[2025-06-03 13:52:23] ✅ pip Version: 25.1.1[0m
|
||||
[0;32m[2025-06-03 13:52:23] ✅ Robuste Python-Umgebung installiert[0m
|
||||
[0;32m[2025-06-03 13:52:23] === ROBUSTE NODE.JS UND NPM INSTALLATION ===[0m
|
||||
[0;32m[2025-06-03 14:12:10] ✅ pip Version: 25.1.1[0m
|
||||
[0;32m[2025-06-03 14:12:10] ✅ Robuste Python-Umgebung installiert[0m
|
||||
[0;32m[2025-06-03 14:12:10] === ROBUSTE NODE.JS UND NPM INSTALLATION ===[0m
|
||||
[0;35m[FORTSCHRITT] Bereinige alte Node.js-Installationen...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Node.js mit Fallback-Strategie...[0m
|
||||
[0;35m[FORTSCHRITT] Verwende Debian Repository als Fallback...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: nodejs npm[0m
|
||||
[0;32m[2025-06-03 13:53:55] ✅ Node.js via Debian Repository installiert[0m
|
||||
[0;32m[2025-06-03 14:13:47] ✅ Node.js via Debian Repository installiert[0m
|
||||
[0;35m[FORTSCHRITT] Validiere Node.js Installation...[0m
|
||||
[0;32m[2025-06-03 13:53:55] ✅ Node.js Version: v18.19.0[0m
|
||||
[0;32m[2025-06-03 13:53:56] ✅ npm Version: 9.2.0[0m
|
||||
[0;32m[2025-06-03 14:13:47] ✅ Node.js Version: v18.19.0[0m
|
||||
[0;32m[2025-06-03 14:13:48] ✅ npm Version: 9.2.0[0m
|
||||
[0;35m[FORTSCHRITT] Optimiere npm-Konfiguration...[0m
|
||||
[0;32m[2025-06-03 13:53:57] ✅ Node.js und npm erfolgreich installiert[0m
|
||||
[0;32m[2025-06-03 13:53:57] === ROBUSTE SSL-ZERTIFIKATE KONFIGURATION ===[0m
|
||||
[0;32m[2025-06-03 14:13:50] ✅ Node.js und npm erfolgreich installiert[0m
|
||||
[0;32m[2025-06-03 14:13:50] === TIMEOUT-GESICHERTE SSL-ZERTIFIKATE KONFIGURATION ===[0m
|
||||
[0;35m[FORTSCHRITT] Installiere SSL-Grundkomponenten...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Pakete: ca-certificates openssl[0m
|
||||
[0;35m[FORTSCHRITT] Aktualisiere CA-Zertifikate...[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Mercedes Corporate Zertifikate (robust)...[0m
|
||||
[0;35m[FORTSCHRITT] Aktualisiere CA-Zertifikate (timeout-gesichert)...[0m
|
||||
[0;36m[ERFOLG] ✅ CA-Zertifikate erfolgreich aktualisiert[0m
|
||||
[0;34m[DEBUG] SSL-Verzeichnis erstellt: /usr/local/share/ca-certificates/myp[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Mercedes Corporate Zertifikate (timeout-gesichert)...[0m
|
||||
[0;35m[FORTSCHRITT] Lade CA-Zertifikate nach Mercedes-Import neu (timeout-gesichert)...[0m
|
||||
[0;36m[ERFOLG] ✅ Mercedes-Zertifikate erfolgreich in CA-Store integriert[0m
|
||||
[0;35m[FORTSCHRITT] Konfiguriere SSL-Umgebungsvariablen...[0m
|
||||
[0;35m[FORTSCHRITT] Validiere SSL-Konfiguration...[0m
|
||||
[0;32m[2025-06-03 14:13:55] ✅ SSL-Zertifikate verfügbar: 144 CA-Zertifikate[0m
|
||||
[0;35m[FORTSCHRITT] Finalisiere SSL-Konfiguration...[0m
|
||||
[0;36m[ERFOLG] ✅ Finale CA-Zertifikate Integration abgeschlossen[0m
|
||||
[0;32m[2025-06-03 14:13:57] ✅ SSL-Zertifikate timeout-gesichert konfiguriert[0m
|
||||
[0;34m[DEBUG] SSL-Konfiguration abgeschlossen ohne hängende Prozesse[0m
|
||||
[0;32m[2025-06-03 14:13:57] === ROBUSTE PYTHON-PAKETE INSTALLATION ===[0m
|
||||
[0;35m[FORTSCHRITT] Installiere Python-Pakete mit verbesserter Strategie...[0m
|
||||
[0;35m[FORTSCHRITT] Versuche direkte requirements.txt Installation...[0m
|
||||
|
||||
@ -118,3 +118,4 @@
|
||||
2025-06-03 13:18:52 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-03 13:23:54 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-03 13:27:15 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-03 14:14:08 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
|
||||
@ -3311,3 +3311,19 @@
|
||||
2025-06-03 13:27:40 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 5/6: 192.168.0.102
|
||||
2025-06-03 13:27:46 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 6/6: 192.168.0.105
|
||||
2025-06-03 13:27:52 - [printer_monitor] printer_monitor - [INFO] INFO - ✅ Steckdosen-Erkennung abgeschlossen: 0/6 Steckdosen gefunden in 36.0s
|
||||
2025-06-03 14:14:07 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-03 14:14:07 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-03 14:14:09 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Starte automatische Tapo-Steckdosenerkennung...
|
||||
2025-06-03 14:14:09 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Teste 6 Standard-IPs aus der Konfiguration
|
||||
2025-06-03 14:14:09 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 1/6: 192.168.0.103
|
||||
2025-06-03 14:14:09 - [printer_monitor] printer_monitor - [INFO] INFO - 🚀 Starte Steckdosen-Initialisierung beim Programmstart...
|
||||
2025-06-03 14:14:11 - [printer_monitor] printer_monitor - [WARNING] WARNING - ❌ Tapo P110 (192.168.0.103): Steckdose konnte nicht ausgeschaltet werden
|
||||
2025-06-03 14:14:13 - [printer_monitor] printer_monitor - [WARNING] WARNING - ❌ Tapo P110 (192.168.0.104): Steckdose konnte nicht ausgeschaltet werden
|
||||
2025-06-03 14:14:13 - [printer_monitor] printer_monitor - [INFO] INFO - 🎯 Steckdosen-Initialisierung abgeschlossen: 0/2 erfolgreich
|
||||
2025-06-03 14:14:15 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 2/6: 192.168.0.104
|
||||
2025-06-03 14:14:21 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 3/6: 192.168.0.100
|
||||
2025-06-03 14:14:22 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-03 14:14:22 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Prüfe Status von 2 aktiven Druckern...
|
||||
2025-06-03 14:14:24 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-03 14:14:24 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Prüfe Status von 2 aktiven Druckern...
|
||||
2025-06-03 14:14:27 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 4/6: 192.168.0.101
|
||||
|
||||
@ -6712,3 +6712,6 @@
|
||||
2025-06-02 15:31:02 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 2 Drucker
|
||||
2025-06-02 15:31:02 - [printers] printers - [INFO] INFO - ✅ API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 1.42ms
|
||||
2025-06-03 13:31:45 - [printers] printers - [INFO] INFO - Schnelles Laden abgeschlossen: 6 Drucker geladen (ohne Status-Check)
|
||||
2025-06-03 14:14:22 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
2025-06-03 14:14:24 - [printers] printers - [INFO] INFO - Schnelles Laden abgeschlossen: 6 Drucker geladen (ohne Status-Check)
|
||||
2025-06-03 14:14:24 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
|
||||
@ -29970,3 +29970,31 @@
|
||||
2025-06-03 13:37: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 0x000002446CDC5AE0>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 13:37:15 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 4 nicht einschalten
|
||||
2025-06-03 13:37:15 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 5: test
|
||||
2025-06-03 14:14:07 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-03 14:14:13 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
|
||||
2025-06-03 14:14:13 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
|
||||
2025-06-03 14:14:13 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 7: test
|
||||
2025-06-03 14:14: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 0x000001B51E3C4F50>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:15 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 7 nicht einschalten
|
||||
2025-06-03 14:14:15 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 8: test
|
||||
2025-06-03 14:14: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 0x000001B51E3DDBA0>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:17 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 8 nicht einschalten
|
||||
2025-06-03 14:14:17 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 1: test
|
||||
2025-06-03 14:14: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 0x000001B51F945350>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:19 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 1 nicht einschalten
|
||||
2025-06-03 14:14:19 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 2: test
|
||||
2025-06-03 14:14: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 0x000001B51F958050>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:21 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 2 nicht einschalten
|
||||
2025-06-03 14:14:21 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 3: test
|
||||
2025-06-03 14:14:24 - [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 0x000001B51E4B4D10>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:24 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 3 nicht einschalten
|
||||
2025-06-03 14:14:24 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 4: test
|
||||
2025-06-03 14:14:26 - [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 0x000001B51E457130>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:26 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 4 nicht einschalten
|
||||
2025-06-03 14:14:26 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 5: test
|
||||
2025-06-03 14:14:28 - [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 0x000001B51E4B4D10>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:28 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 5 nicht einschalten
|
||||
2025-06-03 14:14:28 - [scheduler] scheduler - [INFO] INFO - 🚀 Starte geplanten Job 6: test
|
||||
2025-06-03 14:14:30 - [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 0x000001B51E4B4F30>, 'Connection to 192.168.0.103 timed out. (connect timeout=2)'))
|
||||
2025-06-03 14:14:30 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose für Job 6 nicht einschalten
|
||||
2025-06-03 14:14:30 - [scheduler] scheduler - [INFO] INFO - ⚡ Starte Sofort-Job 9: zi
|
||||
|
||||
@ -118,3 +118,4 @@
|
||||
2025-06-03 13:18:52 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-03 13:23:54 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-03 13:27:15 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-03 14:14:08 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
|
||||
@ -208,3 +208,4 @@
|
||||
2025-06-03 13:24:49 - [shutdown_manager] shutdown_manager - [INFO] INFO - ✅ Koordiniertes Shutdown abgeschlossen in 0.0s
|
||||
2025-06-03 13:24:49 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🏁 System wird beendet...
|
||||
2025-06-03 13:27:15 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
2025-06-03 14:14:08 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
|
||||
@ -1070,3 +1070,12 @@
|
||||
2025-06-03 13:27:15 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-03 13:27:15 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-03 13:27:15 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - 🚀 MYP Platform Backend wird gestartet...
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - 🐍 Python Version: 3.13.3 (tags/v3.13.3:6280bb5, Apr 8 2025, 14:47:33) [MSC v.1943 64 bit (AMD64)]
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-03T14:14:08.701687
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-03 14:14:08 - [startup] startup - [INFO] INFO - ==================================================
|
||||
|
||||
@ -1,3 +1,4 @@
|
||||
2025-06-02 15:18:16 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
2025-06-02 15:29:07 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
2025-06-03 13:18:52 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
2025-06-03 14:14:08 - [system_control] system_control - [INFO] INFO - 🔧 System-Control-Manager initialisiert
|
||||
|
||||
@ -507,3 +507,7 @@
|
||||
2025-06-03 13:27:14 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-03 13:27:14 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-03 13:27:14 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
2025-06-03 14:14:06 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
|
||||
2025-06-03 14:14:06 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-03 14:14:06 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-03 14:14:06 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
|
||||
Reference in New Issue
Block a user