core/Projektarbeit-MYP
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

📚 Improved log file structure & organization 🚀

Browse Source
This commit is contained in:
Till Tomczak
2025-06-11 08:42:54 +02:00
parent b1bcb12e3d
commit 23d6a8c6d0
14 changed files with 79 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
backend/instance/printer_manager.db
View File

Binary file not shown.

21
backend/logs/app/app.log
View File

@ -3843,3 +3843,24 @@ AttributeError: module 'os' has no attribute 'geteuid'. Did you mean: 'getpid'?
2025-06-10 13:30:33 - [app] app - [ERROR] ERROR - ❌ SSL-Zertifikat-Erstellung fehlgeschlagen: [WinError 2] Das System kann die angegebene Datei nicht finden
2025-06-10 13:30:33 - [app] app - [ERROR] ERROR - ❌ Netzwerk-Fehler: [WinError 2] Das System kann die angegebene Datei nicht finden
2025-06-10 13:30:33 - [app] app - [INFO] INFO - ✅ Cleanup abgeschlossen
2025-06-11 08:42:18 - [app] app - [WARNING] WARNING - DatabaseCleanupManager nicht verfügbar - Fallback auf Legacy-Cleanup
2025-06-11 08:42:18 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\instance\printer_manager.db
2025-06-11 08:42:19 - [app] app - [INFO] INFO - SQLite für Raspberry Pi optimiert (reduzierte Cache-Größe, SD-Karten I/O)
2025-06-11 08:42:19 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
2025-06-11 08:42:20 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
2025-06-11 08:42:20 - [app] app - [INFO] INFO - [START] Server startet auf 0.0.0.0:5000
2025-06-11 08:42:23 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/static/icons/icon-192.png
2025-06-11 08:42:26 - [app] app - [ERROR] ERROR - Fehler beim Laden des Benutzers 1: (sqlite3.InterfaceError) bad parameter or other API misuse
[SQL: SELECT users.id AS users_id, users.email AS users_email, users.username AS users_username, users.password_hash AS users_password_hash, users.name AS users_name, users.role AS users_role, users.active AS users_active, users.created_at AS users_created_at, users.last_login AS users_last_login, users.updated_at AS users_updated_at, users.settings AS users_settings, users.last_activity AS users_last_activity, users.department AS users_department, users.position AS users_position, users.phone AS users_phone, users.bio AS users_bio, users.theme_preference AS users_theme_preference, users.language_preference AS users_language_preference, users.email_notifications AS users_email_notifications, users.browser_notifications AS users_browser_notifications, users.dashboard_layout AS users_dashboard_layout, users.compact_mode AS users_compact_mode, users.show_completed_jobs AS users_show_completed_jobs, users.auto_refresh_interval AS users_auto_refresh_interval, users.auto_logout_timeout AS users_auto_logout_timeout
FROM users
WHERE users.id = ?
LIMIT ? OFFSET ?]
[parameters: (1, 1, 0)]
(Background on this error at: https://sqlalche.me/e/20/rvf5)
2025-06-11 08:42:26 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/static/icons/icon-192.png
2025-06-11 08:42:38 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 1, Status: disconnected, Quelle: system
2025-06-11 08:42:38 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/api/jobs
2025-06-11 08:42:38 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/api/printers
2025-06-11 08:42:38 - [app] app - [INFO] INFO - Not Found (404): http://127.0.0.1:5000/static/icons/icon-192.png
2025-06-11 08:42:41 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 2, Status: disconnected, Quelle: system
2025-06-11 08:42:43 - [app] app - [INFO] INFO - Steckdosen-Status geloggt: Drucker 3, Status: disconnected, Quelle: system

2
backend/logs/auth/auth.log
View File

@ -27,3 +27,5 @@
2025-06-10 10:02:16 - [auth] auth - [WARNING] WARNING - Fehlgeschlagener Login-Versuch für Benutzer admin@example.com
2025-06-10 10:02:24 - [auth] auth - [WARNING] WARNING - JSON-Parsing fehlgeschlagen: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand.
2025-06-10 10:02:24 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich erfolgreich angemeldet
2025-06-11 08:42:24 - [auth] auth - [WARNING] WARNING - JSON-Parsing fehlgeschlagen: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand.
2025-06-11 08:42:25 - [auth] auth - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich erfolgreich angemeldet

1
backend/logs/permissions/permissions.log
View File

@ -55,3 +55,4 @@
2025-06-10 13:10:47 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
2025-06-10 13:11:47 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
2025-06-10 13:30:33 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
2025-06-11 08:42:19 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert

11
backend/logs/printer_monitor/printer_monitor.log
View File

@ -547,3 +547,14 @@
2025-06-10 13:11:47 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
2025-06-10 13:30:33 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
2025-06-10 13:30:33 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
2025-06-11 08:42:19 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
2025-06-11 08:42:19 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
2025-06-11 08:42:26 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
2025-06-11 08:42:26 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Prüfe Status von 6 aktiven Druckern...
2025-06-11 08:42:35 - [printer_monitor] printer_monitor - [WARNING] WARNING - 🔌 Tapo P110 (192.168.0.102): UNREACHABLE (Ping fehlgeschlagen)
2025-06-11 08:42:35 - [printer_monitor] printer_monitor - [WARNING] WARNING - 🔌 Tapo P110 (192.168.0.106): UNREACHABLE (Ping fehlgeschlagen)
2025-06-11 08:42:35 - [printer_monitor] printer_monitor - [WARNING] WARNING - 🔌 Tapo P110 (192.168.0.104): UNREACHABLE (Ping fehlgeschlagen)
2025-06-11 08:42:35 - [printer_monitor] printer_monitor - [WARNING] WARNING - 🔌 Tapo P110 (192.168.0.101): UNREACHABLE (Ping fehlgeschlagen)
2025-06-11 08:42:35 - [printer_monitor] printer_monitor - [WARNING] WARNING - 🔌 Tapo P110 (192.168.0.103): UNREACHABLE (Ping fehlgeschlagen)
2025-06-11 08:42:35 - [printer_monitor] printer_monitor - [WARNING] WARNING - 🔌 Tapo P110 (192.168.0.100): UNREACHABLE (Ping fehlgeschlagen)
2025-06-11 08:42:35 - [printer_monitor] printer_monitor - [INFO] INFO - ✅ Status-Update abgeschlossen für 6 Drucker

3
backend/logs/printers/printers.log
View File

@ -312,3 +312,6 @@
2025-06-10 10:02:26 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
2025-06-10 10:02:35 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 6 Drucker
2025-06-10 10:02:35 - [printers] printers - [INFO] INFO - [OK] API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 9039.95ms
2025-06-11 08:42:26 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
2025-06-11 08:42:35 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 6 Drucker
2025-06-11 08:42:35 - [printers] printers - [INFO] INFO - [OK] API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 9034.14ms

11
backend/logs/queue_manager/queue_manager.log
View File

@ -262,3 +262,14 @@
2025-06-10 10:02:43 - [queue_manager] queue_manager - [INFO] INFO - 🛑 Shutdown-Signal empfangen - beende Monitor-Loop
2025-06-10 10:02:43 - [queue_manager] queue_manager - [INFO] INFO - 🔚 Monitor-Loop beendet
2025-06-10 10:02:43 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestoppt
2025-06-11 08:42:20 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Initialisiere neuen Queue-Manager...
2025-06-11 08:42:20 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Zentrale Shutdown-Verwaltung erkannt - deaktiviere lokale Signal-Handler
2025-06-11 08:42:20 - [queue_manager] queue_manager - [INFO] INFO - 🚀 Starte Printer Queue Manager...
2025-06-11 08:42:20 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Queue-Überwachung gestartet (Intervall: 120 Sekunden)
2025-06-11 08:42:20 - [queue_manager] queue_manager - [INFO] INFO - ✅ Printer Queue Manager gestartet
2025-06-11 08:42:20 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestartet
2025-06-11 08:42:44 - [queue_manager] queue_manager - [INFO] INFO - 🔄 Stoppe Queue-Manager...
2025-06-11 08:42:44 - [queue_manager] queue_manager - [INFO] INFO - ⏳ Warte auf Monitor-Thread...
2025-06-11 08:42:44 - [queue_manager] queue_manager - [INFO] INFO - 🛑 Shutdown-Signal empfangen - beende Monitor-Loop
2025-06-11 08:42:44 - [queue_manager] queue_manager - [INFO] INFO - 🔚 Monitor-Loop beendet
2025-06-11 08:42:44 - [queue_manager] queue_manager - [INFO] INFO - ✅ Queue-Manager erfolgreich gestoppt

3
backend/logs/scheduler/scheduler.log
View File

@ -118,3 +118,6 @@
2025-06-10 13:10:47 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
2025-06-10 13:11:47 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
2025-06-10 13:30:33 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
2025-06-11 08:42:19 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
2025-06-11 08:42:20 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
2025-06-11 08:42:20 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet

1
backend/logs/security/security.log
View File

@ -55,3 +55,4 @@
2025-06-10 13:10:47 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
2025-06-10 13:11:47 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
2025-06-10 13:30:33 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
2025-06-11 08:42:19 - [security] security - [INFO] INFO - 🔒 Security System initialisiert

9
backend/logs/startup/startup.log
View File

@ -429,3 +429,12 @@
2025-06-10 13:30:33 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
2025-06-10 13:30:33 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
2025-06-10 13:30:33 - [startup] startup - [INFO] INFO - ==================================================
2025-06-11 08:42:19 - [startup] startup - [INFO] INFO - ==================================================
2025-06-11 08:42:19 - [startup] startup - [INFO] INFO - [START] MYP Platform Backend wird gestartet...
2025-06-11 08:42:19 - [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-11 08:42:19 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
2025-06-11 08:42:19 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
2025-06-11 08:42:19 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-11T08:42:19.839775
2025-06-11 08:42:19 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
2025-06-11 08:42:19 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
2025-06-11 08:42:19 - [startup] startup - [INFO] INFO - ==================================================

4
backend/logs/tapo_control/tapo_control.log
View File

@ -23,3 +23,7 @@
2025-06-10 10:02:38 - [tapo_control] tapo_control - [WARNING] WARNING - ⚠️ Tapo-Steckdose 192.168.0.104 nicht erreichbar
2025-06-10 10:02:40 - [tapo_control] tapo_control - [WARNING] WARNING - ⚠️ Tapo-Steckdose 192.168.0.106 nicht erreichbar
2025-06-10 10:02:40 - [tapo_control] tapo_control - [INFO] INFO - Dashboard geladen: 6 Steckdosen, 0 online
2025-06-11 08:42:36 - [tapo_control] tapo_control - [INFO] INFO - Tapo Dashboard aufgerufen von Benutzer: Administrator
2025-06-11 08:42:38 - [tapo_control] tapo_control - [WARNING] WARNING - ⚠️ Tapo-Steckdose 192.168.0.100 nicht erreichbar
2025-06-11 08:42:41 - [tapo_control] tapo_control - [WARNING] WARNING - ⚠️ Tapo-Steckdose 192.168.0.101 nicht erreichbar
2025-06-11 08:42:43 - [tapo_control] tapo_control - [WARNING] WARNING - ⚠️ Tapo-Steckdose 192.168.0.102 nicht erreichbar

7
backend/logs/tapo_controller/tapo_controller.log
View File

@ -292,3 +292,10 @@
2025-06-10 13:30:20 - [tapo_controller] tapo_controller - [INFO] INFO - 🔄 teste 6 standard-ips aus der konfiguration
2025-06-10 13:30:20 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 1/6: 192.168.0.103
2025-06-10 13:30:33 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo controller initialisiert
2025-06-11 08:42:19 - [tapo_controller] tapo_controller - [INFO] INFO - ✅ tapo controller initialisiert
2025-06-11 08:42:21 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 starte automatische tapo-steckdosenerkennung...
2025-06-11 08:42:21 - [tapo_controller] tapo_controller - [INFO] INFO - 🔄 teste 6 standard-ips aus der konfiguration
2025-06-11 08:42:21 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 1/6: 192.168.0.103
2025-06-11 08:42:27 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 2/6: 192.168.0.104
2025-06-11 08:42:33 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 3/6: 192.168.0.100
2025-06-11 08:42:39 - [tapo_controller] tapo_controller - [INFO] INFO - 🔍 teste ip 4/6: 192.168.0.101

2
backend/logs/user/user.log
View File

@ -93,3 +93,5 @@
2025-06-09 19:32:06 - [user] user - [INFO] INFO - User admin retrieved settings via API
2025-06-09 19:32:13 - [user] user - [INFO] INFO - User admin retrieved settings via API
2025-06-10 10:02:26 - [user] user - [INFO] INFO - User admin retrieved settings via API
2025-06-11 08:42:26 - [user] user - [INFO] INFO - User admin retrieved settings via API
2025-06-11 08:42:38 - [user] user - [INFO] INFO - User admin retrieved settings via API

4
backend/logs/windows_fixes/windows_fixes.log
View File

@ -70,3 +70,7 @@
2025-06-10 13:30:33 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
2025-06-10 13:30:33 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
2025-06-10 13:30:33 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
2025-06-11 08:42:18 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
2025-06-11 08:42:18 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
2025-06-11 08:42:18 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
2025-06-11 08:42:18 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet