NEWS
Alpha Test js-controller 5.0
Tester
140
Beiträge
25
Kommentatoren
23.8k
Aufrufe
31
Watching
-
@ilovegym Ok, dann haben wir vllt doch eine "lange zeit deprecation" jetzt härter ... Danke!
Backitup-Adapter V2.6.16 zickt hier seltsam und steigt aus, weil er die Objects nicht sichern kann..?? hmm? das geht so mit anscheinend allem, was in vis, userdata etc gelagert ist.. ?
Datenbank ist redis/redis auf einer externen VM..
Ansonsten laeft alles unauffaellig... -
Backitup-Adapter V2.6.16 zickt hier seltsam und steigt aus, weil er die Objects nicht sichern kann..?? hmm? das geht so mit anscheinend allem, was in vis, userdata etc gelagert ist.. ?
Datenbank ist redis/redis auf einer externen VM..
Ansonsten laeft alles unauffaellig... -
@ilovegym Führe mal bitte das Backup über die CLI aus und poste mal die Ausgabe
iob backup -
-
@ilovegym Mach da mal bitte ein Issue beim js-controller auf. Der Befehl "iob backup" wird direkt vom js-controller bearbeitet. Backitup bedient sich nur der Backup Funktionen des js-controllers
-
@apollon77 sagte in Alpha Test js-controller 5.0:
@ilovegym Und Danke, ist in der nächsten Alpha gefixt
Ist die bereits verfügbar?
-
@apollon77 sagte in Alpha Test js-controller 5.0:
@ilovegym Und Danke, ist in der nächsten Alpha gefixt
Ist die bereits verfügbar?
-
Bei mir ging der Umstieg auf die v5 auch recht reibungslo über die Bühne.
Ich habe das bekannte Problem mit dem iQontrol-Adapter und ich musste einen Upload im VIS-Adapter manuell anwerfen, danach waren meine Visualisierungen auch wieder erreichbar -
hab soeben auch mal v5 aktiv, soweit läuft alles fürs erste, allerdings sind sehr viele meiner installierten Instanzen aktuell nicht aktiv/nicht in gebrauch.
admin.0 (945379) starting. Version 6.4.3 in /opt/iobroker/node_modules/iobroker.admin, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569was nun zu Beginn auffiel und nur bedingt etwas mit dem controller zu tun hat, sind
- im mqtt Adapter war wie in der Instanz beschrieben, bis dato eingetragen
These states will be published. (Divided by comma, e.g. 'mqtt.0.,javascript.')
dies wurde nun aber angemeckert
2023-04-09 10:46:53.490 - warn: host.IoBroker-Server States 127.0.0.1:51508 Error from InMemDB: Error: The pattern "'mqtt.0.*" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2388:15) at StatesInMemoryServer.handleSubscribe (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (/opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:258:14) at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:394:26) at RedisHandler.emit (node:events:513:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:209:37) at processImmediate (node:internal/timers:476:21) 2023-04-09 10:46:53.607 - error: mqtt.0 (946388) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:46:53.611 - error: mqtt.0 (946388) unhandled promise rejection: Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:53.619 - error: mqtt.0 (946388) ReplyError: Error The pattern "'mqtt.0.*" is not a valid ID pattern 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) 2023-04-09 10:46:53.620 - error: mqtt.0 (946388) Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:54.199 - warn: mqtt.0 (946388) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-09 10:46:55.271 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-04-09 10:46:55.272 - error: host.IoBroker Caught by controller[0]: ReplyError: Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:55.273 - error: host.IoBroker Caught by controller[0]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) 2023-04-09 10:46:55.274 - error: host.IoBroker Caught by controller[0]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) 2023-04-09 10:46:55.274 - error: host.IoBroker instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-04-09 10:46:55.275 - info: host.IoBroker Restart adapter system.adapter.mqtt.0 because enabled2023-04-09 11:00:17.823 - error: mqtt.0 (955755) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 11:00:17.827 - error: mqtt.0 (955755) unhandled promise rejection: Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:17.831 - error: mqtt.0 (955755) ReplyError: Error The pattern "javascript.*'" is not a valid ID pattern 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) 2023-04-09 11:00:17.833 - error: mqtt.0 (955755) Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:18.381 - warn: mqtt.0 (955755) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-09 11:00:19.111 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-04-09 11:00:19.112 - error: host.IoBroker Caught by controller[0]: ReplyError: Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:19.112 - error: host.IoBroker Caught by controller[0]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) 2023-04-09 11:00:19.113 - error: host.IoBroker Caught by controller[0]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) 2023-04-09 11:00:19.113 - error: host.IoBroker instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-04-09 11:00:19.114 - info: host.IoBroker Restart adapter system.adapter.mqtt.0 because enabledhab es nun auf mqtt.* geändert
- der Adapter Linux-control meckert nun über einen Service
2023-04-09 10:48:42.818 - warn: host.IoBroker-Server States 127.0.0.1:42674 Error from InMemDB: Error: The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-24e36031\x2d735b\x2d4199\x2da17d\x2d58b14117589e.start" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2388:15) at StatesInMemoryServer.handleSubscribe (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (/opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:258:14) at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:394:26) at RedisHandler.emit (node:events:513:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:209:37) at processImmediate (node:internal/timers:476:21) 2023-04-09 10:48:42.825 - info: trashschedule.0 (947981) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569 2023-04-09 10:48:42.836 - error: linux-control.0 (947081) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:48:42.843 - error: linux-control.0 (947081) unhandled promise rejection: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 2023-04-09 10:48:42.855 - error: linux-control.0 (947081) ReplyError: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 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) 2023-04-09 10:48:42.856 - error: linux-control.0 (947081) Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 2023-04-09 10:48:42.915 - error: linux-control.0 (947081) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:48:42.917 - error: linux-control.0 (947081) unhandled promise rejection: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.start" is not a valid ID pattern 2023-04-09 10:48:42.922 - error: linux-control.0 (947081) ReplyError: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.start" is not a valid ID pattern 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)hab den vorübergehend nun mal deaktiviert in der Instanz
und was noch auftrat, direkt nach dem iob start mit v5 war nun bei mir ebenfalls die Log-Größe am rödeln, hat irgendwann aufgehört hochzuzählen und sich dann wieder normalisiert
umgestiegen von Proxmox auf Unraid
- im mqtt Adapter war wie in der Instanz beschrieben, bis dato eingetragen
-
hab soeben auch mal v5 aktiv, soweit läuft alles fürs erste, allerdings sind sehr viele meiner installierten Instanzen aktuell nicht aktiv/nicht in gebrauch.
admin.0 (945379) starting. Version 6.4.3 in /opt/iobroker/node_modules/iobroker.admin, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569was nun zu Beginn auffiel und nur bedingt etwas mit dem controller zu tun hat, sind
- im mqtt Adapter war wie in der Instanz beschrieben, bis dato eingetragen
These states will be published. (Divided by comma, e.g. 'mqtt.0.,javascript.')
dies wurde nun aber angemeckert
2023-04-09 10:46:53.490 - warn: host.IoBroker-Server States 127.0.0.1:51508 Error from InMemDB: Error: The pattern "'mqtt.0.*" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2388:15) at StatesInMemoryServer.handleSubscribe (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (/opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:258:14) at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:394:26) at RedisHandler.emit (node:events:513:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:209:37) at processImmediate (node:internal/timers:476:21) 2023-04-09 10:46:53.607 - error: mqtt.0 (946388) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:46:53.611 - error: mqtt.0 (946388) unhandled promise rejection: Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:53.619 - error: mqtt.0 (946388) ReplyError: Error The pattern "'mqtt.0.*" is not a valid ID pattern 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) 2023-04-09 10:46:53.620 - error: mqtt.0 (946388) Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:54.199 - warn: mqtt.0 (946388) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-09 10:46:55.271 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-04-09 10:46:55.272 - error: host.IoBroker Caught by controller[0]: ReplyError: Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:55.273 - error: host.IoBroker Caught by controller[0]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) 2023-04-09 10:46:55.274 - error: host.IoBroker Caught by controller[0]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) 2023-04-09 10:46:55.274 - error: host.IoBroker instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-04-09 10:46:55.275 - info: host.IoBroker Restart adapter system.adapter.mqtt.0 because enabled2023-04-09 11:00:17.823 - error: mqtt.0 (955755) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 11:00:17.827 - error: mqtt.0 (955755) unhandled promise rejection: Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:17.831 - error: mqtt.0 (955755) ReplyError: Error The pattern "javascript.*'" is not a valid ID pattern 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) 2023-04-09 11:00:17.833 - error: mqtt.0 (955755) Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:18.381 - warn: mqtt.0 (955755) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-09 11:00:19.111 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-04-09 11:00:19.112 - error: host.IoBroker Caught by controller[0]: ReplyError: Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:19.112 - error: host.IoBroker Caught by controller[0]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) 2023-04-09 11:00:19.113 - error: host.IoBroker Caught by controller[0]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) 2023-04-09 11:00:19.113 - error: host.IoBroker instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-04-09 11:00:19.114 - info: host.IoBroker Restart adapter system.adapter.mqtt.0 because enabledhab es nun auf mqtt.* geändert
- der Adapter Linux-control meckert nun über einen Service
2023-04-09 10:48:42.818 - warn: host.IoBroker-Server States 127.0.0.1:42674 Error from InMemDB: Error: The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-24e36031\x2d735b\x2d4199\x2da17d\x2d58b14117589e.start" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2388:15) at StatesInMemoryServer.handleSubscribe (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (/opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:258:14) at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:394:26) at RedisHandler.emit (node:events:513:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:209:37) at processImmediate (node:internal/timers:476:21) 2023-04-09 10:48:42.825 - info: trashschedule.0 (947981) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569 2023-04-09 10:48:42.836 - error: linux-control.0 (947081) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:48:42.843 - error: linux-control.0 (947081) unhandled promise rejection: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 2023-04-09 10:48:42.855 - error: linux-control.0 (947081) ReplyError: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 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) 2023-04-09 10:48:42.856 - error: linux-control.0 (947081) Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 2023-04-09 10:48:42.915 - error: linux-control.0 (947081) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:48:42.917 - error: linux-control.0 (947081) unhandled promise rejection: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.start" is not a valid ID pattern 2023-04-09 10:48:42.922 - error: linux-control.0 (947081) ReplyError: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.start" is not a valid ID pattern 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)hab den vorübergehend nun mal deaktiviert in der Instanz
und was noch auftrat, direkt nach dem iob start mit v5 war nun bei mir ebenfalls die Log-Größe am rödeln, hat irgendwann aufgehört hochzuzählen und sich dann wieder normalisiert
@crunchip sagte in Alpha Test js-controller 5.0:
und was noch auftrat, direkt nach dem iob start mit v5 war nun bei mir ebenfalls die Log-Größe am rödeln, hat irgendwann aufgehört hochzuzählen und sich dann wieder normalisiert
Das Problem mit der falsch angezeigten Log Größe wurde beim Admin gemeldet https://github.com/ioBroker/ioBroker.admin/issues/1913
- im mqtt Adapter war wie in der Instanz beschrieben, bis dato eingetragen
-
hab soeben auch mal v5 aktiv, soweit läuft alles fürs erste, allerdings sind sehr viele meiner installierten Instanzen aktuell nicht aktiv/nicht in gebrauch.
admin.0 (945379) starting. Version 6.4.3 in /opt/iobroker/node_modules/iobroker.admin, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569was nun zu Beginn auffiel und nur bedingt etwas mit dem controller zu tun hat, sind
- im mqtt Adapter war wie in der Instanz beschrieben, bis dato eingetragen
These states will be published. (Divided by comma, e.g. 'mqtt.0.,javascript.')
dies wurde nun aber angemeckert
2023-04-09 10:46:53.490 - warn: host.IoBroker-Server States 127.0.0.1:51508 Error from InMemDB: Error: The pattern "'mqtt.0.*" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2388:15) at StatesInMemoryServer.handleSubscribe (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (/opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:258:14) at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:394:26) at RedisHandler.emit (node:events:513:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:209:37) at processImmediate (node:internal/timers:476:21) 2023-04-09 10:46:53.607 - error: mqtt.0 (946388) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:46:53.611 - error: mqtt.0 (946388) unhandled promise rejection: Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:53.619 - error: mqtt.0 (946388) ReplyError: Error The pattern "'mqtt.0.*" is not a valid ID pattern 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) 2023-04-09 10:46:53.620 - error: mqtt.0 (946388) Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:54.199 - warn: mqtt.0 (946388) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-09 10:46:55.271 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-04-09 10:46:55.272 - error: host.IoBroker Caught by controller[0]: ReplyError: Error The pattern "'mqtt.0.*" is not a valid ID pattern 2023-04-09 10:46:55.273 - error: host.IoBroker Caught by controller[0]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) 2023-04-09 10:46:55.274 - error: host.IoBroker Caught by controller[0]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) 2023-04-09 10:46:55.274 - error: host.IoBroker instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-04-09 10:46:55.275 - info: host.IoBroker Restart adapter system.adapter.mqtt.0 because enabled2023-04-09 11:00:17.823 - error: mqtt.0 (955755) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 11:00:17.827 - error: mqtt.0 (955755) unhandled promise rejection: Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:17.831 - error: mqtt.0 (955755) ReplyError: Error The pattern "javascript.*'" is not a valid ID pattern 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) 2023-04-09 11:00:17.833 - error: mqtt.0 (955755) Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:18.381 - warn: mqtt.0 (955755) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-09 11:00:19.111 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2023-04-09 11:00:19.112 - error: host.IoBroker Caught by controller[0]: ReplyError: Error The pattern "javascript.*'" is not a valid ID pattern 2023-04-09 11:00:19.112 - error: host.IoBroker Caught by controller[0]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) 2023-04-09 11:00:19.113 - error: host.IoBroker Caught by controller[0]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) 2023-04-09 11:00:19.113 - error: host.IoBroker instance system.adapter.mqtt.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-04-09 11:00:19.114 - info: host.IoBroker Restart adapter system.adapter.mqtt.0 because enabledhab es nun auf mqtt.* geändert
- der Adapter Linux-control meckert nun über einen Service
2023-04-09 10:48:42.818 - warn: host.IoBroker-Server States 127.0.0.1:42674 Error from InMemDB: Error: The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-24e36031\x2d735b\x2d4199\x2da17d\x2d58b14117589e.start" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2388:15) at StatesInMemoryServer.handleSubscribe (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (/opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:258:14) at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:394:26) at RedisHandler.emit (node:events:513:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:209:37) at processImmediate (node:internal/timers:476:21) 2023-04-09 10:48:42.825 - info: trashschedule.0 (947981) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569 2023-04-09 10:48:42.836 - error: linux-control.0 (947081) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:48:42.843 - error: linux-control.0 (947081) unhandled promise rejection: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 2023-04-09 10:48:42.855 - error: linux-control.0 (947081) ReplyError: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 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) 2023-04-09 10:48:42.856 - error: linux-control.0 (947081) Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.restart" is not a valid ID pattern 2023-04-09 10:48:42.915 - error: linux-control.0 (947081) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-09 10:48:42.917 - error: linux-control.0 (947081) unhandled promise rejection: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.start" is not a valid ID pattern 2023-04-09 10:48:42.922 - error: linux-control.0 (947081) ReplyError: Error The pattern "linux-control.0.proxmox531.services.systemd-fsck@dev-disk-by\x2duuid-0a2debdb\x2df60b\x2d494d\x2d8190\x2d5f1f98fbfef9.start" is not a valid ID pattern 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)hab den vorübergehend nun mal deaktiviert in der Instanz
und was noch auftrat, direkt nach dem iob start mit v5 war nun bei mir ebenfalls die Log-Größe am rödeln, hat irgendwann aufgehört hochzuzählen und sich dann wieder normalisiert
- im mqtt Adapter war wie in der Instanz beschrieben, bis dato eingetragen
-
Alpha Update
5.0.1-alpha.0-20230406-4552d569
- Fixes compact mode
- Hide warning about "www folder not found" for widgets adapters
Wenn alles so stabil bleibt würde wir überlegen Mitte nächste Woche in den Beta Test im Latest Repo zu gehen ...
@apollon77 sagte in Alpha Test js-controller 5.0:
Alpha Update
5.0.1-alpha.0-20230406-4552d569Update auf meinem Master Slave System lief wieder ohne Probleme. Bisher keine Auffälligkeiten.
-
@crunchip sagte in Alpha Test js-controller 5.0:
und was noch auftrat, direkt nach dem iob start mit v5 war nun bei mir ebenfalls die Log-Größe am rödeln, hat irgendwann aufgehört hochzuzählen und sich dann wieder normalisiert
Das Problem mit der falsch angezeigten Log Größe wurde beim Admin gemeldet https://github.com/ioBroker/ioBroker.admin/issues/1913
@feuersturm ich hatte das Problem vorher aber noch gar nicht, erst nach dem Controller upgrade trat es auf, aber ich häng es dort mal mit an
umgestiegen von Proxmox auf Unraid
-
@feuersturm ich hatte das Problem vorher aber noch gar nicht, erst nach dem Controller upgrade trat es auf, aber ich häng es dort mal mit an
-
@crunchip ja neuer Controller validiert die patterns
Hallo,
Besteht mit der Version 5.0 eigentlich die Hoffnung, dass diese "Alias Error Bursts", die mich alle 2-3 Tage heimsuchen, aufhören.
Das Error Log zeigt nur einen kleinen Ausschnitt. Es sind alle meine ca. 400 Aliases betroffen.
Auswirkung auf die Funktion scheinen diese Fehlermeldung nicht zu haben. Sie nerven nur.2023-04-10 03:48:35.417 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.KEQ0971413.2.ENERGY_COUNTER, sourceObj={"type":"state","common":{"def":0,"type":"number","read":true,"write":false,"min":0,"max":838860.7,"unit":"Wh","name":"K1_Waschen_Messen.ENERGY_COUNTER","role":"value.power.consumption"},"native":{"CONTROL":"POWERMETER.ENERGY_COUNTER","DEFAULT":0,"FLAGS":1,"ID":"ENERGY_COUNTER","MAX":838860.7,"MIN":0,"OPERATIONS":5,"TAB_ORDER":0,"TYPE":"FLOAT","UNIT":"Wh"},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089040406,"_id":"hm-rpc.0.KEQ0971413.2.ENERGY_COUNTER","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.424 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.OEQ0125847.0.UNREACH, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":true,"write":false,"role":"indicator.unreach","name":"Deckenlampe im Wohnzimmer:0.UNREACH"},"native":{"DEFAULT":false,"FLAGS":9,"ID":"UNREACH","MAX":true,"MIN":false,"OPERATIONS":5,"TAB_ORDER":0,"TYPE":"BOOL","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089035775,"_id":"hm-rpc.0.OEQ0125847.0.UNREACH","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.OEQ0125847.2.STATE, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":true,"write":true,"role":"switch","name":"WZ_Deckenlampe.STATE"},"native":{"CONTROL":"SWITCH.STATE","DEFAULT":false,"FLAGS":1,"ID":"STATE","MAX":true,"MIN":false,"OPERATIONS":7,"TAB_ORDER":0,"TYPE":"BOOL","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089035853,"_id":"hm-rpc.0.OEQ0125847.2.STATE","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.OEQ0125847.0.UNREACH, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":true,"write":false,"role":"indicator.unreach","name":"Deckenlampe im Wohnzimmer:0.UNREACH"},"native":{"DEFAULT":false,"FLAGS":9,"ID":"UNREACH","MAX":true,"MIN":false,"OPERATIONS":5,"TAB_ORDER":0,"TYPE":"BOOL","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089035775,"_id":"hm-rpc.0.OEQ0125847.0.UNREACH","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.LEQ0413828.1.LEVEL, sourceObj={"type":"state","common":{"def":0,"type":"number","read":true,"write":true,"min":0,"max":100,"unit":"%","role":"level.blind","workingID":"WORKING","name":"K3_Fensteroeffner.LEVEL"},"native":{"CONTROL":"BLIND.LEVEL","DEFAULT":0,"FLAGS":1,"ID":"LEVEL","MAX":1,"MIN":0,"OPERATIONS":7,"TAB_ORDER":0,"TYPE":"FLOAT","UNIT":"100%"},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089036364,"_id":"hm-rpc.0.LEQ0413828.1.LEVEL","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.LEQ0413828.1.STOP, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":false,"write":true,"role":"button.stop","name":"K3_Fensteroeffner.STOP"},"native":{"CONTROL":"BLIND.STOP","DEFAULT":false,"FLAGS":1,"ID":"STOP","MAX":true,"MIN":false,"OPERATIONS":2,"TAB_ORDER":1,"TYPE":"ACTION","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089036367,"_id":"hm-rpc.0.LEQ0413828.1.STOP","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}HW:NUC (16 GB Ram)
OS: Debian Bullseye, Promox V7, node v16.x npm 8.19.3 -
@marty56 reine Vermutung von mir, da ich dieses Problem auch hatte.
Es wurden immer unterschiedliche alias angemeckert, nicht immer die selben,
daher die Frage, wie hast du die alias angelegt, per alias manager oder mit dem device Adapter? Letzterer hat sowieso ein Problem in der Version 1.1.2
https://github.com/ioBroker/ioBroker.devices/issues/217zu Beginn hatte ich auch alias mit dem device adapter angelegt, aber dann zum alias manager gewechselt und somit auch alle bestehenden alias, die mit dem device adapter erstellt wurden, gelöscht und neu mit dem alias manager erstellt.
Seit dem ist Ruhe.Vllt hat es auch Einfluss, wenn alias mit unterschiedlichen Adapter Versionen angelegt wurden.
Kann Zufall sein oder ein möglicher Ansatz. -
@marty56 reine Vermutung von mir, da ich dieses Problem auch hatte.
Es wurden immer unterschiedliche alias angemeckert, nicht immer die selben,
daher die Frage, wie hast du die alias angelegt, per alias manager oder mit dem device Adapter? Letzterer hat sowieso ein Problem in der Version 1.1.2
https://github.com/ioBroker/ioBroker.devices/issues/217zu Beginn hatte ich auch alias mit dem device adapter angelegt, aber dann zum alias manager gewechselt und somit auch alle bestehenden alias, die mit dem device adapter erstellt wurden, gelöscht und neu mit dem alias manager erstellt.
Seit dem ist Ruhe.Vllt hat es auch Einfluss, wenn alias mit unterschiedlichen Adapter Versionen angelegt wurden.
Kann Zufall sein oder ein möglicher Ansatz. -
Hallo,
Besteht mit der Version 5.0 eigentlich die Hoffnung, dass diese "Alias Error Bursts", die mich alle 2-3 Tage heimsuchen, aufhören.
Das Error Log zeigt nur einen kleinen Ausschnitt. Es sind alle meine ca. 400 Aliases betroffen.
Auswirkung auf die Funktion scheinen diese Fehlermeldung nicht zu haben. Sie nerven nur.2023-04-10 03:48:35.417 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.KEQ0971413.2.ENERGY_COUNTER, sourceObj={"type":"state","common":{"def":0,"type":"number","read":true,"write":false,"min":0,"max":838860.7,"unit":"Wh","name":"K1_Waschen_Messen.ENERGY_COUNTER","role":"value.power.consumption"},"native":{"CONTROL":"POWERMETER.ENERGY_COUNTER","DEFAULT":0,"FLAGS":1,"ID":"ENERGY_COUNTER","MAX":838860.7,"MIN":0,"OPERATIONS":5,"TAB_ORDER":0,"TYPE":"FLOAT","UNIT":"Wh"},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089040406,"_id":"hm-rpc.0.KEQ0971413.2.ENERGY_COUNTER","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.424 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.OEQ0125847.0.UNREACH, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":true,"write":false,"role":"indicator.unreach","name":"Deckenlampe im Wohnzimmer:0.UNREACH"},"native":{"DEFAULT":false,"FLAGS":9,"ID":"UNREACH","MAX":true,"MIN":false,"OPERATIONS":5,"TAB_ORDER":0,"TYPE":"BOOL","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089035775,"_id":"hm-rpc.0.OEQ0125847.0.UNREACH","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.OEQ0125847.2.STATE, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":true,"write":true,"role":"switch","name":"WZ_Deckenlampe.STATE"},"native":{"CONTROL":"SWITCH.STATE","DEFAULT":false,"FLAGS":1,"ID":"STATE","MAX":true,"MIN":false,"OPERATIONS":7,"TAB_ORDER":0,"TYPE":"BOOL","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089035853,"_id":"hm-rpc.0.OEQ0125847.2.STATE","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.OEQ0125847.0.UNREACH, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":true,"write":false,"role":"indicator.unreach","name":"Deckenlampe im Wohnzimmer:0.UNREACH"},"native":{"DEFAULT":false,"FLAGS":9,"ID":"UNREACH","MAX":true,"MIN":false,"OPERATIONS":5,"TAB_ORDER":0,"TYPE":"BOOL","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089035775,"_id":"hm-rpc.0.OEQ0125847.0.UNREACH","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.LEQ0413828.1.LEVEL, sourceObj={"type":"state","common":{"def":0,"type":"number","read":true,"write":true,"min":0,"max":100,"unit":"%","role":"level.blind","workingID":"WORKING","name":"K3_Fensteroeffner.LEVEL"},"native":{"CONTROL":"BLIND.LEVEL","DEFAULT":0,"FLAGS":1,"ID":"LEVEL","MAX":1,"MIN":0,"OPERATIONS":7,"TAB_ORDER":0,"TYPE":"FLOAT","UNIT":"100%"},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089036364,"_id":"hm-rpc.0.LEQ0413828.1.LEVEL","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} 2023-04-10 03:48:35.425 - error: web.0 (900) Alias subscription error. Please check your alias definitions: sourceId=hm-rpc.0.LEQ0413828.1.STOP, sourceObj={"type":"state","common":{"def":false,"type":"boolean","read":false,"write":true,"role":"button.stop","name":"K3_Fensteroeffner.STOP"},"native":{"CONTROL":"BLIND.STOP","DEFAULT":false,"FLAGS":1,"ID":"STOP","MAX":true,"MIN":false,"OPERATIONS":2,"TAB_ORDER":1,"TYPE":"ACTION","UNIT":""},"from":"system.adapter.hm-rega.0","user":"system.user.admin","ts":1671089036367,"_id":"hm-rpc.0.LEQ0413828.1.STOP","acl":{"object":1636,"state":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} -
Hi,
gerade den Master auf 5.0.1 angehoben:
Web adapter crasht wegen Trashschedule fehler. Ich vermute das "ü" als Übeltäter wobei ich auch ein "ä" verwende was nicht angemeckert wird:
2023-04-11 12:21:46.870 - error: web.0 (8220) uncaught exception: The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern 2023-04-11 12:21:46.873 - error: web.0 (8220) Error: The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2161:15) at pattern2RegEx (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:489:26) at commands.subscribe (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) at Socket.emit (node:events:513:28) at /opt/iobroker/node_modules/socket.io/lib/socket.js:531:14 at process.processTicksAndRejections (node:internal/process/task_queues:77:11) 2023-04-11 12:21:46.874 - error: web.0 (8220) The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID patternLinux Control läuft nicht mehr zum steuern meiner Wandtablets
mirko@iobroker:/opt/iobroker$ tail -f /opt/iobroker/log/iobroker.current.log |grep linux 2023-04-11 12:30:02.872 - info: host.iobroker instance system.adapter.linux-control.0 started with pid 8596 2023-04-11 12:30:07.502 - warn: linux-control.0 (8596) Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string" 2023-04-11 12:30:07.503 - warn: linux-control.0 (8596) This object will not be created in future versions. Please report this to the developer. 2023-04-11 12:30:07.544 - info: linux-control.0 (8596) starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.linux-control, node: v18.14.2, js-controller: 5.0.1-alpha.0-20230406-4552d569 2023-04-11 12:30:07.872 - warn: linux-control.0 (8596) Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string" 2023-04-11 12:30:07.893 - warn: linux-control.0 (8596) This object will not be created in future versions. Please report this to the developer. 2023-04-11 12:30:07.990 - info: linux-control.0 (8596) getting data from VIS-OG (192.168.178.215:22, Adapter start) 2023-04-11 12:30:08.000 - info: linux-control.0 (8596) getting data from VIS-EG (192.168.178.216:22, Adapter start) 2023-04-11 12:30:24.355 - warn: host.iobroker-Server States 127.0.0.1:33208 Error from InMemDB: Error: The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern 2023-04-11 12:30:24.359 - error: linux-control.0 (8596) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-11 12:30:24.360 - error: linux-control.0 (8596) unhandled promise rejection: Error The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern 2023-04-11 12:30:24.361 - error: linux-control.0 (8596) ReplyError: Error The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern 2023-04-11 12:30:24.361 - error: linux-control.0 (8596) Error The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern 2023-04-11 12:30:24.380 - info: linux-control.0 (8596) cleaned everything up... 2023-04-11 12:30:24.381 - info: linux-control.0 (8596) terminating 2023-04-11 12:30:24.381 - warn: linux-control.0 (8596) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-11 12:30:24.385 - error: linux-control.0 (8596) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-11 12:30:24.386 - error: linux-control.0 (8596) unhandled promise rejection: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern 2023-04-11 12:30:24.387 - error: linux-control.0 (8596) Error: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern 2023-04-11 12:30:24.387 - error: linux-control.0 (8596) The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern 2023-04-11 12:30:24.401 - warn: host.iobroker-Server States 127.0.0.1:33208 Error from InMemDB: Error: The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.404 - error: linux-control.0 (8596) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-11 12:30:24.404 - error: linux-control.0 (8596) unhandled promise rejection: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.405 - error: linux-control.0 (8596) ReplyError: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.405 - error: linux-control.0 (8596) Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.736 - error: linux-control.0 (8596) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-11 12:30:24.737 - error: linux-control.0 (8596) unhandled promise rejection: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern 2023-04-11 12:30:24.737 - error: linux-control.0 (8596) Error: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern 2023-04-11 12:30:24.737 - error: linux-control.0 (8596) The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern 2023-04-11 12:30:24.783 - warn: host.iobroker-Server States 127.0.0.1:33208 Error from InMemDB: Error: The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.792 - error: linux-control.0 (8596) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-11 12:30:24.792 - error: linux-control.0 (8596) unhandled promise rejection: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.793 - error: linux-control.0 (8596) ReplyError: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.793 - error: linux-control.0 (8596) Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern 2023-04-11 12:30:24.888 - info: linux-control.0 (8596) terminating 2023-04-11 12:30:24.900 - warn: linux-control.0 (8596) get state error: Connection is closed. 2023-04-11 12:30:24.907 - error: linux-control.0 (8596) [servicesInfo] VIS-OG (192.168.178.215:22): error: DB closed, stack: Error: DB closed 2023-04-11 12:30:25.038 - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): datapoint-id: VIS_OG_ScreenOff, description: ViS-OG_ScreenOff 2023-04-11 12:30:25.039 - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): error: DB closed, stack: Error: DB closed 2023-04-11 12:30:25.041 - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): datapoint-id: VIS_OG_ScreenOn, description: VIS-OG_ScreenOn 2023-04-11 12:30:25.042 - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): error: DB closed, stack: Error: DB closed 2023-04-11 12:30:25.494 - error: host.iobroker instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-04-11 12:30:25.502 - info: host.iobroker Restart adapter system.adapter.linux-control.0 because enabledNehme an es liegt an dem "dicken" Punkt im Namen und ist ein Adapter issue, oder?
Enigma 2 Adapter läuft nicht mehr:
mirko@iobroker:/opt/iobroker$ tail -f /opt/iobroker/log/iobroker.current.log |grep enigma 2023-04-11 12:36:12.099 - info: host.iobroker instance system.adapter.enigma2.0 started with pid 8762 2023-04-11 12:36:12.802 - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js 2023-04-11 12:36:12.802 - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/main.js 2023-04-11 12:36:12.802 - error: host.iobroker Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js:46:25) 2023-04-11 12:36:12.805 - error: host.iobroker Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js', 2023-04-11 12:36:12.805 - error: host.iobroker Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.enigma2/main.js' 2023-04-11 12:36:12.805 - error: host.iobroker instance system.adapter.enigma2.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2023-04-11 12:36:12.812 - info: host.iobroker Rebuild for adapter system.adapter.enigma2.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually. 2023-04-11 12:36:28.124 - info: host.iobroker "system.adapter.enigma2.0" disabled 2023-04-11 12:36:34.443 - info: host.iobroker "system.adapter.enigma2.0" enabled 2023-04-11 12:36:34.613 - info: host.iobroker instance system.adapter.enigma2.0 started with pid 8775 2023-04-11 12:36:36.424 - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js 2023-04-11 12:36:36.425 - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/main.js 2023-04-11 12:36:36.425 - error: host.iobroker Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js:46:25) 2023-04-11 12:36:36.426 - error: host.iobroker Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js', 2023-04-11 12:36:36.426 - error: host.iobroker Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.enigma2/main.js' 2023-04-11 12:36:36.426 - error: host.iobroker instance system.adapter.enigma2.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2023-04-11 12:36:36.426 - info: host.iobroker Rebuild for adapter system.adapter.enigma2.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.EDIT: Ergänzung zum Enigma2 Adapter:
2023-04-11 12:48:29.329 - info: trashschedule.0 (10113) [ical] configurured ical preview is 34 days - increase this value to find more events in the future 2023-04-11 12:48:46.571 - info: host.iobroker iobroker npm-rebuild: rebuilt dependencies successfully 2023-04-11 12:48:46.776 - info: host.iobroker iobroker npm-rebuild: Rebuilding native modules done 2023-04-11 12:48:47.781 - info: host.iobroker iobroker npm-rebuild: exit 0 2023-04-11 12:48:47.972 - info: host.iobroker instance system.adapter.enigma2.0 started with pid 10173 2023-04-11 12:48:49.184 - error: host.iobroker Caught by controller[0]: node:internal/modules/cjs/loader:1078 2023-04-11 12:48:49.184 - error: host.iobroker Caught by controller[0]: throw err; 2023-04-11 12:48:49.184 - error: host.iobroker Caught by controller[0]: ^ 2023-04-11 12:48:49.184 - error: host.iobroker Caught by controller[0]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js' 2023-04-11 12:48:49.184 - error: host.iobroker Caught by controller[0]: Require stack: 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/main.js 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:920:27) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1141:19) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at require (node:internal/modules/cjs/helpers:110:18) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js:46:25) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1254:14) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1308:10) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1117:32) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:958:12) 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1141:19) { 2023-04-11 12:48:49.185 - error: host.iobroker Caught by controller[0]: code: 'MODULE_NOT_FOUND', 2023-04-11 12:48:49.186 - error: host.iobroker Caught by controller[0]: requireStack: [ 2023-04-11 12:48:49.186 - error: host.iobroker Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js', 2023-04-11 12:48:49.186 - error: host.iobroker Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.enigma2/main.js' 2023-04-11 12:48:49.186 - error: host.iobroker Caught by controller[0]: ] 2023-04-11 12:48:49.186 - error: host.iobroker Caught by controller[0]: } 2023-04-11 12:48:49.186 - error: host.iobroker Caught by controller[0]: Node.js v18.14.2 2023-04-11 12:48:49.186 - error: host.iobroker instance system.adapter.enigma2.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2023-04-11 12:48:49.186 - info: host.iobroker Adapter system.adapter.enigma2.0 needs rebuild and will be restarted afterwards. 2023-04-11 12:48:49.186 - info: host.iobroker system.adapter.enigma2.0 will be rebuilt 2023-04-11 12:48:49.186 - warn: host.iobroker adapter "enigma2" seems to be installed for a different version of Node.js. Trying to rebuild it... 3 attempt 2023-04-11 12:48:49.187 - info: host.iobroker iobroker rebuild 2023-04-11 12:48:52.129 - info: host.iobroker iobroker npm-rebuild: Rebuilding native modules ...Bitte keine Fragen per PN, die gehören ins Forum!
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Support us
373
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge