no one is publishing to path 'cam'

[AntouanK]

Hi there.

Trying to serve rtsp for a couple of usb cameras I have.
I'm starting the docker container with my device, and when a client ( motioneye ) connects, I get this log

connected
OPTIONS
DESCRIBE
ERR: no one is publishing to path 'cam'
disconnected

my config

/rtsp-server >>> cat rtsp-simple-server.yml                                                                               [130]
                                                                                                                                 
paths:                                                                                                                           
  cam:                                                                                                                           
    runOnInit: vlc  -f v4l2 -i /dev/video0 -f rtsp --rtsp-tcp rtsp://localhost:$RTSP_PORT/$RTSP_PATH                             
    runOnInitRestart: yes   

also tried with

ffmpeg -f v4l2 -i /dev/video0 -f rtsp rtsp://localhost:$RTSP_PORT/$RTSP_PATH

my command

docker run -d --name rtsp-server --device=/dev/video0 -v $(pwd)/rtsp-simple-server.yml:/rtsp-simple-server.yml -e RTSP_PROTOCOLS=tcp -p 8554:8554 aler9/rtsp-simple-server

any idea why I cannot see the camera video?
do I have to publish it somehow?

thank you

[aler9]

Hello,
This configuration works perfectly on my pc:

paths:                                                                                                                           
  cam:                                                                                                                           
    runOnInit: ffmpeg -f v4l2 -i /dev/video0 -f rtsp rtsp://localhost:$RTSP_PORT/$RTSP_PATH
    runOnInitRestart: yes

Try it with a normal release (not with docker).

Afterwards, after you succeeded in making the camera works, you can try docker.
The docker image doesn't include ffmpeg (otherwise it would be huge), you must create a custom image with both rtsp-simple-server and ffmpeg inside, like this

docker build -t myimage - << EOF
FROM aler9/rtsp-simple-server AS server
FROM alpine:3.12
RUN apk add --no-cache ffmpeg
COPY --from=server /rtsp-simple-server /rtsp-simple-server
ENTRYPOINT [ "/rtsp-simple-server" ]
EOF

then

docker run --rm -it --network=host \
--device=/dev/video0 \
-e RTSP_PATHS_CAM_RUNONINIT='ffmpeg -f v4l2 -i /dev/video0 -f rtsp rtsp://localhost:$RTSP_PORT/$RTSP_PATH' \
myimage

(and it works)

[AntouanK]

Thank you for the answer.

I ended up using https://github.com/gen2brain/cam2ip to just expose them as mjpeg cameras.
I'll try to find time to see if I can try the rtsp server again.

[AntouanK]

@aler9 I was trying the example you gave.
In the example you have a rtsp host and port.
I'm confused, I thought this container starts an rtsp server, why is it looking for one?
I don't have some rtsp server somewhere, I want to make one, to expose those /dev/videoX devices.

to explain what I'm trying to do
basically I have 2 usb cameras on a laptop, and I want to expose them to some cctv software ( like shinobi or motioneye )
The whole reason is that the laptop is very old and weak, so all it can do is expose the cameras. And then on my main PC at home I can connect to the cameras.

[AntouanK]

I started a docker container with the server, and then a separate one with ffmpeg like you posted.
the second one seems to be working fine, I can see the ffmpeg streaming and it's not breaking.

I get this log when the second one starts :

020/11/13 10:41:45 [1/0/0] [client 172.17.0.1:50542] connected                                 
2020/11/13 10:41:45 [1/0/0] [client 172.17.0.1:50542] OPTIONS                                   
2020/11/13 10:41:45 [1/0/0] [client 172.17.0.1:50542] ANNOUNCE                                  
2020/11/13 10:41:45 [1/0/0] [client 172.17.0.1:50542] SETUP
2020/11/13 10:41:45 [1/0/0] [client 172.17.0.1:50542] ERR: UDP streaming is disabled
2020/11/13 10:41:45 [1/0/0] [client 172.17.0.1:50542] SETUP
2020/11/13 10:41:45 [1/0/0] [client 172.17.0.1:50542] RECORD
2020/11/13 10:41:45 [1/1/0] [client 172.17.0.1:50542] is publishing to path 'cam', 1 track with 
tcp

but when a client tries to connect I get

2020/11/13 10:41:51 [2/1/0] [client xxx:38532] connected
2020/11/13 10:41:51 [1/1/0] [client xxx:38532] disconnected
2020/11/13 10:41:51 [2/1/0] [client xxx:38534] connected
2020/11/13 10:41:51 [2/1/0] [client xxx:38534] ERR: unable to parse url (/cam)

any idea why?
I'm using "cam" in the yml file, and /cam at the end of the url

[aler9]

I'm confused, I thought this container starts an rtsp server, why is it looking for one?
I don't have some rtsp server somewhere, I want to make one, to expose those /dev/videoX devices.

given this command

docker build -t myimage - << EOF
FROM aler9/rtsp-simple-server AS server
FROM alpine:3.12
RUN apk add --no-cache ffmpeg
COPY --from=server /rtsp-simple-server /rtsp-simple-server
ENTRYPOINT [ "/rtsp-simple-server" ]
EOF
docker run --rm -it --network=host \
--device=/dev/video0 \
-e RTSP_PATHS_CAM_RUNONINIT='ffmpeg -f v4l2 -i /dev/video0 -f rtsp rtsp://localhost:$RTSP_PORT/$RTSP_PATH' \
myimage

here's what happens

1. rtsp-simple-server is started
2. rtsp-simple-server, during initialization, also starts an ffmpeg instance that grabs the camera and sends it to the server itself

I started a docker container with the server, and then a separate one with ffmpeg like you posted.

If you used the command above, you shouldn't run two containers, one is enough

when a client tries to connect I get

which client are you using?

[bluenviron-bot]

This discussion is being locked automatically because the last update was more than 2 years ago.

Do not use the content of this discussion as reference since it's probably outdated!

The official documentation is the only place in which you can find up-to-date answers.