diff --git a/backend/database/myp.db b/backend/database/myp.db index b72cdc1a..0949d523 100644 Binary files a/backend/database/myp.db and b/backend/database/myp.db differ diff --git a/backend/database/myp.db-shm b/backend/database/myp.db-shm new file mode 100644 index 00000000..e9f50081 Binary files /dev/null and b/backend/database/myp.db-shm differ diff --git a/backend/database/myp.db-wal b/backend/database/myp.db-wal new file mode 100644 index 00000000..871aff14 Binary files /dev/null and b/backend/database/myp.db-wal differ diff --git a/backend/logs/analytics/analytics.log b/backend/logs/analytics/analytics.log index 1fbbea1a..c0506392 100644 --- a/backend/logs/analytics/analytics.log +++ b/backend/logs/analytics/analytics.log @@ -103,3 +103,5 @@ 2025-06-02 07:10:47 - [analytics] analytics - [INFO] INFO - πŸ“ˆ Analytics Engine initialisiert 2025-06-02 07:14:29 - [analytics] analytics - [INFO] INFO - πŸ“ˆ Analytics Engine initialisiert 2025-06-02 07:16:41 - [analytics] analytics - [INFO] INFO - πŸ“ˆ Analytics Engine initialisiert +2025-06-02 08:21:39 - [analytics] analytics - [INFO] INFO - πŸ“ˆ Analytics Engine initialisiert +2025-06-02 08:22:36 - [analytics] analytics - [INFO] INFO - πŸ“ˆ Analytics Engine initialisiert diff --git a/backend/logs/app/app.log b/backend/logs/app/app.log index fec0a71c..a03dade4 100644 --- a/backend/logs/app/app.log +++ b/backend/logs/app/app.log @@ -2452,3 +2452,37 @@ WHERE jobs.status = ?) AS anon_1] 2025-06-02 07:16:46 - [app] app - [INFO] INFO - Starte Debug-Server auf 0.0.0.0:5000 (HTTP) 2025-06-02 07:16:46 - [app] app - [INFO] INFO - Windows-Debug-Modus: Auto-Reload deaktiviert 2025-06-02 08:18:35 - [app] app - [ERROR] ERROR - CSRF-Fehler fΓΌr /api/session/heartbeat: 400 Bad Request: The CSRF token has expired. +2025-06-02 08:21:39 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\database\myp.db +2025-06-02 08:21:40 - [app] app - [INFO] INFO - SQLite fΓΌr Raspberry Pi optimiert (reduzierte Cache-Grâße, SD-Karten I/O) +2025-06-02 08:21:40 - [app] app - [INFO] INFO - βœ… Timeout Force-Quit Manager geladen +2025-06-02 08:21:40 - [app] app - [INFO] INFO - βœ… Zentraler Shutdown-Manager initialisiert +2025-06-02 08:21:40 - [app] app - [INFO] INFO - πŸ”„ Starte Datenbank-Setup und Migrationen... +2025-06-02 08:21:40 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert +2025-06-02 08:21:40 - [app] app - [INFO] INFO - βœ… JobOrder-Tabelle bereits vorhanden +2025-06-02 08:21:40 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurΓΌckgesetzt. +2025-06-02 08:21:40 - [app] app - [INFO] INFO - βœ… Datenbank-Setup und Migrationen erfolgreich abgeschlossen +2025-06-02 08:21:40 - [app] app - [INFO] INFO - πŸ–¨οΈ Starte automatische Steckdosen-Initialisierung... +2025-06-02 08:21:45 - [app] app - [INFO] INFO - βœ… Steckdosen-Initialisierung: 0/2 Drucker erfolgreich +2025-06-02 08:21:45 - [app] app - [WARNING] WARNING - ⚠️ 2 Drucker konnten nicht initialisiert werden +2025-06-02 08:21:45 - [app] app - [INFO] INFO - πŸ”„ Debug-Modus: Queue Manager deaktiviert fΓΌr Entwicklung +2025-06-02 08:21:45 - [app] app - [INFO] INFO - Job-Scheduler gestartet +2025-06-02 08:21:45 - [app] app - [INFO] INFO - Starte Debug-Server auf 0.0.0.0:5000 (HTTP) +2025-06-02 08:21:45 - [app] app - [INFO] INFO - Windows-Debug-Modus: Auto-Reload deaktiviert +2025-06-02 08:21:49 - [app] app - [INFO] INFO - Admin-Check fΓΌr Funktion admin_page: User authenticated: True, User ID: 1, Is Admin: True +2025-06-02 08:21:56 - [app] app - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich abgemeldet +2025-06-02 08:22:36 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\database\myp.db +2025-06-02 08:22:37 - [app] app - [INFO] INFO - SQLite fΓΌr Raspberry Pi optimiert (reduzierte Cache-Grâße, SD-Karten I/O) +2025-06-02 08:22:37 - [app] app - [INFO] INFO - βœ… Timeout Force-Quit Manager geladen +2025-06-02 08:22:38 - [app] app - [INFO] INFO - βœ… Zentraler Shutdown-Manager initialisiert +2025-06-02 08:22:38 - [app] app - [INFO] INFO - πŸ”„ Starte Datenbank-Setup und Migrationen... +2025-06-02 08:22:38 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert +2025-06-02 08:22:38 - [app] app - [INFO] INFO - βœ… JobOrder-Tabelle bereits vorhanden +2025-06-02 08:22:38 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurΓΌckgesetzt. +2025-06-02 08:22:38 - [app] app - [INFO] INFO - βœ… Datenbank-Setup und Migrationen erfolgreich abgeschlossen +2025-06-02 08:22:38 - [app] app - [INFO] INFO - πŸ–¨οΈ Starte automatische Steckdosen-Initialisierung... +2025-06-02 08:22:42 - [app] app - [INFO] INFO - βœ… Steckdosen-Initialisierung: 0/2 Drucker erfolgreich +2025-06-02 08:22:42 - [app] app - [WARNING] WARNING - ⚠️ 2 Drucker konnten nicht initialisiert werden +2025-06-02 08:22:42 - [app] app - [INFO] INFO - πŸ”„ Debug-Modus: Queue Manager deaktiviert fΓΌr Entwicklung +2025-06-02 08:22:42 - [app] app - [INFO] INFO - Job-Scheduler gestartet +2025-06-02 08:22:42 - [app] app - [INFO] INFO - Starte Debug-Server auf 0.0.0.0:5000 (HTTP) +2025-06-02 08:22:42 - [app] app - [INFO] INFO - Windows-Debug-Modus: Auto-Reload deaktiviert diff --git a/backend/logs/backup/backup.log b/backend/logs/backup/backup.log index 14254f98..0ae93e2b 100644 --- a/backend/logs/backup/backup.log +++ b/backend/logs/backup/backup.log @@ -107,3 +107,5 @@ 2025-06-02 07:10:47 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation) 2025-06-02 07:14:29 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation) 2025-06-02 07:16:41 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation) +2025-06-02 08:21:39 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation) +2025-06-02 08:22:36 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation) diff --git a/backend/logs/dashboard/dashboard.log b/backend/logs/dashboard/dashboard.log index c86da19c..4d0e20ab 100644 --- a/backend/logs/dashboard/dashboard.log +++ b/backend/logs/dashboard/dashboard.log @@ -413,3 +413,11 @@ 2025-06-02 07:16:41 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet 2025-06-02 07:16:41 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback) 2025-06-02 07:16:41 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading) +2025-06-02 08:21:40 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet +2025-06-02 08:21:40 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet +2025-06-02 08:21:40 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback) +2025-06-02 08:21:40 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading) +2025-06-02 08:22:37 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet +2025-06-02 08:22:37 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet +2025-06-02 08:22:37 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback) +2025-06-02 08:22:37 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading) diff --git a/backend/logs/database/database.log b/backend/logs/database/database.log index 2026cf5d..af020d45 100644 --- a/backend/logs/database/database.log +++ b/backend/logs/database/database.log @@ -103,3 +103,5 @@ 2025-06-02 07:10:47 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet 2025-06-02 07:14:29 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet 2025-06-02 07:16:41 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet +2025-06-02 08:21:39 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet +2025-06-02 08:22:36 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet diff --git a/backend/logs/email_notification/email_notification.log b/backend/logs/email_notification/email_notification.log index 737be562..f3079b82 100644 --- a/backend/logs/email_notification/email_notification.log +++ b/backend/logs/email_notification/email_notification.log @@ -100,3 +100,5 @@ 2025-06-02 07:10:48 - [email_notification] email_notification - [INFO] INFO - πŸ“§ Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand) 2025-06-02 07:14:30 - [email_notification] email_notification - [INFO] INFO - πŸ“§ Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand) 2025-06-02 07:16:41 - [email_notification] email_notification - [INFO] INFO - πŸ“§ Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand) +2025-06-02 08:21:40 - [email_notification] email_notification - [INFO] INFO - πŸ“§ Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand) +2025-06-02 08:22:37 - [email_notification] email_notification - [INFO] INFO - πŸ“§ Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand) diff --git a/backend/logs/maintenance/maintenance.log b/backend/logs/maintenance/maintenance.log index 3d335c90..cec64bc0 100644 --- a/backend/logs/maintenance/maintenance.log +++ b/backend/logs/maintenance/maintenance.log @@ -206,3 +206,7 @@ 2025-06-02 07:16:41 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet 2025-06-02 08:00:41 - [maintenance] maintenance - [INFO] INFO - Generiere wΓΆchentlichen Wartungsbericht... 2025-06-02 08:00:41 - [maintenance] maintenance - [INFO] INFO - Generiere wΓΆchentlichen Wartungsbericht... +2025-06-02 08:21:40 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet +2025-06-02 08:21:40 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet +2025-06-02 08:22:37 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet +2025-06-02 08:22:37 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet diff --git a/backend/logs/multi_location/multi_location.log b/backend/logs/multi_location/multi_location.log index f38ccbc7..894b9614 100644 --- a/backend/logs/multi_location/multi_location.log +++ b/backend/logs/multi_location/multi_location.log @@ -204,3 +204,7 @@ 2025-06-02 07:14:30 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt 2025-06-02 07:16:41 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt 2025-06-02 07:16:41 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt +2025-06-02 08:21:40 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt +2025-06-02 08:21:40 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt +2025-06-02 08:22:37 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt +2025-06-02 08:22:37 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt diff --git a/backend/logs/permissions/permissions.log b/backend/logs/permissions/permissions.log index 9372c807..5d95da94 100644 --- a/backend/logs/permissions/permissions.log +++ b/backend/logs/permissions/permissions.log @@ -102,3 +102,5 @@ 2025-06-02 07:10:48 - [permissions] permissions - [INFO] INFO - πŸ” Permission Template Helpers registriert 2025-06-02 07:14:30 - [permissions] permissions - [INFO] INFO - πŸ” Permission Template Helpers registriert 2025-06-02 07:16:41 - [permissions] permissions - [INFO] INFO - πŸ” Permission Template Helpers registriert +2025-06-02 08:21:40 - [permissions] permissions - [INFO] INFO - πŸ” Permission Template Helpers registriert +2025-06-02 08:22:37 - [permissions] permissions - [INFO] INFO - πŸ” Permission Template Helpers registriert diff --git a/backend/logs/printer_monitor/printer_monitor.log b/backend/logs/printer_monitor/printer_monitor.log index 8f95d743..f6b9868e 100644 --- a/backend/logs/printer_monitor/printer_monitor.log +++ b/backend/logs/printer_monitor/printer_monitor.log @@ -2943,3 +2943,43 @@ 2025-06-02 08:18:52 - [printer_monitor] printer_monitor - [WARNING] WARNING - πŸ”Œ Tapo P110 (192.168.0.103): UNREACHABLE (Ping fehlgeschlagen) 2025-06-02 08:18:52 - [printer_monitor] printer_monitor - [WARNING] WARNING - πŸ”Œ Tapo P110 (192.168.0.104): UNREACHABLE (Ping fehlgeschlagen) 2025-06-02 08:18:52 - [printer_monitor] printer_monitor - [INFO] INFO - βœ… Status-Update abgeschlossen fΓΌr 2 Drucker +2025-06-02 08:21:39 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ–¨οΈ Drucker-Monitor initialisiert +2025-06-02 08:21:39 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Automatische Tapo-Erkennung in separatem Thread gestartet +2025-06-02 08:21:40 - [printer_monitor] printer_monitor - [INFO] INFO - πŸš€ Starte Steckdosen-Initialisierung beim Programmstart... +2025-06-02 08:21:41 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Starte automatische Tapo-Steckdosenerkennung... +2025-06-02 08:21:41 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ”„ Teste 6 Standard-IPs aus der Konfiguration +2025-06-02 08:21:41 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 1/6: 192.168.0.103 +2025-06-02 08:21:43 - [printer_monitor] printer_monitor - [WARNING] WARNING - ❌ Tapo P110 (192.168.0.103): Steckdose konnte nicht ausgeschaltet werden +2025-06-02 08:21:45 - [printer_monitor] printer_monitor - [WARNING] WARNING - ❌ Tapo P110 (192.168.0.104): Steckdose konnte nicht ausgeschaltet werden +2025-06-02 08:21:45 - [printer_monitor] printer_monitor - [INFO] INFO - 🎯 Steckdosen-Initialisierung abgeschlossen: 0/2 erfolgreich +2025-06-02 08:21:45 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ”„ Aktualisiere Live-Druckerstatus... +2025-06-02 08:21:45 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” PrΓΌfe Status von 2 aktiven Druckern... +2025-06-02 08:21:47 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ”„ Aktualisiere Live-Druckerstatus... +2025-06-02 08:21:47 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” PrΓΌfe Status von 2 aktiven Druckern... +2025-06-02 08:21:47 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 2/6: 192.168.0.104 +2025-06-02 08:21:53 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 3/6: 192.168.0.100 +2025-06-02 08:21:54 - [printer_monitor] printer_monitor - [WARNING] WARNING - πŸ”Œ Tapo P110 (192.168.0.103): UNREACHABLE (Ping fehlgeschlagen) +2025-06-02 08:21:54 - [printer_monitor] printer_monitor - [WARNING] WARNING - πŸ”Œ Tapo P110 (192.168.0.104): UNREACHABLE (Ping fehlgeschlagen) +2025-06-02 08:21:54 - [printer_monitor] printer_monitor - [INFO] INFO - βœ… Status-Update abgeschlossen fΓΌr 2 Drucker +2025-06-02 08:21:56 - [printer_monitor] printer_monitor - [WARNING] WARNING - πŸ”Œ Tapo P110 (192.168.0.103): UNREACHABLE (Ping fehlgeschlagen) +2025-06-02 08:21:56 - [printer_monitor] printer_monitor - [WARNING] WARNING - πŸ”Œ Tapo P110 (192.168.0.104): UNREACHABLE (Ping fehlgeschlagen) +2025-06-02 08:21:56 - [printer_monitor] printer_monitor - [INFO] INFO - βœ… Status-Update abgeschlossen fΓΌr 2 Drucker +2025-06-02 08:21:59 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 4/6: 192.168.0.101 +2025-06-02 08:22:05 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 5/6: 192.168.0.102 +2025-06-02 08:22:11 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 6/6: 192.168.0.105 +2025-06-02 08:22:17 - [printer_monitor] printer_monitor - [INFO] INFO - βœ… Steckdosen-Erkennung abgeschlossen: 0/6 Steckdosen gefunden in 36.2s +2025-06-02 08:22:36 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ–¨οΈ Drucker-Monitor initialisiert +2025-06-02 08:22:36 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Automatische Tapo-Erkennung in separatem Thread gestartet +2025-06-02 08:22:38 - [printer_monitor] printer_monitor - [INFO] INFO - πŸš€ Starte Steckdosen-Initialisierung beim Programmstart... +2025-06-02 08:22:38 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Starte automatische Tapo-Steckdosenerkennung... +2025-06-02 08:22:38 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ”„ Teste 6 Standard-IPs aus der Konfiguration +2025-06-02 08:22:38 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 1/6: 192.168.0.103 +2025-06-02 08:22:40 - [printer_monitor] printer_monitor - [WARNING] WARNING - ❌ Tapo P110 (192.168.0.103): Steckdose konnte nicht ausgeschaltet werden +2025-06-02 08:22:42 - [printer_monitor] printer_monitor - [WARNING] WARNING - ❌ Tapo P110 (192.168.0.104): Steckdose konnte nicht ausgeschaltet werden +2025-06-02 08:22:42 - [printer_monitor] printer_monitor - [INFO] INFO - 🎯 Steckdosen-Initialisierung abgeschlossen: 0/2 erfolgreich +2025-06-02 08:22:44 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 2/6: 192.168.0.104 +2025-06-02 08:22:50 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 3/6: 192.168.0.100 +2025-06-02 08:22:56 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 4/6: 192.168.0.101 +2025-06-02 08:23:02 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 5/6: 192.168.0.102 +2025-06-02 08:23:08 - [printer_monitor] printer_monitor - [INFO] INFO - πŸ” Teste IP 6/6: 192.168.0.105 +2025-06-02 08:23:14 - [printer_monitor] printer_monitor - [INFO] INFO - βœ… Steckdosen-Erkennung abgeschlossen: 0/6 Steckdosen gefunden in 36.1s diff --git a/backend/logs/printers/printers.log b/backend/logs/printers/printers.log index 65349b9d..98b0609c 100644 --- a/backend/logs/printers/printers.log +++ b/backend/logs/printers/printers.log @@ -5881,3 +5881,12 @@ 2025-06-02 08:20:43 - [printers] printers - [INFO] INFO - πŸ”„ Live-Status-Abfrage von Benutzer Administrator (ID: 1) 2025-06-02 08:20:43 - [printers] printers - [INFO] INFO - βœ… Live-Status-Abfrage erfolgreich: 2 Drucker 2025-06-02 08:20:43 - [printers] printers - [INFO] INFO - βœ… API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 0.38ms +2025-06-02 08:21:45 - [printers] printers - [INFO] INFO - πŸ”„ Live-Status-Abfrage von Benutzer Administrator (ID: 1) +2025-06-02 08:21:47 - [printers] printers - [INFO] INFO - πŸ”„ Live-Status-Abfrage von Benutzer Administrator (ID: 1) +2025-06-02 08:21:54 - [printers] printers - [INFO] INFO - βœ… Live-Status-Abfrage erfolgreich: 2 Drucker +2025-06-02 08:21:54 - [printers] printers - [INFO] INFO - βœ… API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 9034.44ms +2025-06-02 08:21:56 - [printers] printers - [INFO] INFO - βœ… Live-Status-Abfrage erfolgreich: 2 Drucker +2025-06-02 08:21:56 - [printers] printers - [INFO] INFO - βœ… API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 9015.05ms +2025-06-02 08:21:56 - [printers] printers - [INFO] INFO - πŸ”„ Live-Status-Abfrage von Benutzer Administrator (ID: 1) +2025-06-02 08:21:56 - [printers] printers - [INFO] INFO - βœ… Live-Status-Abfrage erfolgreich: 2 Drucker +2025-06-02 08:21:56 - [printers] printers - [INFO] INFO - βœ… API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 0.91ms diff --git a/backend/logs/scheduler/scheduler.log b/backend/logs/scheduler/scheduler.log index e481b3cf..8ff435c1 100644 --- a/backend/logs/scheduler/scheduler.log +++ b/backend/logs/scheduler/scheduler.log @@ -19600,3 +19600,71 @@ 2025-06-02 08:20: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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) 2025-06-02 08:20:43 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 4 nicht einschalten 2025-06-02 08:20:43 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 5: test +2025-06-02 08:21:39 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True +2025-06-02 08:21:45 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet +2025-06-02 08:21:45 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet +2025-06-02 08:21:45 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 7: test +2025-06-02 08:21:47 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:21:47 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 7 nicht einschalten +2025-06-02 08:21:47 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 8: test +2025-06-02 08:21:49 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:21:49 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 8 nicht einschalten +2025-06-02 08:21:49 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 1: test +2025-06-02 08:21:51 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:21:51 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 1 nicht einschalten +2025-06-02 08:21:51 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 2: test +2025-06-02 08:21:53 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:21:53 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 2 nicht einschalten +2025-06-02 08:21:53 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 3: test +2025-06-02 08:21:55 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:21:55 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 3 nicht einschalten +2025-06-02 08:21:55 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 4: test +2025-06-02 08:21:57 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:21:57 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 4 nicht einschalten +2025-06-02 08:21:57 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 5: test +2025-06-02 08:21:59 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:21:59 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 5 nicht einschalten +2025-06-02 08:21:59 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 6: test +2025-06-02 08:22:02 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:02 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 6 nicht einschalten +2025-06-02 08:22:02 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 9: zi +2025-06-02 08:22:04 - [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(, 'Connection to 192.168.0.104 timed out. (connect timeout=2)')) +2025-06-02 08:22:04 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 9 nicht einschalten +2025-06-02 08:22:04 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 10: zi +2025-06-02 08:22:06 - [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(, 'Connection to 192.168.0.104 timed out. (connect timeout=2)')) +2025-06-02 08:22:06 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 10 nicht einschalten +2025-06-02 08:22:06 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 11: fee +2025-06-02 08:22:08 - [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(, 'Connection to 192.168.0.104 timed out. (connect timeout=2)')) +2025-06-02 08:22:08 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 11 nicht einschalten +2025-06-02 08:22:08 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 12: fee +2025-06-02 08:22:10 - [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(, 'Connection to 192.168.0.104 timed out. (connect timeout=2)')) +2025-06-02 08:22:10 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 12 nicht einschalten +2025-06-02 08:22:10 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 13: e2 +2025-06-02 08:22:12 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:12 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 13 nicht einschalten +2025-06-02 08:22:12 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 14: e2 +2025-06-02 08:22:14 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:14 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 14 nicht einschalten +2025-06-02 08:22:14 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 15: test +2025-06-02 08:22:16 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:16 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 15 nicht einschalten +2025-06-02 08:22:16 - [scheduler] scheduler - [INFO] INFO - ⚑ Starte Sofort-Job 16: test +2025-06-02 08:22:18 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:18 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Sofort-Job 16 nicht einschalten +2025-06-02 08:22:19 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 7: test +2025-06-02 08:22:22 - [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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:22 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 7 nicht einschalten +2025-06-02 08:22:22 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 8: test +2025-06-02 08:22: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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:24 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 8 nicht einschalten +2025-06-02 08:22:24 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 1: test +2025-06-02 08:22: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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:26 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 1 nicht einschalten +2025-06-02 08:22:26 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 2: test +2025-06-02 08:22: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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:28 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 2 nicht einschalten +2025-06-02 08:22:28 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 3: test +2025-06-02 08:22: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(, 'Connection to 192.168.0.103 timed out. (connect timeout=2)')) +2025-06-02 08:22:30 - [scheduler] scheduler - [ERROR] ERROR - ❌ Konnte Steckdose fΓΌr Job 3 nicht einschalten +2025-06-02 08:22:30 - [scheduler] scheduler - [INFO] INFO - πŸš€ Starte geplanten Job 4: test +2025-06-02 08:22:36 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True diff --git a/backend/logs/security/security.log b/backend/logs/security/security.log index 07cd1b66..e22fdfea 100644 --- a/backend/logs/security/security.log +++ b/backend/logs/security/security.log @@ -102,3 +102,5 @@ 2025-06-02 07:10:48 - [security] security - [INFO] INFO - πŸ”’ Security System initialisiert 2025-06-02 07:14:30 - [security] security - [INFO] INFO - πŸ”’ Security System initialisiert 2025-06-02 07:16:41 - [security] security - [INFO] INFO - πŸ”’ Security System initialisiert +2025-06-02 08:21:40 - [security] security - [INFO] INFO - πŸ”’ Security System initialisiert +2025-06-02 08:22:37 - [security] security - [INFO] INFO - πŸ”’ Security System initialisiert diff --git a/backend/logs/shutdown_manager/shutdown_manager.log b/backend/logs/shutdown_manager/shutdown_manager.log index abf7c1ec..25c6c614 100644 --- a/backend/logs/shutdown_manager/shutdown_manager.log +++ b/backend/logs/shutdown_manager/shutdown_manager.log @@ -188,3 +188,5 @@ 2025-06-02 07:10:48 - [shutdown_manager] shutdown_manager - [INFO] INFO - πŸ”§ Shutdown-Manager initialisiert 2025-06-02 07:14:30 - [shutdown_manager] shutdown_manager - [INFO] INFO - πŸ”§ Shutdown-Manager initialisiert 2025-06-02 07:16:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - πŸ”§ Shutdown-Manager initialisiert +2025-06-02 08:21:40 - [shutdown_manager] shutdown_manager - [INFO] INFO - πŸ”§ Shutdown-Manager initialisiert +2025-06-02 08:22:37 - [shutdown_manager] shutdown_manager - [INFO] INFO - πŸ”§ Shutdown-Manager initialisiert diff --git a/backend/logs/startup/startup.log b/backend/logs/startup/startup.log index d07a09e7..186321c9 100644 --- a/backend/logs/startup/startup.log +++ b/backend/logs/startup/startup.log @@ -926,3 +926,21 @@ 2025-06-02 07:16:41 - [startup] startup - [INFO] INFO - πŸͺŸ Windows-Modus: Aktiviert 2025-06-02 07:16:41 - [startup] startup - [INFO] INFO - πŸ”’ Windows-sichere Log-Rotation: Aktiviert 2025-06-02 07:16:41 - [startup] startup - [INFO] INFO - ================================================== +2025-06-02 08:21:40 - [startup] startup - [INFO] INFO - ================================================== +2025-06-02 08:21:40 - [startup] startup - [INFO] INFO - πŸš€ MYP Platform Backend wird gestartet... +2025-06-02 08:21:40 - [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-02 08:21:40 - [startup] startup - [INFO] INFO - πŸ’» Betriebssystem: nt (win32) +2025-06-02 08:21:40 - [startup] startup - [INFO] INFO - πŸ“ Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend +2025-06-02 08:21:40 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-02T08:21:40.576431 +2025-06-02 08:21:40 - [startup] startup - [INFO] INFO - πŸͺŸ Windows-Modus: Aktiviert +2025-06-02 08:21:40 - [startup] startup - [INFO] INFO - πŸ”’ Windows-sichere Log-Rotation: Aktiviert +2025-06-02 08:21:40 - [startup] startup - [INFO] INFO - ================================================== +2025-06-02 08:22:37 - [startup] startup - [INFO] INFO - ================================================== +2025-06-02 08:22:37 - [startup] startup - [INFO] INFO - πŸš€ MYP Platform Backend wird gestartet... +2025-06-02 08:22:37 - [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-02 08:22:37 - [startup] startup - [INFO] INFO - πŸ’» Betriebssystem: nt (win32) +2025-06-02 08:22:37 - [startup] startup - [INFO] INFO - πŸ“ Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend +2025-06-02 08:22:37 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-02T08:22:37.800164 +2025-06-02 08:22:37 - [startup] startup - [INFO] INFO - πŸͺŸ Windows-Modus: Aktiviert +2025-06-02 08:22:37 - [startup] startup - [INFO] INFO - πŸ”’ Windows-sichere Log-Rotation: Aktiviert +2025-06-02 08:22:37 - [startup] startup - [INFO] INFO - ================================================== diff --git a/backend/logs/windows_fixes/windows_fixes.log b/backend/logs/windows_fixes/windows_fixes.log index e9c66b14..1348ade2 100644 --- a/backend/logs/windows_fixes/windows_fixes.log +++ b/backend/logs/windows_fixes/windows_fixes.log @@ -439,3 +439,11 @@ 2025-06-02 07:16:40 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Subprocess automatisch gepatcht fΓΌr UTF-8 Encoding (run + Popen) 2025-06-02 07:16:40 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Globaler subprocess-Patch angewendet 2025-06-02 07:16:40 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Alle Windows-Fixes erfolgreich angewendet +2025-06-02 08:21:39 - [windows_fixes] windows_fixes - [INFO] INFO - πŸ”§ Wende Windows-spezifische Fixes an... +2025-06-02 08:21:39 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Subprocess automatisch gepatcht fΓΌr UTF-8 Encoding (run + Popen) +2025-06-02 08:21:39 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Globaler subprocess-Patch angewendet +2025-06-02 08:21:39 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Alle Windows-Fixes erfolgreich angewendet +2025-06-02 08:22:36 - [windows_fixes] windows_fixes - [INFO] INFO - πŸ”§ Wende Windows-spezifische Fixes an... +2025-06-02 08:22:36 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Subprocess automatisch gepatcht fΓΌr UTF-8 Encoding (run + Popen) +2025-06-02 08:22:36 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Globaler subprocess-Patch angewendet +2025-06-02 08:22:36 - [windows_fixes] windows_fixes - [INFO] INFO - βœ… Alle Windows-Fixes erfolgreich angewendet