Pimatic not running as 'service'

---

Hello specialists
I’m currently setting up my Pimatic from scratch on a Raspi 4B with buster (node v10.20.1, npm 6.14.4)

That far the whole installation went well on basis on the installation Wiki
… incl. also re-installation of all modules, after copying of my already existing ‘config.json’ into the ‘pimatic-app’ directory and then starting Pimatic. Also the WEB.Gui works fine.

But: I’m not able to get Pimatic running as a service, resp. as autstart after a reboot.
Starting/Stopping it manually by ‘sudo pimatic.js start/stop’ works fine, so I guess the installation itself is fine.

For making it available as service (incl. autostart), I also used the commands from the Wiki: https://pimatic.teamemo.com/Guide/Autostarting

Some detailed output for maybe investigations:
(I skipped the return on ‘systemctl status pimatic.service’ as it shows the same result as ‘sudo service pimatic status’)

pi@raspberrypi:/ $ sudo wget https://raw.githubusercontent.com/pimatic/pimatic/master/install/pimatic.service
--2020-05-08 08:21:52--  https://raw.githubusercontent.com/pimatic/pimatic/master/install/pimatic.service
Auflösen des Hostnamens raw.githubusercontent.com (raw.githubusercontent.com)… 151.101.112.133
Verbindungsaufbau zu raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK
Länge: 427 [text/plain]
Wird in »pimatic.service« gespeichert.

pimatic.service          100%[==================================>]     427  --.-KB/s    in 0s      

2020-05-08 08:21:53 (5,97 MB/s) - »pimatic.service« gespeichert [427/427]

pi@raspberrypi:/ $ sudo cp pimatic.service /lib/systemd/system/
pi@raspberrypi:/ $ sudo chown root:root /lib/systemd/system/pimatic.service
pi@raspberrypi:/ $ sudo systemctl daemon-reload
pi@raspberrypi:/ $ sudo systemctl enable pimatic
Created symlink /etc/systemd/system/multi-user.target.wants/pimatic.service → /lib/systemd/system/pimatic.service.
pi@raspberrypi:/ $ sudo systemctl restart pimatic
Job for pimatic.service failed because the control process exited with error code.
See "systemctl status pimatic.service" and "journalctl -xe" for details.

pi@raspberrypi:~ $ sudo reboot

pi@raspberrypi:~ $ sudo service pimatic status
● pimatic.service - Pimatic home automation framework
   Loaded: loaded (/lib/systemd/system/pimatic.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2020-05-08 08:27:46 CEST; 8s ago
  Process: 1119 ExecStart=/usr/local/bin/pimatic.js start (code=exited, status=203/EXEC)
pi@raspberrypi:~ $ sudo service pimatic start
Job for pimatic.service failed because the control process exited with error code.
See "systemctl status pimatic.service" and "journalctl -xe" for details.

pi@raspberrypi:~ $ journalctl -xe
-- Subject: Process /usr/local/bin/pimatic.js could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The process /usr/local/bin/pimatic.js could not be executed and failed.
-- 
-- The error number returned by this process is ERRNO.
Mai 08 08:34:57 raspberrypi systemd[1]: pimatic.service: Control process exited, code=exited, status
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- An ExecStart= process belonging to unit pimatic.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 203.
Mai 08 08:34:57 raspberrypi systemd[1]: pimatic.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit pimatic.service has entered the 'failed' state with result 'exit-code'.
Mai 08 08:34:57 raspberrypi systemd[1]: Failed to start Pimatic home automation framework.
-- Subject: A start job for unit pimatic.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit pimatic.service has finished with a failure.
-- 
-- The job identifier is 3668 and the job result is failed.
lines 4541-4569/4569 (END)

Would be very happy about any helpful hint, as that seems to go too deep into Raspbian for me, with my poor Linux knowledge

Pedder

Hi, did you install pimatic globally?
In the pimatic directory the following commands

cd ./node_modules/pimatic
npm install
sudo npm link

Hi @bertreb,
yes sure, I did also these steps.
It is possible to start Pimatic not only out of its own directory, what should, to my understanding, proof that, or!?

Did/can you check if /usr/local/bin/pimatic.js exists?

Yes I can, but I will have access to the PI earliest again in ~2 hours, sorry.
I will then directly check an post here again.

Ok, and when /usr/local/bin/pimatic.js does not exist, try to install pimatic globally again.

Ok, that seems to be the right direction, as /usr/local/bin/pimatic.js does not exist.
And it stays ‘not existing’ after making Pimatic again globally.

Here some details, whereas I remember, that in my last installation on Stretch on a P3B, I got a similiar bunch of vulnerability errors and also didn’t care about:

pi@raspberrypi:~ $ cd /home/pi/pimatic-app/node_modules/pimatic
pi@raspberrypi:~/pimatic-app/node_modules/pimatic $ npm install
audited 2944 packages in 13.499s

21 packages are looking for funding
  run `npm fund` for details

found 93 vulnerabilities (33 low, 38 moderate, 21 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details
pi@raspberrypi:~/pimatic-app/node_modules/pimatic $ sudo npm link
audited 2944 packages in 13.017s

21 packages are looking for funding
  run `npm fund` for details

found 93 vulnerabilities (33 low, 38 moderate, 21 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details
/usr/bin/pimatic.js -> /usr/lib/node_modules/pimatic/pimatic.js
/usr/lib/node_modules/pimatic -> /home/pi/pimatic-app/node_modules/pimatic

This old Stretch installation is now running roughly a year without any issues…

Shall I try ‘npm audit fix’, as said in the answer of the commands?

Hi, i think you found the problem area.
You can try the npm recommendation.
What happens if you use the command “sudo pimatic.js status”

@bertreb said in Pimatic not running as 'service':

sudo pimatic.js status

I did the fix, which fixed 45 of th 93 vulnaribilities.
Having Pimatic started manually now ‘status’ says, …oh no!:

Pidfile exists, but process is dead.

So I’m not able to start it any longer now…

The pimatic.pid file only contains ‘1820’.
But the Logfile contains an error now:

12:31:09.126 2020-05-08 Friday
12:31:10.805 [pimatic] info: Starting pimatic version 0.9.54
12:31:10.808 [pimatic] info: Node.js version 10.20.1
12:31:10.809 [pimatic] info: OpenSSL version 1.1.1e
12:31:11.966 [pimatic, ppm] info: 2.15.12
Fatal TypeError: _this.knex(…).transacting(…).insert(…).return is not a function

Did you restart the system and tried the manual start?

Did a quick reboot, but result stays the same, before trying to restart manually; I checked the status of the service again:

pi@raspberrypi:~ $ service pimatic status
● pimatic.service - Pimatic home automation framework
   Loaded: loaded (/lib/systemd/system/pimatic.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2020-05-08 12:39:36 CEST; 2s ago
  Process: 1113 ExecStart=/usr/local/bin/pimatic.js start (code=exited, status=203/EXEC)
pi@raspberrypi:~ $ sudo pimatic.js start
Started.
pi@raspberrypi:~ $ sudo pimatic.js status
Pidfile exists, but process is dead.
pi@raspberrypi:~ $ ^C
pi@raspberrypi:~ $ 

In the logfile I find the same error-message again.
… and sorry, have again to interrupt here for ~30minutes …

and the command sudo node_modules/pimatic/pimatic.js in the directory pimatic-app?

If this doesn’t work anymore, my step would be deleting the sqlite folder, but you could also remove and reinstall pimatic (that’s clean and easy, if you don’t got any customizing)

OK I’m back

I checked in addition, that usr/local/bin is still empty, so no pimatic.js there.

But I found a kind of link in usr/bin:

It contains a kind of script which looks as following:

!/usr/bin/env node
process.umask(0);
var moduleAlias = require('module-alias');
moduleAlias.addAlias('i18n', __dirname + '/node_modules/i18n-pimatic')
require('./coffee-cache.js')
var path = require('path');
var init = require('./lib/daemon');
var semver = require('semver');

if(semver.lt(process.version, '4.0.0')) {
  console.log("Error: Your node.js version " + process.version + " is too old. "
    + "Please update node.js to version >=4.0.0 and run pimatic again. See you again.");
  process.exit(1);
}

run = function (command) {
  require('./startup').startup(command).done();
};

var command = process.argv[2];
if(!command || command === "run" || command === "install") {
  run(command);
} else {
  logFile = path.resolve(__dirname, '../../pimatic-daemon.log');
  pidFile = path.resolve(__dirname, '../../pimatic.pid');

  init.simple({
    pidfile: pidFile,
    logfile: logFile,
    command: process.argv[3],
    run: run
  });
}

May I copy/move(?) this to usr/local/bin ?

Is pimatic manually running again?

No it doesn’t, it looks like that:

pi@raspberrypi:~ $ sudo pimatic.js start
Started.
pi@raspberrypi:~ $ sudo pimatic.js status
Pidfile exists, but process is dead.

Just recognized that you posted some more. Trying to start within the directory also shows some errors but maybe with some more details as the logfile, please have a look:

pi@raspberrypi:~ $ cd /home/pi/pimatic-app
pi@raspberrypi:~/pimatic-app $ sudo node_modules/pimatic/pimatic.js
13:25:07.572 2020-05-08 Friday
13:25:09.265 [pimatic] Starting pimatic version 0.9.54
13:25:09.269 [pimatic] Node.js version 10.20.1
13:25:09.269 [pimatic] OpenSSL version 1.1.1e
13:25:10.467 [pimatic, ppm] 2.15.12
Fatal TypeError: _this.knex(...).transacting(...).insert(...).return is not a function
    at /home/pi/pimatic-app/node_modules/pimatic/lib/database.coffee:495:16
    at /home/pi/pimatic-app/node_modules/pimatic/lib/database.coffee:202:20
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:517:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:574:18)
    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:619:10)
    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:699:18)
    at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:12)
    at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:147:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)

With regard to a re-install: I did that already yesterday evening two times, really incl. wiping the SD card.
I will try your hint regarding the sqlite folder

Hi, just to isolate problems.
When you do a reinstall, you can start with the default plugin set (only cron and mobile-frontend). And then implement the autorun.
When you got the autorun working with that config, you can replace the config.json with your config.json.

Yes, well hint, I will do that!

… and something other popped up in my mind:

I did the node installation not according the Pimatic guide with:

wget https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-armv7l.tar.gz -P /tmp
cd /usr/local
sudo tar xzvf /tmp/node-v10.16.3-linux-armv7l.tar.gz --strip=1

… as there is below mentioned, that node can also be installed by/from another platform.

As some time ago I ran into trouble by doing it that way with a ioBroker installation, I did it as following:

curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
sudo apt install -y nodejs

… but I guess as my current installation, before that testing with autostarting, already worked, that shouldn’t be the issue, or maybe is it?

Probably not a problem because it already worked.
I don’t know the alternative node installation. The first 1 is the way is install node.
Also that should not be the issue.