-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Open
Description
The systemd service provided by services.clipse fails to start for me
with the following error being logged to ~/.config/clipse/clipse.log:
logger.go:19: ERROR: exec: "nohup": executable file not found in $PATH
Plus the occasional:
logger.go:19: ERROR: failed to kill process: exec: "kill": executable file not found in $PATH
Systemd unit logs:
systemd[3161]: Starting Clipse listener...
clipse[10836]: goroutine 1 [running]:
clipse[10836]: runtime/debug.Stack()
clipse[10836]: runtime/debug/stack.go:26 +0x5e
clipse[10836]: runtime/debug.PrintStack()
clipse[10836]: runtime/debug/stack.go:18 +0x13
clipse[10836]: github.com/savedra1/clipse/utils.HandleError({0x6c6340, 0xc000014d60})
clipse[10836]: github.com/savedra1/clipse/utils/err.go:11 +0x2c
clipse[10836]: github.com/savedra1/clipse/shell.RunNohupListener({0x626aa4?, 0xc00007a0e8?})
clipse[10836]: github.com/savedra1/clipse/shell/cmd.go:81 +0x17e
clipse[10836]: main.handleListen({0x626aa4, 0x7})
clipse[10836]: github.com/savedra1/clipse/main.go:115 +0xe5
clipse[10836]: main.main()
clipse[10836]: github.com/savedra1/clipse/main.go:71 +0x3ce
systemd[3161]: clipse.service: Main process exited, code=exited, status=1/FAILURE
systemd[3161]: clipse.service: Failed with result 'exit-code'.
systemd[3161]: Failed to start Clipse listener.
I tried fixing this myself by adding coreutils' and util-linux'
bin directory to the services PATH via
systemd.user.services.clipse.Service.Environment and while this does
get rid of the errors, it just leads to clipse instantly exiting upon
service activation.
Unit logs with the above packages' binaries added to the units PATH:
systemd[3161]: Starting Clipse listener...
systemd[3161]: Finished Clipse listener.
Possibly related to #8034
Metadata
Metadata
Assignees
Labels
No labels