Gstreamer Error

[brendan-Wursta]

Hi All, had the following dockerfile working great for streaming a local file two weeks ago but it isn't working now. Any thoughts?

Dockerfile:

FROM gcr.io/visionai-public-images/vaictl

COPY stream1.mp4 .
COPY myCredentials.json .

ENV GOOGLE_APPLICATION_CREDENTIALS=./myCredentials.json

CMD echo "Google Application Credentials are set to: $GOOGLE_APPLICATION_CREDENTIALS"
ENTRYPOINT vaictl -p myProjectName -l us-central1 -c application-cluster-0 --service-endpoint visionai.googleapis.com send video-file to streams myStreamName --file-path stream1.mp4 --loop

Running in docker with the following:

docker build -t visionai .
docker run -it visionai

(also tried above with docker run --platform linux/amd64 -it visionai as it sometimes errors out)

[dchao34]

Hi!

Do you have any logs or error messages?

Also, do you have the your project id? Is it literally "myProjectName"?

Thanks!

• Daniel

FYI @yxue

[brendan-Wursta]

Hi Daniel, Thanks for taking a look! Errors included below. I have the right project name in my personal vaictl command, but just put myProjectName for simplicity above.

E20230505 15:42:29.542289   545 gstreamer_runner.cc:88] Additional debug info: third_party/gstreamer/subprojects/gst_plugins_good/gst/isomp4/qtdemux.c(501): gst_qtdemux_post_no_playable_stream_error (): /GstPipeline:pipeline517/GstQTDemux:qtdemux517:
no known streams found
E20230505 15:42:29.542340   545 gstreamer_runner.cc:90] Got gstreamer error; shutting down event loop
E20230505 15:42:29.544477     8 ingester.cc:241] UNKNOWN: Stream removed; while checking if a stream exists in the cluster; while opening event "jz6dr96x"; while writing a packet into an event sink; while handling a packet filtered element
E20230505 15:42:29.546437     8 ingester_app.cc:71] UNKNOWN: The dataflow encounterd an error. See logs for more details.; while stopping modules
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted

[dchao34]

Ah, I observe this problem elsewhere too. Will get back to you.

[dchao34]

I believe we found the problem. The fix will land in production some time late next week.

[brendan-Wursta]

Hi @dchao34 , any update on this issue?

[dchao34]

Hey! I think it should be resolved now. You can try again.

[brendan-Wursta]

Working now. Thanks @dchao34, appreciate your help!