This message was deleted.

Hey @stale-boots-73139 can you describe what the issue is?

I'm currently using egress with docker up and using a vm with 8cpu 32GB specs. Currently, after completing the socket connection to the room, when I request egress to start recording the room, egress is terminated and the recording is not recorded for more than a certain number of seconds. @dry-elephant-14928

what kind of egress are you performing? it'd be best to look at Egress logs for clues

2023-06-27T08:59:33.660812458Z 2023-06-27T08:59:33.660Z INFO    egress  source/web.go:240       chrome: START_RECORDING {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G"}
2023-06-27T08:59:35.983356953Z 2023-06-27T08:59:35.983Z INFO    egress  pipeline/watch.go:152   pipeline playing        {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G"}
2023-06-27T08:59:35.983395928Z 2023-06-27T08:59:35.983Z INFO    egress  service/handler.go:214  egress updated  {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G", "egressID": "EG_M6aU8bDBhe6G", "request_type": "room_composite", "output_type": "file", "status": "EGRESS_ACTIVE"}
2023-06-27T08:59:48.670726892Z 2023-06-27T08:59:48.670Z INFO    egress  source/web.go:250       chrome: END_RECORDING   {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G"}
2023-06-27T08:59:48.670749202Z 2023-06-27T08:59:48.670Z INFO    egress  service/handler.go:214  egress updated  {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G", "egressID": "EG_M6aU8bDBhe6G", "request_type": "room_composite", "output_type": "file", "status": "EGRESS_ENDING"}
2023-06-27T08:59:48.671413679Z 2023-06-27T08:59:48.671Z INFO    egress  pipeline/pipeline.go:382        sending EOS to pipeline {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G"}
2023-06-27T08:59:48.685403444Z 2023-06-27T08:59:48.685Z INFO    egress  pipeline/watch.go:68    EOS received, stopping pipeline {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G"}
2023-06-27T08:59:48.691829418Z 2023-06-27T08:59:48.691Z INFO    egress  pipeline/pipeline.go:498        pipeline stopped        {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G"}
2023-06-27T08:59:48.936383283Z 2023-06-27T08:59:48.936Z DEBUG   egress  sink/file.go:59 removing temporary directory    {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G", "path": "/tmp/lkegress/EG_M6aU8bDBhe6G/"}
2023-06-27T08:59:48.936458405Z 2023-06-27T08:59:48.936Z INFO    egress  service/handler.go:208  egress completed        {"nodeID": "NE_mqpkJ9RAHmEL", "handlerID": "EGH_cAGVmo9siBh3", "clusterID": "", "egressID": "EG_M6aU8bDBhe6G", "egressID": "EG_M6aU8bDBhe6G", "request_type": "room_composite", "output_type": "file"}

here is my egress logs, and i use roomComposite recording, and also I dont request egress ended after connection finished. @dry-elephant-14928