Hi team, I am self hosting livekit. The egress service abruptly stops sometimes after logging that it's connecting to redis. The livekit server cancels the recording after 10s since it doesn't get any response from egress service.

2026-02-13T07:05:59.764Z	INFO	egress	pipeline/watch.go:115	pipeline received EOS	{"nodeID": "NE_JGn2CW6uEUET", "handlerID": "EGH_DCTYA66WgMtY", "clusterID": "", "egressID": "EG_qfzmKVSQR9wb"}
2026-02-13T07:06:00.127Z	INFO	egress	info/io.go:269	egress_complete	{"nodeID": "NE_JGn2CW6uEUET", "clusterID": "", "egressID": "EG_qfzmKVSQR9wb", "requestType": "room_composite", "outputType": "file", "error": "", "code": 0, "details": "End reason: Source closed"}
2026-02-13T07:24:38.141Z	INFO	egress	server/server_rpc.go:59	request received	{"nodeID": "NE_JGn2CW6uEUET", "clusterID": "", "egressID": "EG_dz3JMaE3cvex"}
2026-02-13T07:24:38.141Z	INFO	egress	server/server_rpc.go:69	request validated	{"nodeID": "NE_JGn2CW6uEUET", "clusterID": "", "egressID": "EG_dz3JMaE3cvex", "requestType": "room_composite", "sourceType": "EGRESS_SOURCE_TYPE_WEB", "outputType": "file", "room": "study_698dc93713cf9c6e82b1a8e3_participant_698dcb4d13cf9c6e82b1a8e6_e0d60f", "request": {"RoomComposite":{"room_name":"study_698dc93713cf9c6e82b1a8e3_participant_698dcb4d13cf9c6e82b1a8e6_e0d60f","layout":"grid-dark","Output":null,"Options":null,"file_outputs":[{"file_type":1,"filepath":"study_698dc93713cf9c6e82b1a8e3_participant_698dcb4d13cf9c6e82b1a8e6_e0d60f/media","Output":{"Azure":{"account_name":"{account_name}","account_key":"{account_key}","container_name":"interview"}}}]}}}
2026-02-13T07:24:38.156Z	INFO	egress	redis/redis.go:144	connecting to redis	{"nodeID": "NE_JGn2CW6uEUET", "handlerID": "EGH_iSDJGyGmoBXM", "clusterID": "", "egressID": "EG_dz3JMaE3cvex", "simple": true, "addr": "localhost:6379"}

I am running egress, livekit and redis on a single machine. Attached is my init script for all the docker containers.

Hey @strong-hydrogen-34992 - you will have to look into debug logs - please set DEBUG level logs and try to reproduce. These logs will likely point you to the problem.

Hey @clever-nail-49292, thanks for the advice, I was able to debug the issue by using debug logs. Issue: I was running it on a 4 core machine which only supports 1 concurrent recording. One small feedback: Can you update the documention of logging in egress service. It would really help the future developers. Current documentation:

log_level: debug, info, warn, or error (default info)

Updated docs:

logging: 
    level: debug, info, warn, or error (default info)