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.0/3.1 jetzt im Latest!

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 3.0/3.1 jetzt im Latest!

    This topic has been deleted. Only users with topic management privileges can see it.
    • D3ltoroxp
      D3ltoroxp @Thomas Braun last edited by D3ltoroxp

      @Thomas-Braun Also ich habs jetzt noch mal zurückgesetzt und die Updates erneut durchgeführt. Danach nicht die Hammer Methode sondern mit

      iobroker rebuild maxcul

      Das hat leider überhaupt nichts gebracht.

      Könnte ich das dann noch mal versuchen ?

      iobroker rebuild maxcul--install
      Thomas Braun 1 Reply Last reply Reply Quote -1
      • Thomas Braun
        Thomas Braun Most Active @D3ltoroxp last edited by

        @D3ltoroxp sagte in js-controller 3.0/3.1 jetzt im Latest!:

        iobroker rebuild maxcul--install

        Da fehlt ein Leerzeichen:

        iobroker rebuild maxcul --install
        D3ltoroxp 1 Reply Last reply Reply Quote 0
        • D3ltoroxp
          D3ltoroxp @Thomas Braun last edited by

          @Thomas-Braun

          Also das hat zumindest den Adapter wieder zum laufen gebracht, Fehler sind aber immer noch vorhanden. Danke

          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @D3ltoroxp last edited by

            @D3ltoroxp
            Fehler heißt?

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

              @Marty56 Ignorieren. Bite ein Issue bei "cloud" bitte anlegen

              1 Reply Last reply Reply Quote 0
              • D3ltoroxp
                D3ltoroxp @Thomas Braun last edited by D3ltoroxp

                @Thomas-Braun Sowas ähnliches wie hier. Sobald er wieder in der Log auftaucht, ,melde ich mich noch mal. Grad mal reingeschaut, war nichts zu sehen. Ist aber nicht exakt gleich wie beim verlinkten Fehler.

                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().

                EDIT: Und schon sind sie wieder da.

                
host.iobroker	2020-05-23 13:11:26.853	info	Restart adapter system.adapter.maxcul.0 because enabled
host.iobroker	2020-05-23 13:11:26.853	info	instance system.adapter.maxcul.0 terminated with code 0 (NO_ERROR)
host.iobroker	2020-05-23 13:11:26.852	error	Caught by controller[0]: Cannot load serialport module
maxcul.0	2020-05-23 13:11:26.311	info	(2353) Terminated (NO_ERROR): Without reason
maxcul.0	2020-05-23 13:11:26.309	info	(2353) terminating
maxcul.0	2020-05-23 13:11:26.260	error	(2353) Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'. at Object.Module._extensions..node (internal/modules/cjs/loader.js:1183:1
maxcul.0	2020-05-23 13:11:26.258	error	(2353) unhandled promise rejection: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
maxcul.0	2020-05-23 13:11:26.257	error	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().
maxcul.0	2020-05-23 13:11:25.903	info	(2353) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.16.3, js-controller: 3.1.4
host.iobroker	2020-05-23 13:11:23.689	info	instance system.adapter.maxcul.0 started with pid 2353
fhem.0	2020-05-23 13:11:15.511	info	(345) stateChange: fhem.0.info.Commands.sendFHEM | set fhem.0.alive on-for-timer 360 > set fhem.0.alive on-for-timer 360
host.iobroker	2020-05-23 13:10:53.650	info	Restart adapter system.adapter.maxcul.0 because enabled
host.iobroker	2020-05-23 13:10:53.650	info	instance system.adapter.maxcul.0 terminated with code 0 (NO_ERROR)
host.iobroker	2020-05-23 13:10:53.649	error	Caught by controller[0]: Cannot load serialport module
maxcul.0	2020-05-23 13:10:53.101	info	(2336) Terminated (NO_ERROR): Without reason
maxcul.0	2020-05-23 13:10:53.099	info	(2336) terminating
maxcul.0	2020-05-23 13:10:53.084	error	(2336) Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'. at Object.Module._extensions..node (internal/modules/cjs/loader.js:1183:1
maxcul.0	2020-05-23 13:10:53.083	error	(2336) unhandled promise rejection: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
maxcul.0	2020-05-23 13:10:53.081	error	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().
maxcul.0	2020-05-23 13:10:52.725	info	(2336) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.16.3, js-controller: 3.1.4
host.iobroker	2020-05-23 13:10:50.676	info	instance system.adapter.maxcul.0 started with pid 2336
javascript.0	2020-05-23 13:10:46.103	info	(29269) script.js.Heizung.Buero_HT: setForeignState(id=0_userdata.0.Buero.Fenster_Auf, state=true)
javascript.0	2020-05-23 13:10:46.102	info	(29269) script.js.Heizung.Buero_HT: getState(id=zigbee.0.00158d0003216589.opened, timerId=undefined) => {"val":true,"ack":true,"ts":1590229353761,"q":0,"from":"system.adapter.zigbee.0","user":"system.
javascript.0	2020-05-23 13:10:46.101	info	(29269) script.js.Heizung.Buero_HT: getState(id=0_userdata.0.Aussen.Heizperiode, timerId=undefined) => {"val":true,"ack":false,"ts":1588514198512,"q":0,"from":"system.adapter.admin.0","user":"system.u
host.iobroker	2020-05-23 13:10:20.640	info	Restart adapter system.adapter.maxcul.0 because enabled
host.iobroker	2020-05-23 13:10:20.639	info	instance system.adapter.maxcul.0 terminated with code 0 (NO_ERROR)
host.iobroker	2020-05-23 13:10:20.638	error	Caught by controller[0]: Cannot load serialport module
maxcul.0	2020-05-23 13:10:20.107	info	(2315) Terminated (NO_ERROR): Without reason
maxcul.0	2020-05-23 13:10:20.105	info	(2315) terminating
maxcul.0	2020-05-23 13:10:20.052	error	(2315) Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'. at Object.Module._extensions..node (internal/modules/cjs/loader.js:1183:1
maxcul.0	2020-05-23 13:10:20.051	error	(2315) unhandled promise rejection: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
maxcul.0	2020-05-23 13:10:20.050	error	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().
maxcul.0	2020-05-23 13:10:19.717	info	(2315) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.16.3, js-controller: 3.1.4
host.iobroker	2020-05-23 13:10:17.629	info	instance system.adapter.maxcul.0 started with pid 2315

                Jetzt läuft er auch gar nicht mehr, startet immer wieder neu.

                host.iobroker	2020-05-23 13:14:16.770	info	Do not restart adapter system.adapter.maxcul.0 because disabled or deleted
host.iobroker	2020-05-23 13:14:16.770	error	instance system.adapter.maxcul.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
host.iobroker	2020-05-23 13:14:16.769	error	Caught by controller[0]: Cannot load serialport module
maxcul.0	2020-05-23 13:14:16.229	warn	(2473) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
maxcul.0	2020-05-23 13:14:16.213	error	(2473) adapter disabled
host.iobroker	2020-05-23 13:14:13.558	info	"system.adapter.maxcul.0" disabled
host.iobroker	2020-05-23 13:13:43.918	info	Restart adapter system.adapter.maxcul.0 because enabled
host.iobroker	2020-05-23 13:13:43.917	info	instance system.adapter.maxcul.0 terminated with code 0 (NO_ERROR)
host.iobroker	2020-05-23 13:13:43.916	error	Caught by controller[0]: Cannot load serialport module
maxcul.0	2020-05-23 13:13:43.377	info	(2452) Terminated (NO_ERROR): Without reason
maxcul.0	2020-05-23 13:13:43.376	info	(2452) terminating
maxcul.0	2020-05-23 13:13:43.362	error	at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
maxcul.0	2020-05-23 13:13:43.362	error	at Module._compile (internal/modules/cjs/loader.js:1133:30)
maxcul.0	2020-05-23 13:13:43.362	error	at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/index.js:14:22)
maxcul.0	2020-05-23 13:13:43.362	error	at require (internal/modules/cjs/helpers.js:77:18)
maxcul.0	2020-05-23 13:13:43.362	error	at Module.require (internal/modules/cjs/loader.js:1019:19)
maxcul.0	2020-05-23 13:13:43.362	error	at Function.Module._load (internal/modules/cjs/loader.js:877:14)
maxcul.0	2020-05-23 13:13:43.362	error	at Module.load (internal/modules/cjs/loader.js:977:32)
maxcul.0	2020-05-23 13:13:43.362	error	at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
maxcul.0	2020-05-23 13:13:43.362	error	at Module._compile (internal/modules/cjs/loader.js:1133:30)
maxcul.0	2020-05-23 13:13:43.362	error	at Object.<anonymous> (/opt/iobroker/node_modules/@serialport/bindings/lib/linux.js:2:36)
maxcul.0	2020-05-23 13:13:43.362	error	at bindings (/opt/iobroker/node_modules/@serialport/bindings/node_modules/bindings/bindings.js:112:48)
maxcul.0	2020-05-23 13:13:43.362	error	at require (internal/modules/cjs/helpers.js:77:18)
maxcul.0	2020-05-23 13:13:43.362	error	at Module.require (internal/modules/cjs/loader.js:1019:19)
maxcul.0	2020-05-23 13:13:43.362	error	at Function.Module._load (internal/modules/cjs/loader.js:877:14)
maxcul.0	2020-05-23 13:13:43.362	error	at Module.load (internal/modules/cjs/loader.js:977:32)
maxcul.0	2020-05-23 13:13:43.362	error	at Object.Module._extensions..node (internal/modules/cjs/loader.js:1183:18)
maxcul.0	2020-05-23 13:13:43.362	error	(2452) Error: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
maxcul.0	2020-05-23 13:13:43.361	error	(2452) unhandled promise rejection: Module did not self-register: '/opt/iobroker/node_modules/@serialport/bindings/build/Release/bindings.node'.
Unhandled	2020-05-23 13:13:43.360	error	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().
maxcul.0	2020-05-23 13:13:42.993	info	(2452) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.16.3, js-controller: 3.1.4
host.iobroker	2020-05-23 13:13:40.372	info	instance system.adapter.maxcul.0 started with pid 2452

                Das sieht so aus, wie vor meinem

                iobroker rebuild maxcul --install

                Also bis jetzt keine Chance, er lief nicht mehr. Hab dann den NUC einmal komplett ausgeschaltet neu hochgefahren. Den Stick ab wieder dran, immer noch nichts.

                Nun hab ich noch mal's rebuild gemacht und er startet ohne Fehler.

                maxcul.0	2020-05-23 16:56:26.256	info	(1463) serialPort /dev/ttyUSB0 is open!
maxcul.0	2020-05-23 16:56:26.237	info	(1463) using serial device /dev/ttyUSB0@38400
maxcul.0	2020-05-23 16:56:25.892	info	(1463) starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.maxcul, node: v12.16.3, js-controller: 3.1.4
host.iobroker	2020-05-23 16:56:23.619	info	instance system.adapter.maxcul.0 started with pid 1463
host.iobroker	2020-05-23 16:56:23.582	info	"system.adapter.maxcul.0" enabled

                Er lief jetzt nen guten Tag ohne Probleme, dann fingen sie an.

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

                  @D3ltoroxp

                  Also scheinbar hat es das serialport zerhauen irgendwie. Geh mal in /opt/iobroker/node_modules/@serialport/ und ruf dort "npm rebuild" auf

                  D3ltoroxp 3 Replies Last reply Reply Quote 1
                  • D3ltoroxp
                    D3ltoroxp @apollon77 last edited by

                    @apollon77 said in js-controller 3.0/3.1 jetzt im Latest!:

                    /@serialport/

                    Blöde Frage, wie gebe ich in der Konsole @ ein ? Ich komme in diesen Ordner nicht rein, auch wenn ich @serialport/ kopiere..

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @D3ltoroxp last edited by Thomas Braun

                      @D3ltoroxp AltGr-Q ?
                      Blöde Gegenfrage: Wie soll man das denn auch sonst eingeben?

                      D3ltoroxp 1 Reply Last reply Reply Quote 1
                      • D3ltoroxp
                        D3ltoroxp @Thomas Braun last edited by D3ltoroxp

                        @Thomas-Braun Also ich kenne es mit strg-alt-q.

                        Da lief ganz schön was durch, normal ? Kleiner ausschnitt !! Davor auch noch jede Menge anderes, mit türkiser, lila, gelber Schrift, aber das hats mir abgeschnitten.

                        cert-info@1.5.1 /opt/iobroker/node_modules/cert-info
greenlock-store-fs@3.2.2 /opt/iobroker/node_modules/greenlock-store-fs
safe-replace@1.1.0 /opt/iobroker/node_modules/safe-replace
le-challenge-fs@2.0.9 /opt/iobroker/node_modules/le-challenge-fs
le-sni-auto@2.1.9 /opt/iobroker/node_modules/le-sni-auto
le-store-certbot@2.2.3 /opt/iobroker/node_modules/le-store-certbot
pyconf@1.1.7 /opt/iobroker/node_modules/pyconf
js2xmlparser@4.0.1 /opt/iobroker/node_modules/js2xmlparser
xmlcreate@2.0.3 /opt/iobroker/node_modules/xmlcreate
luxon@1.22.2 /opt/iobroker/node_modules/luxon
memory-pager@1.5.0 /opt/iobroker/node_modules/memory-pager
node-addon-api@2.0.0 /opt/iobroker/node_modules/node-addon-api
saslprep@1.0.3 /opt/iobroker/node_modules/saslprep
sparse-bitfield@3.0.3 /opt/iobroker/node_modules/sparse-bitfield
unix-dgram@2.0.3 /opt/iobroker/node_modules/unix-dgram
ursa-optional@0.9.10 /opt/iobroker/node_modules/ursa-optional
winston-syslog@2.4.4 /opt/iobroker/node_modules/winston-syslog
vm2@3.9.2 /opt/iobroker/node_modules/vm2
bcrypt@3.0.6 /opt/iobroker/node_modules/bcrypt
nan@2.13.2 /opt/iobroker/node_modules/bcrypt/node_modules/nan
node-pre-gyp@0.12.0 /opt/iobroker/node_modules/node-pre-gyp
tar@4.4.13 /opt/iobroker/node_modules/node-pre-gyp/node_modules/tar
fs-minipass@1.2.7 /opt/iobroker/node_modules/node-pre-gyp/node_modules/fs-minipa                                     ss
minipass@2.9.0 /opt/iobroker/node_modules/node-pre-gyp/node_modules/minipass
yallist@3.1.1 /opt/iobroker/node_modules/node-pre-gyp/node_modules/yallist
minizlib@1.3.3 /opt/iobroker/node_modules/node-pre-gyp/node_modules/minizlib
mdns@2.5.1 /opt/iobroker/node_modules/mdns
bindings@1.2.1 /opt/iobroker/node_modules/mdns/node_modules/bindings
mongodb@3.5.7 /opt/iobroker/node_modules/mongodb
bl@2.2.0 /opt/iobroker/node_modules/mongodb/node_modules/bl
require_optional@1.0.1 /opt/iobroker/node_modules/require_optional
resolve-from@2.0.0 /opt/iobroker/node_modules/require_optional/node_modules/reso                                     lve-from
le-acme-core@2.1.4 /opt/iobroker/node_modules/le-acme-core
rsa-compat@1.9.4 /opt/iobroker/node_modules/le-acme-core/node_modules/rsa-compat
node-forge@0.7.6 /opt/iobroker/node_modules/le-acme-core/node_modules/node-forge
sharp@0.25.2 /opt/iobroker/node_modules/sharp
color@3.1.2 /opt/iobroker/node_modules/sharp/node_modules/color
semver@7.3.2 /opt/iobroker/node_modules/sharp/node_modules/semver
smarthome@iobroker:/opt/iobroker/node_modules/@serialport$

                        Ist auf jeden Fall durchgelaufen, ich beobachte mal die Log.

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @D3ltoroxp last edited by Thomas Braun

                          @D3ltoroxp

                          Also ich kenne es mit strg-alt-q.

                          Da bricht man sich ja die Finger bei...

                          Da fehlt die Eingabezeile... Woher soll denn jetzt hier jemand wissen was du da eingegeben hast?

                          D3ltoroxp 1 Reply Last reply Reply Quote 0
                          • D3ltoroxp
                            D3ltoroxp @Thomas Braun last edited by

                            @Thomas-Braun Leider komm ich so nicht mehr zurück.. Habe bis hoch gescrollt. Auf jeden Fall in

                            opt/iobroker/node_modules/@serialport$ npm rebuild
                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @D3ltoroxp last edited by

                              @D3ltoroxp Dann hat die Kiste da jetzt rumgebaut.

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

                                @apollon77 said in js-controller 3.0/3.1 jetzt im Latest!:

                                Also scheinbar hat es das serialport zerhauen irgendwie. Geh mal in /opt/iobroker/node_modules/@serialport/ und ruf dort "npm rebuild" auf

                                Sollte ich ja so machen. Also passt das dann, wenn er dort jede menge umgebaut hat ? Hätte mit 2-3 Zeilen gerechnet. Aber das das soviel wurde.

                                Kann dabei was schief gehen, oder sollte das alles noch passen ? Da war ja irgendwie alles Dabei, zigbee, tr064 usw.

                                Thomas Braun Garfonso 2 Replies Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @D3ltoroxp last edited by

                                  @D3ltoroxp Siehst du ja, wenn der entsprechende Adapter startet.

                                  1 Reply Last reply Reply Quote 1
                                  • Garfonso
                                    Garfonso Developer @D3ltoroxp last edited by

                                    @D3ltoroxp
                                    npm rebuild kann (eigentlich) nichts kaputt machen. Bei den meisten Paketen wird er vermutlich einfach gemerkt haben, dass es nichts zu bauen gibt. Ich glaube das gezieltere Kommando wäre npm rebuild @serialport gewesen in /opt/iobroker ausgeführt. Aber am Ende ist es egal. 😉

                                    apollon77 1 Reply Last reply Reply Quote 1
                                    • apollon77
                                      apollon77 @Garfonso last edited by

                                      @Garfonso Naja ich hab ja gesagt in welches Verzeichnis er soll ... dann wird an sich nur "Lokal" rebuild gemacht 🙂

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        steimi last edited by steimi

                                        ich weiss nicht ob der Fehler zum js-Controller gehört...
                                        er kommt regelmäßig jeden Tag um 02:00 Uhr

                                        2020-05-25 02:00:22.221 - warn: host.iobroker-01 Objects 127.0.0.1:50160 Error from InMemDB: Error: ERROR readDir id=0_userdata.0: Not exists
2020-05-25 02:00:22.222 - warn: host.iobroker-01 Objects 127.0.0.1:50160 Error from InMemDB: Error: ERROR readDir id=admin.0: Not exists
2020-05-25 02:00:22.223 - warn: host.iobroker-01 Objects 127.0.0.1:50160 Error from InMemDB: Error: ERROR readDir id=material.0: Not exists
2020-05-25 02:00:22.223 - warn: host.iobroker-01 Objects 127.0.0.1:50160 Error from InMemDB: Error: ERROR readDir id=web.0: Not exists
                                        apollon77 1 Reply Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 @steimi last edited by

                                          @steimi Such mal hier in diesem Thread, wurde schon mehrfach behandelt

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            steimi @Dr. Bakterius last edited by

                                            @apollon77 sorry und Danke, habs gefunden

                                            Einfach die bemängelten fehlenden Ordner in '/opt/iobroker/iobroker-data/files/' (bei Standardinstallation) erstellen und die Warnungen sind weg.

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

                                            Support us

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

                                            914
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            127
                                            1340
                                            413386
                                            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