UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[crunchip]

Gestern schon versucht den iogo Adapter zu aktualisieren mit dem Ergebnis

$ ./iobroker upgrade iogo
Update iogo from @0.4.4 to @0.4.5
NPM version: 6.9.0
npm install iobroker.iogo@0.4.5 --production --save --prefix "/opt/iobroker" (System call)
npm WARN
 @typescript-eslint/eslint-plugin@1.12.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.npm WARN @typescript-eslint/parser@1.12.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm WARN
 optional
 SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})


npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.iogo"
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm 
WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN
 tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm
 WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN
 tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm
 WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write

npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm
 WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar
 ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, writenpm WARN
 tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN 
tar ENOSPC: no space left on device, writenpm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write
npm WARN tar ENOSPC: no space left on device, write

npm WARN
 tar ENOSPC: no space left on device, write
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

got /opt/iobroker/node_modules/iobroker.iogo/admin
upload [3] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/words.js words.js application/javascript
Update "system.adapter.iogo.0"
upload [2] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/iogo.png iogo.png image/png
upload [1] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/index_m.html index_m.html text/html
upload [0] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/index.html index.html text/html
Adapter "iogo" updated
process exited with code 0

Heute Nacht Punkt 0.00 Uhr ist dann IoBroker abgekackt

2019-09-13 00:00:00.364 - error: iogo.0 uncaught exception: Function DocumentReference.set() called with invalid data. Unsupported field value: undefined (found in field min)
2019-09-13 00:00:00.364 - error: iogo.0 FirebaseError: Function DocumentReference.set() called with invalid data. Unsupported field value: undefined (found in field min)
at new FirestoreError (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:354:28)
at ParseContext.createError (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:19832:16)
at UserDataConverter.parseScalarValue (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20179:27)
at UserDataConverter.parseData (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20045:29)
at /opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20061:41
at forEach (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:458:13)
at UserDataConverter.parseObject (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20060:13)
at UserDataConverter.parseData (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20019:25)
at UserDataConverter.parseSetData (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:19884:31)
at DocumentReference.set (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20829:45)
2019-09-13 00:00:00.365 - info: iogo.0 cleaned everything up...
2019-09-13 00:00:00.365 - info: iogo.0 triggered listener removed
2019-09-13 00:00:00.369 - info: iogo.0 listener removed
2019-09-13 00:00:00.375 - info: iogo.0 signed out
2019-09-13 00:00:00.392 - info: iogo.0 triggered listener removed
2019-09-13 00:00:00.392 - info: iogo.0 listener removed
2019-09-13 00:00:00.099 - info: host.IoBroker instance system.adapter.dwd.0 started with pid 24147
2019-09-13 00:00:00.379 - info: javascript.0 script.js.Visualisierung.Wegezeit_Arbeit_Landstraße: Anzahl Wegepunkte: 28
2019-09-13 00:00:00.445 - info: javascript.0 script.js.Visualisierung.Wegezeit_Arbeit_Autobahn: Anzahl Wegepunkte: 19
2019-09-13 00:00:00.284 - info: host.IoBroker instance system.adapter.daswetter.0 started with pid 24155
2019-09-13 00:00:00.500 - info: sourceanalytix.0 Updated SourceAnalytix configuration for : wiffi-wz.0.root.192_168_178_33.w_counter_1
2019-09-13 00:00:00.503 - info: sourceanalytix.0 Setting start value Day for device : wiffi-wz.0.root.192_168_178_33.w_counter_2 succeeded with value + 2591.14
2019-09-13 00:00:00.512 - info: influxdb.0 enabled logging of wiffi-wz.0.root.192_168_178_33.w_counter_1, Alias=false
2019-09-13 00:00:00.515 - warn: iogo.0 You are not logged in
2019-09-13 00:00:00.515 - warn: iogo.0 You are not logged in
2019-09-13 00:00:00.362 - info: host.IoBroker instance system.adapter.ical.0 started with pid 24157
2019-09-13 00:00:00.494 - info: host.IoBroker instance system.adapter.feiertage.0 started with pid 24169
2019-09-13 00:00:00.535 - info: iogo.0 terminating
2019-09-13 00:00:00.544 - info: sourceanalytix.0 Setting start value Day for device : wiffi-wz.0.root.192_168_178_33.w_counter_1 succeeded with value + 112242.41
2019-09-13 00:00:00.966 - error: Caught by controller[0]: { FirebaseError: Function DocumentReference.set() called with invalid data. Unsupported field value: undefined (found in field min)
2019-09-13 00:00:02.143 - info: javascript.0 script.js.common.System.Logfiles2: Start new Tail process. File path to current log: [/opt/iobroker/log/iobroker.2019-09-13.log]
2019-09-13 00:00:00.967 - error: Caught by controller[0]: at new FirestoreError (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:354:28)
2019-09-13 00:00:00.967 - error: Caught by controller[0]: at ParseContext.createError (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:19832:16)
2019-09-13 00:00:00.967 - error: Caught by controller[0]: at UserDataConverter.parseScalarValue (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20179:27)
2019-09-13 00:00:00.967 - error: Caught by controller[0]: at UserDataConverter.parseData (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20045:29)
2019-09-13 00:00:00.967 - error: Caught by controller[0]: at /opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20061:41
2019-09-13 00:00:00.967 - error: Caught by controller[0]: at forEach (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:458:13)
2019-09-13 00:00:01.012 - error: Caught by controller[0]: at UserDataConverter.parseObject (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20060:13)
2019-09-13 00:00:01.012 - error: Caught by controller[0]: at UserDataConverter.parseData (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20019:25)
2019-09-13 00:00:01.012 - error: Caught by controller[0]: at UserDataConverter.parseSetData (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:19884:31)
2019-09-13 00:00:01.012 - error: Caught by controller[0]: at DocumentReference.set (/opt/iobroker/node_modules/@firebase/firestore/dist/index.node.cjs.js:20829:45)
2019-09-13 00:00:01.012 - error: Caught by controller[0]: code: 'invalid-argument',
2019-09-13 00:00:01.012 - error: Caught by controller[0]: name: 'FirebaseError',
2019-09-13 00:00:01.012 - error: Caught by controller[0]: toString: [Function] }
2019-09-13 00:00:01.012 - error: host.IoBroker instance system.adapter.iogo.0 terminated with code 0 (OK)

Hab nun ein Backup eingespielt und nochmal versucht

vm in proxmox
node.js10.16
npm6.9.0
admin 3.6.4
rootdisk 15G
Iobroker 6.5G
Ram 3G von 4,5

[crunchip]

Den Adapter habe ich nun mal komplett gelöscht und neu installiert

$ ./iobroker add iogo  --host IoBroker
NPM version: 6.9.0
npm install iobroker.iogo@0.4.5 --production --save --prefix "/opt/iobroker" (System call)
node-pre-gyp
 WARN Using request for node-pre-gyp https download 
npm WARN @typescript-eslint/eslint-plugin@1.12.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.npm WARN @typescript-eslint/parser@1.12.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself.

npm
 WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

host.IoBroker install adapter iogo
got /opt/iobroker/node_modules/iobroker.iogo/admin
upload [3] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/words.js words.js application/javascript
upload [2] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/iogo.png iogo.png image/png
upload [1] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/index_m.html index_m.html text/html
upload [0] iogo.admin /opt/iobroker/node_modules/iobroker.iogo/admin/index.html index.html text/html
host.IoBroker object system.adapter.iogo created
host.IoBroker create instance iogo
host.IoBroker object iogo.0.info.ts created
host.IoBroker object iogo.0.info.connection created
host.IoBroker object system.adapter.iogo.0.outputCount created
host.IoBroker object system.adapter.iogo.0.inputCount created
host.IoBroker object system.adapter.iogo.0.uptime created
host.IoBroker object system.adapter.iogo.0.memRss created
host.IoBroker object system.adapter.iogo.0.memHeapTotal created
host.IoBroker object system.adapter.iogo.0.memHeapUsed created
host.IoBroker object system.adapter.iogo.0.cputime created
host.IoBroker object system.adapter.iogo.0.cpu created
host.IoBroker object system.adapter.iogo.0.connected created
host.IoBroker object system.adapter.iogo.0.alive created
host.IoBroker object system.adapter.iogo.0 created
process exited with code 0

scheint wieder zu funktionieren

[Negalein]

@crunchip sagte in Error:ENOSPC: no space left:

scheint wieder zu funktionieren

Wenn ein Thema gelöst wurde bitte den Beitrag der die Lösung beinhaltet als gelöst markieren.
-> 3 Punkte Menü rechts unten am Beitrag -> Mark this post as the correct answer

[crunchip]

@Negalein wollte ich noch nicht, da vllt sich jemand noch dazu meldet, was den Fehler verursacht haben könnte, bzw was diese Meldungen bedeuten.

[Negalein]

@crunchip sagte in Error:ENOSPC: no space left:

@Negalein wollte ich noch nicht, da vllt sich jemand noch dazu meldet, was den Fehler verursacht haben könnte, bzw was diese Meldungen bedeuten.

Oki Doki :)