if you’re on a fresh stretch/buster follow stupid 1:1 the guide https://pimatic.teamemo.com/Guide/Getting-Started and it should work.
only if you use hap read my post above. good luck
-
Pimatic & Node 8.0
-
@pedder
One last try…
sudo su
npm install cassert
cd pimatic-app
cd ./node_modules/pimatic
sudo npm link -
… to late, but I’m just starting to cry
I set up a completely fresh stretch with node 10.15.3 and running currently in the same problems with that damn ERR! code 128 after
sudo npm linkHow can that be? I did exactly the same while the installation last weekend.
I however continued with the ‘Autostart’ setup, rebooted, but pimatic crashed while starting:
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 Jun 29 17:45:25 raspberrypi pimatic[1068]: /etc/init.d/pimatic: 25: /etc/init.d/pimatic: pimatic.js: Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Control process exited, code=exited status= Jun 29 17:45:25 raspberrypi systemd[1]: Failed to start LSB: pimatic service. -- Subject: Unit pimatic.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has failed. -- -- The result is failed. Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Unit entered failed state. Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Failed with result 'exit-code'. Jun 29 17:45:25 raspberrypi sudo[1040]: pam_unix(sudo:session): session closed for user root Jun 29 17:46:17 raspberrypi sudo[1073]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/u Jun 29 17:46:17 raspberrypi sudo[1073]: pam_unix(sudo:session): session opened for user root by (uid Jun 29 17:46:17 raspberrypi systemd[1]: Starting LSB: pimatic service... -- Subject: Unit pimatic.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has begun starting up. Jun 29 17:46:17 raspberrypi pimatic[1082]: /etc/init.d/pimatic: 25: /etc/init.d/pimatic: pimatic.js: Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Control process exited, code=exited status= Jun 29 17:46:17 raspberrypi systemd[1]: Failed to start LSB: pimatic service. -- Subject: Unit pimatic.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has failed. -- -- The result is failed. Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Unit entered failed state. Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Failed with result 'exit-code'. Jun 29 17:46:17 raspberrypi sudo[1073]: pam_unix(sudo:session): session closed for user root lines 1717-1750/1750 (END) Jun 29 17:45:25 raspberrypi pimatic[1068]: /etc/init.d/pimatic: 25: /etc/init.d/pimatic: pimatic.js: Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Control process exited, code=exited status= Jun 29 17:45:25 raspberrypi systemd[1]: Failed to start LSB: pimatic service. -- Subject: Unit pimatic.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has failed. -- -- The result is failed. Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Unit entered failed state. Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Failed with result 'exit-code'. Jun 29 17:45:25 raspberrypi sudo[1040]: pam_unix(sudo:session): session closed for user root Jun 29 17:46:17 raspberrypi sudo[1073]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/u Jun 29 17:46:17 raspberrypi sudo[1073]: pam_unix(sudo:session): session opened for user root by (uid Jun 29 17:46:17 raspberrypi systemd[1]: Starting LSB: pimatic service... -- Subject: Unit pimatic.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has begun starting up. Jun 29 17:46:17 raspberrypi pimatic[1082]: /etc/init.d/pimatic: 25: /etc/init.d/pimatic: pimatic.js: Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Control process exited, code=exited status= Jun 29 17:46:17 raspberrypi systemd[1]: Failed to start LSB: pimatic service. -- Subject: Unit pimatic.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has failed. -- -- The result is failed. Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Unit entered failed state. Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Failed with result 'exit-code'. Jun 29 17:46:17 raspberrypi sudo[1073]: pam_unix(sudo:session): session closed for user root ~ ~ ~ ~ ~ ~ lines 1717-1750/1750 (END) Jun 29 17:45:25 raspberrypi pimatic[1068]: /etc/init.d/pimatic: 25: /etc/init.d/pimatic: pimatic.js: not f Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Control process exited, code=exited status=127 Jun 29 17:45:25 raspberrypi systemd[1]: Failed to start LSB: pimatic service. -- Subject: Unit pimatic.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has failed. -- -- The result is failed. Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Unit entered failed state. Jun 29 17:45:25 raspberrypi systemd[1]: pimatic.service: Failed with result 'exit-code'. Jun 29 17:45:25 raspberrypi sudo[1040]: pam_unix(sudo:session): session closed for user root Jun 29 17:46:17 raspberrypi sudo[1073]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/sbi Jun 29 17:46:17 raspberrypi sudo[1073]: pam_unix(sudo:session): session opened for user root by (uid=0) Jun 29 17:46:17 raspberrypi systemd[1]: Starting LSB: pimatic service... -- Subject: Unit pimatic.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has begun starting up. Jun 29 17:46:17 raspberrypi pimatic[1082]: /etc/init.d/pimatic: 25: /etc/init.d/pimatic: pimatic.js: not f Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Control process exited, code=exited status=127 Jun 29 17:46:17 raspberrypi systemd[1]: Failed to start LSB: pimatic service. -- Subject: Unit pimatic.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit pimatic.service has failed. -- -- The result is failed. Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Unit entered failed state. Jun 29 17:46:17 raspberrypi systemd[1]: pimatic.service: Failed with result 'exit-code'. Jun 29 17:46:17 raspberrypi sudo[1073]: pam_unix(sudo:session): session closed for user root ~ ~ ~I now just started to unistall pimatic to do the node update to 10.16.0
But doingsudo npm unlinkagain produces that damn code 128I’m short before throwing everything in the waste …
-
Just try
sudo su
npm install cassert
beforesudo npm link -
@bill-blacksoll said in Pimatic & Node 8.0:
One last try…
Ok, did the node update and started pimatic with
sudo node_modules/pimatic/pimatic.js
which worked fine.Then gave your last hint @Bill-BlackSoll a try, but that happend:
root@raspberrypi:/home/pi# npm install cassert npm ERR! Cannot read property 'resolve' of undefined npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-06-29T16_25_36_861Z-debug.logfurther ideas?
-
if it helps, I now fetched the log file from
root@raspberrypi:/home/pi# npm install cassertinfo it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'install', 1 verbose cli 'cassert' ] 2 info using npm@6.9.0 3 info using node@v10.16.0 4 verbose npm-session 99c64eadd2b0c1fe 5 silly install loadCurrentTree 6 silly install readLocalPackageData 7 silly fetchPackageMetaData error for cassert@latest Cannot read property 'resolve' of undefined 8 timing stage:rollbackFailedOptional Completed in 9ms 9 timing stage:runTopLevelLifecycles Completed in 197ms 10 verbose stack TypeError: Cannot read property 'resolve' of undefined 10 verbose stack at regFetch (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/index.j$ 10 verbose stack at fetchPackument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/$ 10 verbose stack at packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/regis$ 10 verbose stack at getManifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/reg$ 10 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/regist$ 10 verbose stack at Object.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers$ 10 verbose stack at Object.Fetcher#manifest [as manifest] (/usr/local/lib/node_modules/npm/node_modul$ 10 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetch.js:23:18) 10 verbose stack at pinflight (/usr/local/lib/node_modules/npm/node_modules/pacote/manifest.js:24:12) 10 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:29:24 10 verbose stack at Promise._execute (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/releas$ 10 verbose stack at Promise._resolveFromExecutor (/usr/local/lib/node_modules/npm/node_modules/bluebi$ 10 verbose stack at new Promise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/pro$ 10 verbose stack at _inflight (/usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight$ 10 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:22:14 10 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util$ 11 verbose cwd /home/pi 12 verbose Linux 4.14.98-v7+ 13 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "cassert" 14 verbose node v10.16.0 15 verbose npm v6.9.0 16 error Cannot read property 'resolve' of undefined 17 verbose exit [ 1, true ]I remembered to the hint evtl. to use a lower npm version.
Went to ‘pimatic-app’ and tried, but:root@raspberrypi:/home/pi/pimatic-app# npm install -g npm@6.4.1 npm ERR! Cannot read property 'resolve' of undefined npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-06-29T16_47_34_383Z-debug.log…and for completeness tested
root@raspberrypi:/home/pi/pimatic-app# node_modules/pimatic/pimatic.jswhich works and is reachable via WEB frontend.I then did again
root@raspberrypi:/home/pi/pimatic-app/node_modules/pimatic# npm link npm ERR! Cannot read property 'resolve' of undefined npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-06-29T17_13_33_089Z-debug.logand with root rights, was now able also to fetch the related log-file, which looks as follows:
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'link' ] 2 info using npm@6.9.0 3 info using node@v10.16.0 4 verbose linkPkg /home/pi/pimatic-app/node_modules/pimatic 5 verbose link build target /usr/local/lib/node_modules/pimatic 6 verbose npm-session dda87a37b94e6975 7 silly install runPreinstallTopLevelLifecycles 8 silly preinstall pimatic@0.9.49 9 info lifecycle pimatic@0.9.49~preinstall: pimatic@0.9.49 10 silly install loadCurrentTree 11 silly install readLocalPackageData 12 timing stage:loadCurrentTree Completed in 102ms 13 silly install loadIdealTree 14 silly install cloneCurrentTreeToIdealTree 15 timing stage:loadIdealTree:cloneCurrentTree Completed in 2ms 16 silly install loadShrinkwrap 17 timing stage:loadIdealTree:loadShrinkwrap Completed in 31ms 18 silly install loadAllDepsIntoIdealTree 19 silly fetchPackageMetaData error for blanket@^1.2.2 Cannot read property 'resolve' of undefined 20 silly fetchPackageMetaData error for coffee-errors@^0.8.6 Cannot read property 'resolve' of undefined 21 silly fetchPackageMetaData error for grunt@^1.0.1 Cannot read property 'resolve' of undefined 22 silly fetchPackageMetaData error for grunt-bump@0.8.0 Cannot read property 'resolve' of undefined 23 silly fetchPackageMetaData error for grunt-cli@^1.2.0 Cannot read property 'resolve' of undefined 24 silly fetchPackageMetaData error for grunt-coffeelint@^0.0.16 Cannot read property 'resolve' of undefined 25 silly fetchPackageMetaData error for grunt-mocha-test@^0.13.2 Cannot read property 'resolve' of undefined 26 silly fetchPackageMetaData error for mocha@^3.2.0 Cannot read property 'resolve' of undefined 27 silly fetchPackageMetaData error for sinon@^1.17.3 Cannot read property 'resolve' of undefined 28 silly fetchPackageMetaData error for supertest@^2.0.1 Cannot read property 'resolve' of undefined 29 silly fetchPackageMetaData error for basic-auth@^1.1.0 Cannot read property 'resolve' of undefined 30 silly fetchPackageMetaData error for bluebird@^3.5.4 Cannot read property 'resolve' of undefined 31 silly fetchPackageMetaData error for body-parser@^1.15.2 Cannot read property 'resolve' of undefined 32 silly fetchPackageMetaData error for byline@~5.0.0 Cannot read property 'resolve' of undefined 33 silly fetchPackageMetaData error for coffee-script@^1.11.1 Cannot read property 'resolve' of undefined 34 silly fetchPackageMetaData error for colors@^1.1.2 Cannot read property 'resolve' of undefined 35 silly fetchPackageMetaData error for connect-timeout@^1.6.2 Cannot read property 'resolve' of undefined 36 silly fetchPackageMetaData error for cookie-parser@^1.4.4 Cannot read property 'resolve' of undefined 37 silly fetchPackageMetaData error for cookie-session@^1.2.0 Cannot read property 'resolve' of undefined 38 silly fetchPackageMetaData error for cross-spawn@^5.0.1 Cannot read property 'resolve' of undefined 39 silly fetchPackageMetaData error for daemon@1.1.0 Cannot read property 'resolve' of undefined 40 silly fetchPackageMetaData error for date-format-lite@^0.9.1 Cannot read property 'resolve' of undefined 41 silly fetchPackageMetaData error for decl-api@0.0.24 Cannot read property 'resolve' of undefined 42 silly fetchPackageMetaData error for express@^4.14.0 Cannot read property 'resolve' of undefined 43 silly fetchPackageMetaData error for fs.extra@^1.3.2 Cannot read property 'resolve' of undefined 44 silly fetchPackageMetaData error for gethub@^2.0.2 Cannot read property 'resolve' of undefined 45 silly fetchPackageMetaData error for human-format@^0.7.0 Cannot read property 'resolve' of undefined 46 silly fetchPackageMetaData error for i18n-pimatic@^0.8.3 Cannot read property 'resolve' of undefined 47 silly fetchPackageMetaData error for jayschema@^0.3.1 Cannot read property 'resolve' of undefined 48 silly fetchPackageMetaData error for knex@^0.12.6 Cannot read property 'resolve' of undefined 49 silly fetchPackageMetaData error for lodash@^4.17.11 Cannot read property 'resolve' of undefined 50 silly fetchPackageMetaData error for logrotate-stream@^0.2.5 Cannot read property 'resolve' of undefined 51 silly fetchPackageMetaData error for method-override@^2.3.7 Cannot read property 'resolve' of undefined 52 silly fetchPackageMetaData error for module-alias@^2.2.0 Cannot read property 'resolve' of undefined 53 silly fetchPackageMetaData error for moment@^2.16.0 Cannot read property 'resolve' of undefined 54 silly fetchPackageMetaData error for npm@^2.5.11 Cannot read property 'resolve' of undefined 55 silly fetchPackageMetaData error for relaxed-json@^1.0.0 Cannot read property 'resolve' of undefined 56 silly fetchPackageMetaData error for request-promise@^2.0.1 Cannot read property 'resolve' of undefined 57 silly fetchPackageMetaData error for semver@^5.1.0 Cannot read property 'resolve' of undefined 58 silly fetchPackageMetaData error for socket.io@^1.7.4 Cannot read property 'resolve' of undefined 59 silly fetchPackageMetaData error for source-map-support@^0.4.0 Cannot read property 'resolve' of undefined 60 silly fetchPackageMetaData error for string@^3.3.3 Cannot read property 'resolve' of undefined 61 silly fetchPackageMetaData error for winston@^2.4.4 Cannot read property 'resolve' of undefined 62 silly fetchPackageMetaData error for yet-another-jsonlint@^1.0.1 Cannot read property 'resolve' of undefin$ 63 silly fetchPackageMetaData error for basic-auth@^1.1.0 Cannot read property 'resolve' of undefined 64 silly fetchPackageMetaData error for bluebird@^3.5.4 Cannot read property 'resolve' of undefined 65 silly fetchPackageMetaData error for body-parser@^1.15.2 Cannot read property 'resolve' of undefined 66 silly fetchPackageMetaData error for byline@~5.0.0 Cannot read property 'resolve' of undefined 67 silly fetchPackageMetaData error for coffee-script@^1.11.1 Cannot read property 'resolve' of undefined 68 silly fetchPackageMetaData error for colors@^1.1.2 Cannot read property 'resolve' of undefined 69 silly fetchPackageMetaData error for connect-timeout@^1.6.2 Cannot read property 'resolve' of undefined 70 silly fetchPackageMetaData error for cookie-parser@^1.4.4 Cannot read property 'resolve' of undefined 71 silly fetchPackageMetaData error for cookie-session@^1.2.0 Cannot read property 'resolve' of undefined 72 silly fetchPackageMetaData error for cross-spawn@^5.0.1 Cannot read property 'resolve' of undefined 73 silly fetchPackageMetaData error for daemon@1.1.0 Cannot read property 'resolve' of undefined 74 silly fetchPackageMetaData error for date-format-lite@^0.9.1 Cannot read property 'resolve' of undefined 75 silly fetchPackageMetaData error for decl-api@0.0.24 Cannot read property 'resolve' of undefined 76 silly fetchPackageMetaData error for express@^4.14.0 Cannot read property 'resolve' of undefined 77 silly fetchPackageMetaData error for fs.extra@^1.3.2 Cannot read property 'resolve' of undefined 78 silly fetchPackageMetaData error for gethub@^2.0.2 Cannot read property 'resolve' of undefined 79 silly fetchPackageMetaData error for human-format@^0.7.0 Cannot read property 'resolve' of undefined 80 silly fetchPackageMetaData error for i18n-pimatic@^0.8.3 Cannot read property 'resolve' of undefined 81 silly fetchPackageMetaData error for jayschema@^0.3.1 Cannot read property 'resolve' of undefined 82 silly fetchPackageMetaData error for knex@^0.12.6 Cannot read property 'resolve' of undefined 83 silly fetchPackageMetaData error for lodash@^4.17.11 Cannot read property 'resolve' of undefined 84 silly fetchPackageMetaData error for logrotate-stream@^0.2.5 Cannot read property 'resolve' of undefined 85 silly fetchPackageMetaData error for method-override@^2.3.7 Cannot read property 'resolve' of undefined 86 silly fetchPackageMetaData error for module-alias@^2.2.0 Cannot read property 'resolve' of undefined 87 silly fetchPackageMetaData error for moment@^2.16.0 Cannot read property 'resolve' of undefined 88 silly fetchPackageMetaData error for npm@^2.5.11 Cannot read property 'resolve' of undefined 89 silly fetchPackageMetaData error for relaxed-json@^1.0.0 Cannot read property 'resolve' of undefined 90 silly fetchPackageMetaData error for request-promise@^2.0.1 Cannot read property 'resolve' of undefined 91 silly fetchPackageMetaData error for semver@^5.1.0 Cannot read property 'resolve' of undefined 92 silly fetchPackageMetaData error for socket.io@^1.7.4 Cannot read property 'resolve' of undefined 93 silly fetchPackageMetaData error for source-map-support@^0.4.0 Cannot read property 'resolve' of undefined 94 silly fetchPackageMetaData error for string@^3.3.3 Cannot read property 'resolve' of undefined 95 silly fetchPackageMetaData error for winston@^2.4.4 Cannot read property 'resolve' of undefined 96 silly fetchPackageMetaData error for yet-another-jsonlint@^1.0.1 Cannot read property 'resolve' of undefin$ 97 silly fetchPackageMetaData error for cassert@git+https://github.com/sweetpi/cassert.git#master Command fai$ 97 silly fetchPackageMetaData fatal: Konnte führende Verzeichnisse von '/root/.npm/_cacache/tmp/git-clone-c9a$ 98 timing stage:rollbackFailedOptional Completed in 19ms 99 timing stage:runTopLevelLifecycles Completed in 1687ms 100 silly saveTree pimatic@0.9.49 101 verbose stack TypeError: Cannot read property 'resolve' of undefined 101 verbose stack at regFetch (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/index.js:7$ 101 verbose stack at fetchPackument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/reg$ 101 verbose stack at packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry$ 101 verbose stack at getManifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/regist$ 101 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/$ 101 verbose stack at Object.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/re$ 101 verbose stack at Object.Fetcher#manifest [as manifest] (/usr/local/lib/node_modules/npm/node_modules/$ 101 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetch.js:23:18) 101 verbose stack at pinflight (/usr/local/lib/node_modules/npm/node_modules/pacote/manifest.js:24:12) 101 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:29:24 101 verbose stack at Promise._execute (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/d$ 101 verbose stack at Promise._resolveFromExecutor (/usr/local/lib/node_modules/npm/node_modules/bluebird/$ 101 verbose stack at new Promise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promis$ 101 verbose stack at _inflight (/usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js$ 101 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:22:14 101 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js$ 102 verbose cwd /home/pi/pimatic-app/node_modules/pimatic 103 verbose Linux 4.14.98-v7+ 104 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "link" 105 verbose node v10.16.0 106 verbose npm v6.9.0 107 error Cannot read property 'resolve' of undefined 108 verbose exit [ 1, true ]Ok, this is the last for today.
Have to do something else now
Regards
Pedder -
Hi all,
to make a long story short, I now simply cloned the SD card of my Prod-Raspi to get a 1:1 test environment
So don’t spend any further effort to find a solution for my ‘personal’ npm problems.I will myself try to take care for it at another point of time.
Thanks again to all who tried to help
Pedder -
@00lex said in Pimatic & Node 8.0:
if you’re on a fresh stretch/buster follow stupid 1:1 the guide https://pimatic.teamemo.com/Guide/Getting-Started and it should work.
i’m on a fresh stretch and followed the installation guide. and got
npm ERR! code 128 npm ERR! Command failed: git clone --depth=1 -q -b master https://github.com/sweetpi/cassert.git /root/.npm/_cacache/tmp/git-clone-0832f28d npm ERR! fatal: could not create leading directories of '/root/.npm/_cacache/tmp/git-clone-0832f28d': Permission denied npm ERR! npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-07-01T14_28_59_276Z-debug.logwhen doing
sudo npm link -
Which version of npm do you have?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig npm 6.9.0 and node.js is 10.16.0
-
@quotschmacher said in Pimatic & Node 8.0:
@mwittig npm 6.9.0 and node.js is 10.16.0
… same as me, which also didn’t work and produced the same ERR code 128
-
@pedder said in Pimatic & Node 8.0:
nd produced the same ERR code
Try
sudo npm cache clean -fhttps://stackoverflow.com/questions/56016698/npm-install-permission-denied-npm-cacache
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@pedder said in Pimatic & Node 8.0:
sudo -s npm cache clean --force
already tested, pls see below in the threat
-
Had the same problem and in pimatic folder I
sudo su
npm install cassert
before sudo npm link -
steps to reproduce:
used etcher to bring2019-04-08-raspbian-stretch-lite.imgto a sd card, createdsshandwpa_supplicant.conffiles and then:1 sudo raspi-config nonint do_hostname "pimatic" && sudo raspi-config nonint do_boot_behaviour B2 && sudo raspi-config nonint do_boot_wait 0 && sudo timedatectl set-timezone Europe/Berlin && sudo raspi-config --expand-rootfs && sudo reboot 2 sudo timedatectl status 3 sudo apt-get update && sudo apt-get upgrade -y 4 sudo apt-get install build-essential git -y 5 wget https://nodejs.org/dist/v10.16.0/node-v10.16.0-linux-armv7l.tar.gz -P /tmp 6 cd /usr/local 7 sudo tar xzvf /tmp/node-v10.16.0-linux-armv7l.tar.gz --strip=1 8 /usr/bin/env node --version 9 cd ~ 10 mkdir pimatic-app 11 npm install pimatic --prefix pimatic-app --production 12 cd pimatic-app 13 cd node_modules/pimatic 14 sudo npm link -
@pedder said in Pimatic & Node 8.0:
root@raspberrypi:/home/pi# npm install cassert
npm ERR! Cannot read property ‘resolve’ of undefinednpm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-06-29T16_25_36_861Z-debug.logHi, already tested that (pls see below) but again got errors
The sympthons in my installation seems absolutely equal with @quotschmacher
-
@quotschmacher said in Pimatic & Node 8.0:
steps to reproduce:
with 0.9.50 those steps don’t produce any error and setup is running as described in the wiki!
thanks @mwittig
