Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Ich weis nicht mehr weiter!

    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

    Ich weis nicht mehr weiter!

    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      pskiel last edited by Homoran

      Moin Moin,

      nach dem Update bekomme ich den IOBroker nicht mehr zum laufen!

      Auch eine neue Installation bringt mir diesen Fehler! Kann mir einer einen Tipp Geben?
      Raspberry 4 ist am Start. und ext. Festplatte, läuft aber auch auf der SD Karte nicht.

      
          Installing ioBroker (3/4)
      ==========================================================================
      
      In file included from ../../nan/nan.h:58,
                       from ../src/main.cpp:3:
      /home/pi/.cache/node-gyp/12.22.5/include/node/node.h:736:43: 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]
             (node::addon_register_func) (regfunc),                          \
                                                 ^
      /home/pi/.cache/node-gyp/12.22.5/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’
         NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
         ^~~~~~~~~~~~~
      ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’
       NODE_MODULE(diskusage, Init)
       ^~~~~~~~~~~
      In file included from ../../nan/nan.h:58,
                       from ../src/unix_dgram.cc:5:
      /home/pi/.cache/node-gyp/12.22.5/include/node/node.h:736:43: 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]
             (node::addon_register_func) (regfunc),                          \
                                                 ^
      /home/pi/.cache/node-gyp/12.22.5/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’
         NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
         ^~~~~~~~~~~~~
      ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
       NODE_MODULE(unix_dgram, Initialize)
       ^~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:78:69: 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]
         uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
                                                                           ^~~~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:135:71: 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]
         uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
                                                                             ^~~~~~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:175:70: 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]
         uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
                                                                            ^~~~~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:215:70: 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]
         uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
                                                                            ^~~~~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:271:68: 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]
         uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
                                                                          ^~~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:316:68: 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]
         uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
                                                                          ^~~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:366:76: 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]
         uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
                                                                                  ^~~~~~~~~~~~~~~~~~~~
      ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
      ../src/serialport.cpp:412:70: 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]
         uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                                                                            ^~~~~~~~~~~~~~
      ../src/serialport.cpp: At global scope:
      ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
       SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
                                  ^
      ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
       SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                                    ^
      In file included from ../../../nan/nan.h:58,
                       from ../src/./serialport.h:13,
                       from ../src/serialport.cpp:1:
      /home/pi/.cache/node-gyp/12.22.5/include/node/node.h:736:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
             (node::addon_register_func) (regfunc),                          \
                                                 ^
      /home/pi/.cache/node-gyp/12.22.5/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’
         NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
         ^~~~~~~~~~~~~
      ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’
       NODE_MODULE(serialport, init);
       ^~~~~~~~~~~
      ../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’:
      ../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=]
           snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~
      ../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024
           snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
           ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’:
      ../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=]
           snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
                                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~
      ../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024
           snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
           ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      ATTENTION: Error reporting via Sentry will be activated on next start of ioBroker
      
      ioBroker wants to make sure to deliver the most stable smart home system.
      To allow this we decided to implement an automatic error and crash reporting solution into the js-controller and also into adapters.
      
      THIS REPORTING WILL BE ENABLED WITH THE NEXT START OF YOUR IOBROKER!
      
      For any error that leads to the crash of the js-controller or one of the relevant adapters the error details are send to a server. For the js-controller and core adapters this server is located and operated in germany. For community adapters please check the Github Readme of the affected adapter for details which Sentry server is used.
      
      If you want to disable the error reporting you can use the command
      'iobroker plugin disable sentry'
      This command will also make sure that no adapter that runs on this host will send crash reporting data to sentry.
      

      MOD-Edit: Code in code-tags gesetzt!

      Homoran 1 Reply Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @pskiel last edited by

        @pskiel sagte in Ich weis nicht mehr weiter!:

        Auch eine neue Installation bringt mir diesen Fehler! Kann mir einer einen Tipp Geben?

        Geduld!
        da ist kein Fehler. Da läuft die Installation noch im Hintergrund weiter.
        Das dauert schon ein paar Minuten, dann erscheint auch wieder was auf dem Schirm

        P 1 Reply Last reply Reply Quote 0
        • P
          pskiel @Homoran last edited by Homoran

          @homoran ok , herzlichen Dank, nun scheint es durch zu sein, aber ich komme nun nicht auf die htts://192.xxx.xxx.xxx:8081

          die Instance lebt

          pi@raspberrypi:/opt/iobroker $ iobroker start
          pi@raspberrypi:/opt/iobroker $ node -v
          v12.22.5
          pi@raspberrypi:/opt/iobroker $ npm -v
          6.14.14
          pi@raspberrypi:/opt/iobroker $ iobroker list instances
          
          
          + instance is alive
          

          MOD-Edit: Code in code-tags gesetzt!

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

            @pskiel

            Bitte Konsolentext in CodeTags einbetten.

            iobroker list adapters
            iobroker status
            
            P 1 Reply Last reply Reply Quote 0
            • P
              pskiel @Thomas Braun last edited by

              @thomas-braun

              Entschuldigung, ich lerne noch 🙂

              pi@raspberrypi:/opt/iobroker $ iobroker start
              pi@raspberrypi:/opt/iobroker $ node -v
              v12.22.5
              pi@raspberrypi:/opt/iobroker $ npm -v
              6.14.14
              pi@raspberrypi:/opt/iobroker $ iobroker list instances
              
              
              + instance is alive
              
              
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @pskiel last edited by

                @pskiel

                Da läuft nix.
                Bitte noch

                iobroker list adapters
                iobroker status
                

                nachreichen.

                P 2 Replies Last reply Reply Quote 0
                • P
                  pskiel @Thomas Braun last edited by pskiel

                  @thomas-braun said in Ich weis nicht mehr weiter!:

                  pi@raspberrypi:/opt/iobroker $ iobroker status
                  iobroker is running on this host.
                  
                  
                  Objects type: file
                  States  type: file
                  pi@raspberrypi:/opt/iobroker $ iobroker list adapters
                  pi@raspberrypi:/opt/iobroker $
                  
                  
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • P
                    pskiel @Thomas Braun last edited by

                    @thomas-braun

                    pi@raspberrypi:/opt/iobroker $ iobroker status
                    iobroker is running on this host.
                    
                    
                    Objects type: file
                    States  type: file
                    pi@raspberrypi:/opt/iobroker $ iobroker list adapters
                    pi@raspberrypi:/opt/iobroker $
                    
                    
                    1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @pskiel last edited by

                      @pskiel

                      Da sind überhaupt keine Adapter hinterlegt.
                      Versuch mal

                      iobroker add admin
                      iobroker start admin
                      
                      P 1 Reply Last reply Reply Quote 0
                      • P
                        pskiel @Thomas Braun last edited by pskiel

                        @thomas-braun

                        ich habe ja schon mit iobroker gearbeitet, aber anscheint bin ich zu blöd geworden! Oder beim ersten Mal ohne Probleme durchgelaufen! Ab es bewahrheitet sich "“Never change a running system”"

                        pi@raspberrypi:/opt/iobroker $ iobroker start admin
                        Cannot find any instances of "admin"!
                        
                        

                        Ich habe es nun gelöscht und installiere NEU!

                        Herzlichen Dank und schönen Sonntag

                        Homoran 1 Reply Last reply Reply Quote 0
                        • Homoran
                          Homoran Global Moderator Administrators @pskiel last edited by

                          @pskiel sagte in Ich weis nicht mehr weiter!:

                          die Instance lebt

                          nope! da lebt gar nix

                          1 Reply Last reply Reply Quote 0
                          • Homoran
                            Homoran Global Moderator Administrators @pskiel last edited by

                            @pskiel sagte in Ich weis nicht mehr weiter!:

                            Ab es bewahrheitet sich "“Never change a running system”"

                            absolut falscher Ansatz in der schnelllebigen Smarthome Thematik!

                            @pskiel sagte in Ich weis nicht mehr weiter!:

                            Ich habe es nun gelöscht und installiere NEU!

                            bitte wie hast du es denn zuletzt gemacht?

                            P Meister Mopper 2 Replies Last reply Reply Quote 0
                            • P
                              pskiel @Homoran last edited by

                              @homoran

                              ich habe es nun NEU aufgesetzt und nun läuft es.... nur!! noch die Sicherung einspielen... OH MANN und drei Kreuze machen.

                              Homoran 1 Reply Last reply Reply Quote 0
                              • Homoran
                                Homoran Global Moderator Administrators @pskiel last edited by

                                @pskiel sagte in Ich weis nicht mehr weiter!:

                                ch habe es nun NEU aufgesetzt und nun läuft es.... nur!! noch die Sicherung einspielen...

                                so sollte es sein.
                                Aber bitte etwa 1-2 Stunden Zeit einplanen, bis alles wieder sauber nachinstalliert wurde

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  pskiel @Homoran last edited by

                                  @homoran naja 2 -3 Stunden wir nichts, ich glaube eher an 2 - 3 Tage 😉

                                  LG Peter

                                  Homoran 1 Reply Last reply Reply Quote 0
                                  • Meister Mopper
                                    Meister Mopper @Homoran last edited by

                                    @homoran sagte in Ich weis nicht mehr weiter!:

                                    absolut falscher Ansatz in der schnelllebigen Smarthome Thematik!

                                    @pskiel
                                    Und insbesondere in der Sicherheitsproblematik 🤦‍♂️

                                    1 Reply Last reply Reply Quote 0
                                    • Homoran
                                      Homoran Global Moderator Administrators @pskiel last edited by

                                      @pskiel sagte in Ich weis nicht mehr weiter!:

                                      naja 2 -3 Stunden wir nichts, ich glaube eher an 2 - 3 Tage
                                      LG Peter

                                      wieso?

                                      Der Restore geht relativ schnell bis das System sagt: "restore completetd" (oder ähnlich)

                                      Damit sind aber nur die Konfigurationsdateien, die VIS, die Scripte und die Objects eingelesen.
                                      Alle Instanzen werden neu installiert. Das dauert auf einem Pi4 je nach Umfang der Installation etwa 1-2 Stunden in denen du nichts am System ändern solltest.

                                      Danach ist alles wieder beim "alten".

                                      P 1 Reply Last reply Reply Quote 0
                                      • P
                                        pskiel @Homoran last edited by

                                        @homoran
                                        Wenn es denn so einfach ist...nur nicht bei mir!

                                        pi@raspberrypi:/opt/iobroker $ iobroker stop
                                        pi@raspberrypi:/opt/iobroker $ iobroker restore 0
                                        host.raspberrypi Using backup file iobroker_2021_07_05-02_40_10_backupiobroker.tar.gz
                                        iobroker controller daemon is not running
                                        host.raspberrypi OK.
                                        
                                        <--- Last few GCs --->
                                        
                                        [1111:0x21a4388]    15599 ms: Mark-sweep 471.1 (472.6) -> 471.2 (473.9) MB, 287.4 / 0.0 ms  (average mu = 0.172, current mu = 0.083) allocation failure scavenge might not succeed
                                        [1111:0x21a4388]    15925 ms: Mark-sweep 472.4 (473.9) -> 472.4 (474.6) MB, 170.8 / 0.0 ms  (+ 119.0 ms in 6 steps since start of marking, biggest step 82.2 ms, walltime since start of marking 303 ms) (average mu = 0.142, current mu = 0.110) allocation fa
                                        
                                        <--- JS stacktrace --->
                                        
                                        ==== JS stack trace =========================================
                                        
                                        Security context: 0x2ff8ea35 <JSObject>
                                            0: builtin exit frame: parse(this=0x2ff865bd <Object map = 0x44080a15>,0x916c008d <Very long string[106779942]>,0x2ff865bd <Object map = 0x44080a15>)
                                        
                                            1: restoreAfterStop [0x2e4dc279] [/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:649] [bytecode=0x2e4f4ba1 offset=161](this=0x244ac9d9 <BackupRestore map = 0x4c610d25>,0x3a8803c1 <false>,0x244ac9bd <JSFunction (sfi ...
                                        
                                        FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                                        /usr/bin/iobroker: Zeile 8:  1110 Abgebrochen             sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@"
                                        pi@raspberrypi:/opt/iobroker $ iobroker start all
                                        pi@raspberrypi:/opt/iobroker $ iobroker start
                                        
                                        
                                        Homoran 1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators @pskiel last edited by

                                          @pskiel sagte in Ich weis nicht mehr weiter!:

                                          nur nicht bei mir!

                                          was ist denn bei dir anders als bei anderen?

                                          @pskiel sagte in Ich weis nicht mehr weiter!:

                                          JavaScript heap out of memory

                                          was sagt
                                          htop

                                          P 1 Reply Last reply Reply Quote 0
                                          • P
                                            pskiel @Homoran last edited by

                                            @homoran

                                            nur der Kopf

                                            MEM 229M/1.83G

                                            Sollte reichen

                                            Homoran 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

                                            669
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            4
                                            37
                                            1561
                                            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