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

configuration file not found, using an empty configuration #1788

Closed
1 of 13 tasks
Ninja-Spotted opened this issue May 11, 2023 · 3 comments
Closed
1 of 13 tasks

configuration file not found, using an empty configuration #1788

Ninja-Spotted opened this issue May 11, 2023 · 3 comments

Comments

@Ninja-Spotted
Copy link

Which version are you using?

v0.22.2

Which operating system are you using?

  • Linux amd64 standard
  • Linux amd64 Docker
  • Linux arm64 standard
  • Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

After I extracted the mediamtx_v0.22.2_linux_amd64.tar.gz in my Download folder, running the executable with ./mediamtx_v0.22.2_linux_amd64/mediamtx shows me the following message in the Logs:

    2023/05/11 13:10:14 INF MediaMTX / rtsp-simple-server v0.22.2
    2023/05/11 13:10:14 WAR configuration file not found, using an empty configuration
    2023/05/11 13:10:14 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
    2023/05/11 13:10:14 INF [RTMP] listener opened on :1935
    2023/05/11 13:10:14 INF [HLS] listener opened on :8888
    2023/05/11 13:10:14 INF [WebRTC] listener opened on :8889 (HTTP)

Not finding the configuration file. After starting the stream some more messages appeared:

    2023/05/11 13:34:32 INF [RTSP] [conn 192.168.30.232:54176] opened
    2023/05/11 13:34:32 INF [RTSP] [conn 192.168.30.232:54176] closed (path 'mystream' is not configured)

The weird aspect is that this issue only showed up today. I have been running mediamtx for about 2 weeks before and never had this problem starting the streaming.

Describe how to replicate the issue

  1. start the server

  2. start the stream with ffmpeg: ffmpeg -f v4l2 -i /dev/video0 -profile:v high -pix_fmt yuvj420p -level:v 4.1 -preset ultrafast -tune zerolatency -vcodec libx264 -r 10 -b:v 512k -s 1920x1080 -strict -2 -ac 2 -ab 32k -ar 44100 -f mpegts -f rtsp -rtsp_transport tcp rtsp://192.168.30.232:8554/mystream (the command I have been using)

  3. Check the configuration file located in ./mediamtx_v0.22.2_linux_amd64/mediamtx.yml after searching on the internet for a solution I tried to edit the end of the file where paths are specified and left only:

     paths:
         mystream:
             source: Camera
    

Did you attach the server logs?

no

Did you attach a network dump?

no

@Tokolosh
Copy link

Tokolosh commented May 22, 2023

try going into the folder where you have mediamtx and mediamtx.yml

example:
cd /path/to/mediamtx_v0.22.2_linux_amd64
./mediamtx

or follow the instructions to add it as a service that will auto start on boot...
https://github.com/bluenviron/mediamtx#linux

@Ninja-Spotted
Copy link
Author

Thank you so much! This resolved the issue I was having.

Copy link
Contributor

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants