Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Cloud Dienste
    4. iot Adapter in restart loop

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    iot Adapter in restart loop

    This topic has been deleted. Only users with topic management privileges can see it.
    • G. K.
      G. K. last edited by

      Hallo
      seit gestern wirft der iot Adapter Fehler und geht in eine restart loop.
      Vorher lief das Ganze in genau dieser Umgebung klaglos.

      Bereits versucht habe ich eine Adapter Neuinstallation.
      Wird in der iot Config keine der drei Cloudumgebungen angewählt startet der Adapter auch ohne Probleme, nur ist das ja nicht der Zweck des Ganzen.

      Hier mal einen Ausgabe wenn nur Google angewählt wurde.

      2022-08-04 09:35:13.234  - info: host.smart1 instance system.adapter.iot.0 started with pid 1907
      2022-08-04 09:35:14.731  - debug: iot.0 (1907) Redis Objects: Use Redis connection: 172.17.0.2:6379
      2022-08-04 09:35:14.768  - debug: iot.0 (1907) Objects client ready ... initialize now
      2022-08-04 09:35:14.771  - debug: iot.0 (1907) Objects create System PubSub Client
      2022-08-04 09:35:14.772  - debug: iot.0 (1907) Objects create User PubSub Client
      2022-08-04 09:35:15.115  - debug: iot.0 (1907) Objects client initialize lua scripts
      2022-08-04 09:35:15.131  - debug: iot.0 (1907) Objects connected to redis: 172.17.0.2:6379
      2022-08-04 09:35:15.136  - silly: iot.0 (1907) redis psubscribe cfg.o.system.user.*
      2022-08-04 09:35:15.165  - silly: iot.0 (1907) redis psubscribe cfg.o.enum.*
      2022-08-04 09:35:15.171  - silly: iot.0 (1907) objectDB connected
      2022-08-04 09:35:15.174  - debug: iot.0 (1907) Redis States: Use Redis connection: 172.17.0.2:6379
      2022-08-04 09:35:15.184  - debug: iot.0 (1907) States create System PubSub Client
      2022-08-04 09:35:15.185  - debug: iot.0 (1907) States create User PubSub Client
      2022-08-04 09:35:15.207  - debug: iot.0 (1907) States connected to redis: 172.17.0.2:6379
      2022-08-04 09:35:15.209  - silly: iot.0 (1907) statesDB connected
      2022-08-04 09:35:15.310  - debug: iot.0 (1907) Plugin sentry Initialize Plugin (enabled=true)
      2022-08-04 09:35:16.047  - info: iot.0 (1907) starting. Version 1.11.8 in /opt/iobroker/node_modules/iobroker.iot, node: v14.20.0, js-controller: 4.0.23
      2022-08-04 09:35:16.134  - silly: iot.0 (1907) States system redis pmessage io.system.adapter.iot.0.logLevel/io.system.adapter.iot.0.logLevel:{"val":"silly","ack":true,"ts":1659598516108,"q":0,"from":"system.adapter.iot.0","lc":1659596812053}
      2022-08-04 09:35:16.153  - info: iot.0 (1907) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
      2022-08-04 09:35:16.394  - debug: iot.0 (1907) [GHOME] Unsubscribe 0 states for google home
      2022-08-04 09:35:16.395  - debug: iot.0 (1907) [GHOME] Unsubscribe done
      2022-08-04 09:35:16.702  - info: iot.0 (1907) Connection changed: connect
      2022-08-04 09:35:16.884  - error: iot.0 (1907) 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().
      2022-08-04 09:35:16.885  - error: iot.0 (1907) unhandled promise rejection: Cannot read property '_id' of null
      2022-08-04 09:35:16.888  - error: iot.0 (1907) TypeError: Cannot read property '_id' of null
          at /opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3422:42
          at Array.map (<anonymous>)
          at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3414:39)
          at processTicksAndRejections (internal/process/task_queues.js:95:5)
      2022-08-04 09:35:16.889  - error: iot.0 (1907) Cannot read property '_id' of null
      2022-08-04 09:35:16.915  - info: iot.0 (1907) terminating
      2022-08-04 09:35:16.916  - debug: iot.0 (1907) Plugin sentry destroyed
      2022-08-04 09:35:16.916  - warn: iot.0 (1907) Terminated (UNCAUGHT_EXCEPTION): Without reason
      2022-08-04 09:35:16.962  - info: iot.0 (1907) Connection changed: disconnect
      2022-08-04 09:35:16.963  - info: iot.0 (1907) Connection lost
      2022-08-04 09:35:17.507  - error: host.smart1 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:
      2022-08-04 09:35:17.508  - error: host.smart1 Caught by controller[1]: TypeError: Cannot read property '_id' of null
      2022-08-04 09:35:17.508  - error: host.smart1 Caught by controller[1]:     at /opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3422:42
      2022-08-04 09:35:17.509  - error: host.smart1 Caught by controller[1]:     at Array.map (<anonymous>)
      2022-08-04 09:35:17.509  - error: host.smart1 Caught by controller[1]:     at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3414:39)
      2022-08-04 09:35:17.509  - error: host.smart1 Caught by controller[1]:     at processTicksAndRejections (internal/process/task_queues.js:95:5)
      2022-08-04 09:35:17.510  - error: host.smart1 instance system.adapter.iot.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2022-08-04 09:35:17.510  - error: host.smart1 instance system.adapter.iot.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      2022-08-04 09:35:17.510  - info: host.smart1 Restart adapter system.adapter.iot.0 because enabled
      2022-08-04 09:35:17.511  - warn: host.smart1 Do not restart adapter system.adapter.iot.0 because restart loop detected
      

      Ein paar Grunddaten.
      Docker Umgebung (iobrokker/iobroker) mit redis in einem zweiten verlinkten Container
      Node v14.20.0 (wie vom docker image vorinstalliert)
      Controller 4.0.23

      Also was tun ?

      G. K. 1 Reply Last reply Reply Quote 0
      • G. K.
        G. K. @G. K. last edited by

        @g-k Selber gelöst 😃
        auf der redis instanz mustte dies hier helfen.

        redis-cli set meta.objects.features.useSets '0'
        
        1 Reply Last reply Reply Quote 1
        • First post
          Last post

        Support us

        ioBroker
        Community Adapters
        Donate
        FAQ Cloud / IOT
        HowTo: Node.js-Update
        HowTo: Backup/Restore
        Downloads
        BLOG

        597
        Online

        31.8k
        Users

        80.0k
        Topics

        1.3m
        Posts

        cloud iot pro
        1
        2
        247
        Loading More Posts
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes
        Reply
        • Reply as topic
        Log in to reply
        Community
        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
        The ioBroker Community 2014-2023
        logo