Похоже на типичный случай, когда алгоритм в прятки. Давай отследим его следы и посмотрим, куда он нас тянет. Принеси код, разберёмся вместе.

2024-01-17 14:02:33,112 ERROR ModuleLoader: Failed to load module 'auth'. Traceback (most recent call last): File 'loader.py', line 58, in load_module ModuleNotFoundError: No module named 'auth' 2024-01-17 14:02:33,113 WARNING UserSession: Session ID 4f7e6c could not be validated, defaulting to guest 2024-01-17 14:02:33,114 INFO Server: Starting maintenance routine, checking health of all services 2024-01-17 14:02:33,115 DEBUG HealthCheck: Checking database connectivity... 2024-01-17 14:02:33,116 DEBUG HealthCheck: Database connection established 2024-01-17 14:02:33,117 INFO AuthService: Authentication service started, listening on port 8080 2024-01-17 14:02:33,118 ERROR AuthService: Unexpected exception during authentication: ValueError('Invalid input') Traceback (most recent call last): File 'auth_service.py', line 102, in authenticate ValueError: Invalid input 2024-01-17 14:02:33,119 INFO Server: All services running, but some errors detected 2024-01-17 14:02:34,010 WARNING Cache: Cache miss for key user_1234 2024-01-17 14:02:34,011 DEBUG Cache: Cache size 0, initializing new cache entry 2024-01-17 14:02:34,012 INFO Cache: Cache entry created for key user_1234 2024-01-17 14:02:34,013 WARNING DiskIO: Disk space low, only 5% remaining 2024-01-17 14:02:34,014 DEBUG DiskIO: Checking available partitions 2024-01-17 14:02:34,015 ERROR DiskIO: Failed to write to /var/log/server.log: Permission denied 2024-01-17 14:02:34,016 WARNING DiskIO: Falling back to temporary storage 2024-01-17 14:02:34,017 DEBUG DiskIO: Temporary storage path /tmp/server.log set 2024-01-17 14:02:34,018 INFO DiskIO: Logging redirected to temporary storage 2024-01-17 14:02:34,019 INFO Server: Running diagnostics on all services 2024-01-17 14:02:34,020 DEBUG Diagnostics: Checking memory usage 2024-01-17 14:02:34,021 INFO Diagnostics: Memory usage at 73% 2024-01-17 14:02:34,022 DEBUG Diagnostics: Checking CPU usage 2024-01-17 14:02:34,023 INFO Diagnostics: CPU usage at 58% 2024-01-17 14:02:34,024 WARNING Security: Unauthorized login attempt from IP 192.168.1.100 2024-01-17 14:02:34,025 DEBUG Security: Rate limiting applied to IP 192.168.1.100 2024-01-17 14:02:34,026 INFO Security: Monitoring continued 2024-01-17 14:02:34,027 DEBUG Security: Checking session tokens 2024-01-17 14:02:34,028 ERROR Security: Token validation failed for session 4f7e6c, potential session hijack 2024-01-17 14:02:34,029 WARNING Security: Session 4f7e6c terminated 2024-01-17 14:02:34,030 INFO Server: Session cleanup completed 2024-01-17 14:02:34,031 DEBUG Network: Performing health check on all endpoints 2024-01-17 14:02:34,032 INFO Network: All endpoints reachable 2024-01-17 14:02:34,033 WARNING Network: Unexpected latency spike detected on endpoint /api/v1/users 2024-01-17 14:02:34,034 DEBUG Network: Latency 250ms, threshold 200ms 2024-01-17 14:02:34,035 ERROR Network: Timeout when fetching user data, retrying 2024-01-17 14:02:34,036 DEBUG Network: Retry attempt 1 for /api/v1/users 2024-01-17 14:02:34,037 WARNING Network: Retry failed, escalating to higher priority 2024-01-17 14:02:34,038 DEBUG Network: Escalation: contacting backup server 2024-01-17 14:02:34,039 INFO Network: Backup server reachable, redirecting traffic 2024-01-17 14:02:34,040 INFO Server: User data fetch successful from backup server 2024-01-17 14:02:34,041 DEBUG Analytics: Tracking user activity for session 4f7e6c 2024-01-17 14:02:34,042 INFO Analytics: Event logged: user_login 2024-01-17 14:02:34,043 WARNING Analytics: Data retention policy violation detected for user_1234 2024-01-17 14:02:34,044 DEBUG Analytics: Purging old data for user_1234 2024-01-17 14:02:34,045 INFO Analytics: Data purged for user_1234 2024-01-17 14:02:34,046 DEBUG Scheduler: Running scheduled tasks 2024-01-17 14:02:34,047 INFO Scheduler: Daily backup task started 2024-01-17 14:02:34,048 WARNING Scheduler: Backup task taking longer than expected 2024-01-17 14:02:34,049 DEBUG Scheduler: Checking backup progress 2024-01-17 14:02:34,050 ERROR Scheduler: Backup failed due to disk full error 2024-01-17 14:02:34,051 WARNING Scheduler: Attempting to clean up temporary backup files 2024-01-17 14:02:34,052 DEBUG Scheduler: Temporary files cleaned, retrying backup 2024-01-17 14:02:34,053 INFO Scheduler: Backup task completed successfully 2024-01-17 14:02:34,054 DEBUG Server: All scheduled tasks completed 2024-01-17 14:02:34,055 INFO Server: System status normal, but anomalies logged 2024-01-17 14:02:34,056 WARNING System: High memory usage detected, consider scaling 2024-01-17 14:02:34,057 DEBUG System: Current memory usage 80% 2024-01-17 14:02:34,058 INFO System: Auto-scaling not triggered yet 2024-01-17 14:02:34,059 WARNING System: CPU usage nearing threshold, 85% 2024-01-17 14:02:34,060 DEBUG System: Checking for CPU-intensive processes 2024-01-17 14:02:34,061 INFO System: No unusual CPU usage detected 2024-01-17 14:02:34,062 WARNING System: Network latency spike observed, 300ms average 2024-01-17 14:02:34,063 DEBUG System: Investigating potential causes 2024-01-17 14:02:34,064 ERROR System: Unknown error in network diagnostics module Traceback (most recent call last): File 'network_diag.py', line 22, in run DiagnosticsError: Network interface down 2024-01-17 14:02:34,065 WARNING System: Network interface down, restarting service 2024-01-17 14:02:34,066 INFO System: Network interface restarted successfully 2024-01-17 14:02:34,067 DEBUG System: Rechecking network status 2024-01-17 14:02:34,068 INFO System: Network status normal again 2024-01-17 14:02:34,069 WARNING System: CPU usage spike during restart, 90% 2024-01-17 14:02:34,070 DEBUG System: CPU usage spike attributed to restart processes 2024-01-17 14:02:34,071 INFO System: CPU usage returning to normal 2024-01-17 14:02:34,072 WARNING System: Memory usage spike during restart, 88% 2024-01-17 14:02:34,073 DEBUG System: Memory spike due to temporary allocations 2024-01-17 14:02:34,074 INFO System: Memory usage normalized 2024-01-17 14:02:34,075 DEBUG Server: Performing routine health check on all modules 2024-01-17 14:02:34,076 INFO Server: All modules healthy 2024-01-17 14:02:34,077 WARNING Server: Unexpected high I/O wait detected 2024-01-17 14:02:34,078 DEBUG I/O: Checking disk queue length 2024-01-17 14:02:34,079 ERROR I/O: Disk queue length exceeded threshold, 120ms 2024-01-17 14:02:34,080 WARNING I/O: Investigating slow disk operations 2024-01-17 14:02:34,081 DEBUG Disk: Checking SMART status 2024-01-17 14:02:34,082 ERROR Disk: SMART attribute failure detected, disk health degraded 2024-01-17 14:02:34,083 WARNING Disk: Scheduling disk replacement, notify admin 2024-01-17 14:02:34,084 INFO Disk: Replacement in progress, system will reboot in 2 minutes 2024-01-17 14:02:34,085 DEBUG Server: Scheduling reboot, no critical operations running 2024-01-17 14:02:34,086 INFO Server: Reboot scheduled 2024-01-17 14:02:34,087 WARNING Server: Reboot imminent, pending tasks will be terminated 2024-01-17 14:02:34,088 DEBUG Server: Gracefully shutting down services 2024-01-17 14:02:34,089 INFO Server: All services stopped 2024-01-17 14:02:34,090 INFO Server: Rebooting now 2024-01-17 14:02:34,091 INFO Server: Reboot complete, services restarting 2024-01-17 14:02:34,092 DEBUG Server: Services are online, checking startup logs 2024-01-17 14:02:34,093 INFO Server: Startup logs cleaned, system ready for operation 2024-01-17 14:02:34,094 WARNING Server: High CPU usage detected during startup, 95% 2024-01-17 14:02:34,095 DEBUG Server: CPU usage spike due to initialization routines 2024-01-17 14:02:34,096 INFO Server: CPU usage normalized 2024-01-17 14:02:34,097 WARNING Server: Disk write latency high, 200ms 2024-01-17 14:02:34,098 DEBUG Disk: Checking write throughput 2024-01-17 14:02:34,099 ERROR Disk: Write throughput decreased, 10% below baseline 2024-01-17 14:02:34,100 WARNING Disk: Potential bottleneck detected 2024-01-17 14:02:34,101 DEBUG Disk: Initiating performance test 2024-01-17 14:02:34,102 INFO Disk: Performance test completed, results logged 2024-01-17 14:02:34,103 WARNING Disk: Disk performance below acceptable levels, recommend replacement soon 2024-01-17 14:02:34,104 INFO Disk: Replacement recommendation recorded 2024-01-17 14:02:34,105 DEBUG Server: All diagnostics complete, system stable 2024-01-17 14:02:34,106 INFO Server: Monitoring ongoing, no critical alerts The timestamp that keeps circling around the stack trace is 2024-01-17 14:02:34,102 where the performance test is logged; that’s where the ghost might be hiding.