Navigation

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

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    js-controller 4.0 jetzt im BETA/LATEST!

    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      e-i-k-e @paul53 last edited by

      @paul53
      Ach oaky! Das erklärt das natürlich.

      Nur wie behebe ich den Fehler @apollon77 ?

      1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 @e-i-k-e last edited by

        @e-i-k-e hi, hier muss der binäre Teil neu ge auth. werden. Hast du mal da volle log? An sich sollte er jetzt bis zu drei mal versuchen über rebuilds das zu fixen

        E 1 Reply Last reply Reply Quote 0
        • ice987
          ice987 last edited by

          ich hab' mich auch versucht mit dem
          System: ioBroker.docker v6.0.0
          und erhalte folgende Fehlermeldung:

          root@iobroker-v600-testsystem7:/opt/iobroker# pkill -u iobroker
          root@iobroker-v600-testsystem7:/opt/iobroker# iobroker update
          Used repository: latest
          hash unchanged, use cached sources
          update done
          Adapter    "admin"         : 5.2.3    , installed 5.1.25 [Updateable]
          Controller "js-controller" : 4.0.4    , installed 3.3.21 [Updateable]
          root@iobroker-v600-testsystem7:/opt/iobroker# iobroker upgrade self
          Update js-controller from @3.3.21 to @4.0.4
          NPM version: 6.14.16
          npm install iobroker.js-controller@4.0.4 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
          In file included from ../../nan/nan.h:58,
                           from ../src/unix_dgram.cc:5:
          /opt/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
            793 |       (node::addon_register_func) (regfunc),                          \
                |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          /opt/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
            827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                |   ^~~~~~~~~~~~~
          ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
            404 | NODE_MODULE(unix_dgram, Initialize)
                | ^~~~~~~~~~~
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
          Server States 127.0.0.1:45560 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
          Server States 127.0.0.1:45562 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: Unknown LUA script load
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: Unknown LUA script load
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: Unknown LUA script load
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
          Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: multi NOT SUPPORTED
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: sadd NOT SUPPORTED
          Server Objects 127.0.0.1:36016 Error from InMemDB: Error: exec NOT SUPPORTED
          root@iobroker-v600-testsystem7:/opt/iobroker# iobroker upgrade
          
          This upgrade of "admin" will introduce the following changes:
          ==========================================================================
          -> 5.2.3:
          Fixed error in `AutocompleteSendTo`
          Fixed error in charts
          
          -> 5.2.2:
          Changed the minimal required js-controller version to 3.3.22 
          Used web-socket library 8 (no node 10 support anymore)
          
          -> 5.2.1:
          Allow in expert mode the creation of states and channels in mqtt branch
          
          -> 5.2.0:
          Fix crash cases reported via sentry
          Added support for multi-repositories
          
          -> 5.1.29:
          Fix crash cases reported via sentry
          Added support for multi-repositories
          
          -> 5.1.28:
          Fixed discovery function
          Fixed some GUI bugs
          ==========================================================================
          
          Would you like to upgrade admin from @5.1.25 to @5.2.3 now? [(y)es, (n)o]: y
          Update admin from @5.1.25 to @5.2.3
          host.iobroker-v600-testsystem7 Adapter "system.adapter.admin.0" is stopped.
          NPM version: 6.14.16
          Installing iobroker.admin@5.2.3... (System call)
          + iobroker.admin@5.2.3
          updated 7 packages in 32.186s
          
          17 packages are looking for funding
            run `npm fund` for details
          
          host.iobroker-v600-testsystem7 Adapter "system.adapter.admin.0" is started
          Update "system.adapter.admin.0"
          upload [14] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png
          upload [13] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/de/translations.json i18n/de/translations.json application/json
          upload [12] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/en/translations.json i18n/en/translations.json application/json
          upload [11] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/es/translations.json i18n/es/translations.json application/json
          upload [10] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
          upload [9] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/it/translations.json i18n/it/translations.json application/json
          upload [8] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
          upload [7] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
          upload [6] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
          upload [5] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
          upload [4] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
          upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html
          upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html
          upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/jsonConfig.json jsonConfig.json application/json
          upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript
          root@iobroker-v600-testsystem7:/opt/iobroker# iobroker start
          Starting iobroker controller daemon...
          iobroker controller daemon started. PID: 1425
          

          ioBroker ist nicht zu erreichen

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

            @ice987 ok was steht im log? Ich Seherin den Ausgaben keine Fehler. Da ist an sich alles ok

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

              @apollon77

              der Restart vom Container ergibt nun:

              --------------------------------------------------------------------------------
              -------------------------     2022-02-06 15:04:25      -------------------------
              --------------------------------------------------------------------------------
               
              --------------------------------------------------------------------------------
              -----                 Welcome to your ioBroker-container!                  -----
              -----                    Startupscript is now running.                     -----
              -----                          Please be patient!                          -----
              --------------------------------------------------------------------------------
               
              --------------------------------------------------------------------------------
              -----                        Debugging information                         -----
              -----                                                                      -----
              -----                                System                                -----
              -----                    arch:                x86_64                       -----
              -----                                                                      -----
              -----                             Docker-Image                             -----
              -----                    image:               v6.0.0                       -----
              -----                    build:               2021-12-17T03:48:21+00:00    -----
              -----                                                                      -----
              -----                               Versions                               -----
              -----                    /opt/scripts/iobroker_startup.sh: line 48: /usr/bin/node: Operation not permitted
              node:                                             -----
              -----                    /usr/bin/env: ‘node’: Operation not permitted
              npm:                                              -----
              -----                                                                      -----
              -----                                 ENV                                  -----
              -----                    SETGID:              1000                         -----
              -----                    SETUID:              1000                         -----
              --------------------------------------------------------------------------------
               
              --------------------------------------------------------------------------------
              -----                  Step 1 of 5: Preparing container                   -----
              --------------------------------------------------------------------------------
               
              Nothing to do here.
               
              --------------------------------------------------------------------------------
              -----             Step 2 of 5: Detecting ioBroker installation             -----
              --------------------------------------------------------------------------------
               
              Existing installation of ioBroker detected in /opt/iobroker.
               
              --------------------------------------------------------------------------------
              -----             Step 3 of 5: Checking ioBroker installation              -----
              --------------------------------------------------------------------------------
               
              (Re)Setting folder permissions (This might take a while! Please be patient!)...
              Done.
               
              Fixing "sudo-bug" by replacing sudo in iobroker with gosu...
              Done.
               
              error: exec failed: operation not permitted
              /opt/scripts/iobroker_startup.sh: line 199: [: !=: unary operator expected
              --------------------------------------------------------------------------------
              -----                Step 4 of 5: Applying special settings                -----
              --------------------------------------------------------------------------------
               
              Some adapters have special requirements/ settings which can be activated by the use of environment variables.
              For more information take a look at readme.md on Github!
               
              --------------------------------------------------------------------------------
              -----                    Step 5 of 5: ioBroker startup                     -----
              --------------------------------------------------------------------------------
               
              Starting ioBroker...
               
              error: exec failed: operation not permitted
              
              1 Reply Last reply Reply Quote 0
              • apollon77
                apollon77 @Chaot last edited by

                @chaot was ist denn de ubuntu Adapter? Und was gefällt ihm nicht?

                Chaot 1 Reply Last reply Reply Quote 0
                • ste_glei
                  ste_glei @ice987 last edited by

                  @ice987
                  Ich hatte den gleichen log

                  iobroker fix
                  

                  hat geholfen

                  ice987 1 Reply Last reply Reply Quote 0
                  • E
                    e-i-k-e @apollon77 last edited by

                    @apollon77
                    Hallo,
                    anbei wie gewünscht die komplette log.
                    b04d2521-d6ec-46a9-ab5a-18d5ad80331e-iobroker.2022-02-06.log

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

                      @ste_glei
                      kann ich bestätigen:

                      iobroker fix
                      

                      hilft und ioBroker läuft nun

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

                        @apollon77 Das ist ne uralte Leiche die mitgelaufen ist.
                        https://github.com/Standarduser/ioBroker.ubuntu
                        Ist mir nie aufgefallen dass das noch aktiv ist.
                        Meinerseits bereits entsorgt, da überflüssig.
                        Ausgegebener Fehler:

                        
                        ubuntu.0
                        2022-02-06 12:57:13.847	error	Cannot read property 'getObjectList' of undefined
                        ubuntu.0
                        2022-02-06 12:57:13.846	error	TypeError: Cannot read property 'getObjectList' of undefined at Object.ready (/opt/iobroker/node_modules/iobroker.ubuntu/main.js:35:25) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8225:68
                        ubuntu.0
                        2022-02-06 12:57:13.842	error	unhandled promise rejection: Cannot read property 'getObjectList' of undefined
                        ubuntu.0
                        2022-02-06 12:57:13.837	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().
                        
                        amg_666 apollon77 2 Replies Last reply Reply Quote 1
                        • amg_666
                          amg_666 @Chaot last edited by

                          Eben den latest/Beta runtergeladen, einmal Raspi Slave, ohne Probleme und danach auf Proxmox/Debian, biedes ohne irgendwelche Probleme.

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

                            @chaot Naja,d er Hätte mit controller 3.x schon Fehler wegen "adapter.objects.getObjectList" loggen müssen und muss angepasst werden. Leg doch mal ein issue an

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

                              @ice987 Verstehe ich nicht weil der Container macht eigentlich genauein Fix beim startup soweit ich weiss ... also das wäre interessant das sich das Andre mal anschaut

                              ice987 F 3 Replies Last reply Reply Quote 0
                              • apollon77
                                apollon77 @e-i-k-e last edited by

                                @e-i-k-e Ahhh der RPI2 Adapter ist "zu nett" und fängt den Fehler so ab das der Rebuild Mechanismus vom Controller nicht greifen kann. Willste mal was versuchen?

                                Editiere mal /opt/iobroker/node_modules/iobroker.rp2/main.js und füge bei Zeile 648 das hinzu https://github.com/iobroker-community-adapters/ioBroker.rpi2/blob/master/main.js#L648

                                Danach bitte adapter neu starten ... Dann schauen wir mal was das System so macht. Hätte dann gern das log. Also er sollte - wenn er sich dann wegen dem Folgefehler beendet - der Controller sagen das er rebuild machen will ... bis zu 3x !!

                                frankthegreat E 2 Replies Last reply Reply Quote 1
                                • Chaot
                                  Chaot @apollon77 last edited by

                                  @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                  .... Leg doch mal ein issue an

                                  Beim Adapter? Der wird scheinbar seit 3 Jahren nicht mehr gepflegt bzw. ist nie über die eine Version hinausentwickelt worden. Letzte Aktivität 20.01.2019
                                  Ist eher sinnlos. Löschen und nicht darüber nachdenken.

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

                                    @chaot Jo ... aber dann sehen es andere das es bekannt ist 🙂

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

                                      @apollon77
                                      Update auf 4.0.4 auf meinem Testsystem sauber durchgelaufen. 👍

                                      Was mir auf die Schnelle aufgefallen ist:
                                      Die "Clean" Befehle zicken rum. Weis aber nicht, ob es damit zusammenhängt. Mit der 3.0.3 ging das denk ich.

                                      pi@raspberrypi:~ $ iob stop
                                      pi@raspberrypi:~ $ Sudo apt-get clean
                                      -bash: Sudo: Kommando nicht gefunden.
                                      pi@raspberrypi:~ $ Sudo apt-get autoclean
                                      -bash: Sudo: Kommando nicht gefunden.
                                      
                                      
                                      apollon77 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @frankthegreat last edited by

                                        @frankthegreat Also jetzt langsam ....

                                        1.) "apt" ist ein Linux kommando und hat mit ioBroker NICHTS zu tun
                                        2.) Steht genau da was das issue is ... "Sudo" gibts nicht ... weil heisst "sudo"

                                        frankthegreat 1 Reply Last reply Reply Quote 0
                                        • E
                                          e-i-k-e @apollon77 last edited by e-i-k-e

                                          @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                          l ... bis zu 3x !!

                                          Ja gerne! Allerdings endet meine Datei bei Zeile 525. 😕
                                          cb4f762f-0e18-47f5-8016-a54e92ccd659-main.js

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

                                            @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                            @frankthegreat Also jetzt langsam ....

                                            "Sudo" gibts nicht ... weil heisst "sudo"

                                            Ahh, sorry, sch... Rechtschreibkorrektur in Word 😉

                                            Läuft jetzt.

                                            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

                                            602
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            70
                                            747
                                            150501
                                            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