Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Cannot read property 'rows' of undefined

    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

    Cannot read property 'rows' of undefined

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

      Hallo,

      auf einem Debian Stretch/9/OMV System auf AMD64 funktioniert die Installation nicht:
      Iobroker startet nicht, bzw. stürzt gleich wieder ab:
      /opt/iobroker/log/iobroker.2019-10-05.log

      2019-10-05 15:59:10.200  - info: host.openmediavault InMemoryDB connected
      2019-10-05 15:59:10.205  - error: uncaught exception: Cannot read property 'rows' of undefined
      2019-10-05 15:59:10.207  - error: TypeError: Cannot read property 'rows' of undefined
          at /opt/iobroker/node_modules/iobroker.js-controller/controller.js:1239:28
          at _getObjectView (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2817:13)
          at checkObjectRights (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2844:28)
          at checkObjectRights (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1869:20)
          at ObjectsInMemServer.getObjectView (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2840:13)
          at setMeta (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:1237:13)
          at checkHost (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:347:29)
          at /opt/iobroker/node_modules/iobroker.js-controller/controller.js:705:17
          at _getObjectView (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2817:13)
          at checkObjectRights (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2844:28)
      2019-10-05 15:59:10.209  - info: host.openmediavault terminated
      2019-10-05 15:59:10.212  - info: iobroker _restart
      2019-10-05 15:59:10.533  - info: iobroker Starting node restart.js
      2019-10-05 15:59:10.548  - info: iobroker exit 0
      

      Dies hier hilft auch nicht:

      npm i iobroker.js-controller --production
      npm i iobroker.admin --production
      npm i iobroker.discovery --production
      

      Versionen:

      root@openmediavault:~# node -v
      v10.16.3
      root@openmediavault:~# nodejs -v
      v10.16.3
      root@openmediavault:~# npm -v
      6.9.0
      

      Weiß vielleicht jemand Rat?
      Würde mich sehr freuen.

      Danke, Tomte

      sigi234 1 Reply Last reply Reply Quote 0
      • sigi234
        sigi234 Forum Testing Most Active @Tomte last edited by

        @Tomte

        Was kommt bei:

        cd /opt/iobroker
        iobroker list instances
        node -v
        nodejs -v
        npm -v

        1 Reply Last reply Reply Quote 0
        • T
          Tomte last edited by

          npm habe ich im Vergleich zu oben mittlerweile aktualisiert:

          root@openmediavault:~# cd /opt/iobroker
          root@openmediavault:/opt/iobroker# iobroker list instances
          
          
          + instance is alive
          root@openmediavault:/opt/iobroker# node -v
          v10.16.3
          root@openmediavault:/opt/iobroker# nodejs -v
          v10.16.3
          root@openmediavault:/opt/iobroker# npm -v
          6.11.3
          root@openmediavault:/opt/iobroker#
          
          
          1 Reply Last reply Reply Quote 0
          • T
            Tomte last edited by

            Hallo,

            jetzt läuft es.
            irgendwie hat mein nodejs in /usr/bin/ auf eine andere Version gezeigt, keine Ahnung warum.
            Das habe ich geflickt, und nun gibt es keine Probleme mehr.
            Wichtig scheint zu sein, dass die Einträge in diesem Verzeichnis ok sind, und nicht nur, dass die node version im Pfad ist.

            Viele Grüße, Tomte

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Support us

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

            618
            Online

            31.9k
            Users

            80.1k
            Topics

            1.3m
            Posts

            inmemorydb uncaught exception installation
            2
            4
            812
            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