Hi again,
as mentioned in my other problem (https://forum.pimatic.org/topic/4459/trouble-after-switching-from-ethernet-to-wlan), I started to set up a new PI3 with Pimatic (complete new HW with fresh raspian only XRDP additionally installed), but …
I strongly followed the installation guide (https://pimatic.org/guide/getting-started/installation/), but got now the third time tonnes of warning/error-messages.
By executing: npm install pimatic --prefix pimatic-app --production
I always get the below pasted long series of warnings.
After starting Pimatic by (for sure config.json is prepared):
sudo node_modules/pimatic/pimatic.js start
I get:
coffee-cache: compiling coffee-script file “lib/daemon.coffee”…Done
Started.
Asking on the status then says:
Pidfile exists, but process is dead.
Making the service available globally:
sudo npm link
again causes a long list of warnings with simillar content than before (see below).
Checking the status afterwards:
sudo pimatic.js status
brings the same result:
Pidfile exists, but process is dead.
Has anything changed in the installation routine in the last time, or has any body an idea what I can do to solve that problem?
I already installed my 1st PI3+Pimatic according to the guideline some weeks ago and had no problems.
List of Warnings:
’’'npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to “coffeescript” (no hyphen)
npm WARN deprecated jayschema@0.3.2: this project is no longer maintained
npm WARN installMany coffee-script was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany express was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany i18n was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany winston was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany cassert was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany lodash was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany bluebird was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany semver was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany fs.extra was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany daemon was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany date-format-lite was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany string was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany byline was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany knex was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany moment was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany colors was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany decl-api was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany jayschema was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany relaxed-json was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany source-map-support was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany human-format was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany gethub was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN installMany npm was bundled with pimatic@0.9.43, but bundled package wasn’t found in unpacked tree
npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
npm WARN engine graceful-fs@4.1.14: wanted: {“node”:">=6"} (current: {“node”:“4.6.2”,“npm”:“2.15.11”})
npm WARN engine graceful-fs@4.1.14: wanted: {“node”:">=6"} (current: {“node”:“4.6.2”,“npm”:“2.15.11”})
typechecker@2.0.8 preinstall /home/pi/pimatic-app/node_modules/pimatic/node_modules/i18n/node_modules/messageformat/node_modules/watchr/node_modules/extendr/node_modules/typechecker
node ./cyclic.js
typechecker@2.0.8 preinstall /home/pi/pimatic-app/node_modules/pimatic/node_modules/i18n/node_modules/messageformat/node_modules/watchr/node_modules/extract-opts/node_modules/typechecker
node ./cyclic.js
pimatic@0.9.43 pimatic-app/node_modules/pimatic
├── byline@5.0.0
├── basic-auth@1.1.0
├── date-format-lite@0.9.2
├── semver@5.6.0
├── human-format@0.7.0
├── decl-api@0.0.22
├── daemon@1.1.0
├── cassert@0.1.2 (callsite@1.0.0)
├── colors@1.3.2
├── string@3.3.3
├── cookie-parser@1.4.3 (cookie-signature@1.0.6, cookie@0.3.1)
├── coffee-script@1.12.7
├── connect-timeout@1.9.0 (ms@2.0.0, on-headers@1.0.1, on-finished@2.3.0, http-errors@1.6.3)
├── cookie-session@1.3.2 (on-headers@1.0.1, cookies@0.7.1, debug@2.6.9)
├── method-override@2.3.10 (methods@1.1.2, vary@1.1.2, parseurl@1.3.2, debug@2.6.9)
├── bluebird@3.5.2
├── source-map-support@0.4.18 (source-map@0.5.7)
├── cross-spawn@5.1.0 (shebang-command@1.2.0, lru-cache@4.1.3, which@1.3.1)
├── relaxed-json@1.0.1 (commander@2.19.0, chalk@1.1.3)
├── fs.extra@1.3.2 (mkdirp@0.3.5, walk@2.3.14, fs-extra@0.6.4)
├── winston@2.4.4 (cycle@1.0.3, stack-trace@0.0.10, eyes@0.1.8, isstream@0.1.2, async@1.0.0, colors@1.0.3)
├── express@4.16.4 (cookie-signature@1.0.6, methods@1.1.2, content-type@1.0.4, vary@1.1.2, parseurl@1.3.2, cookie@0.3.1, escape-html@1.0.3, array-flatten@1.1.1, setprototypeof@1.1.0, utils-merge@1.0.1, merge-descriptors@1.0.1, encodeurl@1.0.2, fresh@0.5.2, range-parser@1.2.0, etag@1.8.1, serve-static@1.13.2, content-disposition@0.5.2, path-to-regexp@0.1.7, safe-buffer@5.1.2, statuses@1.4.0, depd@1.1.2, on-finished@2.3.0, qs@6.5.2, finalhandler@1.1.1, proxy-addr@2.0.4, debug@2.6.9, send@0.16.2, type-is@1.6.16, accepts@1.3.5)
├── body-parser@1.18.3 (content-type@1.0.4, bytes@3.0.0, depd@1.1.2, on-finished@2.3.0, qs@6.5.2, http-errors@1.6.3, raw-body@2.3.3, debug@2.6.9, type-is@1.6.16, iconv-lite@0.4.23)
├── logrotate-stream@0.2.5 (byt@0.1.0, log-rotate@0.2.8, optimist@0.6.1)
├── socket.io@1.7.4 (object-assign@4.1.0, socket.io-adapter@0.5.0, has-binary@0.1.7, debug@2.3.3, socket.io-parser@2.3.1, engine.io@1.8.5, socket.io-client@1.7.4)
├── gethub@2.0.2 (promise@7.3.1, hyperquest@1.3.0, rimraf@2.6.2, tar@2.2.1)
├── jayschema@0.3.2 (when@3.4.6)
├── i18n@0.8.3 (mustache@3.0.0, sprintf-js@1.1.1, debug@4.1.0, math-interval-parser@1.1.0, make-plural@3.0.6, messageformat@0.3.1)
├── jsonlint@1.6.2 (nomnom@1.8.1, JSV@4.0.2)
├── moment@2.22.2
├── lodash@3.10.1
├── request-promise@2.0.1 (bluebird@2.11.0, request@2.88.0, lodash@4.17.11)
├── knex@0.12.9 (inherits@2.0.3, safe-buffer@5.1.2, commander@2.19.0, interpret@0.6.6, pg-connection-string@0.1.3, generic-pool@2.5.4, minimist@1.1.3, uuid@3.3.2, tildify@1.0.0, v8flags@2.1.1, debug@2.6.9, readable-stream@1.1.14, chalk@1.1.3, mkdirp@0.5.1, liftoff@2.2.5, lodash@4.17.11, babel-runtime@6.26.0)
└── npm@2.15.12’’’
