Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test js-controller v2.0.x (GitHub)

    NEWS

    • Informationen zum Spamschutz im Forum

    • Beta-Start ioBroker-Matter Adapter

    • JAHRESRÜCKBLICK 2024 ✨

    Test js-controller v2.0.x (GitHub)

    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      Jan1 @AlCalzone last edited by

      @apollon77
      Also mit 2.0.25 sind sämtliche Errors und Warnungen aus dem Log verschwunden die ich oben gepostet hatte.

      @AlCalzone
      bei mir geht auch nur die zweite Variante des Update Befehl, egal ob root oder normaler User.

      D 1 Reply Last reply Reply Quote 0
      • D
        darkiop Most Active @Jan1 last edited by

        @Jan1 sagte in [Aufruf] js-controller 2.0 Beta Test:

        bei mir geht auch nur die zweite Variante des Update Befehl, egal ob root oder normaler User.

        Dem schließ mich mich an, sowohl im Container (immer root) als auch aufm RPI (mein User).

        1 Reply Last reply Reply Quote 0
        • E
          e-s @AlCalzone last edited by

          @AlCalzone
          das mit dem sudo kommt erst wenn man npm auf 6.11.3 updated, alle User die dies noch nicht gemacht haben, die brauchen den sudo Befehl auch nicht.

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

            @msauer Ja das ist irgendwelcher npm Rechte-Foo ...

            Ein iobroker upgrade selfsollte immer mit automatisch alles quasi mit "sudo -u iobroker -H" ausführen was es startet, damit sollte das Problem hier nicht auftreten.

            J AlCalzone 2 Replies Last reply Reply Quote 0
            • J
              Jan1 @apollon77 last edited by

              @apollon77
              OK, muss meine Aussage von oben doch noch mal korrigieren. Eben noch mal in die Logs geschaut und das hier gefunden:

              host.Beelink	2019-10-10 08:45:02.335	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.335	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.335	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.335	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.334	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.333	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.331	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.331	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.330	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.329	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.328	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.327	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.326	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[14]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[14]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[14]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[14]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[14]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[14]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[13]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.325	error	Caught by controller[13]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[13]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[13]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[13]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[13]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[12]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[12]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[12]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[12]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.324	error	Caught by controller[12]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[12]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[11]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[11]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[11]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[11]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[11]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[11]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[10]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.323	error	Caught by controller[10]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[10]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[10]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[10]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[10]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[9]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[9]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[9]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[9]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.322	error	Caught by controller[9]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[9]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[8]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[8]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[8]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[8]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[8]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[8]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[7]: at process._tickCallback (internal/process/next_tick.js:68:7)
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[7]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
host.Beelink	2019-10-10 08:45:02.321	error	Caught by controller[7]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
host.Beelink	2019-10-10 08:45:02.320	error	Caught by controller[7]: at client.get (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:436:21)
host.Beelink	2019-10-10 08:45:02.320	error	Caught by controller[7]: at /opt/iobroker/node_modules/iobroker.fritzdect/main.js:127:46
host.Beelink	2019-10-10 08:45:02.320	error	Caught by controller[7]: ReferenceError: log is not defined
host.Beelink	2019-10-10 08:45:02.320	error	Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:68:7)

              Müsste wieder das DB Problemchen sein, nur der Neustart liegt lag zu dem Zeitpunkt schon ein paar Minuten in der Vergangenheit.

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

                @Jan1 sagte in [Aufruf] js-controller 2.0 Beta Test:

                iobroker.fritzdect

                Ne, Adapter Bug
                https://github.com/Apollon77/ioBroker.fritzdect/blob/master/main.js#L127 das "-" ist falsch

                Ist 'Comet_' + id + '.targettemp' (musst mal schauen welch "id" das betreffen kann) leer?

                Fix für dich zum checken: Editiere /opt/iobroker/node_modules/iobroker.fritzdect/main.js: zeile 127 und schreibe "adapter.log" anstelle "adapter-log". Geht es dann wieder wie erwartet? Wirst halt diese "log meldung als Fehler" bekommen... aber da kenne ich die semantik des Adapters nicht

                J 1 Reply Last reply Reply Quote 0
                • AlCalzone
                  AlCalzone Developer @apollon77 last edited by

                  @apollon77 sagte in [Aufruf] js-controller 2.0 Beta Test:

                  Ein iobroker upgrade selfsollte immer mit automatisch alles quasi mit "sudo -u iobroker -H" ausführen was es startet, damit sollte das Problem hier nicht auftreten.

                  Außer es ist schon kaputt 😉

                  @e-s Ich hab ähnliche Fehler bei mir schon mit 6.9.x gehabt.

                  apollon77 1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User @apollon77 last edited by

                    @apollon77

                    ok, werde ich heute testen - Bericht kommt heute Abend.

                    DANKE

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

                      @AlCalzone Was sollte ich denn in die Anleitung für "latest"schreiben? Offiziell war ich bei "iobroker upgrade self" ... mus da im Notfall auch nochmal das sudo zeug avor?

                      AlCalzone 1 Reply Last reply Reply Quote 0
                      • SBorg
                        SBorg Forum Testing Most Active last edited by

                        Tut was er soll 🙂
                        Ist das eigentlich ein Überbleibsel, Mac geschuldet, Schönheitsfehler, ...(ist ja nicht wirklich relevant):
                        Bild 1.png
                        Einen "Fehler" hatte ich aber. Gestern den JS-Adapter von 4.1.16 auf 4.2.1 gezogen, lief soweit auch alles. Dann heute den JS-Controller auf die 2.0.25 und dann das:

                        2019-10-10 09:16:45.770 - info: host.Ubuntu iobroker.js-controller version 2.0.25 js-controller starting
2019-10-10 09:16:45.786 - info: host.Ubuntu Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
2019-10-10 09:16:45.788 - info: host.Ubuntu hostname: Ubuntu, node: v8.16.1
2019-10-10 09:16:45.795 - info: host.Ubuntu ip addresses: 192.168.1.30
2019-10-10 09:16:47.351 - info: host.Ubuntu connected to Objects and States
2019-10-10 09:16:47.982 - info: host.Ubuntu 82 instances found
2019-10-10 09:16:48.097 - info: host.Ubuntu starting 60 instances
2019-10-10 09:16:48.134 - warn: host.Ubuntu startInstance cannot find adapter "javascript@4.1.16". Try to install it... 1 attempt
2019-10-10 09:16:48.135 - info: host.Ubuntu iobroker install javascript@4.1.16 using installedVersion

                        ❓
                        Ok, kein echtes Problem, also nach dem automatischen downgrade wieder auf die 4.2.1 gezogen, aber anscheinend hat da was mit der neuen speichern Funktion nicht so ganz funktioniert?

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

                          zu 1.) Da sist leider NPM. ioBroker unterstützts Linux, Windows und Macos und daher brauchen wir Libraries für alle drei Systeme und einige sind damit auf den anderen Systemen optional. Das sind diese Meldungen. Ignore. Keine Ahnung wie man die wegbekommt.

                          2.) Schau mal bitte ob Du in deinem Objekten (alle Filter aus machen) ein "system.adapter.javascript@4.1.16" hast? Es gab in der 1.5.10/11 glaube ich einen Bug der solche komischen Dinge verursacht hat. Wenn das - warum auch immer - aktiv wird könnte der Fehler da her kommen.
                          Falls solche system.adapter.x" einträge mit nem "@" im Namen da sind bitte alle löschen.

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

                            @apollon77
                            verhällt es sich bei mir ähnlich?
                            1bc68052-e901-4ac5-b5f7-aa4620dfcf6d-grafik.png

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

                              Ok, zu 2.) Nochmal: Falls Du solche kaputten Verzeichnisse hast ... Wie hast Du denn auf die 4.2.1 aktualisiert?
                              Dieser Fehler kommt wenn das Verzeichnis vom javascript Adapter weg ist ... Any idea?

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

                                @BBTown Jupp, ist schon immer so und können wir nichts gegen tun

                                BBTown 1 Reply Last reply Reply Quote 0
                                • J
                                  Jan1 @apollon77 last edited by

                                  @apollon77 sagte in [Aufruf] js-controller 2.0 Beta Test:

                                  @Jan1 sagte in [Aufruf] js-controller 2.0 Beta Test:

                                  iobroker.fritzdect

                                  Ne, Adapter Bug
                                  https://github.com/Apollon77/ioBroker.fritzdect/blob/master/main.js#L127 das "-" ist falsch

                                  Ist 'Comet_' + id + '.targettemp' (musst mal schauen welch "id" das betreffen kann) leer?

                                  Fix für dich zum checken: Editiere /opt/iobroker/node_modules/iobroker.fritzdect/main.js: zeile 127 und schreibe "adapter.log" anstelle "adapter-log". Geht es dann wieder wie erwartet? Wirst halt diese "log meldung als Fehler" bekommen... aber da kenne ich die semantik des Adapters nicht

                                  Habs geändert und behalte es im Auge, wenn was im Log auftaucht, poste ich es einfach hier 🙂

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

                                    @apollon77
                                    ok ...

                                    helfen/benötigst Du darüber hinaus solche Informationen?
                                    8836d1e9-6813-423d-86ab-881ef40c1336-grafik.png

                                    Nachtrag:
                                    Ein npm install hat das nicht behoben

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

                                      @BBTown Naja "npm audit" wäre interessant bei einem System was komplett in den letzten 2-3 Monaten aufgesetzt wurde mit dem neuen Installer 🙂

                                      Alles ältere (und vor allem gewachsene Systeme) bringen genau wegen Meldungen wie dem ws Du gepostet hast nichts weil einfach selbst wenn eine package-lock da ist die meist Müll ist (weil Sie halt nicht alles abdeckt).

                                      Also: In dem Fall Danke, aber eher weniger Aussagekräftig 🙂

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

                                        @apollon77 gibt es bzw. brauche ich hier eine Lösung?

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

                                          @BBTown Nö, "Npm audit fix" ist eh voll gefährlich und ein kommendes Update vom Installer/Fixer wird das ausschalten. Zu viele User haben sich durch unbedachte Nutzung Ihre Systeme zerschossen. Von daher 😉

                                          Wenn das System tut ist alles ok.

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

                                            @apollon77 sagte in [Aufruf] js-controller 2.0 Beta Test:

                                            bei einem System was komplett in den letzten 2-3 Monaten aufgesetzt wurde mit dem neuen Installer

                                            Mein System wurde in der Tat erst vor einigen Wochen neu aufgesetzt.
                                            Im Anschluss dann über eine backitup Sicherung wieder auf Stand gebracht ...

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.1k
                                            Online

                                            31.1k
                                            Users

                                            78.3k
                                            Topics

                                            1.2m
                                            Posts

                                            js-controller
                                            48
                                            1047
                                            127814
                                            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