https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
a
Copy code
s023-07-03T12:22:41.523Z    INFO    egress  redis/redis.go:92   connecting to redis {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": "", "simple": true, "addr": "redis-svc:6379"}
2023-07-03T12:22:41.563Z    INFO    egress  stats/monitor.go:135    available CPU cores: 6 max cost: 4.000000   {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": ""}
2023-07-03T12:22:41.581Z    DEBUG   egress  service/debug.go:24 debug handler disabled  {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": ""}
2023-07-03T12:22:41.581Z    DEBUG   egress  service/service.go:77   starting service    {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": "", "version": "1.7.3"}
2023-07-03T12:22:41.581Z    DEBUG   egress  service/templates_server.go:24  starting template server on address localhost:7980  {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": ""}
2023-07-03T12:22:41.585Z    DEBUG   egress  service/service_deprecated.go:27    service ready   {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": ""}
2023-07-03T12:22:52.163Z    INFO    egress  service/service.go:111  request received    {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": "", "egressID": "EG_8tr8kWochxP4"}
2023-07-03T12:22:52.165Z    INFO    egress  service/service.go:119  request validated   {"nodeID": "NE_oAL7YXrDkx5P", "clusterID": "", "egressID": "EG_8tr8kWochxP4", "request_type": "room_composite", "output_type": "file", "room": "my-room", "request": {"RoomComposite":{"room_name":"my-room","layout":"speaker","Output":{"File":{"file_type":1,"filepath":"livekit-demo/","Output":null}},"Options":null}}}
2023-07-03T12:22:52.262Z    DEBUG   egress  server/main.go:169  handler launched    {"nodeID": "NE_oAL7YXrDkx5P", "handlerID": "EGH_SYVBrA7QnjD5", "clusterID": "", "egressID": "EG_8tr8kWochxP4"}
2023-07-03T12:22:52.263Z    INFO    egress  redis/redis.go:92   connecting to redis {"nodeID": "NE_oAL7YXrDkx5P", "handlerID": "EGH_SYVBrA7QnjD5", "clusterID": "", "egressID": "EG_8tr8kWochxP4", "simple": true, "addr": "redis-svc:6379"}
2023-07-03T12:22:52.285Z    DEBUG   egress  source/web.go:143   launching xvfb  {"nodeID": "NE_oAL7YXrDkx5P", "handlerID": "EGH_SYVBrA7QnjD5", "clusterID": "", "egressID": "EG_8tr8kWochxP4", "display": ":1033851095", "dims": "1920x1080x24"}
2023-07-03T12:22:52.286Z    DEBUG   egress  source/web.go:174   launching chrome    {"nodeID": "NE_oAL7YXrDkx5P", "handlerID": "EGH_SYVBrA7QnjD5", "clusterID": "", "egressID": "EG_8tr8kWochxP4", "url": "<http://localhost:7980/?layout=speaker&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2ODg0NzMzNzIsImlzcyI6ImRldmtleSIsIm5iZiI6MTY4ODM4Njk3Miwic3ViIjoiRUdfOHRyOGtXb2NoeFA0IiwidmlkZW8iOnsiY2FuUHVibGlzaCI6ZmFsc2UsImNhblB1Ymxpc2hEYXRhIjpmYWxzZSwiY2FuU3Vic2NyaWJlIjp0cnVlLCJoaWRkZW4iOnRydWUsInJlY29yZGVyIjp0cnVlLCJyb29tIjoibXktcm9vbSIsInJvb21Kb2luIjp0cnVlfX0.9I9nfQCehlgyI-96fbAm-yCy61_Owsm_4RmDjvxKSZs&url=ws%3A%2F%2Flivekit%3A7880>"}
2023-07-03T12:22:52.958Z    DEBUG   egress  pipeline/pipeline.go:166    waiting for start signal    {"nodeID": "NE_oAL7YXrDkx5P", "handlerID": "EGH_SYVBrA7QnjD5", "clusterID": "", "egressID": "EG_8tr8kWochxP4"}
2023-07-03T12:23:07.987Z    INFO    egress  source/web.go:252   chrome: END_RECORDING   {"nodeID": "NE_oAL7YXrDkx5P", "handlerID": "EGH_SYVBrA7QnjD5", "clusterID": "", "egressID": "EG_8tr8kWochxP4"}
d
did anyone publish to the room? the default template would start recording only when the first track has been published: https://github.com/livekit/egress/blob/main/template-default/src/Room.tsx#L66
a
@dry-elephant-14928 I'm calling startRoomCompositeEgress as soon as the room is created, using wehooks event. And then media is publish before the "waiting for start signal" (not sure if it is relevant or not). But on the webhook I don't receive track_published event. Which makes me think that something is not configured properly.
Copy code
leiaa-interview-service-livekit-1         | {"level":"info","ts":1688466045.5395367,"logger":"livekit","caller":"rtc/participant.go:1198","msg":"mediaTrack published","room":"my-room","roomID":"RM_J6jCvyuTYvUF","participant":"rabreu","pID":"PA_XbEzyuzRzcgU","remote":false,"kind":"video","trackID":"TR_VCAojGm4PxGbf2","webrtcTrackID":"b66243bf-939b-44e7-923b-57ea7b48e856","rid":"q","SSRC":4128474531,"mime":"video/VP8"}
leiaa-interview-service-livekit-1         | {"level":"info","ts":1688466045.5500493,"logger":"livekit","caller":"rtc/participant.go:1198","msg":"mediaTrack published","room":"my-room","roomID":"RM_J6jCvyuTYvUF","participant":"rabreu","pID":"PA_XbEzyuzRzcgU","remote":false,"kind":"video","trackID":"TR_VCAojGm4PxGbf2","webrtcTrackID":"b66243bf-939b-44e7-923b-57ea7b48e856","rid":"h","SSRC":2569397893,"mime":"video/VP8"}
leiaa-interview-service-livekit-1         | {"level":"info","ts":1688466045.552106,"logger":"livekit","caller":"rtc/participant.go:1198","msg":"mediaTrack published","room":"my-room","roomID":"RM_J6jCvyuTYvUF","participant":"rabreu","pID":"PA_XbEzyuzRzcgU","remote":false,"kind":"audio","trackID":"TR_AMdeXF2r7AaQqh","webrtcTrackID":"6dd96904-53f0-42fc-8e50-3d8fbda6d7ae","rid":"","SSRC":3363822786,"mime":"audio/red"}
leiaa-interview-service-livekit-1         | {"level":"info","ts":1688466045.7664754,"logger":"livekit","caller":"rtc/participant.go:1198","msg":"mediaTrack published","room":"my-room","roomID":"RM_J6jCvyuTYvUF","participant":"rabreu","pID":"PA_XbEzyuzRzcgU","remote":false,"kind":"video","trackID":"TR_VCAojGm4PxGbf2","webrtcTrackID":"b66243bf-939b-44e7-923b-57ea7b48e856","rid":"f","SSRC":3892662080,"mime":"video/VP8"}
I think the bigger problem is not receiving the event swith this livekit version, I feel that something might be missing in my config:
Copy code
port: 7880
rtc:
    tcp_port: 7881
    use_external_ip: true
room:
    auto_create: true
redis:
  address: redis-svc:6379
keys:
    devkey: <mykey>
logging:
    json: true
    level: info
    pion_level: debug
webhook:
    api_key: devkey
    urls:
        - "<http://backend-server:3010/webhooks>"
turn:
    enabled: true
    udp_port: 443
Livekit works but I don't receive the events
d
your config looks correct. it's not clear why your webhooks aren't being received.. are there any errors in livekit server logs?
a
No, not even warnings, I downgraded livekit to version 1.4.1, and the webhooks work fine now. Although now I get all the events, I needed to also downgrade egress because the Start signal wouldn’t trigger for some reason. I’m not sure if is something related to the “psrpc”, or some additional config. Although version 1,6 seem to work properly in terms of the described flow in the docs. Anyway the recordings seem to end after aprox 15 seconds and the file is empty. I’m using the default room composite but tried track and web it does the same thing 🤔
@dry-elephant-14928 Do you have any ideia of what might be happening here? The rest works fine I can make calls normally but for recordings, doesn't work. I'm running everything through a docker compose don't know if that's relevant here.
d
sorry, it's not clear what's happening. as noted, Egress does not appear to be recording because 
START_RECORDING
was not logged to console. try using our default templates and ensure someone is actually publishing a 
Source.VIDEO
track to the room
in terms of webhook, if configured properly, you should see these log lines:
Copy code
2023-07-06T23:48:16.312-0700	INFO	livekit	webhook/url_notifier.go
2 Views
Open in Slack
PreviousNext
Powered by