Tipi does not auto start since 2.05
My tipi.service looks like this
[Unit]
Description=tipi
Requires=docker.service multi-user.target
After=docker.service network-online.target dhcpd.service
[Service]
Restart=always
RemainAfterExit=yes
WorkingDirectory=/home/<user>/runtipi
ExecStart=/home/<user>/runtipi/scripts/runtipi-cli start
ExecStop=/home/<user>/runtipi/scripts/runtipi-cli stop
[Install]
WantedBy=multi-user.target
Yet tipi does not start after a reboot. However my apps do start which confuses me. I need to run this manually
sudo ./runtipi-cli start
running as Ubuntu 22.04.3
4 Replies
hmm
what does sudo journalctl -efu runtipi give you?
(replace runtipi with your service name)
I get this:
Oct 09 12:44:36 tipi systemd[1]: Started Docker Application Container Engine.
Oct 09 12:44:36 tipi systemd[1]: Started tipi.
Oct 09 12:44:36 tipi systemd[1503]: tipi.service: Failed to locate executable /home/roo/runtipi/scripts/runtipi-cli: No such file or directory
Oct 09 12:44:36 tipi systemd[1503]: tipi.service: Failed at step EXEC spawning /home/roo/runtipi/scripts/runtipi-cli: No such file or directory
Oct 09 12:44:36 tipi systemd[1]: Reached target Multi-User System.
Oct 09 12:44:36 tipi systemd[1]: Reached target Graphical Interface.
Oct 09 12:44:36 tipi systemd[1]: Starting Record Runlevel Change in UTMP...
Oct 09 12:44:36 tipi systemd[1]: tipi.service: Main process exited, code=exited, status=203/EXEC
Oct 09 12:44:36 tipi systemd[1]: tipi.service: Failed with result 'exit-code'.
Oct 09 12:44:36 tipi systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Oct 09 12:44:36 tipi systemd[1]: Finished Record Runlevel Change in UTMP.
Oct 09 12:44:36 tipi systemd[1]: Startup finished in 4.593s (kernel) + 43.746s (userspace) = 48.340s.
Oct 09 12:44:36 tipi systemd[1]: tipi.service: Scheduled restart job, restart counter is at 1.
and so on...
which answers my own question as th error log is correct the runtipi-cli is not at this location.
I corrected the file path to ExecStart=/home/<user>/runtipi/runtipi-cli startand good to go
thank you
Exactly
That was the problem
@Mxrcy we can close this
Unknown User•15mo ago
Message Not Public
Sign In & Join Server To View