-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
[BUG] Media collecter cannot find smartctl when run by cron #2 #304
Comments
Hey @TehloWasTaken are you running the Scrutiny collector via a manual install? or is this inside the Docker image? |
@AnalogJ I'd like to request that an explicit path to smartctl can be defined in the collector.yaml file and/or an environment variable. It might resolve cron spawned env PATH issues, and be safer than running an arbitrary executable named smartctl somewhere in the path with root privilege. e.g. |
…ry used by metrics collector. - fixes #304
@gofaster great idea, I just implemented this change in the the collector config file would need to be edited:
|
@AnalogJ Thanks for the quick feature addition. Can you please build an amd64 linux binary for the beta collector? My collectors run standalone without docker. |
Hey @gofaster sorry for the delay, I had to fix some tests. You can download a zip file containing all the binaries here
|
@AnalogJ The definable smartctl path option works great. Thanks! |
great, this will be included in v0.4.14 (when it's released) |
Describe the bug
scrutiny-collector-metrics-linux-amd64 cannot find smartctl when run by cron.
Expected behavior
Collector program to run
Screenshots
If applicable, add screenshots to help explain your problem.
Log Files
CRON command is the following (set to one minute for testing purposes)
*/1 * * * * . /etc/profile; /opt/scrutiny/bin/scrutiny-collector-metrics-linux-amd64 run --api-endpoint "http://10.0.1.114:8080" > /tmp/scrutiny.log 2>&1
It's the exact same issue as in issue #76
The text was updated successfully, but these errors were encountered: