strong-xylophone-89556
03/24/2025, 7:44 AMMarch 22, 2025 at 15:16 (UTC+5:30)
2025-03-22 09:46:50,851 - INFO - killing process {"pid": 3394}
March 22, 2025 at 15:16 (UTC+5:30)
2025-03-22 09:46:50,657 - INFO - killing process {"pid": 3391}
March 22, 2025 at 15:16 (UTC+5:30)
2025-03-22 09:46:50,657 - ERROR - initialization timed out, killing process {"pid": 3391}
March 22, 2025 at 15:16 (UTC+5:30)
2025-03-22 09:46:49,066 - ERROR - initialization timed out, killing process {"pid": 3388}
March 22, 2025 at 15:16 (UTC+5:30)
2025-03-22 09:46:49,067 - INFO - killing process {"pid": 3388}
Notably, once the CPU maxes out to 100%, no new sessions are being made; the system does not recover or cool down, remaining at maximum usage consistently. I understand that one simple fix would be to switch to an instance with more vCPU, but I’m looking for alternative solutions.refined-appointment-81829
03/24/2025, 2:49 PMstrong-xylophone-89556
03/25/2025, 6:10 AMrefined-appointment-81829
03/25/2025, 1:16 PMtop or find what thread/processes were consuming the CPU? See anything interesting in the log at that time what it was doing that led up to that state? It would be good to try and isolate the root cause of that issue if you can so we can validate it is not something in the Agent code (which I suspect it is not)strong-xylophone-89556
03/25/2025, 1:17 PMrefined-appointment-81829
03/25/2025, 1:18 PMdev right?strong-xylophone-89556
03/25/2025, 1:18 PMnumerous-planet-40727
03/27/2025, 12:16 PMstrong-xylophone-89556
03/27/2025, 12:17 PMstrong-xylophone-89556
03/27/2025, 12:18 PMnumerous-planet-40727
03/27/2025, 12:20 PMstrong-xylophone-89556
03/27/2025, 12:21 PMstrong-xylophone-89556
03/27/2025, 12:21 PM