NEWS
Test js-controller v2.0.x (GitHub)
-
iobroker status geht ja jetzt, es kommt aber noch ein Fehler:
root@MSNUC-IOB:~# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed. root@MSNUC-IOB:~#UPDATE: Wenn ich ins /opt/iobroker wechsel, dann kommt die Fehlermeldung nicht
root@MSNUC-IOB:~# cd /opt/iobroker/ root@MSNUC-IOB:/opt/iobroker# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis root@MSNUC-IOB:/opt/iobroker#Proxmox 3 Node HA-Cluster TRIGKEY Mini-PC N100 mit 32 GB RAM und 3x1TB shared SSDs. VM- iobroker ,Raspberrymatic. LXC - Adguard, , Traccar, iSpy, Fileserver (emby, MiniDLNA)...usw
-
iobroker status geht ja jetzt, es kommt aber noch ein Fehler:
root@MSNUC-IOB:~# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed. root@MSNUC-IOB:~#UPDATE: Wenn ich ins /opt/iobroker wechsel, dann kommt die Fehlermeldung nicht
root@MSNUC-IOB:~# cd /opt/iobroker/ root@MSNUC-IOB:/opt/iobroker# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis root@MSNUC-IOB:/opt/iobroker# -
Habe heute Zeit gefunden den neuen js-controller zu installieren, funktioniert auch soweit alles ohne Fehler.
Jetzt wollte ich noch auf redis/redis umstellen, dass will aber irgendwie nicht, bräuchte da mal Hilfe.
Hier der Konsole Mitschnitt:root@debian:/opt/iobroker# iobroker setup custom Current configuration: - Objects database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9001 - States database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9000 - Data Directory: ../../iobroker-data/ Type of objects DB [(f)ile, (r)edis], default [file]: r When Objects and Files are stored in a Redis database please consider the following: 1. All data will be stored in RAM, make sure to have enough free RAM available! 2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss! 3. The Redis persistence files can get big, make sure not to use an SD card to store them. Host / Unix Socket of objects DB(redis), default[127.0.0.1]: Port of objects DB(redis), default[6379]: Type of states DB [(f)file, (r)edis], default [redis]: r Host / Unix Socket of states DB (redis), default[127.0.0.1]: Port of states DB (redis), default[6379]: Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: n Important: Using Redis for the Objects database is only supported with js-controller 2.0 or higher! When your system consists of multiple hosts please make sure to have js-controller 2.0 or higher installed on ALL hosts *before* continuing! Important #2: If you already did the migration on an other host please *do not* migrate again! This can destroy your system! Important #3: The process will migrate all files that were officially uploaded into the ioBroker system. If you have manually copied files into iobroker-data/files/... into own directories then these files will NOT be migrated! Make sure all files are in adapter directories inside the files directory! Do you want to migrate objects and states from "file/file" to "redis/redis" [y/N]: y Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y Connecting to previous DB "file"... Creating backup ... This can take some time ... please be patient! host.debian 38585 states saved host.debian 44464 objects saved Backup created: /opt/iobroker/backups/2019_10_01-11_46_17_backupiobroker-migration.tar.gz Connecting to new DB "redis" ... /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:28 if (!options.states) throw 'Invalid arguments: states is missing'; ^ Invalid arguments: states is missing root@debian:/opt/iobroker# -
@arteck said in [Aufruf] js-controller 2.0 Beta Test:
@msauer machmal
service redis-server statusroot@MSNUC-IOB:/opt/iobroker# service redis-server status ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-10-01 08:44:47 CEST; 3h 31min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 408 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 462 (redis-server) Tasks: 4 (limit: 4701) Memory: 232.3M CGroup: /system.slice/redis-server.service └─462 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 08:44:46 MSNUC-IOB systemd[1]: Starting Advanced key-value store... Okt 01 08:44:47 MSNUC-IOB systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Okt 01 08:44:47 MSNUC-IOB systemd[1]: Started Advanced key-value store. root@MSNUC-IOB:/opt/iobroker#Proxmox 3 Node HA-Cluster TRIGKEY Mini-PC N100 mit 32 GB RAM und 3x1TB shared SSDs. VM- iobroker ,Raspberrymatic. LXC - Adguard, , Traccar, iSpy, Fileserver (emby, MiniDLNA)...usw
-
@arteck said in [Aufruf] js-controller 2.0 Beta Test:
@msauer machmal
service redis-server statusroot@MSNUC-IOB:/opt/iobroker# service redis-server status ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-10-01 08:44:47 CEST; 3h 31min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 408 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 462 (redis-server) Tasks: 4 (limit: 4701) Memory: 232.3M CGroup: /system.slice/redis-server.service └─462 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 08:44:46 MSNUC-IOB systemd[1]: Starting Advanced key-value store... Okt 01 08:44:47 MSNUC-IOB systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Okt 01 08:44:47 MSNUC-IOB systemd[1]: Started Advanced key-value store. root@MSNUC-IOB:/opt/iobroker# -
Habe heute Zeit gefunden den neuen js-controller zu installieren, funktioniert auch soweit alles ohne Fehler.
Jetzt wollte ich noch auf redis/redis umstellen, dass will aber irgendwie nicht, bräuchte da mal Hilfe.
Hier der Konsole Mitschnitt:root@debian:/opt/iobroker# iobroker setup custom Current configuration: - Objects database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9001 - States database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9000 - Data Directory: ../../iobroker-data/ Type of objects DB [(f)ile, (r)edis], default [file]: r When Objects and Files are stored in a Redis database please consider the following: 1. All data will be stored in RAM, make sure to have enough free RAM available! 2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss! 3. The Redis persistence files can get big, make sure not to use an SD card to store them. Host / Unix Socket of objects DB(redis), default[127.0.0.1]: Port of objects DB(redis), default[6379]: Type of states DB [(f)file, (r)edis], default [redis]: r Host / Unix Socket of states DB (redis), default[127.0.0.1]: Port of states DB (redis), default[6379]: Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: n Important: Using Redis for the Objects database is only supported with js-controller 2.0 or higher! When your system consists of multiple hosts please make sure to have js-controller 2.0 or higher installed on ALL hosts *before* continuing! Important #2: If you already did the migration on an other host please *do not* migrate again! This can destroy your system! Important #3: The process will migrate all files that were officially uploaded into the ioBroker system. If you have manually copied files into iobroker-data/files/... into own directories then these files will NOT be migrated! Make sure all files are in adapter directories inside the files directory! Do you want to migrate objects and states from "file/file" to "redis/redis" [y/N]: y Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y Connecting to previous DB "file"... Creating backup ... This can take some time ... please be patient! host.debian 38585 states saved host.debian 44464 objects saved Backup created: /opt/iobroker/backups/2019_10_01-11_46_17_backupiobroker-migration.tar.gz Connecting to new DB "redis" ... /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:28 if (!options.states) throw 'Invalid arguments: states is missing'; ^ Invalid arguments: states is missing root@debian:/opt/iobroker#@coyote du weisst aber schon dass du dafür einen RedisServer brauchst.. ??
zigbee hab ich, zwave auch, nuc's genauso und HA auch
-
Habe heute Zeit gefunden den neuen js-controller zu installieren, funktioniert auch soweit alles ohne Fehler.
Jetzt wollte ich noch auf redis/redis umstellen, dass will aber irgendwie nicht, bräuchte da mal Hilfe.
Hier der Konsole Mitschnitt:root@debian:/opt/iobroker# iobroker setup custom Current configuration: - Objects database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9001 - States database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9000 - Data Directory: ../../iobroker-data/ Type of objects DB [(f)ile, (r)edis], default [file]: r When Objects and Files are stored in a Redis database please consider the following: 1. All data will be stored in RAM, make sure to have enough free RAM available! 2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss! 3. The Redis persistence files can get big, make sure not to use an SD card to store them. Host / Unix Socket of objects DB(redis), default[127.0.0.1]: Port of objects DB(redis), default[6379]: Type of states DB [(f)file, (r)edis], default [redis]: r Host / Unix Socket of states DB (redis), default[127.0.0.1]: Port of states DB (redis), default[6379]: Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: n Important: Using Redis for the Objects database is only supported with js-controller 2.0 or higher! When your system consists of multiple hosts please make sure to have js-controller 2.0 or higher installed on ALL hosts *before* continuing! Important #2: If you already did the migration on an other host please *do not* migrate again! This can destroy your system! Important #3: The process will migrate all files that were officially uploaded into the ioBroker system. If you have manually copied files into iobroker-data/files/... into own directories then these files will NOT be migrated! Make sure all files are in adapter directories inside the files directory! Do you want to migrate objects and states from "file/file" to "redis/redis" [y/N]: y Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y Connecting to previous DB "file"... Creating backup ... This can take some time ... please be patient! host.debian 38585 states saved host.debian 44464 objects saved Backup created: /opt/iobroker/backups/2019_10_01-11_46_17_backupiobroker-migration.tar.gz Connecting to new DB "redis" ... /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:28 if (!options.states) throw 'Invalid arguments: states is missing'; ^ Invalid arguments: states is missing root@debian:/opt/iobroker# -
@arteck Ich hab im Code kaputt gemacht mit letzter Version :-(
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
@apollon77 waaaaaaaaaaatttttttttt...
-
@arteck na klar, der läuft auch.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Oct 1 12:02:55 2019 from 192.168.66.55 root@debian:~# systemctl status redis-server ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor pre Active: active (running) since Tue 2019-10-01 12:02:46 CEST; 42min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 327 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exite Main PID: 380 (redis-server) Tasks: 4 (limit: 3482) Memory: 10.4M CGroup: /system.slice/redis-server.service └─380 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 12:02:45 debian systemd[1]: Starting Advanced key-value store... Okt 01 12:02:46 debian systemd[1]: redis-server.service: Can't open PID file /ru Okt 01 12:02:46 debian systemd[1]: Started Advanced key-value store.@apollon77 ah ok, dann bin ich ja beruhigt, dachte ich mache was falsch :smirk:
-
@arteck na klar, der läuft auch.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Oct 1 12:02:55 2019 from 192.168.66.55 root@debian:~# systemctl status redis-server ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor pre Active: active (running) since Tue 2019-10-01 12:02:46 CEST; 42min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 327 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exite Main PID: 380 (redis-server) Tasks: 4 (limit: 3482) Memory: 10.4M CGroup: /system.slice/redis-server.service └─380 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 12:02:45 debian systemd[1]: Starting Advanced key-value store... Okt 01 12:02:46 debian systemd[1]: redis-server.service: Can't open PID file /ru Okt 01 12:02:46 debian systemd[1]: Started Advanced key-value store.@apollon77 ah ok, dann bin ich ja beruhigt, dachte ich mache was falsch :smirk:
-
Starte ich nur den iobroker-master durch, schafft es der iobroker-hwr auch nicht mehr sich zu verbinden und alle io* Prozesse auf dem -hwr beenden sich.
-
iobroker status geht ja jetzt, es kommt aber noch ein Fehler:
root@MSNUC-IOB:~# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed. root@MSNUC-IOB:~#UPDATE: Wenn ich ins /opt/iobroker wechsel, dann kommt die Fehlermeldung nicht
root@MSNUC-IOB:~# cd /opt/iobroker/ root@MSNUC-IOB:/opt/iobroker# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis root@MSNUC-IOB:/opt/iobroker# -
@apollon77 Sorry, viel Text heute Morgen - hier noch die Aktualisierung auf 2.0.16:
Alle Prozesse gestoppt, beide aktualisiert:
┬─[root@iobroker-master:/opt/iobroker]─[06:31:25] ╰─># sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller > iobroker.js-controller@2.0.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.4.1 > iobroker.js-controller@2.0.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first 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 WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/iobroker.pushbullet/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.0 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) + iobroker.js-controller@2.0.16 added 1 package from 3 contributors, removed 1 package, updated 8 packages and audited 40363 packages in 147.811s found 87 vulnerabilities (32 low, 10 moderate, 45 high) run `npm audit fix` to fix them, or `npm audit` for details┬─[darkiop@iobroker-hwr:/opt/iobroker]─[06:31:49] ╰─>$ sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller [sudo] Passwort für darkiop: > iobroker.js-controller@2.0.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.9.0 > iobroker.js-controller@2.0.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.0 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) 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":"arm"}) + iobroker.js-controller@2.0.16 removed 1 package, updated 8 packages and audited 1867 packages in 62.052s found 12 vulnerabilities (9 low, 3 high) run `npm audit fix` to fix them, or `npm audit` for detailsDann
- iobroker-master Container neu gestartet
- iobroker-hwr reboot
Nach reboot auf iobroker-hwr:
┬─[darkiop@iobroker-hwr:~]─[06:40:21] ╰─>$ iobroker status iobroker is not running on this host. At least one iobroker host is running. Objects type: file States type: file ┬─[darkiop@iobroker-hwr:~]─[06:40:26] ╰─>$ ps -ef | grep ^io ┬─[darkiop@iobroker-hwr:~]─[06:40:31] ╰─>$ tail -n 50 /opt/iobroker/log/iobroker.2019-10-01.log 2019-10-01 02:33:27.294 - warn: host.iobroker-hwr Slave controller detected disconnection. Stop all instances. 2019-10-01 02:33:27.301 - info: host.iobroker-hwr stopInstance system.adapter.smartmeter.0 2019-10-01 02:33:27.302 - error: host.iobroker-hwr result is not defined 2019-10-01 02:33:29.315 - warn: host.iobroker-hwr Cannot get view: ReplyError: Error Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f 2019-10-01 02:33:29.319 - info: host.iobroker-hwr instance system.adapter.smartmeter.1 terminated with code 0 (NO_ERROR) 2019-10-01 02:33:29.320 - info: host.iobroker-hwr Do not restart adapter system.adapter.smartmeter.1 because disabled or deleted 2019-10-01 02:33:29.360 - warn: host.iobroker-hwr Cannot get view: ReplyError: Error Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f 2019-10-01 02:33:29.361 - info: host.iobroker-hwr instance system.adapter.smartmeter.0 terminated with code 0 (NO_ERROR) 2019-10-01 02:33:29.362 - info: host.iobroker-hwr Do not restart adapter system.adapter.smartmeter.0 because disabled or deleted 2019-10-01 02:33:42.303 - info: host.iobroker-hwr iobroker _restart 2019-10-01 02:33:42.816 - info: host.iobroker-hwr iobroker Starting node restart.js 2019-10-01 06:37:53.718 - info: host.iobroker-hwr iobroker.js-controller version 2.0.16 js-controller starting 2019-10-01 06:37:53.726 - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker 2019-10-01 06:37:53.726 - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3 2019-10-01 06:37:53.728 - info: host.iobroker-hwr ip addresses: 2019-10-01 06:37:53.749 - error: host.iobroker-hwr uncaught exception: connect ENETUNREACH 192.168.1.82:9001 - Local (0.0.0.0:0) 2019-10-01 06:37:53.750 - error: host.iobroker-hwr Error: connect ENETUNREACH 192.168.1.82:9001 - Local (0.0.0.0:0) at internalConnect (net.js:881:16) at defaultTriggerAsyncIdScope (internal/async_hooks.js:294:19) at defaultTriggerAsyncIdScope (net.js:971:9) at process._tickCallback (internal/process/next_tick.js:61:11) 2019-10-01 06:37:53.752 - info: host.iobroker-hwr terminated. Could not reset alive status for instances 2019-10-01 06:37:53.756 - info: host.iobroker-hwr iobroker _restart ┬─[darkiop@iobroker-hwr:~]─[06:41:17] ╰─>$ iobroker start Starting iobroker controller daemon... iobroker controller daemon started. PID: 1448Dann startet der iobroker-hwr sauber:
2019-10-01 06:42:00.051 - info: host.iobroker-hwr iobroker.js-controller version 2.0.16 js-controller starting 2019-10-01 06:42:00.059 - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker 2019-10-01 06:42:00.059 - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3 2019-10-01 06:42:00.061 - info: host.iobroker-hwr ip addresses: 10.3.1.22 fe80::dea6:32ff:fe17:78f5 2019-10-01 06:42:00.585 - info: host.iobroker-hwr connected to Objects and States 2019-10-01 06:42:00.628 - warn: host.iobroker-hwr Multihost discovery server: service started on 0.0.0.0:50005 2019-10-01 06:42:01.523 - info: host.iobroker-hwr Delete state "system.host.iobroker-hwr.compactModeEnabled" 2019-10-01 06:42:01.755 - info: host.iobroker-hwr 85 instances found 2019-10-01 06:42:01.773 - info: host.iobroker-hwr starting 2 instances 2019-10-01 06:42:01.793 - info: host.iobroker-hwr instance system.adapter.smartmeter.0 started with pid 1474 2019-10-01 06:42:02.063 - info: host.iobroker-hwr Some obsolete host states deleted. 2019-10-01 06:42:05.790 - info: host.iobroker-hwr instance system.adapter.smartmeter.1 started with pid 1489 -
Außer dem Node-RED Dashboard habe ich dann noch zwei Adapter die wohl ein Upgrade brauchen:
host.Ubuntu 2019-10-01 08:58:03.795 error instance system.adapter.daswetter.0 terminated with code 15 (15) daswetter.0 2019-10-01 08:58:03.774 error (32174) force terminate, objects still in list: 1571läuft unter 1.15.14 problemlos, und
broadlink2.0 2019-10-01 09:12:24.100 warn (865) sendState could not find command or scene named 'LG_TV-Power'als Beispiel. Den state gibt es definitiv und läuft ebenfalls unter 1.15.14 klaglos.
LG SBorg ( SBorg auf GitHub)
Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation -
@SBorg den Fehler von daswetter hatte ich aber auch vor dem Update schon
@apollon77 @arteck ist es normal, dass mir das angezeigt wird bei der Umstellung auf redis/redis?
Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: nIch hab kein Master/Slave System
-
@SBorg den Fehler von daswetter hatte ich aber auch vor dem Update schon
@apollon77 @arteck ist es normal, dass mir das angezeigt wird bei der Umstellung auf redis/redis?
Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: nIch hab kein Master/Slave System
@coyote sagte in [Aufruf] js-controller 2.0 Beta Test:
@SBorg den Fehler von daswetter hatte ich aber auch vor dem Update schon
Bei mir nicht. Bis heute morgen mit dem JS 1.15.14 lief es auch und die Daten waren korrekt, jetzt mit dem 2er steigt er mit dem error aus und liefert auch keine Daten mehr. Liegt aber am Adapter, nicht am Controller.
LG SBorg ( SBorg auf GitHub)
Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation -
@coyote sagte in [Aufruf] js-controller 2.0 Beta Test:
@SBorg den Fehler von daswetter hatte ich aber auch vor dem Update schon
Bei mir nicht. Bis heute morgen mit dem JS 1.15.14 lief es auch und die Daten waren korrekt, jetzt mit dem 2er steigt er mit dem error aus und liefert auch keine Daten mehr. Liegt aber am Adapter, nicht am Controller.
@SBorg Hm ok, komisch. Bei mir war es vorher schon, hier ein Auszug vom Log von gestern, da war ich noch bei 1.5.14
2019-09-30 10:31:07.279 - [31merror[39m: daswetter.0 force terminate, objects still in list: 1887 2019-09-30 10:31:07.441 - [32minfo[39m: host.debian instance system.adapter.daswetter.0 terminated with code 11 (Desired termination) -
Nicht ganz, du hast eine "desired termination" mit Code 11 (also eine 'erwünschte', die ist normal), ich habe eine "echte" Terminierung mit Code 15 (=harter Abbruch wegen Fehler).
LG SBorg ( SBorg auf GitHub)
Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation -
Außer dem Node-RED Dashboard habe ich dann noch zwei Adapter die wohl ein Upgrade brauchen:
host.Ubuntu 2019-10-01 08:58:03.795 error instance system.adapter.daswetter.0 terminated with code 15 (15) daswetter.0 2019-10-01 08:58:03.774 error (32174) force terminate, objects still in list: 1571läuft unter 1.15.14 problemlos, und
broadlink2.0 2019-10-01 09:12:24.100 warn (865) sendState could not find command or scene named 'LG_TV-Power'als Beispiel. Den state gibt es definitiv und läuft ebenfalls unter 1.15.14 klaglos.
@SBorg sagte in [Aufruf] js-controller 2.0 Beta Test:
broadlink2.0 2019-10-01 09:12:24.100 warn (865) sendState could not find command or scene named 'LG_TV-Power'
Naja ich fürchte das gleiche Problem könnte es sein wie bei radar2, das die myadapter-Klasse falsch ist. Kannst Du mal testen bitte:
File /opt/iobroker/node_modules/@frankjoke/myadapter/myadapter.js und dort die Änderungen aus https://github.com/frankjoke/myAdapter/pull/1/files einbauen (oder ganzes file mit https://github.com/frankjoke/myAdapter/blob/f06343bfe6e132536f6740a7f025b2122ecef6b6/myAdapter.js ersetzen)Ist der Fehler dann weg? Wenn ja bitte Issue bei broadlink2 anlegen und reinschreiben und mir schicken, dann müssen wir ggf wie bei radar2 ein Zwischenrelease bauen.
Zu Daswetter weiss ich nix ... kommt das immer? Bzw war es schon vorher da. Kannst ja mal durch die alten Logfiles der 7 Tage in /opt/iobroker/logs suchen ...
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
Support us
829
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge