-
Notifications
You must be signed in to change notification settings - Fork 26
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
Systemd service not working #73
Comments
Hey @fanis, thanks for your report. I tested it the same way you did, I cloned the project to /usr/local/src and found this problem:
After fixing this problem, I was able to run with the systemd service exactly as you did, the only difference is that I set the python from a venv, so you need to make sure that all the dependencies in
I'll send the fix so you can test it. |
Hey @phsmith , thanks for the fix, not sure why I hadn't gotten a notifciation from Github on your comments. I was just coming here to update that I just found the problem and fixed it, the systemd file just needed a
I noticed that when testing running the command manually I was already in that directory - moving out of it surfaced the error. Perhaps this is a side-effect of what you fixed anyway, but it works for me :) |
I used the example systemd service, set
RUNDECK_TOKEN
andOPTIONS
in a new/etc/default/rundeck_exporter
file, however it fails to start.I'm pasting below the files after editing out the token/ip/port/url.
/etc/default/rundeck_exporter
:/etc/systemd/system/rundeck_exporter.service
:/var/log/rundeckexporter.log
shows nothing./var/log/syslog
shows:Running the exact same command with hardcoded command parameters (the ones in the env variable
OPTIONS
from/etc/default/rundeck_exporter
) and the env variableRUNDECK_TOKEN
prefixed works just fine:RUNDECK_TOKEN=[token_here] /usr/local/src/rundeck_exporter/rundeck_exporter.py --host [ip] --port [port] --rundeck.url [rundeck_url] --rundeck.skip_ssl --rundeck.api.version 41 --rundeck.username exporter --rundeck.projects.executions --rundeck.projects.executions.cache --rundeck.cpu.stats --rundeck.memory.stats
Any help in determine what the issue is with the systemd configuration would be appreciated.
The text was updated successfully, but these errors were encountered: