Debian
服務無法在啟動時啟動
我正在 Debian 9 機器上自動啟動 Jenkins 服務。
我的服務很好。服務定義是:
[Unit] SourcePath=/etc/init.d/jenkins Description=LSB: Start Jenkins at boot time Before=runlevel2.target runlevel3.target runlevel4.target runlevel5.target shutdown.target After=remote-fs.target systemd-journald-dev-log.socket network-online.target Wants=network-online.target Conflicts=shutdown.target [Service] Type=forking Restart=no TimeoutStartSec=5min TimeoutStopSec=10s IgnoreSIGPIPE=no KillMode=process GuessMainPID=no RemainAfterExit=yes SysVStartPriority=2 ExecStart=/etc/init.d/jenkins start ExecStop=/etc/init.d/jenkins stop
但問題是當我重新啟動節點時,服務不會自動啟動。我必須手動執行
systemctl start jenkins
由於我自動部署此 VM,
systemctl enable jenkins
因此無法選擇手動操作。創建新的 jenkins vm 後,它應該已經能夠在重新啟動後啟動服務。
即使我做一本手冊
systemctl enable jenkins
,我也會得到:# systemctl enable jenkins Synchronizing state of jenkins.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable jenkins The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified.
我在這裡缺少什麼嗎?
[Install]
就像它說的那樣,您似乎確實錯過了該部分。從 Jenkins 網站,Installing Jenkins as a Unix daemon,嘗試添加:[Install] WantedBy=multi-user.target
請注意,他們的股票範例直接呼叫 java,而不是分叉一個 shell 腳本。
要使服務在引導時啟動,請執行:
systemctl enable jenkins
或者手動創建符號連結:
ln -s /etc/systemd/system/jenkins.service /etc/systemd/system/multi-user.target.wants/jenkins.service