Lỗi start-limit-hit trong linux

I am trying to run a Node.js API as a service, but am running into problems.

When running systemctl status servicename.service I get the following error:

servicename.service - [Service description]  
Loaded: leaded [/etc/systemd/system/servicename.service; enabled; vendor preset: enabled]  
Active: failed [Result: start-limit-hit] since [timestamp] ago  
Process: 1142 ExecStart=/usr/bin/node /home/pi/Documents/server.js [code=exited, status=0/SUCCESS]  
Main PID: 1142 [code=exited, status=0/SUCCESS]  
[timestamp] hostname systemd[1]: servicename.service: Service hold-off time over, scheduling restart.  
[timestamp] hostname systemd[1]: Stopped [Service description]
[timestamp] hostname systemd[1]: servicename.service: Start request repeated too quickly.  
[timestamp] hostname systemd[1]: Failed to start [Service description]
[timestamp] hostname systemd[1]: servicename.service: Unit entered failed state.  
[timestamp] hostname systemd[1]: servicename.service: Failed with result 'start-limit-hit'.

What is this error and how can I resolve this issue?

I would like to run the script with sudo since part of the script needs admin permissions.

I am trying to start gunicorn on bootup of my machine but when I check the status of my service after enabling and starting it I get an error starting start-limit-hit. I have tried using sudo systemctl restart ssh as suggested in How to resolve service start limit hit. This is my .service file:

[Unit]
Requires=myproject.socket
After = network.target

[Service]
Restart=always
User=ubuntu
WorkingDirectory=/home/ubuntu/myproject
ExecStart=/home/ubuntu/myproject/venv36/bin/gunicorn -w 1 -b 0.0.0.0:8080 wsgi:$
Type=simple


[Install]
WantedBy=multi-user.target

My .socket file:

[Socket]
ListenStream=/run/myproject/socket

[Install]
WantedBy=sockets.target

asked Apr 23, 2019 at 8:59

5

You have Restart=always and a Type of simple, so in case the program specified in ExecStart is a daemon that forks another process and exits, your app will be considered not-active -> it will restart until it hits the limit.

You should either pass a parameter for the program to remain in the foreground, or change the Type to forking. After that run systemctl reset-failed myproject and start it.

Jeff Schaller♦

64.3k33 gold badges104 silver badges235 bronze badges

answered Nov 14, 2019 at 10:04

FloriOnFloriOn

2951 silver badge13 bronze badges

1

ping 

ip add show

sudo ifup 

ping