search

psi-4ward / AskSinAnalyzerXS

Analyzer for radio telegrams in a HomeMatic environment
Other
48 stars 7 forks source link

Nach Update auf node.js 20.13.1 startet der Service nicht mehr #102

Open Johannes200658 opened 3 months ago

Johannes200658 commented 3 months ago

Ich nutze den IoBroker und den Analyzer auf dem gleichen Linux Debian Rechner. Heute morgen habe ich für den IoBroker die Version node.js 20.13.1 installiert und seitdem startet der Dienst nicht mehr:

`smarthome@vm-iobroker:~$ sudo systemctl status analyzer × analyzer.service - Analyzer for radio telegrams in a HomeMatic environment Loaded: loaded (/etc/systemd/system/analyzer.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Sat 2024-05-25 10:07:55 CEST; 19min ago Duration: 121ms Docs: https://github.com/psi-4ward/AskSinAnalyzerXS Process: 5658 ExecStart=/usr/bin/asksin-analyzer-xs -d /opt/analyzer (code=exited, status=1/FAILURE) Main PID: 5658 (code=exited, status=1/FAILURE) CPU: 147ms

Mai 25 10:07:55 vm-iobroker systemd[1]: analyzer.service: Scheduled restart job, restart counter is at 5. Mai 25 10:07:55 vm-iobroker systemd[1]: Stopped analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. Mai 25 10:07:55 vm-iobroker systemd[1]: analyzer.service: Start request repeated too quickly. Mai 25 10:07:55 vm-iobroker systemd[1]: analyzer.service: Failed with result 'exit-code'. Mai 25 10:07:55 vm-iobroker systemd[1]: Failed to start analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. ` Kann man das Problem fixen, oder muss ich mir etwas anderes einfallen lassen?

Gruß, Johannes

psi-4ward commented 3 months ago

journalctl -u analyzer

Johannes200658 commented 3 months ago

Hier nur die letzten Einträge:

Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46918]: Node.js v20.13.1 Mai 25 15:11:10 vm-iobroker systemd[1]: analyzer.service: Main process exited, code=exited, status=1/FAILURE Mai 25 15:11:10 vm-iobroker systemd[1]: analyzer.service: Failed with result 'exit-code'. Mai 25 15:11:10 vm-iobroker systemd[1]: analyzer.service: Scheduled restart job, restart counter is at 4. Mai 25 15:11:10 vm-iobroker systemd[1]: Stopped analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. Mai 25 15:11:10 vm-iobroker systemd[1]: Started analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: /usr/lib/node_modules/asksin-analyzer-xs/node_modules/bindings/bindings.js:121 Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: throw e; Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: ^ Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: Error: The module '/usr/lib/node_modules/asksin-analyzer-xs/node_modules/@serialport/bindings/build/Release/bindings> Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: was compiled against a different Node.js version using Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: NODE_MODULE_VERSION 108. This version of Node.js requires Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: NODE_MODULE_VERSION 115. Please try re-compiling or re-installing Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: the module (for instance, usingnpm rebuildornpm install`). Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Module._extensions..node (node:internal/modules/cjs/loader:1454:18) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Module.load (node:internal/modules/cjs/loader:1208:32) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Module._load (node:internal/modules/cjs/loader:1024:12) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Module.require (node:internal/modules/cjs/loader:1233:19) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at require (node:internal/modules/helpers:179:18) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at bindings (/usr/lib/node_modules/asksin-analyzer-xs/node_modules/bindings/bindings.js:112:48) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Object. (/usr/lib/node_modules/asksin-analyzer-xs/node_modules/@serialport/bindings/lib/linux.js:2> Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Module._compile (node:internal/modules/cjs/loader:1358:14) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: at Module.load (node:internal/modules/cjs/loader:1208:32) { Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: code: 'ERR_DLOPEN_FAILED' Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: } Mai 25 15:11:10 vm-iobroker asksin-analyzer-xs[46926]: Node.js v20.13.1 Mai 25 15:11:10 vm-iobroker systemd[1]: analyzer.service: Main process exited, code=exited, status=1/FAILURE Mai 25 15:11:10 vm-iobroker systemd[1]: analyzer.service: Failed with result 'exit-code'. Mai 25 15:11:11 vm-iobroker systemd[1]: analyzer.service: Scheduled restart job, restart counter is at 5. Mai 25 15:11:11 vm-iobroker systemd[1]: Stopped analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. Mai 25 15:11:11 vm-iobroker systemd[1]: analyzer.service: Start request repeated too quickly. Mai 25 15:11:11 vm-iobroker systemd[1]: analyzer.service: Failed with result 'exit-code'. Mai 25 15:11:11 vm-iobroker systemd[1]: Failed to start analyzer.service - Analyzer for radio telegrams in a HomeMatic environment.

`

psi-4ward commented 3 months ago

da brauchts n npm rebuild. wie hast du den Analyzer installiert?

Johannes200658 commented 3 months ago

Laut Anleitung mit

sudo npm install -g --unsafe asksin-analyzer-xs

psi-4ward commented 3 months ago

sudo npm rebuild -g asksin-analyzer-xs

Johannes200658 commented 3 months ago

Da kommt: smarthome@vm-iobroker:~$ sudo npm rebuild -g asksin-analyzer-xs rebuilt dependencies successfully npm notice npm notice New minor version of npm available! 10.5.2 -> 10.8.0 npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.0 npm notice Run npm install -g npm@10.8.0 to update! npm notice Aber ich kann doch npm nicht neu installieren? Oder was macht der Befehl?

Johannes200658 commented 3 months ago

Nach dem rebuild kommt immer noch:

Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870795]: Node.js v20.13.1 Mai 27 11:06:02 vm-iobroker systemd[1]: analyzer.service: Main process exited, code=exited, status=1/FAILURE Mai 27 11:06:02 vm-iobroker systemd[1]: analyzer.service: Failed with result 'exit-code'. Mai 27 11:06:02 vm-iobroker systemd[1]: analyzer.service: Scheduled restart job, restart counter is at 4. Mai 27 11:06:02 vm-iobroker systemd[1]: Stopped analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. Mai 27 11:06:02 vm-iobroker systemd[1]: Started analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: /usr/lib/node_modules/asksin-analyzer-xs/node_modules/bindings/bindings.js:121 Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: throw e; Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: ^ Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: Error: The module '/usr/lib/node_modules/asksin-analyzer-xs/node_modules/@serialport/bindings/build/Release/bindin> Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: was compiled against a different Node.js version using Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: NODE_MODULE_VERSION 108. This version of Node.js requires Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: NODE_MODULE_VERSION 115. Please try re-compiling or re-installing Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: the module (for instance, usingnpm rebuildornpm install). Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Module._extensions..node (node:internal/modules/cjs/loader:1454:18) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Module.load (node:internal/modules/cjs/loader:1208:32) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Module._load (node:internal/modules/cjs/loader:1024:12) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Module.require (node:internal/modules/cjs/loader:1233:19) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at require (node:internal/modules/helpers:179:18) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at bindings (/usr/lib/node_modules/asksin-analyzer-xs/node_modules/bindings/bindings.js:112:48) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Object.<anonymous> (/usr/lib/node_modules/asksin-analyzer-xs/node_modules/@serialport/bindings/lib/linux.js> Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Module._compile (node:internal/modules/cjs/loader:1358:14) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: at Module.load (node:internal/modules/cjs/loader:1208:32) { Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: code: 'ERR_DLOPEN_FAILED' Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: } Mai 27 11:06:02 vm-iobroker asksin-analyzer-xs[1870802]: Node.js v20.13.1 Mai 27 11:06:02 vm-iobroker systemd[1]: analyzer.service: Main process exited, code=exited, status=1/FAILURE Mai 27 11:06:02 vm-iobroker systemd[1]: analyzer.service: Failed with result 'exit-code'. Mai 27 11:06:03 vm-iobroker systemd[1]: analyzer.service: Scheduled restart job, restart counter is at 5. Mai 27 11:06:03 vm-iobroker systemd[1]: Stopped analyzer.service - Analyzer for radio telegrams in a HomeMatic environment. Mai 27 11:06:03 vm-iobroker systemd[1]: analyzer.service: Start request repeated too quickly. Mai 27 11:06:03 vm-iobroker systemd[1]: analyzer.service: Failed with result 'exit-code'. Mai 27 11:06:03 vm-iobroker systemd[1]: Failed to start analyzer.service - Analyzer for radio telegrams in a HomeMatic environment.

psi-4ward commented 3 months ago

Das sollte eigentlich jetz gehen.

Versuch mal neu-installiern
npm un -g asksin-analyzer-xs zum deinstalliern

Johannes200658 commented 3 months ago

Jau, läuft wieder 👍

Coole Sache. Zum Verständnis, hast du die Version aktualisiert, oder ist das jetzt nur lokal auf meinem System passiert?

psi-4ward commented 3 months ago

Der Analyzer nutzt node-gyp bindings um auf die serielle Schnittstelle zuzugreifen. Diese Bindings sind nicht in Javascript und müssen deshalb kompiliert werden und entsprechend zur Node-Version passen. MaW, das könnte dir wieder passieren (und ist nichts ungewöhnliches).

Johannes200658 commented 3 months ago

Okay, dann weiß ich Bescheid. Vielen Dank für deine schnelle Hilfe 👍