Shutdown, Reboot, Pimatic restart command buttons produce: Error: spawn service pimatic restart ENOENT

---

hej,

i try to follow the HOW To “Shutdown, Reboot, Pimatic restart command buttons” so far so good, but when i press the button i get an Error.

Log messages:

error [pimatic-shell-execute]: [ShellButtons#pimatic-reboot] Error: spawn service pimatic restart ENOENT

@agentjk said in Shutdown, Reboot, Pimatic restart command buttons produce: Error: spawn service pimatic restart ENOENT:

service pimatic restart ENOENT

Did you install pimatic as a service as described in https://pimatic.teamemo.com/Guide/Running and https://pimatic.teamemo.com/Guide/Autostarting? Please try if using the service wrapper works for you as expected:

• Logon you raspberry Pi and open a command shell (remote ssh if you activated it or use the local console)
• Execute the following command sudo service pimatic restart

hello,

i install as described

when i type:

sudo npm link

i get this message:

"…npm ERR! path /home/pi/pimatic-app/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/pimatic-app/package.json’
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-08-08T18_28_15_024Z-debug.log
pi@raspberrypi:~/pimatic-app/node_modules $
…"

“…sudo service pimatic start…” does not work.

Autostart works perfekt, just from the beginning.

Hi, I changed it to pimatic.js restart / pimatic.js stop.
That worked for me.

i try pimatic.js restart / pimatic.js stop., but this didn´t work

@agentjk what abotu sudo pimatic restart and sudo pimatic stop?

@agentjk ENOENT indicates “No such file or directory” thrown by the OS. IT might be the sudo program is not found due to incorrect pathspec. Also make sure the account the Pimatic daemon runs under is a member of the sudo group and has a valid pathspec in its environment.

Try: /usr/bin/sudo service pimatic restart and see if this helps

Alternatively write a small shell script ( e.g. ~/restart_pimatic with mode 755) which helps check the environment of the process:

#!/bin/sh
/usr/bin/env > ~/environment.log 2>&1
/usr/bin/sudo service pimatic restart

Then pass the script instead of the sudo service..... command, and check the ~/environment.log file for the PATH variable. See if the path /usr/bin is listed.