📚 Improved logging structure & efficiency across backend logs 🌐 #123
This commit is contained in:
parent
941ee21c76
commit
99ba574223
128
backend/app.py
128
backend/app.py
@ -151,7 +151,19 @@ from utils.multi_location_system import (
|
||||
# Drucker-Monitor importieren
|
||||
from utils.printer_monitor import printer_monitor
|
||||
|
||||
# Timeout Force-Quit Manager importieren
|
||||
# Logging initialisieren (früh, damit andere Module es verwenden können)
|
||||
setup_logging()
|
||||
log_startup_info()
|
||||
|
||||
# app_logger für verschiedene Komponenten (früh definieren)
|
||||
app_logger = get_logger("app")
|
||||
auth_logger = get_logger("auth")
|
||||
jobs_logger = get_logger("jobs")
|
||||
printers_logger = get_logger("printers")
|
||||
user_logger = get_logger("user")
|
||||
kiosk_logger = get_logger("kiosk")
|
||||
|
||||
# Timeout Force-Quit Manager importieren (nach Logger-Definition)
|
||||
try:
|
||||
from utils.timeout_force_quit_manager import (
|
||||
get_timeout_manager, start_force_quit_timeout, cancel_force_quit_timeout,
|
||||
@ -164,6 +176,108 @@ except ImportError as e:
|
||||
TIMEOUT_FORCE_QUIT_AVAILABLE = False
|
||||
app_logger.warning(f"⚠️ Timeout Force-Quit Manager nicht verfügbar: {e}")
|
||||
|
||||
# ===== AGGRESSIVE SOFORT-SHUTDOWN HANDLER FÜR STRG+C =====
|
||||
import atexit
|
||||
|
||||
def aggressive_shutdown_handler(sig, frame):
|
||||
"""
|
||||
Aggressiver Signal-Handler für sofortiges Herunterfahren bei Strg+C.
|
||||
Schließt sofort alle Datenbankverbindungen und beendet das Programm um jeden Preis.
|
||||
"""
|
||||
print("\n🚨 STRG+C ERKANNT - SOFORTIGES SHUTDOWN!")
|
||||
print("🔥 Schließe Datenbank sofort und beende Programm um jeden Preis!")
|
||||
|
||||
try:
|
||||
# 1. Sofort alle Datenbank-Sessions und Engine schließen
|
||||
try:
|
||||
from models import _engine, _scoped_session, _session_factory
|
||||
|
||||
if _scoped_session:
|
||||
try:
|
||||
_scoped_session.remove()
|
||||
print("✅ Scoped Sessions geschlossen")
|
||||
except Exception as e:
|
||||
print(f"⚠️ Fehler beim Schließen der Scoped Sessions: {e}")
|
||||
|
||||
if _engine:
|
||||
try:
|
||||
_engine.dispose()
|
||||
print("✅ Datenbank-Engine geschlossen")
|
||||
except Exception as e:
|
||||
print(f"⚠️ Fehler beim Schließen der Engine: {e}")
|
||||
except ImportError:
|
||||
print("⚠️ Models nicht verfügbar für Database-Cleanup")
|
||||
|
||||
# 2. Alle offenen DB-Sessions forciert schließen
|
||||
try:
|
||||
import gc
|
||||
# Garbage Collection für nicht geschlossene Sessions
|
||||
gc.collect()
|
||||
print("✅ Garbage Collection ausgeführt")
|
||||
except Exception as e:
|
||||
print(f"⚠️ Garbage Collection fehlgeschlagen: {e}")
|
||||
|
||||
# 3. SQLite WAL-Dateien forciert synchronisieren
|
||||
try:
|
||||
import sqlite3
|
||||
from config.settings import DATABASE_PATH
|
||||
conn = sqlite3.connect(DATABASE_PATH, timeout=1.0)
|
||||
conn.execute("PRAGMA wal_checkpoint(TRUNCATE)")
|
||||
conn.close()
|
||||
print("✅ SQLite WAL-Checkpoint ausgeführt")
|
||||
except Exception as e:
|
||||
print(f"⚠️ WAL-Checkpoint fehlgeschlagen: {e}")
|
||||
|
||||
# 4. Queue Manager stoppen falls verfügbar
|
||||
try:
|
||||
from utils.queue_manager import stop_queue_manager
|
||||
stop_queue_manager()
|
||||
print("✅ Queue Manager gestoppt")
|
||||
except Exception as e:
|
||||
print(f"⚠️ Queue Manager Stop fehlgeschlagen: {e}")
|
||||
|
||||
except Exception as e:
|
||||
print(f"❌ Fehler beim Database-Cleanup: {e}")
|
||||
|
||||
print("🛑 SOFORTIGES PROGRAMM-ENDE - EXIT CODE 0")
|
||||
# Sofortiger Exit ohne weitere Cleanup-Routinen
|
||||
os._exit(0)
|
||||
|
||||
def register_aggressive_shutdown():
|
||||
"""
|
||||
Registriert den aggressiven Shutdown-Handler für alle relevanten Signale.
|
||||
Muss VOR allen anderen Signal-Handlern registriert werden.
|
||||
"""
|
||||
# Signal-Handler für alle Plattformen registrieren
|
||||
signal.signal(signal.SIGINT, aggressive_shutdown_handler) # Strg+C
|
||||
signal.signal(signal.SIGTERM, aggressive_shutdown_handler) # Terminate Signal
|
||||
|
||||
# Windows-spezifische Signale
|
||||
if os.name == 'nt':
|
||||
try:
|
||||
signal.signal(signal.SIGBREAK, aggressive_shutdown_handler) # Strg+Break
|
||||
print("✅ Windows SIGBREAK Handler registriert")
|
||||
except AttributeError:
|
||||
pass # SIGBREAK nicht auf allen Windows-Versionen verfügbar
|
||||
else:
|
||||
# Unix/Linux-spezifische Signale
|
||||
try:
|
||||
signal.signal(signal.SIGHUP, aggressive_shutdown_handler) # Hangup Signal
|
||||
print("✅ Unix SIGHUP Handler registriert")
|
||||
except AttributeError:
|
||||
pass
|
||||
|
||||
# Atexit-Handler als Backup registrieren
|
||||
atexit.register(lambda: print("🔄 Atexit-Handler ausgeführt - Programm beendet"))
|
||||
|
||||
print("🚨 AGGRESSIVER STRG+C SHUTDOWN-HANDLER AKTIVIERT")
|
||||
print("📋 Bei Strg+C wird die Datenbank sofort geschlossen und das Programm beendet!")
|
||||
|
||||
# Aggressive Shutdown-Handler sofort registrieren
|
||||
register_aggressive_shutdown()
|
||||
|
||||
# ===== ENDE AGGRESSIVE SHUTDOWN HANDLER =====
|
||||
|
||||
# Flask-App initialisieren
|
||||
app = Flask(__name__)
|
||||
app.secret_key = SECRET_KEY
|
||||
@ -380,18 +494,6 @@ def format_datetime_filter(value, format='%d.%m.%Y %H:%M'):
|
||||
return value
|
||||
return value.strftime(format)
|
||||
|
||||
# Logging initialisieren
|
||||
setup_logging()
|
||||
log_startup_info()
|
||||
|
||||
# app_logger für verschiedene Komponenten
|
||||
app_logger = get_logger("app")
|
||||
auth_logger = get_logger("auth")
|
||||
jobs_logger = get_logger("jobs")
|
||||
printers_logger = get_logger("printers")
|
||||
user_logger = get_logger("user")
|
||||
kiosk_logger = get_logger("kiosk")
|
||||
|
||||
# HTTP-Request/Response-Middleware für automatisches Debug-Logging
|
||||
@app.before_request
|
||||
def log_request_info():
|
||||
|
||||
Binary file not shown.
Binary file not shown.
@ -3,3 +3,5 @@
|
||||
2025-06-01 03:06:06 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-01 03:29:14 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-01 03:31:39 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-01 03:35:40 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
2025-06-01 03:38:47 - [analytics] analytics - [INFO] INFO - 📈 Analytics Engine initialisiert
|
||||
|
||||
@ -207,3 +207,25 @@
|
||||
2025-06-01 03:29:37 - [app] app - [INFO] INFO - Benutzer admin@mercedes-benz.com hat sich abgemeldet
|
||||
2025-06-01 03:31:39 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\database\myp.db
|
||||
2025-06-01 03:31:40 - [app] app - [INFO] INFO - SQLite für Produktionsumgebung konfiguriert (WAL-Modus, Cache, Optimierungen)
|
||||
2025-06-01 03:35:40 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\database\myp.db
|
||||
2025-06-01 03:35:41 - [app] app - [INFO] INFO - SQLite für Produktionsumgebung konfiguriert (WAL-Modus, Cache, Optimierungen)
|
||||
2025-06-01 03:38:46 - [app] app - [INFO] INFO - Optimierte SQLite-Engine erstellt: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend\database\myp.db
|
||||
2025-06-01 03:38:47 - [app] app - [INFO] INFO - SQLite für Produktionsumgebung konfiguriert (WAL-Modus, Cache, Optimierungen)
|
||||
2025-06-01 03:38:47 - [app] app - [INFO] INFO - ✅ Timeout Force-Quit Manager geladen
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - ✅ Zentraler Shutdown-Manager initialisiert
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - 🔄 Starte Datenbank-Setup und Migrationen...
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - Datenbank mit Optimierungen initialisiert
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - ✅ JobOrder-Tabelle bereits vorhanden
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - Admin-Benutzer admin (admin@mercedes-benz.com) existiert bereits. Passwort wurde zurückgesetzt.
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - ✅ Datenbank-Setup und Migrationen erfolgreich abgeschlossen
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - 🖨️ Starte automatische Steckdosen-Initialisierung...
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - ℹ️ Keine Drucker zur Initialisierung gefunden
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - 🔄 Debug-Modus: Queue Manager deaktiviert für Entwicklung
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - Job-Scheduler gestartet
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - Starte Debug-Server auf 0.0.0.0:5000 (HTTP)
|
||||
2025-06-01 03:38:48 - [app] app - [INFO] INFO - Windows-Debug-Modus: Auto-Reload deaktiviert
|
||||
2025-06-01 03:39:14 - [app] app - [INFO] INFO - Admin-Check für Funktion api_admin_stats_live: User authenticated: True, User ID: 1, Is Admin: True
|
||||
2025-06-01 03:39:14 - [app] app - [INFO] INFO - Admin-Check für Funktion api_admin_system_health: User authenticated: True, User ID: 1, Is Admin: True
|
||||
2025-06-01 03:39:15 - [app] app - [WARNING] WARNING - System-Performance-Metriken nicht verfügbar: argument 1 (impossible<bad format char>)
|
||||
2025-06-01 03:39:15 - [app] app - [INFO] INFO - Admin-Check für Funktion api_admin_stats_live: User authenticated: True, User ID: 1, Is Admin: True
|
||||
2025-06-01 03:39:16 - [app] app - [WARNING] WARNING - System-Performance-Metriken nicht verfügbar: argument 1 (impossible<bad format char>)
|
||||
|
||||
@ -3,3 +3,5 @@
|
||||
2025-06-01 03:06:06 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-01 03:29:14 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-01 03:31:39 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-01 03:35:40 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
2025-06-01 03:38:47 - [backup] backup - [INFO] INFO - BackupManager initialisiert (minimal implementation)
|
||||
|
||||
@ -1,2 +1,3 @@
|
||||
2025-06-01 03:06:34 - [calendar] calendar - [INFO] INFO - 📅 Kalender-Events abgerufen: 0 Einträge für Zeitraum 2025-06-01 00:00:00 bis 2025-06-08 00:00:00
|
||||
2025-06-01 03:08:04 - [calendar] calendar - [INFO] INFO - 📅 Kalender-Events abgerufen: 0 Einträge für Zeitraum 2025-06-01 00:00:00 bis 2025-06-08 00:00:00
|
||||
2025-06-01 03:38:56 - [calendar] calendar - [INFO] INFO - 📅 Kalender-Events abgerufen: 0 Einträge für Zeitraum 2025-06-01 00:00:00 bis 2025-06-08 00:00:00
|
||||
|
||||
@ -15,3 +15,8 @@
|
||||
2025-06-01 03:29:16 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback)
|
||||
2025-06-01 03:29:16 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading)
|
||||
2025-06-01 03:31:40 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-01 03:35:41 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-01 03:38:47 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-01 03:38:47 - [dashboard] dashboard - [INFO] INFO - Dashboard-Background-Worker gestartet
|
||||
2025-06-01 03:38:47 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server wird mit threading initialisiert (eventlet-Fallback)
|
||||
2025-06-01 03:38:47 - [dashboard] dashboard - [INFO] INFO - Dashboard WebSocket-Server initialisiert (async_mode: threading)
|
||||
|
||||
@ -3,3 +3,5 @@
|
||||
2025-06-01 03:06:06 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:29:14 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:31:39 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:35:40 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:38:47 - [database] database - [INFO] INFO - Datenbank-Wartungs-Scheduler gestartet
|
||||
|
||||
@ -7,3 +7,6 @@
|
||||
2025-06-01 03:30:12 - [database_cleanup] database_cleanup - [INFO] INFO - 🧹 Starte umfassendes Datenbank-Cleanup...
|
||||
2025-06-01 03:30:12 - [database_cleanup] database_cleanup - [INFO] INFO - 📝 Schritt 1: Schließe alle Datenbankverbindungen...
|
||||
2025-06-01 03:30:12 - [database_cleanup] database_cleanup - [INFO] INFO - 🔄 Schließe alle aktiven Datenbankverbindungen...
|
||||
2025-06-01 03:39:41 - [database_cleanup] database_cleanup - [INFO] INFO - 🧹 Starte umfassendes Datenbank-Cleanup...
|
||||
2025-06-01 03:39:41 - [database_cleanup] database_cleanup - [INFO] INFO - 📝 Schritt 1: Schließe alle Datenbankverbindungen...
|
||||
2025-06-01 03:39:41 - [database_cleanup] database_cleanup - [INFO] INFO - 🔄 Schließe alle aktiven Datenbankverbindungen...
|
||||
|
||||
@ -3,3 +3,5 @@
|
||||
2025-06-01 03:06:07 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-01 03:29:15 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-01 03:31:40 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-01 03:35:41 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
2025-06-01 03:38:47 - [email_notification] email_notification - [INFO] INFO - 📧 Offline-E-Mail-Benachrichtigung initialisiert (kein echter E-Mail-Versand)
|
||||
|
||||
@ -7,3 +7,6 @@
|
||||
2025-06-01 03:29:16 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:29:16 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:31:40 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:35:41 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:38:47 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
2025-06-01 03:38:47 - [maintenance] maintenance - [INFO] INFO - Wartungs-Scheduler gestartet
|
||||
|
||||
@ -7,3 +7,6 @@
|
||||
2025-06-01 03:29:16 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-01 03:29:16 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-01 03:31:40 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-01 03:35:41 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-01 03:38:47 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
2025-06-01 03:38:47 - [multi_location] multi_location - [INFO] INFO - Standard-Standort erstellt
|
||||
|
||||
@ -2,3 +2,4 @@
|
||||
2025-06-01 03:04:48 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-01 03:06:07 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-01 03:29:16 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
2025-06-01 03:38:47 - [permissions] permissions - [INFO] INFO - 🔐 Permission Template Helpers registriert
|
||||
|
||||
@ -180,3 +180,30 @@
|
||||
2025-06-01 03:29:52 - [printer_monitor] printer_monitor - [INFO] INFO - ✅ Steckdosen-Erkennung abgeschlossen: 0/6 Steckdosen gefunden in 36.0s
|
||||
2025-06-01 03:31:39 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-01 03:31:39 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-01 03:35:40 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-01 03:35:40 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-01 03:38:47 - [printer_monitor] printer_monitor - [INFO] INFO - 🖨️ Drucker-Monitor initialisiert
|
||||
2025-06-01 03:38:47 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Automatische Tapo-Erkennung in separatem Thread gestartet
|
||||
2025-06-01 03:38:48 - [printer_monitor] printer_monitor - [INFO] INFO - 🚀 Starte Steckdosen-Initialisierung beim Programmstart...
|
||||
2025-06-01 03:38:48 - [printer_monitor] printer_monitor - [WARNING] WARNING - ⚠️ Keine aktiven Drucker zur Initialisierung gefunden
|
||||
2025-06-01 03:38:49 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Starte automatische Tapo-Steckdosenerkennung...
|
||||
2025-06-01 03:38:49 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Teste 6 Standard-IPs aus der Konfiguration
|
||||
2025-06-01 03:38:49 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 1/6: 192.168.0.103
|
||||
2025-06-01 03:38:53 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-01 03:38:53 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
2025-06-01 03:38:53 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-01 03:38:53 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
2025-06-01 03:38:55 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 2/6: 192.168.0.104
|
||||
2025-06-01 03:39:01 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 3/6: 192.168.0.100
|
||||
2025-06-01 03:39:07 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 4/6: 192.168.0.101
|
||||
2025-06-01 03:39:13 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 5/6: 192.168.0.102
|
||||
2025-06-01 03:39:14 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-01 03:39:14 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
2025-06-01 03:39:14 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-01 03:39:14 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
2025-06-01 03:39:19 - [printer_monitor] printer_monitor - [INFO] INFO - 🔍 Teste IP 6/6: 192.168.0.105
|
||||
2025-06-01 03:39:25 - [printer_monitor] printer_monitor - [INFO] INFO - ✅ Steckdosen-Erkennung abgeschlossen: 0/6 Steckdosen gefunden in 36.0s
|
||||
2025-06-01 03:39:30 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-01 03:39:30 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
2025-06-01 03:39:30 - [printer_monitor] printer_monitor - [INFO] INFO - 🔄 Aktualisiere Live-Druckerstatus...
|
||||
2025-06-01 03:39:30 - [printer_monitor] printer_monitor - [INFO] INFO - ℹ️ Keine aktiven Drucker gefunden
|
||||
|
||||
@ -2995,3 +2995,12 @@
|
||||
2025-06-01 03:08:12 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 0 Drucker
|
||||
2025-06-01 03:08:12 - [printers] printers - [INFO] INFO - ✅ API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 13.12ms
|
||||
2025-06-01 03:29:28 - [printers] printers - [INFO] INFO - Schnelles Laden abgeschlossen: 6 Drucker geladen (ohne Status-Check)
|
||||
2025-06-01 03:38:53 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
2025-06-01 03:38:53 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 0 Drucker
|
||||
2025-06-01 03:38:53 - [printers] printers - [INFO] INFO - ✅ API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 7.26ms
|
||||
2025-06-01 03:39:14 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
2025-06-01 03:39:14 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 0 Drucker
|
||||
2025-06-01 03:39:14 - [printers] printers - [INFO] INFO - ✅ API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 8.11ms
|
||||
2025-06-01 03:39:30 - [printers] printers - [INFO] INFO - 🔄 Live-Status-Abfrage von Benutzer Administrator (ID: 1)
|
||||
2025-06-01 03:39:30 - [printers] printers - [INFO] INFO - ✅ Live-Status-Abfrage erfolgreich: 0 Drucker
|
||||
2025-06-01 03:39:30 - [printers] printers - [INFO] INFO - ✅ API-Live-Drucker-Status-Abfrage 'get_live_printer_status' erfolgreich in 7.72ms
|
||||
|
||||
@ -2831,3 +2831,9 @@
|
||||
2025-06-01 03:30:12 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread beendet
|
||||
2025-06-01 03:30:12 - [scheduler] scheduler - [INFO] INFO - Scheduler gestoppt
|
||||
2025-06-01 03:31:39 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-01 03:35:40 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-01 03:38:47 - [scheduler] scheduler - [INFO] INFO - Task check_jobs registriert: Intervall 30s, Enabled: True
|
||||
2025-06-01 03:38:48 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread gestartet
|
||||
2025-06-01 03:38:48 - [scheduler] scheduler - [INFO] INFO - Scheduler gestartet
|
||||
2025-06-01 03:39:41 - [scheduler] scheduler - [INFO] INFO - Scheduler-Thread beendet
|
||||
2025-06-01 03:39:41 - [scheduler] scheduler - [INFO] INFO - Scheduler gestoppt
|
||||
|
||||
@ -2,3 +2,4 @@
|
||||
2025-06-01 03:04:48 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-01 03:06:07 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-01 03:29:16 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
2025-06-01 03:38:47 - [security] security - [INFO] INFO - 🔒 Security System initialisiert
|
||||
|
||||
@ -24,3 +24,15 @@
|
||||
2025-06-01 03:31:40 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🧹 Führe 1 Cleanup-Funktionen aus...
|
||||
2025-06-01 03:31:40 - [shutdown_manager] shutdown_manager - [INFO] INFO - ✅ Koordiniertes Shutdown abgeschlossen in 0.0s
|
||||
2025-06-01 03:31:40 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🏁 System wird beendet...
|
||||
2025-06-01 03:35:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
2025-06-01 03:35:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔄 Starte koordiniertes System-Shutdown...
|
||||
2025-06-01 03:35:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🧹 Führe 1 Cleanup-Funktionen aus...
|
||||
2025-06-01 03:35:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - ✅ Koordiniertes Shutdown abgeschlossen in 0.0s
|
||||
2025-06-01 03:35:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🏁 System wird beendet...
|
||||
2025-06-01 03:38:47 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔧 Shutdown-Manager initialisiert
|
||||
2025-06-01 03:39:41 - [shutdown_manager] shutdown_manager - [WARNING] WARNING - 🛑 Signal 2 empfangen - starte koordiniertes Shutdown
|
||||
2025-06-01 03:39:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔄 Starte koordiniertes System-Shutdown...
|
||||
2025-06-01 03:39:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🧹 Führe 5 Cleanup-Funktionen aus...
|
||||
2025-06-01 03:39:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 🔄 Beende Scheduler mit stop()...
|
||||
2025-06-01 03:39:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - ✅ Scheduler erfolgreich gestoppt
|
||||
2025-06-01 03:39:41 - [shutdown_manager] shutdown_manager - [INFO] INFO - 💾 Führe sicheres Datenbank-Cleanup durch...
|
||||
|
||||
@ -34,3 +34,12 @@
|
||||
2025-06-01 03:29:16 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-01 03:29:16 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-01 03:29:16 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-01 03:38:47 - [startup] startup - [INFO] INFO - ==================================================
|
||||
2025-06-01 03:38:47 - [startup] startup - [INFO] INFO - 🚀 MYP Platform Backend wird gestartet...
|
||||
2025-06-01 03:38:47 - [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-01 03:38:47 - [startup] startup - [INFO] INFO - 💻 Betriebssystem: nt (win32)
|
||||
2025-06-01 03:38:47 - [startup] startup - [INFO] INFO - 📁 Arbeitsverzeichnis: C:\Users\TTOMCZA.EMEA\Dev\Projektarbeit-MYP\backend
|
||||
2025-06-01 03:38:47 - [startup] startup - [INFO] INFO - ⏰ Startzeit: 2025-06-01T03:38:47.922824
|
||||
2025-06-01 03:38:47 - [startup] startup - [INFO] INFO - 🪟 Windows-Modus: Aktiviert
|
||||
2025-06-01 03:38:47 - [startup] startup - [INFO] INFO - 🔒 Windows-sichere Log-Rotation: Aktiviert
|
||||
2025-06-01 03:38:47 - [startup] startup - [INFO] INFO - ==================================================
|
||||
|
||||
@ -24,3 +24,13 @@
|
||||
2025-06-01 03:31:39 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-01 03:31:39 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-01 03:31:39 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
2025-06-01 03:35:40 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
|
||||
2025-06-01 03:35:40 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-01 03:35:40 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-01 03:35:40 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
2025-06-01 03:38:46 - [windows_fixes] windows_fixes - [INFO] INFO - 🔧 Wende Windows-spezifische Fixes an...
|
||||
2025-06-01 03:38:46 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Subprocess automatisch gepatcht für UTF-8 Encoding (run + Popen)
|
||||
2025-06-01 03:38:46 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Globaler subprocess-Patch angewendet
|
||||
2025-06-01 03:38:46 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Alle Windows-Fixes erfolgreich angewendet
|
||||
2025-06-01 03:39:41 - [windows_fixes] windows_fixes - [INFO] INFO - 🔄 Starte Windows Thread-Shutdown...
|
||||
2025-06-01 03:39:41 - [windows_fixes] windows_fixes - [INFO] INFO - ✅ Windows Thread-Shutdown abgeschlossen
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user