Node.js 使用systemd在ubuntu 16.04启动时启动脚本

我有一个简单的脚本“start.sh”，我想让它在每次ubuntu 16.04重新启动时自动启动

我跟随这篇文章：

制作一个简单的脚本：

我把它放在这里了

/lib/systemd/system/test_run_at_boot.service

我把它链接起来了

/etc/systemd/system/multi-user.target.wants/test_run_at_boot.service -> /lib/systemd/system/test_run_at_boot.service

每次我重新启动我的机器，它都不会启动

我还尝试附加实际的命令来测试\u boot.service上的\u run\u，但仍然不起作用

[Unit]
Description=test_run_at_boot

[Service]
ExecStart=forever start -a -l forever.log -o out.log -e err.log /home/ubuntu/misc/service/test_run_at_boot/test_run_at_boot.js

[Install]
WantedBy=multi-user.target

更新

在syslog中，我得到了这个<代码>/usr/bin/env:'node'：没有这样的文件或目录，这会导致脚本在启动时失败

Aug  5 06:45:23 xyz start.sh[1557]: /usr/bin/env: ‘node’: No such file or directory
Aug  5 06:45:23 xyz systemd[1]: Starting LSB: Record successful boot for GRUB...
Aug  5 06:45:23 xyz acpid: starting up with netlink and the input layer
Aug  5 06:45:23 xyz acpid: 1 rule loaded
Aug  5 06:45:23 xyz acpid: waiting for events: event logging is off
Aug  5 06:45:23 xyz systemd[1]: Started D-Bus System Message Bus.
Aug  5 06:45:23 xyz dbus[1590]: [system] AppArmor D-Bus mediation is enabled
Aug  5 06:45:23 xyz systemd[1]: Started Cgroup management daemon.
Aug  5 06:45:23 xyz systemd[1]: Starting Thermal Daemon Service...
Aug  5 06:45:23 xyz systemd[1]: Started FUSE filesystem for LXC.
Aug  5 06:45:23 xyz systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
Aug  5 06:45:23 xyz lxcfs[1624]: hierarchies: 0: memory
Aug  5 06:45:23 xyz lxcfs[1624]:  1: blkio
Aug  5 06:45:23 xyz lxcfs[1624]:  2: hugetlb
Aug  5 06:45:23 xyz lxcfs[1624]:  3: cpuset
Aug  5 06:45:23 xyz lxcfs[1624]:  4: freezer
Aug  5 06:45:23 xyz lxcfs[1624]:  5: net_cls,net_prio
Aug  5 06:45:23 xyz lxcfs[1624]:  6: pids
Aug  5 06:45:23 xyz lxcfs[1624]:  7: devices
Aug  5 06:45:23 xyz lxcfs[1624]:  8: cpu,cpuacct
Aug  5 06:45:23 xyz lxcfs[1624]:  9: perf_event
Aug  5 06:45:23 xyz lxcfs[1624]:  10: name=systemd
Aug  5 06:45:23 xyz systemd[1]: Starting System Logging Service...
Aug  5 06:45:23 xyz systemd[1]: Started Snappy daemon.
Aug  5 06:45:23 xyz systemd[1]: Started Regular background program processing daemon.
Aug  5 06:45:23 xyz cron[1648]: (CRON) INFO (pidfile fd = 3)
Aug  5 06:45:23 xyz systemd[1]: Starting Accounts Service...
Aug  5 06:45:23 xyz cron[1648]: (CRON) INFO (Running @reboot jobs)
Aug  5 06:45:23 xyz systemd[1]: Starting Login Service...
Aug  5 06:45:23 xyz systemd[1]: Starting LXD - container startup/shutdown...
Aug  5 06:45:23 xyz systemd[1]: Started System Logging Service.
Aug  5 06:45:23 xyz systemd[1]: test_run_at_boot.service: Main process exited, code=exited, status=127/n/a
Aug  5 06:45:23 xyz systemd[1]: test_run_at_boot.service: Unit entered failed state.
Aug  5 06:45:23 xyz systemd[1]: test_run_at_boot.service: Failed with result 'exit-code'.

更新1

我关注这个帖子

我做了一些改变

它可以在重新启动后启动服务，但在1-2分钟后，服务就会消失。见下文

ubuntu@xyz:~$ ps aux | grep test
root      2155  0.3  3.8 942196 38780 ?        Ssl  13:04   0:00 /home/ubuntu/.nvm/versions/node/v6.3.1/bin/node /home/ubuntu/.nvm/versions/node/v6.3.1/lib/node_modules/forever/bin/monitor /home/ubuntu/misc/service/test_run_at_boot/test_run_at_boot.js
ubuntu    3223  0.0  0.1  12944  1092 pts/0    S+   13:05   0:00 grep --color=auto test
ubuntu@xyz:~$ cd misc/
ubuntu@xyz:~/misc/service/test_run_at_boot$ ls
err.log  node_modules  out.log  package.json  start.sh  stop.sh  test_run_at_boot.js  test_run_at_boot.service
ubuntu@xyz:~/misc/service/test_run_at_boot$ ps aux | grep test
ubuntu    3240  0.0  0.0  12944  1012 pts/0    S+   13:05   0:00 grep --color=auto test
ubuntu@xyz:~/misc/service/test_run_at_boot$ 

更新2

在系统日志中

Aug  6 01:24:22 xyz start.sh[1663]: warn:    --minUptime not set. Defaulting to: 1000ms
Aug  6 01:24:22 xyz start.sh[1663]: warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
Aug  6 01:24:22 xyz start.sh[1663]: info:    Forever processing file: /home/ubuntu/misc/service/test_run_at_boot/test_run_at_boot.js
Aug  6 01:24:22 xyz systemd[1]: test_run_at_boot.service: PID 3347 read from file /home/ubuntu/misc/service/test_run_at_boot/test_run_at_boot.pid does not exist or is a zombie.
....
....
Aug  6 01:24:55 xyz systemd[1]: Started Execute cloud user/final scripts.
Aug  6 01:24:55 xyz systemd[1]: Reached target Cloud-init target.
Aug  6 01:25:00 xyz ntpdate[2709]: adjust time server 91.189.91.157 offset 0.104466 sec
Aug  6 01:25:51 xyz systemd[1]: test_run_at_boot.service: Start operation timed out. Terminating.
Aug  6 01:25:51 xyz systemd[1]: Failed to start test_run_at_boot.
Aug  6 01:25:51 xyz systemd[1]: test_run_at_boot.service: Unit entered failed state.
Aug  6 01:25:51 xyz systemd[1]: test_run_at_boot.service: Failed with result 'timeout'.

---

在systemd下使用forever有点像使用forever来永远运行

如果没有“永远”，systemd配置将变得更简单

[Unit]
Description=test_run_at_boot

[Service]
ExecStart=/usr/bin/nodejs /home/ubuntu/misc/service/test_run_at_boot/test_run_at_boot.js
Type=oneshot
#Restart=on-failure

[Install]
WantedBy=multi-user.target

您正在使用的测试脚本是a，因为该脚本将退出，否则systemd将报告服务失败。一旦要管理长期运行的服务，您可以删除

Type=oneshot

，并使用

Restart=on failure

保持服务正常运行，就像永远一样

来自流程的

stderr

和

stdout

被发送到systemd日志。在Ubuntu上，这将转到syslog

---

如果您真的需要forever的功能，那么systemd需要更多的设置。这个您将需要设置一个

--pidFile

并具有一个匹配的系统D。

您是否已使用

systemctl enable

启用该服务？通常情况下，ubuntua上的

nodejs

，当您拥有系统时，您不需要永远使用它，这更是一个问题