Hallo,
ich habe Watchtower laufen und ob das nun läuft oder nicht ist egal.
Es gibt ein Update für den js-controller das ich von Hand nicht auslösen kann und Watchtower erkennt das nicht.
Wie macht ihr Updates wenn es innerhalb der Lösung Updates gibt?
Hallo,
einen neuen Docker Container (iobroker von buanet) spiele ich nur selten ein.
Bei den kleinen Updates aktualisiere ich direkt im Container.
Also:
pkill -u iobroker
iobroker update
iobroker upgrade self
Und dann Neustart des Containers.
Tschau
Uwe
Hallo Uwe,
machst du das im Terminal des Containers oder direkt auf dem NAS?
Den javascript controller update ich direkt auf der Konsole im Container. (Das geht auch nur so)
Tschau
Uwe
Wenn ich das so machen wie es beschrieben hast kommt folgendes aber das Update hat geklappt.
Danke
root@iobroker:/opt/iobroker# pkill -u iobroker
root@iobroker:/opt/iobroker# iobroker update
Used repository: Beta (latest)
hash changed or no sources cached => force download of new sources
update done
Adapter "admin" : 5.3.0 , installed 5.3.0
Adapter "backitup" : 2.3.2 , installed 2.3.2
Adapter "discovery" : 2.7.5 , installed 2.7.5
Adapter "dwd" : 2.7.7 , installed 2.7.7
Adapter "hue" : 3.6.5 , installed 3.6.5
Adapter "info" : 1.9.18 , installed 1.9.18
Adapter "javascript" : 5.2.21 , installed 5.2.21
Controller "js-controller" : 4.0.9 , installed 3.3.22 [Updateable]
Adapter "luftdaten" : 2.1.3 , installed 2.1.3
Adapter "modbus" : 3.4.17 , installed 3.4.17
Adapter "netatmo" : 1.4.4 , installed 1.4.4
Adapter "pi-hole" : 1.3.4 , installed 1.3.4
Adapter "simple-api" : 2.6.2 , installed 2.6.2
Adapter "sma-em" : 0.6.4 , installed 0.6.4
Adapter "socketio" : 4.1.2 , installed 4.1.2
Adapter "stiebel-isg" : 1.7.5 , installed 1.7.5
Adapter "vis" : 1.4.12 , installed 1.4.12
Adapter "vis-plumb" : 1.0.2 , installed 1.0.2
Adapter "web" : 4.1.4 , installed 4.1.3 [Updateable]
Adapter "ws" : 1.1.4 , installed 1.1.4
root@iobroker:/opt/iobroker# iobroker upgrade self
Update js-controller from @3.3.22 to @4.0.9
NPM version: 6.14.16
npm install iobroker.js-controller@4.0.9 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
In file included from ../../nan/nan.h:58,
from ../src/unix_dgram.cc:5:
/opt/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
793 | (node::addon_register_func) (regfunc), \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
827 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage)
| ^~~~~~~~~~~~~
../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
404 | NODE_MODULE(unix_dgram, Initialize)
| ^~~~~~~~~~~
Server Objects 127.0.0.1:52224 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
Server States 127.0.0.1:53898 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
Server Objects 127.0.0.1:52224 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
Server States 127.0.0.1:53900 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
Server Objects 127.0.0.1:52224 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:52224 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:52224 Error from InMemDB: Error: Unknown LUA script load
Server Objects 127.0.0.1:52224 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
root@iobroker:/opt/iobroker#Das hat dann aber nur solange bestand wie der Container nicht gelöscht wird.
ich habe es mit den in #2 beschriebene Schritten versucht dabei kamen folgende Meldungen
bei "iobroker update"
bei "iobroker upgrade self"
Update js-controller from @3.1.6 to @4.0.24
NPM version: 6.14.6
npm install iobroker.js-controller@4.0.24 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
In file included from ../node_modules/nan/nan.h:60,
from ../src/unix_dgram.cc:5:
/opt/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:608:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
(node::addon_register_func) (regfunc), \
^
/opt/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:642:3: note: in expansion of macro ‘NODE_MODULE_X’
NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage)
^~~~~~~~~~~~~
../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
NODE_MODULE(unix_dgram, Initialize)
^~~~~~~~~~~
Objects 127.0.0.1:48380 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
Objects 127.0.0.1:48380 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
States 127.0.0.1:49672 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
Objects 127.0.0.1:48380 Error from InMemDB: Error: scan NOT SUPPORTED
/opt/iobroker/node_modules/standard-as-callback/built/index.js:6
throw e;
^
ReplyError: Error scan NOT SUPPORTED
at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
Emitted 'error' event on ScanStream instance at:
at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
command: {
name: 'scan',
args: [ '0', 'MATCH', 'cfg.o.system.host.*', 'COUNT', '250' ]
}
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.js-controller@4.0.24 install: `node iobroker.js setup first`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.js-controller@4.0.24 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /opt/iobroker/.npm/_logs/2023-02-22T20_18_34_297Z-debug.log
host.iobroker-test Cannot install iobroker.js-controller@4.0.24: 1Kann mir jemand weiter helfen