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 with status=217/USER #322
Comments
OS: CentOS 7 The work around for me was to delete the Defining the user in a Env var and in the Config it's self seems like double work to me.
|
The idea was to allow the user to be changed by the environment file. Somethings not working though clearly. I need to look into it. |
I can confirm I observed the same behavior on Cent OS 7 making me scratch my head to find out what could cause this. Anyway commenting line User=... helps but LC starts under root even with Environment="LOG_COURIER_USER=log-courier". |
Sorry about the issue. I can confirm that I'm in process of updating the systemd units so they are config files and can be modified. |
The reason there was the |
Yes, if we edit the |
@shameerariff This isn’t the right repository for your query. I have no idea what traccar is. |
Sorry it was wrongly posted. |
I encounter the same problem. just update the |
OS: Ubuntu Xenial
Starting log-courier as a systemd service fails with
status=217/USER
This is due to the default username containing a dash and being set on the service file using an environment variable.
As a workaround the user can be changed to root or any other user without a dash on the /etc/defaults/log-courier file, or set directly on the .service file with
User=log-courier
The text was updated successfully, but these errors were encountered: