wooden-smartphone-55787
07/10/2025, 10:11 AM{
"message": "process is unresponsive, killing process",
"level": "ERROR",
"name": "livekit.agents",
"pid": 158,
"job_id": "qqqqqq",
"timestamp": "2025-07-10T09:48:40.321168+00:00"
}
tall-airline-16756
07/10/2025, 10:11 AMtall-airline-16756
07/10/2025, 10:12 AMprocess is unresponsive, killing process
in livekit.agents
logs indicates that a supervised process stopped responding to periodic health checks (ping-pong messages) sent by the supervisor. When the process fails to respond within the configured ping_timeout
period, it is considered unresponsive and is terminated. The main causes are:
• High processing load or resource exhaustion causes missed or delayed ping responses.
• Configuration issues such as too-short timeout values.
• Exceeded memory limits or process initialization timeouts (though these produce distinct log messages).
Recommended steps:
1. Review ping_interval
, ping_timeout
, and high_ping_threshold
in your configuration, and adjust them if your processes are expected to have high workloads or latency.
2. Monitor process memory and CPU usage to ensure sufficient system resources are available.
3. Check previous log lines for warnings like process is unresponsive
(which include delay information) or memory warnings.
4. If the workload is expected to cause high latency, consider increasing timeout settings and thresholds accordingly.
Adjusting these parameters and monitoring system and application logs should help identify whether this is a configuration, resource, or workload issue. Let me know if you need guidance reviewing your current configuration, or if you can share the relevant timeout and resource settings.
Sources: .github/next-release/changeset-e46145c3.md