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

Systemd service fails #830

Closed
b00ga opened this issue Nov 8, 2023 · 1 comment
Closed

Systemd service fails #830

b00ga opened this issue Nov 8, 2023 · 1 comment
Assignees
Labels

Comments

@b00ga
Copy link
Contributor

b00ga commented Nov 8, 2023

Systemd service is failing to start (tried on Ubuntu 20.04 from DEB install and AlmaLinux 8 by copying unit file from repo). In debugging, I found the following in the Command Lines section of the systemd.service manpage:

Note that the first argument (i.e. the program to execute) may not be a variable.

But this is what is being used in the core-daemon.service file:

ExecStart=$DAEMON

I see that in after-install.sh, the /opt/core/service file referenced by the systemd unit is conditionally setting the path, otherwise I would have just submitted a PR to hard-code this to the venv-path.

Since the Github-published DEB file does install the venv (at least by default), it would nice to tweak this in such a way as the install systemd unit is startable after package install.

@bharnden bharnden self-assigned this Nov 8, 2023
@bharnden bharnden added the bug label Nov 8, 2023
@bharnden
Copy link
Contributor

bharnden commented Nov 8, 2023

adjustments on develop to replace the variable with the hard coded absolute path for either case, depending on install

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

No branches or pull requests

2 participants