-
Notifications
You must be signed in to change notification settings - Fork 2
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 files were not found #12
Comments
That's weird. I've tested it under TurrisOS 5.3.8 running on Omnia and I didn't have any issues. Can you post here contents of your init script? If you take a look at the init scripr installed by the package Makefile (https://github.com/angelcam/turris-packages/blob/master/angelcam-connector/files/init-script), you'll see that the Arrow Client is configured to look up its configuration files in Aren't those log messages that you saw in your log just some remnants from a previous experimentation? You'd see log messages like this if you attempted to start the angelcam-connector app directly without the init script. In such case the application would try to look up its configuration files under the default path which is |
You got me on this one. I am not sure right now! I was testing this after midnight. I will re-check this.
Maybe, it would be good to use one folder across different packages instead of multiple folders for each platform. |
It isn't platform dependent. The However, we've decided to name the application and the package for TurrisOS/OpenWrt Angelcam Connector. Angelcam Connector is the marketing name that we use for our Arrow Client. Arrow Client is the code-name under which the application was originally developed. I understand your confusion here but I think that naming the binary |
I haven't look at it further, but it makes sense. OK |
I started angelcam via
/etc/init.d/angelcam-connector start
and I see this in the system log and I don't think it is a correct behavior.Aug 21 23:25:06 turris [6969]: [src/utils/mod.rs:127] unable to read configuration file skeleton"/etc/arrow/config-skel.json" (No such file or directory (os error 2))
Aug 21 23:25:06 turris [6969]: [src/utils/mod.rs:127] unable to read configuration file "/etc/arrow/config.json" (No such file or directory (os error 2))
Aug 21 23:25:06 turris [6969]: [src/storage.rs:283] creating configuration file skeleton "/etc/arrow/config-skel.json"
Aug 21 23:25:06 turris [6969]: [src/utils/mod.rs:127] unable to create configuration file skeleton "/etc/arrow/config-skel.json" (No such file or directory (os error 2))
While checking which files provides angelcam-connector by using
opkg files angelcam-connector
, I see that it does not create folder/etc/arrow
And also, it was not possible to load MJPEG and RTSP paths:
Aug 21 23:25:06 turris [6969]: [src/utils/mod.rs:127] unable to load RTSP paths (No such file or directory (os error 2))
Aug 21 23:25:06 turris [6969]: [src/utils/mod.rs:127] unable to load MJPEG paths (No such file or directory (os error 2))
The text was updated successfully, but these errors were encountered: