Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] mal wieder: No connection to databases possible ...

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    [gelöst] mal wieder: No connection to databases possible ...

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

      @dgr

      CodeTags verwenden:

      code_text
      

      7fccdd42-a74e-403d-8393-e5ef80f678d8-image.png

      Text zwischen die Steuerzeichen kopieren, code_text ersetzend.

      D 1 Reply Last reply Reply Quote 0
      • D
        DGR @Thomas Braun last edited by Homoran

        @thomas-braun

        sudo -H -u iobroker npm install iobroker.js-controller
        npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
        
        > iobroker.js-controller@4.0.21 preinstall /opt/iobroker/node_modules/iobroker.js-controller
        > node lib/preinstallCheck.js
        
        NPM version: 6.14.16
        
        > authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
        > node-gyp rebuild
        
        make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
          CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
        In file included from ../authenticate_pam.cc:23:
        ../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
        ../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
             , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                      ^
        ../authenticate_pam.cc: In function ‘void after_doing_auth(uv_work_t*, int)’:
        ../authenticate_pam.cc:107:87: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
           Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                                                                               ^
        In file included from ../authenticate_pam.cc:23:
        ../../nan/nan.h:1024:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
        ../authenticate_pam.cc:107:87: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
           Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                                                                               ^
        In file included from ../authenticate_pam.cc:23:
        ../../nan/nan.h:1024:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
        ../authenticate_pam.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)’:
        ../authenticate_pam.cc:147:83: error: no matching function for call to ‘v8::Array::Get(v8::Local<v8::String>)’
           Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
                                                                                           ^
        In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67,
                         from ../../nan/nan.h:54,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3717:43: note: candidate: ‘v8::MaybeLocal<v8::Value> v8::Object::Get(v8::Local<v8::Context>, v8::Local<v8::Value>)’
           V8_WARN_UNUSED_RESULT MaybeLocal<Value> Get(Local<Context> context,
                                                   ^~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3717:43: note:   candidate expects 2 arguments, 1 provided
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3720:43: note: candidate: ‘v8::MaybeLocal<v8::Value> v8::Object::Get(v8::Local<v8::Context>, uint32_t)’
           V8_WARN_UNUSED_RESULT MaybeLocal<Value> Get(Local<Context> context,
                                                   ^~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3720:43: note:   candidate expects 2 arguments, 1 provided
        ../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
            serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
                                                                             ^
        In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67,
                         from ../../nan/nan.h:54,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
           int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
               ^~~~~~~~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
        ../authenticate_pam.cc:152:69: error: no matching function for call to ‘v8::Array::Get(v8::Local<v8::String>)’
           res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
                                                                             ^
        In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67,
                         from ../../nan/nan.h:54,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3717:43: note: candidate: ‘v8::MaybeLocal<v8::Value> v8::Object::Get(v8::Local<v8::Context>, v8::Local<v8::Value>)’
           V8_WARN_UNUSED_RESULT MaybeLocal<Value> Get(Local<Context> context,
                                                   ^~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3717:43: note:   candidate expects 2 arguments, 1 provided
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3720:43: note: candidate: ‘v8::MaybeLocal<v8::Value> v8::Object::Get(v8::Local<v8::Context>, uint32_t)’
           V8_WARN_UNUSED_RESULT MaybeLocal<Value> Get(Local<Context> context,
                                                   ^~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3720:43: note:   candidate expects 2 arguments, 1 provided
        ../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
            remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
                                                                          ^
        In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67,
                         from ../../nan/nan.h:54,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
           int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
               ^~~~~~~~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
        ../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
          username->WriteUtf8(m->username, sizeof(m->username) - 1);
                                                                  ^
        In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67,
                         from ../../nan/nan.h:54,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
           int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
               ^~~~~~~~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
        ../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], unsigned int)’
          password->WriteUtf8(m->password, sizeof(m->password) - 1);
                                                                  ^
        In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67,
                         from ../../nan/nan.h:54,
                         from ../authenticate_pam.cc:23:
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note: candidate: ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’
           int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
               ^~~~~~~~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3037:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
        ../authenticate_pam.cc: At global scope:
        ../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void
         void init(Handle<Object> exports) {
                   ^~~~~~
        ../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope
        ../authenticate_pam.cc:170:11: note: suggested alternative: ‘rand_r’
         void init(Handle<Object> exports) {
                   ^~~~~~
                   rand_r
        ../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token
         void init(Handle<Object> exports) {
                                ^
        ../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope
         void init(Handle<Object> exports) {
                                  ^~~~~~~
        In file included from ../../nan/nan.h:54,
                         from ../authenticate_pam.cc:23:
        ../authenticate_pam.cc:175:31: error: ‘init’ was not declared in this scope
         NODE_MODULE(authenticate_pam, init);
                                       ^~~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:36: note: in definition of macro ‘NODE_MODULE_X’
               (node::addon_register_func) (regfunc),                          \
                                            ^~~~~~~
        ../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
         NODE_MODULE(authenticate_pam, init);
         ^~~~~~~~~~~
        ../authenticate_pam.cc:175:31: note: suggested alternative: ‘int’
         NODE_MODULE(authenticate_pam, init);
                                       ^~~~
        /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:36: note: in definition of macro ‘NODE_MODULE_X’
               (node::addon_register_func) (regfunc),                          \
                                            ^~~~~~~
        ../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
         NODE_MODULE(authenticate_pam, init);
         ^~~~~~~~~~~
        make: *** [authenticate_pam.target.mk:109: Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
        make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassen
        gyp ERR! build error
        gyp ERR! stack Error: `make` failed with exit code: 2
        gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
        gyp ERR! stack     at ChildProcess.emit (events.js:400:28)
        gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)
        gyp ERR! System Linux 5.10.103-v7l+
        gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
        gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
        gyp ERR! node -v v14.19.0
        gyp ERR! node-gyp -v v5.1.0
        gyp ERR! not ok
        
        > iobroker.js-controller@4.0.21 install /opt/iobroker/node_modules/iobroker.js-controller
        > node iobroker.js setup first
        
        No connection to databases possible ...
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild`
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
        
        npm ERR! code ELIFECYCLE
        npm ERR! errno 22
        npm ERR! iobroker.js-controller@4.0.21 install: `node iobroker.js setup first`
        npm ERR! Exit status 22
        npm ERR!
        npm ERR! Failed at the iobroker.js-controller@4.0.21 install script.
        npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /home/iobroker/.npm/_logs/2022-03-15T14_56_11_790Z-debug.log
        
        mikeal created this issue in request/request

        open Request’s Past, Present and Future #3142

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

          @dgr

          Deinstallier den Adapter 'terminal'.

          Und verwende CodeTags!

          D 1 Reply Last reply Reply Quote 0
          • D
            DGR @DGR last edited by

            @dgr sorry, unerwartet ist Besuch da gewesen. Offenbar habe ich das Reinkopieren wohl doch nicht korrekt gemacht.

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

              @dgr Kannst auch mal folgendes probieren:

              cd /opt/iobroker
              npm i iobroker.js-controller --ignore-scripts
              

              iobroker.json anpassen, damit connectTimeout höher ist

              iobroker setup first
              
              D 1 Reply Last reply Reply Quote 0
              • D
                DGR @Thomas Braun last edited by

                @thomas-braun
                in /opt/iobroker/node_modules sehe ich keinen Adapter "terminal", zumindest nicht unter diesem Namen.

                ansonsten wäre "sudo rm -r /opt/iobroker/node_modules/iobroker.terminal" richtig ?

                Nebenfrage:
                Wenn bei "Submit" für eine Antwort Error und Forbidden rechts unten erscheint - was ist das für ein Problem ?

                Homoran 1 Reply Last reply Reply Quote 0
                • D
                  DGR @AlCalzone last edited by

                  @alcalzone

                   npm i iobroker.js-controller --ignore-scripts
                  npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  
                  + iobroker.js-controller@4.0.21
                  added 79 packages from 34 contributors in 46.591s
                  
                  67 packages are looking for funding
                    run `npm fund` for details
                  
                  /opt/iobroker $ iobroker setup first
                  No connection to databases possible ...
                  
                  

                  kann das ganze eine Rechtefrage sein ?

                  mikeal created this issue in request/request

                  open Request’s Past, Present and Future #3142

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

                    @dgr

                    cd /opt/iobroker
                    npm ls authenticate-pam
                    
                    D 1 Reply Last reply Reply Quote 0
                    • D
                      DGR @Thomas Braun last edited by

                      @thomas-braun

                      /opt/iobroker $ npm ls authenticate-pam
                      iobroker.inst@2.0.3 /opt/iobroker
                      └─┬ iobroker.terminal@0.1.2
                        └── authenticate-pam@1.0.2
                      
                      
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @DGR last edited by

                        @dgr sagte in mal wieder: No connection to databases possible ...:

                        Wenn bei "Submit" für eine Antwort Error und Forbidden rechts unten erscheint - was ist das für ein Problem ?

                        ein bekannter Bug mit unbekannter Ursache!

                        einfach Browser neu laden und gut ist

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

                          @dgr

                          Da isser doch!

                          iobroker del terminal
                          
                          D 1 Reply Last reply Reply Quote 0
                          • D
                            DGR @Thomas Braun last edited by

                            @thomas-braun

                            /opt/iobroker $ iobroker del terminal
                            No connection to databases possible ...
                            
                            
                            AlCalzone 1 Reply Last reply Reply Quote 0
                            • AlCalzone
                              AlCalzone Developer @DGR last edited by

                              @dgr Hast du denn jetzt schon den connection timeout hochgestellt?

                              D 2 Replies Last reply Reply Quote 0
                              • D
                                DGR @AlCalzone last edited by

                                @alcalzone

                                "objects": {
                                    "type": "jsonl",
                                    "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].",
                                    "host": "127.0.0.1",
                                    "port": 9001,
                                    "user": "",
                                    "pass": "",
                                    "noFileCache": false,
                                    "connectTimeout": 30000,
                                    "options": {
                                      "auth_pass": null,
                                      "retry_max_delay": 2000
                                    },
                                
                                1 Reply Last reply Reply Quote 0
                                • D
                                  DGR @AlCalzone last edited by

                                  @alcalzone stand noch so von gestern

                                  D 1 Reply Last reply Reply Quote 0
                                  • D
                                    DGR @DGR last edited by

                                    @dgr
                                    Die Wahrscheinlichkeit einer erfolgreichen Reparatur schätze ich nach den ganzen Versuchen als nicht mehr so hoch ein.
                                    Ein restore mit dem "aktuellen" Backup wäre noch eine Versuch wert:

                                    iob restore /opt/iobroker/iobroker_2021_12_29-02_00_10_backupiobroker.tar.gz

                                    Sonst bleibt noch die iobroker-Neuinstallation:

                                    1. Wichtig: Vorher würde ich gerne noch einiges retten wenn möglich (wie ???), z.B. Scripte, Datenpunkte, vis, - was wäre noch sinnvoll ?

                                    2. Sollte vor einer Neuinstallation irgendwas bereinigt/gelöscht werden ?

                                    3. Gibt es einen link zu einer Anleitung für eine Neuinstallation iobroker ?

                                    4. Meine Vorgehensweise wäre sonst:

                                    sudo apt-get update
                                    sudo apt-get upgrade
                                    sudo apt-get --purge remove node nodejs
                                    sudo apt-get autoremove
                                    sudo -s
                                    curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
                                    exit
                                    sudo apt-get install -y nodejs
                                    node -v (zum Test)
                                    cd /opt/iobroker
                                    curl -sLf https://iobroker.net/install.sh | bash -
                                    iobroker start

                                    wendy2702 1 Reply Last reply Reply Quote 0
                                    • wendy2702
                                      wendy2702 @DGR last edited by wendy2702

                                      @dgr Node JS wird bei Verwendung des "einzeilers"

                                      curl -sLf https://iobroker.net/install.sh | bash -
                                      

                                      in der richtigen Version mit installiert. Sollte nicht vorher manuell ausgeführt werden.

                                      Du kannst dir diese beiden Dateien sichern wie im Mini how to beschrieben

                                      https://forum.iobroker.net/topic/43325/mini-howto-cannot-find-view-system-for-search-host?_=1647414866222

                                      Wenn auf dem System nur iobroker lief würde ich aber komplett von vorne beginnen mit einem frischen bullseye

                                      D 1 Reply Last reply Reply Quote 0
                                      • D
                                        DGR @wendy2702 last edited by

                                        @wendy2702
                                        Danke, werde ich dann so anpassen (curl...)
                                        bullseye nach der Anleitung erscheint mir dann auch sinnvoll.

                                        Nur wie rette ich meine Scripte (Blockly) und evtl. andere Einstellungen für eine weitere Nutzung nach Neuinstallation ?

                                        wendy2702 1 Reply Last reply Reply Quote 0
                                        • wendy2702
                                          wendy2702 @DGR last edited by

                                          @dgr sagte in mal wieder: No connection to databases possible ...:

                                          Nur wie rette ich meine Scripte (Blockly) und evtl. andere Einstellungen für eine weitere Nutzung nach Neuinstallation ?

                                          Kannst entweder wie geschrieben die beiden Files sichern, alles manuell exportieren/kopieren oder aber du spielst dein Backup wieder ein.

                                          Vielleicht am einfachsten eine weitere SD Karte für die neue installation verwenden oder von der alten ein Image erstellen. Dann kannst du im Bedarfsfall zurück wechseln.

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

                                            Ok @DGR ... nichts ist verloren ... und ich finde es immer wieder erstaunlich (sorry) wie in einem Thread an verschiedensten (ggf komplett unrelated) Themen parallel versucht wird zu arbeiten ohne sich erstmal auf eins zu konzentrieren 🙂

                                            Also dann nochmal ... alles einen Schritt zurück und Konzentration auf das "no connection to db" issue!

                                            1.) "iob version" ... ist es jetzt ein 4.0.21 oder welche Version nutzt du 🙂
                                            2.) Nochmal: Wie gross sind AKTUELL die objects.jsonl und states.jsonl?
                                            3.) Wenn Du ein Kommando startest was in dem Fehler endet - jetzt mit 30s timeouts - dauert es auch ca. 30s bis die Meldung kommt? Bitte mal in einem zweiten Shell-Fenster parallel "top" laufen lassen. Es müsste wenn Du das Kommando startest dann ein node Prozess kommen. Verbraucht der viel CPU? Wieviel RAM?
                                            4.) WENN der Prozess kommt und quasi 30s viel CPU braucht und dann abgebrochen wird dann bitte das Timeout setting weiter erhöhen. Mach ruhig 90000 draus.
                                            5.) Dann nochmal ... geht es dann? Oder braucht der dann 90s so viel CPU und es geht weiter nicht? Wenn es danach tat ... wie gross sind die beiden Files objects.jsonl und states.jsonl jetzt?

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

                                            Support us

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

                                            557
                                            Online

                                            31.7k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            connection database
                                            7
                                            93
                                            8734
                                            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