Active: failed ( Result : start- limit -hit) since Fri 2020-05-22 12:55:35 UTC 1s ago Process: 4838 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=0/SUCCESS) Main PID: 4838 (code=exited, status=0/SUCCESS), Upon investigation, I discovered the service failed to start on my appliance: root@XenOrchestra-FTW:~# systemctl status xo- server .service. xo- server .service – XO Server. Loaded: loaded (/etc/systemd/system/xo- server .service enabled) Active: failed ( Result : start-limit) since Fri 2017-03-10 16:36:34 EST 1min 47s ago.
When you have start-limit-hit or Start request repeated too quickly it may be due to a Restart=on-failure directive in the service definition. Chances are, there is an initial reason for the error but it’s hidden behind the one you see. To find out: (obviously, replace carbon-relay-ng with your service), 10/31/2019 · Active: failed ( Result : service-start- limit -hit) since Wed 2019-10-30 19:25:47 UTC 10h ago Listen: /run/gunicorn.sock (Stream), Active: failed ( Result : service-start- limit -hit) In my mission to deploy a python project, I have gotten to gunicorn setup. Checking for gunicorn status file (I just ran this command earlier today and it returned the following): sudo systemctl status gunicorn.socket Failed to dump process list, ignoring: No such file or directory gunicorn.socket …
You can run systemctl reset- failed to get rid of the start-limit error. Regarding your .service file I would suggest to remove the whitespaces in After = network.target, although I’m not sure if that will help starting the service. – eblock Apr 23 ’19 at 9:30, 7/3/2017 · Nov 19 09:45:15 ts-build1 systemd[1]: docker.service: Failed with result ‘start- limit -hit’. Found removing the -H fd:// parameter allowed Docker to start … ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock –iptables=true –dns –dns 8.8.8.8 -.
Active: failed ( Result : start- limit -hit) since Fri 2020-05-22 12:55:35 UTC 1s ago Process: 4838 ExecStart=/usr/local/bin/node ./bin/xo-server (code=exited, status=0/SUCCESS) Main PID: 4838 (code=exited, status=0/SUCCESS), 5/15/2020 · Active: failed ( Result : start- limit -hit) since Wed 2020-05-13 20:11:24 IST 17min ago. Process: 24122 ExecStart=/etc/NX/nxserver –daemon (code=exited, status=216/GROUP) Main PID: 24122 (code=exited, status=216/GROUP) May 13 20:11:24 blr-ubuntu-42 systemd[1]: nxserver.service: Service hold-off time over, scheduling restart.
sshd.service – OpenSSH Daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service enabled) Active: failed ( Result : start-limit) since Wed 2013-09-11 08:45:13 BST 1min 21s ago Process: 701 ExecStart=/usr/bin/sshd -D (code=exited, status=1/FAILURE) Sep 11 08:45:13 alarmpi systemd[1]: sshd.service: main process exited, code=exited, status=1/FAILURE Sep 11 08:45:13 alarmpi systemd[1]: Unit sshd.service entered failed …
