Beta Test js-controller 3.2.x auf GitHub
-
@Jan1 am Ende sind das wieder die üblichen npm Fehler die du an sich immer bei jedem Adapter Install bzw update sehen solltest. Die kommen nicht vom Controller selbst sondern von anderen Adaptern aber npm versucht es immer wieder. Wenn es aber tut sind das optionale dependencies und daher ok. Könnte man wegbekommen wäre a er eigener Forum thread ;-))
-
@apollon77 und allen Beteiligten!
Hi,
super, vielen Dank, ich verfolge die ganze Zeit die Changes... echt bös viel Arbeit drin!Hier läuft das Update nicht ohne Probleme, das Update selbst von 3.16 mit Node 12.20.1 (Raspi), Node 12.20.0 (Raspi-Zero), nirgends ein Fehler aufgetreten.
Das sind alles Clients ( Redis ).Auf dem Server ( lxc Debian 10, Node 14.15.1 ) startet er nach dem Update leider nicht mehr, scheint was mit Redis zu tun haben, der Redis-server selbst läuft ohne Fehler:
2021-01-09 08:47:23.706 - info: host.VMC123-iobroker iobroker Starting node restart.js 2021-01-09 08:47:24.414 - error: host.VMC123-iobroker Could not delete /opt/iobroker/node_modules/iobroker.js-controller/pids.txt: Error: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt' 2021-01-09 08:47:25.110 - info: host.VMC123-iobroker iobroker.js-controller version 3.2.1 js-controller starting 2021-01-09 08:47:25.113 - info: host.VMC123-iobroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-01-09 08:47:25.113 - info: host.VMC123-iobroker hostname: VMC123-iobroker, node: v14.15.4 2021-01-09 08:47:25.114 - info: host.VMC123-iobroker ip addresses: 192.168.3.41 2021-01-09 08:47:25.221 - info: host.VMC123-iobroker connected to Objects and States 2021-01-09 08:47:25.350 - info: host.VMC123-iobroker added notifications configuration of host 2021-01-09 08:47:26.348 - error: host.VMC123-iobroker uncaught exception: Installation error or unknown objects database type: 127.0.0.1 2021-01-09 08:47:26.349 - error: host.VMC123-iobroker Error: Installation error or unknown objects database type: 127.0.0.1 at objectsDbHasServer (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2640:15) at Object.isLocalObjectsDbServer (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2653:10) at startMultihost (/opt/iobroker/node_modules/iobroker.js-controller/main.js:186:44) at /opt/iobroker/node_modules/iobroker.js-controller/main.js:532:21 at checkHost (/opt/iobroker/node_modules/iobroker.js-controller/main.js:933:21) at /opt/iobroker/node_modules/iobroker.js-controller/main.js:531:17 at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginHandler.js:148:109 at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginHandler.js:133:47 at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:304:17 2021-01-09 08:47:26.354 - info: host.VMC123-iobroker iobroker _restart 2021-01-09 08:47:26.375 - info: host.VMC123-iobroker terminatedHab erstmal den Snapshot wieder hergestellt...
-
@ilovegym zeig bitte mal Ausgabe von „iobroker setup custom“ da scheint was bei dir falsch eingestellt zu sein und up steht im Typ Feld.
Bzw zeig mal dein /opt/iobroker/iobroker-data/iobroker.json
Bei mir läuft redis problemlos.
-
setup custom
ilovegym@VMC123-iobroker:/opt/iobroker$ iobroker setup custom Current configuration: - Objects database: - Type: redis - Host/Unix Socket: 127.0.0.1 - Port: 6379 - States database: - Type: redis - Host/Unix Socket: 127.0.0.1 - Port: 6379 Type of objects DB [(f)ile, (r)edis], default [redis]:das json:
ilovegym@VMC123-iobroker:/opt/iobroker$ cat /opt/iobroker/iobroker-data/iobroker.json { "system": { "memoryLimitMB": 0, "hostname": "", "statisticsInterval": 15000, "statisticsIntervalComment": "Interval how often the counters for input/output in adapters and controller will be updated" }, "multihostService": { "enabled": true, "secure": true, "password": "3edcfbcce1de120ae6c2af0909623e22" }, "network": { "IPv4": true, "IPv6": true, "bindAddress": null }, "objects": { "type": "redis", "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].", "host": "127.0.0.1", "port": 6379, "user": "", "pass": "", "noFileCache": false, "connectTimeout": 2000, "backup": { "disabled": false, "files": 24, "filesComment": "Minimal number of backup files, after the deletion will be executed according to backupTime settings", "hours": 48, "hoursComment": "All backups older than 48 hours will be deleted. But only if the number of files is greater than of backupNumber", "period": 120, "periodComment": "by default backup every 2 hours. Time is in minutes. To disable backup set the value to 0", "path": "", "pathComment": "Absolute path to backup directory or empty to backup in data directory" }, "options": { "auth_pass": null, "retry_max_delay": 5000 } }, "states": { "type": "redis", "typeComment": "Possible values: 'file' - [port 9000], 'redis' - [port 6379].", "host": "127.0.0.1", "port": 6379, "maxQueue": 1000, "options": { "auth_pass": null, "retry_max_delay": 5000 }, "backup": { "disabled": false, "files": 24, "filesComment": "Minimal number of backup files, after the deletion will be executed according to backupTime settings", "hours": 48, "hoursComment": "All backups older than 48 hours will be deleted. But only if the number of files is greater than of backupNumber", "period": 120, "periodComment": "by default backup every 2 hours. Time is in minutes. To disable backup set the value to 0", "path": "", "pathComment": "Absolute path to backup directory or empty to backup in data directory" } }, "log": { "level": "info", "maxDays": 7, "noStdout": true, "transport": { "file1": { "type": "file", "enabled": true, "filename": "log/iobroker", "fileext": ".log", "maxsize": null, "maxFiles": null }, "syslog1": { "type": "syslog", "enabled": false, "host": "localhost", "host_comment": "The host running syslogd, defaults to localhost.", "port_comment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).", "protocol": "udp4", "protocol_comment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).", "path_comment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).", "facility_comment": "Syslog facility to use (Default: local0).", "localhost": "iobroker", "localhost_comment": "Host to indicate that log messages are coming from (Default: localhost).", "sysLogType_comment": "The type of the syslog protocol to use (Default: BSD).", "app_name_comment": "The name of the application (Default: process.title).", "eol_comment": "The end of line character to be added to the end of the message (Default: Message without modifications)." } } }, "dataDirComment": "Always relative to iobroker.js-controller/", "dataDir": "../../iobroker-data/" }ilovegym@VMC123-iobroker:/opt/iobroker$ -
@ilovegym interessant. Checke ich nachher genauer. Legst mir bitte ein issue an dazu?
-
Hallo, hier der Bericht:
Installation unter Windows hat beim 1. Mal nicht geklappt. Nach Neustart und nochmaliger installation dann doch.
Install Logs:
Aktuelle Logs:
hm-rpc.1 2021-01-09 09:33:13.985 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:33:13.072 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:31:43.974 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:31:43.063 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:30:13.970 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:30:13.060 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:28:43.949 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:28:43.054 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:27:13.949 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:27:13.045 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:25:43.939 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:25:43.035 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:24:13.910 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:24:13.031 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:23:10.067 warn (9664) State "hm-rpc.1.00091A49A082FC.1.PRESS_SHORT" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:22:43.899 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:22:43.020 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:22:09.372 warn (9664) State "hm-rpc.1.00091A49A082FC.1.PRESS_SHORT" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:21:13.889 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:21:13.011 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:19:44.202 warn (9664) State "hm-rpc.1.00091A49A082FC.1.PRESS_SHORT" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:19:43.874 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:19:43.001 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:18:43.523 warn (9664) State "hm-rpc.1.00091A49A082FC.1.PRESS_SHORT" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:18:13.877 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:18:12.992 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions hm-rpc.1 2021-01-09 09:16:43.859 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versions hm-rpc.0 2021-01-09 09:16:42.990 warn (7112) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions host.Medion(Test) 2021-01-09 09:16:13.400 error instance system.adapter.ical.1 terminated with code 134 (134) host.Medion(Test) 2021-01-09 09:15:58.592 error instance system.adapter.ical.0 terminated with code 134 (134) hm-rpc.1 2021-01-09 09:15:13.852 warn (9664) State "hm-rpc.1.CENTRAL.0.PONG" has no existing object, this might lead to an error in future versionsPlatform: Windows RAM: 16 GB Node.js: v12.20.1 NPM: 6.14.10 JS Controler: 3.2.1 Admin: 4.2.0 Web: 3.2.0 Socket.io: 3.0.13 Script Engine: 4.10.8 IOT: 1.8.8 VIS: 1.3.6Bericht 2
Update auf Version 3.2.2 hat problemlos geklappt.
open Request’s Past, Present and Future #3142
-
Hi,
hmpff.. na, ich probier noch n bisschen rum..Hier das Issue auf Git
Auf den Clients läufts ja.. aber ich hatte auch 3.17 und 3.18 installiert.. vielleicht ist das vermurkst worden..
-
@apollon77 Ok, habs schon, fix kommt gleich
-
@sigi234 Also das scheint wieder dieses "Windows wirft npm Pakete weg die es nicht sollte sein ... wenn es dann geklappt hat cool.
Die "... has no existing object, this might lead to an error in future versions" sind genau die die ich im Text oben gemeint habe. Bitte bei den Adaptern meldem
-
@apollon77 Ok, 3.2.2 auf GitHub, mach Sinn FÜR ALLE nochmal zu updaten!!
-
@apollon77 Moin Ingo, dann wolle mer mal weider
War noch die 3.2.1, aber die Installation (Linux) lief problemlos. Dafür habe ich von etlichen Adaptern:shelly.0 2021-01-09 09:45:08.668 error (13149) Cannot find search "folder" in "system"wobei er das beim shelly sogar im 5 Sekunden-Raster wirft. Jetzt wohl kein Problem vom JS-Controller (?), bremst aber das System zum testen extrem aus, da sich auch andere Adapter darüber beschweren.
GitHub Issue dazu...
-
@SBorg Bitte stoppe Controller nochmal. Mach nochmal „iobroker setup first“ und starte nochmal. Ist’s dann weg?
-
das war also sowas wie ein "stay at 127.0.0.1 (localhost), dont be a 255.255.255.255 (broadcast) " Problem..
läuft jetzt. Adapter machen Errors... bin am Auswerten...
-
@ilovegym Fehler oder Warnungen?
-
@apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:
@SBorg Bitte stoppe Controller nochmal. Mach nochmal „iobroker setup first“ und starte nochmal. Ist’s dann weg?
Leider nein (jetzt mit 3.2.2 probiert). Scheint er auch beim Installieren ordentlich ausgeführt zu haben:
(Auszug Ausgabe)... > iobroker.js-controller@3.2.2 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme > node scripts/postinstall ... -
@SBorg ok bitte issue Im GitHub. Checken später. File dB oder redis? Bitte mit rein packen.
-
@apollon77
Ja, lag/liegt an npm@7 (Die kommt mit node15 mit)
Zurück auf node14 mit npm@6 läuft die Installation gerade:pi@raspberrypi:/opt/iobroker $ npm install ioBroker/ioBroker.js-controller npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!Also alles i.O., ich war mit den Versionen zu weit draußen.
Wobei ich mit npm@7 Adapter-Updates aus 'latest' machen konnte, offenbar geht das mit git-checkouts nicht mehr in der alten Form. Ich hatte aber soweit ich mich erinnere lange nichts mehr aus git geangelt.[Edit:] Der einzige Adapter, der bei mir aus git kommt zickt jetzt doch rum:
npm ERR! Error while executing: npm ERR! /usr/bin/git ls-remote -h -t https://github.com/luca-saggese/samsungtv.git npm ERR! npm ERR! fatal: unable to access 'https://github.com/luca-saggese/samsungtv.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated. npm ERR! npm ERR! exited with error code: 128 npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-01-09T09_55_27_712Z-debug.log -
@apollon77 Issues:
https://github.com/Apollon77/ioBroker.alexa2/issues/603
https://github.com/Apollon77/ioBroker.alexa2/issues/604
https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/210
https://github.com/jack-blackson/ioBroker.countdown/issues/41
https://github.com/Matten-Matten/ioBroker.enigma2/issues/45
https://github.com/iobroker-community-adapters/ioBroker.proxmox/issues/80
closed js-controller 3.2.2 next one... #604
closed js-controller 3.2.2 uncaught exception... #210
closed js-controller 3.2.2 #41
closed js-controller 3.2.2 #80
-
@Thomas-Braun das ist aber kein Adapter von der url Form her. Da fehlt ioBroker. Im Repo Namen aber ist ja wieder irgend ein npm Fehler.
-
@apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:
@Thomas-Braun das ist aber kein Adapter von der url Form her. Da fehlt ioBroker. Im Repo Namen aber ist ja wieder irgend ein npm Fehler.
so ist es:
wird das Paket in einem Adapter verwendet?
