Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] error 'Start signal not received' #827

Open
yspreen opened this issue Dec 17, 2024 · 0 comments
Open

[BUG] error 'Start signal not received' #827

yspreen opened this issue Dec 17, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@yspreen
Copy link

yspreen commented Dec 17, 2024

livekit-server-1.8.0
egress-1.8.4
ingress-1.2.2

I'm starting an egress with the egress client like

  const egressClient = new EgressClient(
    `ws://${LK_SERVER_URL}`,
    LK_API_KEY,
    LK_API_SECRET
  );

  const fileOutput = new EncodedFileOutput({
    fileType: EncodedFileType.MP4,
    filepath: `recordings/${petName}/${new Date()
      .toISOString()
      .slice(0, 19)}-${roomName}-egress`,
    output: {
      case: "s3",
      value: {
        accessKey: AWS_ACCESS_KEY,
        secret: AWS_SECRET_KEY,
        bucket: AWS_BUCKET,
        region: "us-east-1", // minio region
        endpoint: "http://minio-service:9000",
      },
    },
  });

  const info = await egressClient.startRoomCompositeEgress(
    roomName,
    fileOutput,
    {
      layout: "speaker",
    }
  );

  console.log({ info }, JSON.stringify(info));

where minio-service is a k8s service.

after starting, I get

{
  info: EgressInfo {
    egressId: 'EG_FAo7He3hZmZZ',
    roomId: 'RM_R6wNs7Y6U6wP',
    roomName: 'qpvelvwbadwz',
    status: 0,
    startedAt: 0n,
    endedAt: 0n,
    updatedAt: 1734395184524076748n,
    details: '',
    error: '',
    errorCode: 0,
    request: { case: 'roomComposite', value: [RoomCompositeEgressRequest] },
    result: { case: 'file', value: [FileInfo] },
    streamResults: [],
    fileResults: [ [FileInfo] ],
    segmentResults: [],
    imageResults: [],
    manifestLocation: '',
    backupStorageUsed: false
  }
}

as a response.

when stopping the egress later, no file has been added to my minio bucket. I read back the status and get

{
  info: EgressInfo {
    egressId: 'EG_d7ZpdxrMFCJP',
    roomId: 'RM_c8s6jStdEx7N',
    roomName: 'zbxaoimkcxjd',
    status: 5,
    startedAt: 1734389680767646215n,
    endedAt: 1734389736409104765n,
    updatedAt: 1734389736409104765n,
    details: '',
    error: 'Start signal not received',
    errorCode: 412,
    request: { case: 'roomComposite', value: [RoomCompositeEgressRequest] },
    result: { case: 'file', value: [FileInfo] },
    streamResults: [],
    fileResults: [ [FileInfo] ],
    segmentResults: [],
    imageResults: [],
    manifestLocation: '',
    backupStorageUsed: false
  }
}

other's have said I need to log START_RECORDING but we're talking about an egress service running in k8s here. logging from my client that talks to the egress via the egress api will hardly do anything.

here's the logs of the egress service in k8s

2024-12-17T00:26:24.523Z INFO egress server/server_rpc.go:54 request received {"nodeID": "NE_ngBWXu7hdQmu", "clusterID": "", "egressID": "EG_FAo7He3hZmZZ"}
2024-12-17T00:26:24.528Z INFO egress server/server_rpc.go:71 request validated {"nodeID": "NE_ngBWXu7hdQmu", "clusterID": "", "egressID": "EG_FAo7He3hZmZZ", "requestType": "room_composite", "outputType": "file", "room": "qpvelvwbadwz", "request": {"RoomComposite":{"room_name":"qpvelvwbadwz","layout":"speaker","Output":{"File":{"file_type":1,"filepath":"recordings/relieved_maroon_gibbon/2024-12-17T00:26:23-qpvelvwbadwz-egress","Output":{"S3":{"access_key":"{access_key}","secret":"{secret}","region":"us-east-1","endpoint":"http://minio-service:9000","bucket":"main"}}}},"Options":null,"file_outputs":[{"file_type":1,"filepath":"recordings/relieved_maroon_gibbon/2024-12-17T00:26:23-qpvelvwbadwz-egress","Output":{"S3":{"access_key":"{access_key}","secret":"{secret}","region":"us-east-1","endpoint":"http://minio-service:9000","bucket":"main"}}}]}}}
2024-12-17T00:26:24.549Z INFO egress redis/redis.go:142 connecting to redis {"nodeID": "NE_ngBWXu7hdQmu", "handlerID": "EGH_2abppHJuyrQs", "clusterID": "", "egressID": "EG_FAo7He3hZmZZ", "simple": true, "addr": "redis-headless:6379"}
2024-12-17T00:26:41.390Z INFO egress service/io.go:75 egress updated {"nodeID": "NE_ngBWXu7hdQmu", "clusterID": "", "egressID": "EG_FAo7He3hZmZZ", "requestType": "room_composite", "outputType": "file", "status": "EGRESS_ABORTED"}
@yspreen yspreen added the bug Something isn't working label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants