-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathserver.out
More file actions
96 lines (96 loc) · 5.84 KB
/
server.out
File metadata and controls
96 lines (96 loc) · 5.84 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
[34m[2025-09-07T05:30:11.160Z] 💡 [Prometheus] Custom Prometheus metrics initialized[0m
[34m[2025-09-07T05:30:11.162Z] 💡 [HealthMonitor] Health check registered: cpu_usage[0m
[34m[2025-09-07T05:30:11.162Z] 💡 [HealthMonitor] Health check registered: memory_usage[0m
[34m[2025-09-07T05:30:11.163Z] 💡 [HealthMonitor] Health check registered: disk_usage[0m
[34m[2025-09-07T05:30:11.163Z] 💡 [HealthMonitor] Health check registered: process_health[0m
[34m[2025-09-07T05:30:11.163Z] 💡 [HealthMonitor] Health check registered: error_rate[0m
[34m[2025-09-07T05:30:11.163Z] 💡 [HealthMonitor] Health check registered: response_time[0m
[34m[2025-09-07T05:30:11.163Z] 💡 [HealthMonitor] Health check registered: network_connectivity[0m
[34m[2025-09-07T05:30:11.163Z] 💡 [HealthMonitor] Default health checks registered[0m
[34m[2025-09-07T05:30:11.164Z] 💡 [Alerting] Alert rule added: high_error_rate[0m
[34m[2025-09-07T05:30:11.164Z] 💡 [Alerting] Alert rule added: high_memory_usage[0m
[34m[2025-09-07T05:30:11.164Z] 💡 [Alerting] Alert rule added: model_inference_failures[0m
[34m[2025-09-07T05:30:11.164Z] 💡 [Alerting] Alert rule added: system_health_degraded[0m
[34m[2025-09-07T05:30:11.164Z] 💡 [Alerting] Alert rule added: performance_degradation[0m
[34m[2025-09-07T05:30:11.164Z] 💡 [Alerting] Default alert rules loaded[0m
[34m[2025-09-07T05:30:11.165Z] 💡 [Monitoring] Monitoring component integrations configured[0m
[34m[2025-09-07T05:30:11.179Z] 💡 [Monitoring] Starting monitoring system...[0m
[32m[2025-09-07T05:30:11.182Z] ✅ [Prometheus] Prometheus metrics server started on port 9090[0m
[34m[2025-09-07T05:30:11.182Z] 💡 [Prometheus] Metrics available at: http://localhost:9090/metrics[0m
[32m[2025-09-07T05:30:11.182Z] ✅ [Monitoring] ✓ prometheus started[0m
[34m[2025-09-07T05:30:11.183Z] 💡 [HealthMonitor] Starting health monitor (interval: 10000ms)[0m
[32m[2025-09-07T05:30:11.184Z] ✅ [Monitoring] ✓ health started[0m
[34m[2025-09-07T05:30:11.184Z] 💡 [Alerting] Starting alerting system[0m
[34m[2025-09-07T05:30:11.202Z] 💡 [Config] 🎛️ Configuration initialized:[0m { environment: 'development', strategy: 'balanced' }
[34m[2025-09-07T05:30:11.205Z] 💡 [Router] 🧭 Router initialized with strategy:[0m balanced
[34m[2025-09-07T05:30:11.205Z] 💡 [LLMRouter] 🚀 LLM-Runner-Router initializing...[0m { version: '2.0.0', environment: 'node' }
[[email protected]] injecting env (8) from .env -- tip: 📡 auto-backup env with Radar: https://dotenvx.com/radar
[34m[2025-09-07T05:30:11.206Z] 💡 [Server] 🚀 LLM Router Server Starting...
[0m
[34m[2025-09-07T05:30:11.210Z] 💡 [Config] 🎛️ Configuration initialized:[0m { environment: 'development', strategy: 'balanced' }
[34m[2025-09-07T05:30:11.210Z] 💡 [Router] 🧭 Router initialized with strategy:[0m balanced
[34m[2025-09-07T05:30:11.210Z] 💡 [LLMRouter] 🚀 LLM-Runner-Router initializing...[0m { version: '2.0.0', environment: 'node' }
[34m[2025-09-07T05:30:11.210Z] 💡 [Config] 🎛️ Configuration initialized:[0m { environment: 'development', strategy: 'balanced' }
[31m[2025-09-07T05:30:11.214Z] ❌ [ErrorHandler] 🚨 CRITICAL: Uncaught Exception:[0m Error: listen EADDRINUSE: address already in use 0.0.0.0:3006
at Server.setupListenHandle [as _listen2] (node:net:1908:16)
at listenInCluster (node:net:1965:12)
at doListen (node:net:2139:7)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '0.0.0.0',
port: 3006
}
[31m[2025-09-07T05:30:11.214Z] ❌ [ErrorHandler] 🚨 CRITICAL ERROR from uncaughtException:[0m {
message: 'listen EADDRINUSE: address already in use 0.0.0.0:3006',
stack: 'Error: listen EADDRINUSE: address already in use 0.0.0.0:3006\n' +
' at Server.setupListenHandle [as _listen2] (node:net:1908:16)\n' +
' at listenInCluster (node:net:1965:12)\n' +
' at doListen (node:net:2139:7)\n' +
' at process.processTicksAndRejections (node:internal/process/task_queues:83:21)',
source: 'uncaughtException',
timestamp: '2025-09-07T05:30:11.214Z',
memoryUsage: {
rss: 169578496,
heapTotal: 88555520,
heapUsed: 64751472,
external: 3728714,
arrayBuffers: 1166433
},
uptime: 2.906852027
}
[31m[2025-09-07T05:30:11.215Z] ❌ [LLMRouter] 🚨 Critical system error detected:[0m {
error: Error: listen EADDRINUSE: address already in use 0.0.0.0:3006
at Server.setupListenHandle [as _listen2] (node:net:1908:16)
at listenInCluster (node:net:1965:12)
at doListen (node:net:2139:7)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '0.0.0.0',
port: 3006
},
source: 'uncaughtException'
}
[31m[2025-09-07T05:30:11.215Z] ❌ [LLMRouter] 🚨 Critical system error detected:[0m {
error: Error: listen EADDRINUSE: address already in use 0.0.0.0:3006
at Server.setupListenHandle [as _listen2] (node:net:1908:16)
at listenInCluster (node:net:1965:12)
at doListen (node:net:2139:7)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '0.0.0.0',
port: 3006
},
source: 'uncaughtException'
}
[34m[2025-09-07T05:30:11.216Z] 💡 [Alerting] Loaded 30 persisted alerts[0m
[32m[2025-09-07T05:30:11.216Z] ✅ [Monitoring] ✓ alerting started[0m
[32m[2025-09-07T05:30:11.216Z] ✅ [Monitoring] Monitoring system started in 37ms[0m
[31m[2025-09-07T05:30:12.215Z] ❌ [ErrorHandler] 🛑 Performing emergency graceful shutdown...[0m
[34m[2025-09-07T05:30:12.215Z] 💡 [ErrorHandler] 🛑 Initiating graceful shutdown...[0m
[34m[2025-09-07T05:30:17.216Z] 💡 [ErrorHandler] ✅ Graceful shutdown completed[0m