Describe the bug
By default the systemd unit doesn't define fields User and Group.
If I add it, the process start through systemd is stuck and systemd returns timeout.
$ sudo systemctl start go-carbon.service
Job for go-carbon.service failed because a timeout was exceeded.
See "systemctl status go-carbon.service" and "journalctl -xe" for details.
Go-carbon Configuration:
Almost identical to default really.
Metric retention and aggregation schemas
I think it's irrelevant. Nothing special.
Additional context
Having this process as root is a bad practice especially for anyone who considers it 3rd party. Mind you the carbonapi project does define non-root user+group.
Hi @interfan7
We're running go-carbon under carbon user in production without any issues. So, it's some local issue for your system - maybe pid file can't be created? or selinux doing that.
Describe the bug By default the systemd unit doesn't define fields
User
andGroup
. If I add it, the process start through systemd is stuck and systemd returns timeout.The process however is alive:
Logs This is the log suffix:
Go-carbon Configuration: Almost identical to default really.
Metric retention and aggregation schemas I think it's irrelevant. Nothing special.
Additional context Having this process as root is a bad practice especially for anyone who considers it 3rd party. Mind you the
carbonapi
project does define non-root user+group.