-
Notifications
You must be signed in to change notification settings - Fork 134
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
new user service should be enabled before starting #3
Comments
From the result of |
I cannot reproduce this issue over here (Ubuntu 16.04, systemd 229). The new service starts fine using This is also how things are supposed to work (as far as I understand): Enabling/disabling a service is relevant for connecting/disconnecting the service from systemd targets. From the
These mechanisms are covered in the Automatically Starting the Service during Boot part of the tutorial. According to the error message you pasted, systemd doesn't find your service. If that is the case, then one of the previous steps in the tutorial should already have failed for you. In particular, what does the following command return for you?
|
It's been a long time and I'm not sure how it happened. Thanks anyway for the great tutorial. I used it in my job 👍 |
Good to hear that things are working for you, @mrezzamoradi, and I'm glad you found the tutorial helpful. |
In Manually Starting and Stopping the Service section, if you don't enable the service before starting, it will return
Failed to start python_demo_service.service: Unit python_demo_service.service not found.
when you try to start the service.my systemctl version is 237, and this happened to me as I was following your tutorial. So I enabled the service and it worked.
The text was updated successfully, but these errors were encountered: