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

Unraid, "Failed to read "config.toml" when using unassigned drive as appdata drive #340

Open
justinf10000 opened this issue Feb 20, 2023 · 2 comments
Labels
help-wanted Core team isn't going to work on this, but anyone is welcome to tackle it

Comments

@justinf10000
Copy link

justinf10000 commented Feb 20, 2023

Describe the bug
On unraid, when opening console and entering neolink rtsp --config config.toml , i am getting error "Failed to read "config.toml" caused by "no such file or directory (os error 2)

I use an unassigned drive as my appdata drive, and this is probably the issue but i don't know how to fix it.
The host path set for this container is /mnt/disks/ua_appdata/appdata/neolink/config.toml

It runs fine, i copy the config.toml into /mnt/disks/ua_appdata/appdata/neolink/ , but when i run the above command, it throws those errors.

To Reproduce
Community apps plugin --> install neolink --> keep everything default except change neolink_config host path to /mnt/disks/ua_appdata/appdata/neolink/config.toml and change access mode to Read/Write -Slave.
Copy config.toml file i created to /mnt/disks/ua_appdata/appdata/neolink/
Open console and enter neolink rtsp --config config.toml
Get errors

Expected behavior
expect it to run and show connect to camera messages

Versions
NVR software: n/a
Neolink software: not sure how to tell, but says last updated Jan 8, 2023 on the community applications page.
Reolink camera model and firmware: Reolink Lumus firmware v2.0.0.669_20060200
neolinkissues

@justinf10000 justinf10000 added the bug Something isn't working label Feb 20, 2023
@QuantumEntangledAndy
Copy link
Collaborator

Notice how the command line you are using says config.toml but you are mounting at /etc/neolink.toml.

This should be your first thing to address. Change your command line to be neolink rtsp --config=/etc/neolink.toml

@QuantumEntangledAndy QuantumEntangledAndy added help-wanted Core team isn't going to work on this, but anyone is welcome to tackle it and removed bug Something isn't working labels Feb 20, 2023
@justinf10000
Copy link
Author

neolink rtsp --config=/etc/neolink.toml

wow thank you! that worked, i feel dumb lol. The instructions said "Run the following command (with your correct config file name):" but i forgot itd be remapped.
Anyway TY much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help-wanted Core team isn't going to work on this, but anyone is welcome to tackle it
Projects
None yet
Development

No branches or pull requests

2 participants