Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 3.2 jetzt im Latest!

    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

    js-controller 3.2 jetzt im Latest!

    This topic has been deleted. Only users with topic management privileges can see it.
    • apollon77
      apollon77 @amg_666 last edited by

      @amg_666 Bitte beim Adapter ein Issue anlegen

      lobomau 1 Reply Last reply Reply Quote 0
      • lobomau
        lobomau @apollon77 last edited by

        @apollon77 3.2.7. läuft bei mir den ganzen Tag ohne Probleme. Ohne krumme Version klappt auch wieder das Adapter-Update 👍

        ioBroker als Container unter Proxmox kann ich nur empfehlen 😁

        1 Reply Last reply Reply Quote 1
        • Feuersturm
          Feuersturm last edited by Feuersturm

          @apollon77
          Gerade hat sich der COVID-19 live information Adapter ( @Dutchman ) zu Wort gemeldet. Ist das ein Adapter oder ein js-controller Thema?

          coronavirus-statistics.0	2021-01-17 22:45:45.398	info	(17994) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          coronavirus-statistics.0	2021-01-17 22:45:38.861	error	at Covid19.onReady (/opt/iobroker/node_modules/iobroker.coronavirus-statistics/main.js:599:5)
          coronavirus-statistics.0	2021-01-17 22:45:38.861	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
          coronavirus-statistics.0	2021-01-17 22:45:38.861	error	at runMicrotasks (<anonymous>)
          coronavirus-statistics.0	2021-01-17 22:45:38.861	error	at germanyBundersland (/opt/iobroker/node_modules/iobroker.coronavirus-statistics/main.js:314:35)
          coronavirus-statistics.0	2021-01-17 22:45:38.861	error	(17994) [germanyFederalStates] error: values.features is not iterable, stack: TypeError: values.features is not iterable
          

          Issue: https://github.com/iobroker-community-adapters/ioBroker.coronavirus-statistics/issues/158

          Feuer-sturm created this issue in iobroker-community-adapters/ioBroker.coronavirus-statistics

          closed js-controller 3.2.x - Error features is not iterable #158

          apollon77 Dutchman 2 Replies Last reply Reply Quote 1
          • apollon77
            apollon77 @Feuersturm last edited by

            @feuersturm Eindeutig Adapter

            1 Reply Last reply Reply Quote 0
            • Dutchman
              Dutchman Developer Most Active Administrators @Feuersturm last edited by

              @feuersturm said in js-controller 3.2 jetzt im Latest!:

              Gerade hat sich der COVID-19 live information Adapter ( Dutchman ) zu Wort gemeldet. Ist das ein Adapter oder ein js-controller Thema?

              Thanks fürs git issue kümmern mich drum

              P 1 Reply Last reply Reply Quote 0
              • P
                PrinzEisenherz1 @Dutchman last edited by

                Hab jetzt unter js-controller 3.2.7 schon das zweite mal folgenden fehler vom dwd-Adapter

                2021-01-18 00:00:14.153 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.begin": Error: Connection is closed.
                2021-01-18 00:00:14.163 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.end": Error: Connection is closed.
                2021-01-18 00:00:14.167 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.severity": Error: Connection is closed.
                2021-01-18 00:00:14.168 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.level": Error: Connection is closed.
                2021-01-18 00:00:14.169 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.type": Error: Connection is closed.
                2021-01-18 00:00:14.170 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.text": Error: Connection is closed.
                2021-01-18 00:00:14.171 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.headline": Error: Connection is closed.
                2021-01-18 00:00:14.171 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.description": Error: Connection is closed.
                2021-01-18 00:00:14.175 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.object": Error: Connection is closed.
                2021-01-18 00:00:14.177 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning.map": Error: Connection is closed.
                2021-01-18 00:00:14.200 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.begin": Error: Connection is closed.
                2021-01-18 00:00:14.200 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.end": Error: Connection is closed.
                2021-01-18 00:00:14.201 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.severity": Error: Connection is closed.
                2021-01-18 00:00:14.201 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.level": Error: Connection is closed.
                2021-01-18 00:00:14.211 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.type": Error: Connection is closed.
                2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.text": Error: Connection is closed.
                2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.headline": Error: Connection is closed.
                2021-01-18 00:00:14.212 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.description": Error: Connection is closed.
                2021-01-18 00:00:14.213 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.object": Error: Connection is closed.
                2021-01-18 00:00:14.213 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning1.map": Error: Connection is closed.
                2021-01-18 00:00:14.214 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.begin": Error: Connection is closed.
                2021-01-18 00:00:14.214 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.end": Error: Connection is closed.
                2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.severity": Error: Connection is closed.
                2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.level": Error: Connection is closed.
                2021-01-18 00:00:14.215 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.type": Error: Connection is closed.
                2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.text": Error: Connection is closed.
                2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.headline": Error: Connection is closed.
                2021-01-18 00:00:14.216 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.description": Error: Connection is closed.
                2021-01-18 00:00:14.217 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.object": Error: Connection is closed.
                2021-01-18 00:00:14.217 - error: dwd.0 (5122) Cannot check object existence of "dwd.0.warning2.map": Error: Connection is closed.
                2021-01-18 00:00:14.218 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.numberofwarnings: Error: Cannot check object existence of "dwd.0.numberofwarnings": Error: Connection is closed.
                2021-01-18 00:00:14.223 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.begin: Error: Cannot check object existence of "dwd.0.warning.begin": Error: Connection is closed.
                2021-01-18 00:00:14.224 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.end: Error: Cannot check object existence of "dwd.0.warning.end": Error: Connection is closed.
                2021-01-18 00:00:14.225 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.severity: Error: Cannot check object existence of "dwd.0.warning.severity": Error: Connection is closed.
                2021-01-18 00:00:14.225 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.level: Error: Cannot check object existence of "dwd.0.warning.level": Error: Connection is closed.
                2021-01-18 00:00:14.226 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.type: Error: Cannot check object existence of "dwd.0.warning.type": Error: Connection is closed.
                2021-01-18 00:00:14.227 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.text: Error: Cannot check object existence of "dwd.0.warning.text": Error: Connection is closed.
                2021-01-18 00:00:14.228 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.headline: Error: Cannot check object existence of "dwd.0.warning.headline": Error: Connection is closed.
                2021-01-18 00:00:14.259 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.description: Error: Cannot check object existence of "dwd.0.warning.description": Error: Connection is closed.
                2021-01-18 00:00:14.260 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.object: Error: Cannot check object existence of "dwd.0.warning.object": Error: Connection is closed.
                2021-01-18 00:00:14.260 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning.map: Error: Cannot check object existence of "dwd.0.warning.map": Error: Connection is closed.
                2021-01-18 00:00:14.261 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.begin: Error: Cannot check object existence of "dwd.0.warning1.begin": Error: Connection is closed.
                2021-01-18 00:00:14.262 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.end: Error: Cannot check object existence of "dwd.0.warning1.end": Error: Connection is closed.
                2021-01-18 00:00:14.263 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.severity: Error: Cannot check object existence of "dwd.0.warning1.severity": Error: Connection is closed.
                2021-01-18 00:00:14.264 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.level: Error: Cannot check object existence of "dwd.0.warning1.level": Error: Connection is closed.
                2021-01-18 00:00:14.264 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.type: Error: Cannot check object existence of "dwd.0.warning1.type": Error: Connection is closed.
                2021-01-18 00:00:14.265 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.text: Error: Cannot check object existence of "dwd.0.warning1.text": Error: Connection is closed.
                2021-01-18 00:00:14.266 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.headline: Error: Cannot check object existence of "dwd.0.warning1.headline": Error: Connection is closed.
                2021-01-18 00:00:14.311 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.description: Error: Cannot check object existence of "dwd.0.warning1.description": Error: Connection is closed.
                2021-01-18 00:00:14.312 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.object: Error: Cannot check object existence of "dwd.0.warning1.object": Error: Connection is closed.
                2021-01-18 00:00:14.313 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning1.map: Error: Cannot check object existence of "dwd.0.warning1.map": Error: Connection is closed.
                2021-01-18 00:00:14.314 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.begin: Error: Cannot check object existence of "dwd.0.warning2.begin": Error: Connection is closed.
                2021-01-18 00:00:14.315 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.end: Error: Cannot check object existence of "dwd.0.warning2.end": Error: Connection is closed.
                2021-01-18 00:00:14.316 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.severity: Error: Cannot check object existence of "dwd.0.warning2.severity": Error: Connection is closed.
                2021-01-18 00:00:14.316 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.level: Error: Cannot check object existence of "dwd.0.warning2.level": Error: Connection is closed.
                2021-01-18 00:00:14.317 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.type: Error: Cannot check object existence of "dwd.0.warning2.type": Error: Connection is closed.
                2021-01-18 00:00:14.318 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.text: Error: Cannot check object existence of "dwd.0.warning2.text": Error: Connection is closed.
                2021-01-18 00:00:14.335 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.headline: Error: Cannot check object existence of "dwd.0.warning2.headline": Error: Connection is closed.
                2021-01-18 00:00:14.336 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.description: Error: Cannot check object existence of "dwd.0.warning2.description": Error: Connection is closed.
                2021-01-18 00:00:14.337 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.object: Error: Cannot check object existence of "dwd.0.warning2.object": Error: Connection is closed.
                2021-01-18 00:00:14.337 - warn: dwd.0 (5122) Could not check object existence of state dwd.0.warning2.map: Error: Cannot check object existence of "dwd.0.warning2.map": Error: Connection is closed.
                2021-01-18 00:00:14.373 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.374 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.444 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.445 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.474 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.475 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.476 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.477 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.484 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.486 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.487 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.488 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.494 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.504 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.506 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.506 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.511 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.513 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.515 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.515 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.520 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.520 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.521 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.522 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.531 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.532 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.544 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.545 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.555 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.556 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.557 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.558 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.588 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.590 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.591 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.592 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.606 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.607 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.608 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.609 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.618 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.619 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.622 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.622 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.628 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.629 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.632 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.633 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.637 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.640 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.642 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.644 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.664 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.665 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.667 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.670 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.678 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.679 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.681 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.692 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.699 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.700 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.702 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.703 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.812 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.812 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.814 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.831 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.836 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.837 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.838 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.839 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.844 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.845 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.846 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.847 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.852 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.853 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.855 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.856 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.862 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.863 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.864 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.865 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.870 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.871 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.872 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.873 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.877 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.878 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.879 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.880 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.893 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.894 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.907 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.908 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.915 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.916 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.917 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.918 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.929 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.929 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.934 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.935 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.940 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.940 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.942 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.943 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.952 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.953 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.955 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.955 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.965 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.971 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.972 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.973 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:14.994 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:14.995 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:14.996 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:14.997 - error: dwd.0 (5122) Cannot read property 'setState' of null
                2021-01-18 00:00:15.028 - error: dwd.0 (5122) 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().
                2021-01-18 00:00:15.029 - error: dwd.0 (5122) unhandled promise rejection: Cannot read property 'setState' of null
                2021-01-18 00:00:15.030 - error: dwd.0 (5122) TypeError: Cannot read property 'setState' of null
                at Adapter.setForeignState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6307:35)
                at processTicksAndRejections (internal/process/task_queues.js:97:5)
                2021-01-18 00:00:15.031 - error: dwd.0 (5122) Cannot read property 'setState' of null
                

                Woran liegts? controller oder Adapter?

                apollon77 1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @PrinzEisenherz1 last edited by

                  @prinzeisenherz1 Bitte mal die dwd Github version versuchen. Besser? Habe da im Adapter etwas nachgearbeitet

                  P Feuersturm 2 Replies Last reply Reply Quote 0
                  • P
                    PrinzEisenherz1 @apollon77 last edited by

                    @apollon77 probier ich später. Brauche jetzt n Bett. 🥱

                    JayR 1 Reply Last reply Reply Quote 0
                    • JayR
                      JayR @PrinzEisenherz1 last edited by

                      Ich bekomme folgenden Fehler angezeigt und iobroker startet nicht mehr.

                      2021-01-18 07:14:34.463  - error: host.Collector Cannot read property 'storeNotifications' of undefined
                      Cannot read property 'storeNotifications' of undefined
                      TypeError: Cannot read property 'storeNotifications' of undefined
                          at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
                          at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
                          at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
                          at process.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4619:9)
                          at process.emit (events.js:314:20)
                      2021-01-18 07:14:34.468  - error: host.Collector uncaught exception: Cannot read property 'storeNotifications' of undefined
                      2021-01-18 07:14:34.469  - error: host.Collector TypeError: Cannot read property 'storeNotifications' of undefined
                          at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
                          at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
                          at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
                          at process.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4619:9)
                          at process.emit (events.js:314:20)
                      2021-01-18 07:14:34.478  - error: host.Collector Cannot read property 'storeNotifications' of undefined
                      /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264
                              notificationHandler.storeNotifications();
                                                  ^
                      
                      TypeError: Cannot read property 'storeNotifications' of undefined
                          at /opt/iobroker/node_modules/iobroker.js-controller/main.js:4264:29
                          at stopInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4225:43)
                          at stop (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4262:5)
                          at process.exceptionHandler (/opt/iobroker/node_modules/iobroker.js-controller/main.js:4612:9)
                          at process.emit (events.js:314:20)
                          at process._fatalException (internal/process/execution.js:165:25)
                      
                      
                      apollon77 1 Reply Last reply Reply Quote 0
                      • apollon77
                        apollon77 @JayR last edited by

                        @jayr Interessant, da fliegt bei die scheinbar mega früh irgendeine exception. versuch bitte nochmal drüber zu installieren

                        JayR 1 Reply Last reply Reply Quote 0
                        • JayR
                          JayR @apollon77 last edited by

                          @apollon77 said in js-controller 3.2 jetzt im Latest!:

                          @jayr Interessant, da fliegt bei die scheinbar mega früh irgendeine exception. versuch bitte nochmal drüber zu installieren

                          Also es lief die Ganze Zeit ohne Probleme (Habe gestern morgen geupdated). Der Fehler ist heute morgen gekommen nachdem ich ein Adapter installiert hab.

                          apollon77 Master67 2 Replies Last reply Reply Quote 0
                          • apollon77
                            apollon77 @JayR last edited by

                            @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

                            Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

                            JayR 1 Reply Last reply Reply Quote 0
                            • Master67
                              Master67 @JayR last edited by

                              Läuft bei mir nicht... bekomme X-Fehlermeldungen (leider konnte ich die nicht speichern, lade eine Sicherung und dann habe ich die Meldungen), nur soviel, die Vis ging noch ein Einlogen per IP und Port ging nicht mehr!

                              apollon77 1 Reply Last reply Reply Quote 0
                              • apollon77
                                apollon77 @Master67 last edited by

                                @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

                                Master67 2 Replies Last reply Reply Quote 0
                                • JayR
                                  JayR @apollon77 last edited by

                                  @apollon77 said in js-controller 3.2 jetzt im Latest!:

                                  @jayr Ok, dann bitte mehr log ... das fehlt halt. Es kam also aus dem cli Kommando oder wie wann genau? oder ist der ganze COntroller gecraht?

                                  Aber hab schon nen Fix der mit der 3.2.8 heute abend vorauss kommt.

                                  Kam aus dem CLI Kommand. Mehr wurde nicht angezeigt. Welches Log brauchst du genau?

                                  Der Controller lief noch bin nur nicht mehr auf de WebUi gekommen.

                                  apollon77 1 Reply Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 @JayR last edited by

                                    @jayr Restarte mal controller sodass wieder alles geht. und dann versuch später ob es mit der 3.2.8 noch passiert

                                    1 Reply Last reply Reply Quote 0
                                    • Master67
                                      Master67 @apollon77 last edited by

                                      @apollon77 sagte in js-controller 3.2 jetzt im Latest!:

                                      @master67 Jupp mehr Infos bitte. Bist der erste der solche Probleme hat :-))

                                      Mache ich wenn der ioBroker wieder läuft... spiele doch grade eine Sicherung ein 😉

                                      1 Reply Last reply Reply Quote 0
                                      • Master67
                                        Master67 @apollon77 last edited by

                                        @apollon77 so hier mal die Fehlermeldung die ich erhalte 🙂

                                        Update js-controller from @3.1.6 to @3.2.7
                                        NPM version: 6.14.10
                                        npm install iobroker.js-controller@3.2.7 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                                        In file included from ../authenticate_pam.cc:23:
                                        ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)':
                                        ../../nan/nan.h:2294:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka 'void (*)(uv_work_s*, int)'} [-Wcast-function-type]
                                         2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                              |                                                              ^
                                        ../authenticate_pam.cc: In function 'void after_doing_auth(uv_work_t*, int)':
                                        ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                                          107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                              |                                                                                       ^
                                        In file included from ../authenticate_pam.cc:23:
                                        ../../nan/nan.h:1026:46: note: declared here
                                         1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                              |                                              ^~~~~~~~~~~~
                                        ../authenticate_pam.cc:107:87: warning: 'v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)' is deprecated [-Wdeprecated-declarations]
                                          107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                              |                                                                                       ^
                                        In file included from ../authenticate_pam.cc:23:
                                        ../../nan/nan.h:1026:46: note: declared here
                                         1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                              |                                              ^~~~~~~~~~~~
                                        ../authenticate_pam.cc: In function 'Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)':
                                        ../authenticate_pam.cc:147:83: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                                          147 |   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
                                              |                                                                                   ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                                         from ../../nan/nan.h:56,
                                                         from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                                         3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                              |                                                   ^~~
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                                          328 |   declarator __attribute__((deprecated(message)))
                                              |   ^~~~~~~~~~
                                        ../authenticate_pam.cc:150:30: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                          150 |    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                              |                           ~~~^~~~~~~~~~~
                                              |                              |
                                              |                              char [128]
                                        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                                         from ../../nan/nan.h:56,
                                                         from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                                         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                              |                 ~~~~~~~~~^~~~~~~
                                        ../authenticate_pam.cc:152:69: warning: 'v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)' is deprecated: Use maybe version [-Wdeprecated-declarations]
                                          152 |   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
                                              |                                                                     ^
                                        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8-internal.h:14,
                                                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:27,
                                                         from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                                         from ../../nan/nan.h:56,
                                                         from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:3553:51: note: declared here
                                         3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
                                              |                                                   ^~~
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8config.h:328:3: note: in definition of macro 'V8_DEPRECATED'
                                          328 |   declarator __attribute__((deprecated(message)))
                                              |   ^~~~~~~~~~
                                        ../authenticate_pam.cc:155:29: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                          155 |    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                              |                          ~~~^~~~~~~~~~
                                              |                             |
                                              |                             char [128]
                                        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                                         from ../../nan/nan.h:56,
                                                         from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                                         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                              |                 ~~~~~~~~~^~~~~~~
                                        ../authenticate_pam.cc:160:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                          160 |  username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                              |                      ~~~^~~~~~~~
                                              |                         |
                                              |                         char [128]
                                        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                                         from ../../nan/nan.h:56,
                                                         from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                                         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                              |                 ~~~~~~~~~^~~~~~~
                                        ../authenticate_pam.cc:161:25: error: cannot convert 'char [128]' to 'v8::Isolate*'
                                          161 |  password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                              |                      ~~~^~~~~~~~
                                              |                         |
                                              |                         char [128]
                                        In file included from /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:67,
                                                         from ../../nan/nan.h:56,
                                                         from ../authenticate_pam.cc:23:
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/v8.h:2878:26: note:   initializing argument 1 of 'int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const'
                                         2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
                                              |                 ~~~~~~~~~^~~~~~~
                                        ../authenticate_pam.cc: At global scope:
                                        ../authenticate_pam.cc:170:11: error: variable or field 'init' declared void
                                          170 | void init(Handle<Object> exports) {
                                              |           ^~~~~~
                                        ../authenticate_pam.cc:170:11: error: 'Handle' was not declared in this scope
                                        ../authenticate_pam.cc:170:24: error: expected primary-expression before '>' token
                                          170 | void init(Handle<Object> exports) {
                                              |                        ^
                                        ../authenticate_pam.cc:170:26: error: 'exports' was not declared in this scope
                                          170 | void init(Handle<Object> exports) {
                                              |                          ^~~~~~~
                                        In file included from ../../nan/nan.h:56,
                                                         from ../authenticate_pam.cc:23:
                                        ../authenticate_pam.cc:175:31: error: 'init' was not declared in this scope; did you mean 'int'?
                                          175 | NODE_MODULE(authenticate_pam, init);
                                              |                               ^~~~
                                        /home/iobroker/.cache/node-gyp/12.20.1/include/node/node.h:737:36: note: in definition of macro 'NODE_MODULE_X'
                                          737 |       (node::addon_register_func) (regfunc),                          \
                                              |                                    ^~~~~~~
                                        ../authenticate_pam.cc:175:1: note: in expansion of macro 'NODE_MODULE'
                                          175 | NODE_MODULE(authenticate_pam, init);
                                              | ^~~~~~~~~~~
                                        make: *** [authenticate_pam.target.mk:111: Release/obj.target/authenticate_pam/authenticate_pam.o] Error 1
                                        gyp ERR! build error 
                                        gyp ERR! stack Error: `make` failed with exit code: 2
                                        gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                                        gyp ERR! stack     at ChildProcess.emit (events.js:314:20)
                                        gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
                                        gyp ERR! System Linux 5.4.78-2-pve
                                        gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                        gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
                                        gyp ERR! node -v v12.20.1
                                        gyp ERR! node-gyp -v v5.1.0
                                        gyp ERR! not ok 
                                        Starting node restart.js
                                        
                                        apollon77 1 Reply Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 @Master67 last edited by

                                          @master67 Das ist alles ok ... bzw wenn du gluck hast sind die nach einem "iobroker fix" weg.

                                          Das sind faktisch nur warnungen von einem optionalen Paket

                                          Master67 1 Reply Last reply Reply Quote 0
                                          • Master67
                                            Master67 @apollon77 last edited by

                                            @apollon77 ... freut mich ja... aber ich kommen den noch nicht mehr auf den ioBroker drauf 😉

                                            Thomas Braun apollon77 2 Replies 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

                                            840
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            70
                                            575
                                            108480
                                            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