just like I always do from time to time, I checked for updates yesterday, and since there was one for pimatic-shell-execute, I ran the update and clicked the Restart button after it finished. Unfortunately, Pimatic won’t start anymore now (there’s probably no connection to the plugin, but I can’t be sure).
When I run “sudo service pimatic start” or “sudo node_modules/pimatic/pimatic.js start”, only the current date/time is written to /home/pi/pimatic-app/pimatic-daemon.log, before the process seems to die almost instantaneously. Since there are no further log infos, I’m not sure where to start analyzing.
What I did so far: Restarting, sudo apt-get update/upgrade, power cycling the Pi, remove pimatic-shell-execute from config, remove Pimatic database file - no changes. Help please
pi@raspberrypi:~/pimatic-app $ sudo tail -f -n 200 /home/pi/pimatic-app/pimatic-daemon.log [...] 22:24:53.280 [pimatic] info: Installing: "email@example.com" from npm-registry. 22:25:42.405 [pimatic, ppm] info: WARN unmet dependency /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/hapi/node_modules/subtext/node_modules/pez requires boom@'3.x.x' but will load 22:25:42.422 [pimatic, ppm] info: WARN unmet dependency /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/hapi/node_modules/boom, 22:25:42.425 [pimatic, ppm] info: WARN unmet dependency which is version 4.0.0 22:25:43.023 [pimatic, ppm] info: firstname.lastname@example.org node_modules/pimatic-shell-execute 22:25:43.028 [pimatic, ppm] info: └── email@example.com 22:36:02.983 [pimatic] info: Restarting... 22:36:04.577 [pimatic] info: Flushing database to disk, please wait... 22:36:06.218 [pimatic] info: Flushing database to disk, please wait... Done. 22:36:06.223 [pimatic] info: exiting... 22:42:10.105 2017-04-20 Thursday 22:48:32.904 2017-04-20 Thursday 22:55:06.350 2017-04-20 Thursday 23:00:05.925 2017-04-20 Thursday 06:32:12.868 2017-04-21 Friday pi@raspberrypi:~/pimatic-app sudo node_modules/pimatic/pimatic.js status Pidfile exists, but process is dead.