I have created a service on Debian 8.6 and as I'm trying to start it using the service command, I receive an error.I have tried systemctl daemon-reload, but still getting the same result.$ sudo service cloud9 start$ sudo service cloud9 status cloud9.service - cloud9   Loaded: loaded (/etc/systemd/system/cloud9.service; enabled)   Active: failed (Result: start-limit) since Thu 2016-10-13 07:21:02 UTC; 2s ago  Process: 2610 ExecStart=/opt/bitnami/nodejs/bin/node /home/user/c9sdk/server.js -w /home/user -l 0.0.0.0 -a admin:admin (code=exited, status=216/GROUP) Main PID: 2610 (code=exited, status=216/GROUP)Oct 13 07:21:02 test-vm systemd[1]: cloud9.service: main process exited, code=exited, status=216/GROUPOct 13 07:21:02 test-vm systemd[1]: Unit cloud9.service entered failed state.Oct 13 07:21:02 test-vm systemd[1]: cloud9.service holdoff time over, scheduling restart.Oct 13 07:21:02 test-vm systemd[1]: Stopping cloud9...Oct 13 07:21:02 test-vm systemd[1]: Starting cloud9...Oct 13 07:21:02 test-vm systemd[1]: cloud9.service start request repeated too quickly, refusing to start.Oct 13 07:21:02 test-vm systemd[1]: Failed to start cloud9.Oct 13 07:21:02 test-vm systemd[1]: Unit cloud9.service entered failed state.The config is in /etc/systemd/system/cloud9.service:[Unit]Description=cloud9[Service]ExecStart=/opt/bitnami/nodejs/bin/node /home/user/c9sdk/server.js -w /home/user -l 0.0.0.0 -a admin:adminRestart=alwaysUser=nobodyGroup=nobodyEnvironment=PATH=/bin:/usr/bin:/usr/local/binEnvironment=NODE_ENV=productionWorkingDirectory=/home/user/c9sdk[Install]WantedBy=multi-user.target
Service start request repeated too quickly, refusing to start
debian;systemd;services
2610 ExecStart=/opt/bitnami/nodejs/bin/node /home/user/c9sdk/server.js -w /home/user -l 0.0.0.0 -a admin:admin (code=exited, status=216/GROUP)…Oct 13 07:21:02 test-vm systemd[1]: cloud9.service: main process exited, code=exited, status=216/GROUP… which describes the problem.  Your group nobody is not a valid group on your system.  Specify a valid group.Environment=PATH=/bin:/usr/bin:/usr/local/binThis is probably unnecessary.-w /home/user -l 0.0.0.0In a better world, the cloud9 service program here would receive its listening socket as an open file descriptor, and inherit its working directory (which, ironically, you have explicitly set elsewhere in the unit).Further readinghttps://unix.stackexchange.com/a/316168/5132