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

Stream video to your Kinesis video stream and view the live stream #1188

Open
himadrii27 opened this issue Jun 17, 2024 · 5 comments
Open

Stream video to your Kinesis video stream and view the live stream #1188

himadrii27 opened this issue Jun 17, 2024 · 5 comments
Labels

Comments

@himadrii27
Copy link

himadrii27 commented Jun 17, 2024

On running the command ./kvs_gstreamer_sample camera_37 rtsp://user:password@192.168.1.37:554/Streaming/Channels/102/
I am getting the error
Creating IoT auth callbacks.
[ERROR] [17-06-2024 09:22:32:860.195 GMT] Unable to create Iot Credential provider. Error status: 0x4000000e
[ERROR] [17-06-2024 09:22:32:860.422 GMT] Failed to initialize kinesis video with an exception: Unable to create Iot Credential provider. Error status: 0x4000000e
and 0x4000000e means STATUS_DIRECTORY_ENTRY_STAT_ERROR as per the following documentation. There is no recommended action for this on the documentation.

Do you have any idea how to fix this?

@himadrii27 himadrii27 added the bug label Jun 17, 2024
@disa6302
Copy link
Contributor

@himadrii27 ,

These are some common situations the error could be thrown:

  1. If the path provided to fstat is invalid (e.g., the file does not exist, or there is a typo in the path
  2. If the process does not have the necessary permissions to access the file or directory
  3. An I/O error occurred while trying to retrieve the file status. This could be due to hardware issues or file system corruption

Could you confirm the path provided for the IoT certs is infact valid and has all the necessary permissions?

@disa6302 disa6302 added question and removed bug labels Jun 17, 2024
@sirknightj
Copy link
Contributor

You can also double-check the YouTube tutorial to see if you are missing anything: https://www.youtube.com/watch?v=YoOYTCD_v3Q, it shows running the sample with IoT certificate (X.509) credentials.

Note that for quicker testing, you can also use a standard iam credentials (export AWS_ACCESS_KEY_ID=...): https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/gs-send-data.html#send-data-run-samples

@himadrii27
Copy link
Author

@himadrii27 ,

These are some common situations the error could be thrown:

  1. If the path provided to fstat is invalid (e.g., the file does not exist, or there is a typo in the path
  2. If the process does not have the necessary permissions to access the file or directory
  3. An I/O error occurred while trying to retrieve the file status. This could be due to hardware issues or file system corruption

Could you confirm the path provided for the IoT certs is infact valid and has all the necessary permissions?

@himadrii27
Copy link
Author

@himadrii27 ,

These are some common situations the error could be thrown:

  1. If the path provided to fstat is invalid (e.g., the file does not exist, or there is a typo in the path
  2. If the process does not have the necessary permissions to access the file or directory
  3. An I/O error occurred while trying to retrieve the file status. This could be due to hardware issues or file system corruption

Could you confirm the path provided for the IoT certs is infact valid and has all the necessary permissions?

yea, the path provided for the IoT certs is valid and it has the following permissions

PHOTO-2024-06-18-13-44-42

@himadrii27
Copy link
Author

You can also double-check the YouTube tutorial to see if you are missing anything: https://www.youtube.com/watch?v=YoOYTCD_v3Q, it shows running the sample with IoT certificate (X.509) credentials.

Note that for quicker testing, you can also use a standard iam credentials (export AWS_ACCESS_KEY_ID=...): https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/gs-send-data.html#send-data-run-samples

you mean having all the certificates in cert file and then proceeding? yea, i already did that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants