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 files were not found #12

Open
BKPepe opened this issue Aug 21, 2022 · 4 comments
Open

Configuration files were not found #12

BKPepe opened this issue Aug 21, 2022 · 4 comments

Comments

@BKPepe
Copy link
Contributor

BKPepe commented Aug 21, 2022

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))

@operutka
Copy link
Member

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 /etc/angelcam-connector.

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 /etc/arrow.

@BKPepe
Copy link
Contributor Author

BKPepe commented Aug 22, 2022

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.

You got me on this one. I am not sure right now! I was testing this after midnight. I will re-check this.

In such case the application would try to look up its configuration files under the default path which is /etc/arrow.

Maybe, it would be good to use one folder across different packages instead of multiple folders for each platform.

@operutka
Copy link
Member

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 /etc/arrow folder is the default for the Arrow Client application and it needs to stay like that to avoid breaking existing deployments.

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 arrow-client or using the /etc/arrow config path would be even more confusing here.

@BKPepe
Copy link
Contributor Author

BKPepe commented Aug 22, 2022

I haven't look at it further, but it makes sense. OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants