Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Skripten / Logik
    4. Node-Red
    5. contrib tts lässt sich nicht installieren

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    contrib tts lässt sich nicht installieren

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Saranger @mickym last edited by

      @mickym ok gut zu wissen, vielleicht lässt sich das andere ja noch lösen 🙂

      danke Dir.

      1 Reply Last reply Reply Quote 0
      • S
        Saranger @Saranger last edited by

        anbei mal die Meldung noch im IObroker Log nach dem Versuch diese node zu installieren und das crashen von nodered

        FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
        2022-12-12 14:58:41.183 - warn: node-red.0 (2527) 1: 0xb06730 node::Abort() [node-red]
        2022-12-12 14:58:41.183 - warn: node-red.0 (2527) 2: 0xa1b6d0 [node-red]
        2022-12-12 14:58:41.184 - warn: node-red.0 (2527) 3: 0xce1e60 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node-red]
        2022-12-12 14:58:41.185 - warn: node-red.0 (2527) 4: 0xce2207 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node-red]
        2022-12-12 14:58:41.185 - warn: node-red.0 (2527) 5: 0xe99875 [node-red]
        2022-12-12 14:58:41.186 - warn: node-red.0 (2527) 6: 0xea953d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node-red]
        2022-12-12 14:58:41.187 - warn: node-red.0 (2527) 7: 0xeac23e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node-red]
        2022-12-12 14:58:41.187 - warn: node-red.0 (2527) 8: 0xe6d4b2 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node-red]
        2022-12-12 14:58:41.188 - warn: node-red.0 (2527) 9: 0xe65ac4 v8::internal::FactoryBase::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [node-red]
        2022-12-12 14:58:41.189 - warn: node-red.0 (2527) 10: 0xe67d22 v8::internal::FactoryBase::NewDescriptorArray(int, int, v8::internal::AllocationType) [node-red]
        2022-12-12 14:58:41.189 - warn: node-red.0 (2527) 11: 0x10b5d77 v8::internal::DescriptorArray::CopyUpTo(v8::internal::Isolate*, v8::internal::Handle, int, int) [node-red]
        2022-12-12 14:58:41.191 - warn: node-red.0 (2527) 12: 0x10a3eb1 v8::internal::Map::CopyAddDescriptor(v8::internal::Isolate*, v8::internal::Handle, v8::internal::Descriptor*, v8::internal::TransitionFlag) [node-red]
        13: 0x10a446c v8::internal::Map::CopyWithField(v8::internal::Isolate*, v8::internal::Handle, v8::internal::Handle, v8::internal::Handle, v8::internal::PropertyAttributes, v8::internal::PropertyConstness, v8::internal::Representation, v8::internal::TransitionFlag) [node-red]
        2022-12-12 14:58:41.192 - warn: node-red.0 (2527) 14: 0x10a6298 v8::internal::Map::TransitionToDataProperty(v8::internal::Isolate*, v8::internal::Handle, v8::internal::Handle, v8::internal::Handle, v8::internal::PropertyAttributes, v8::internal::PropertyConstness, v8::internal::StoreOrigin) [node-red]
        2022-12-12 14:58:41.192 - warn: node-red.0 (2527) 15: 0x1094df2 v8::internal::LookupIterator::PrepareTransitionToDataProperty(v8::internal::Handle, v8::internal::Handle, v8::internal::PropertyAttributes, v8::internal::StoreOrigin) [node-red]
        2022-12-12 14:58:41.193 - warn: node-red.0 (2527) 16: 0x10b827a v8::internal::Object::AddDataProperty(v8::internal::LookupIterator*, v8::internal::Handle, v8::internal::PropertyAttributes, v8::Maybe, v8::internal::StoreOrigin) [node-red]
        2022-12-12 14:58:41.194 - warn: node-red.0 (2527) 17: 0x10bc7a3 v8::internal::Object::SetProperty(v8::internal::LookupIterator*, v8::internal::Handle, v8::internal::StoreOrigin, v8::Maybe) [node-red]
        2022-12-12 14:58:41.195 - warn: node-red.0 (2527) 18: 0x11efce6 v8::internal::Runtime::SetObjectProperty(v8::internal::Isolate*, v8::internal::Handle, v8::internal::Handle, v8::internal::Handle, v8::internal::StoreOrigin, v8::Maybe) [node-red]
        2022-12-12 14:58:41.195 - warn: node-red.0 (2527) 19: 0x11f1269 v8::internal::Runtime_SetKeyedProperty(int, unsigned long*, v8::internal::Isolate*) [node-red]
        2022-12-12 14:58:41.196 - warn: node-red.0 (2527) 20: 0x15da159 [node-red]
        2022-12-12 14:58:41.208 - info: node-red.0 (2527) node-red exited with null
        2022-12-12 14:58:46.208 - info: node-red.0 (2527) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
        2022-12-12 14:58:49.542 - warn: node-red.0 (2527) 12 Dec 14:58:49 - [warn] Projects disabled : editorTheme.projects.enabled=false
        2022-12-12 14:58:50.138 - warn: node-red.0 (2527)
        <--- Last few GCs --->
        [4805:0x5fcdf70] 3865 ms: Mark-sweep (reduce) 125.1 (131.4) -> 124.1 (131.4) MB, 50.5 / 0.0 ms (average mu = 0.147, current mu = 0.057) allocation failure scavenge might not succeed
        [4805:0x5fcdf70] 3916 ms: Mark-sweep (reduce) 125.2 (131.4) -> 124.3 (131.7) MB, 47.6 / 0.0 ms (average mu = 0.105, current mu = 0.061) allocation failure scavenge might not succeed
        <--- JS stacktrace --->
        FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
        2022-12-12 14:58:50.138 - warn: node-red.0 (2527) 1: 0xb06730 node::Abort() [node-red]
        2022-12-12 14:58:50.139 - warn: node-red.0 (2527) 2: 0xa1b6d0 [node-red]
        2022-12-12 14:58:50.140 - warn: node-red.0 (2527) 3: 0xce1e60 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node-red]
        2022-12-12 14:58:50.141 - warn: node-red.0 (2527) 4: 0xce2207 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node-red]
        2022-12-12 14:58:50.142 - warn: node-red.0 (2527) 5: 0xe99875 [node-red]
        2022-12-12 14:58:50.143 - warn: node-red.0 (2527) 6: 0xea953d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node-red]
        2022-12-12 14:58:50.145 - warn: node-red.0 (2527) 7: 0xeac23e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node-red]
        2022-12-12 14:58:50.146 - warn: node-red.0 (2527) 8: 0xe6d4b2 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node-red]
        2022-12-12 14:58:50.147 - warn: node-red.0 (2527) 9: 0xe67dcc v8::internal::FactoryBase::AllocateRawArray(int, v8::internal::AllocationType) [node-red]
        2022-12-12 14:58:50.148 - warn: node-red.0 (2527) 10: 0xe67ea5 v8::internal::FactoryBase::NewFixedArrayWithFiller(v8::internal::Handle, int, v8::internal::Handle, v8::internal::AllocationType) [node-red]
        2022-12-12 14:58:50.149 - warn: node-red.0 (2527) 11: 0x1016382 [node-red]
        2022-12-12 14:58:50.150 - warn: node-red.0 (2527) 12: 0x101650c [node-red]
        2022-12-12 14:58:50.151 - warn: node-red.0 (2527) 13: 0x1016668 [node-red]
        2022-12-12 14:58:50.151 - warn: node-red.0 (2527) 14: 0x10744b5 v8::internal::JSObject::AddDataElement(v8::internal::Handle, unsigned int, v8::internal::Handle, v8::internal::PropertyAttributes) [node-red]
        2022-12-12 14:58:50.152 - warn: node-red.0 (2527) 15: 0x10b820e v8::internal::Object::AddDataProperty(v8::internal::LookupIterator*, v8::internal::Handle, v8::internal::PropertyAttributes, v8::Maybe, v8::internal::StoreOrigin) [node-red]
        2022-12-12 14:58:50.153 - warn: node-red.0 (2527) 16: 0x10bc7a3 v8::internal::Object::SetProperty(v8::internal::LookupIterator*, v8::internal::Handle, v8::internal::StoreOrigin, v8::Maybe) [node-red]
        2022-12-12 14:58:50.154 - warn: node-red.0 (2527) 17: 0x11efce6 v8::internal::Runtime::SetObjectProperty(v8::internal::Isolate*, v8::internal::Handle, v8::internal::Handle, v8::internal::Handle, v8::internal::StoreOrigin, v8::Maybe) [node-red]
        2022-12-12 14:58:50.154 - warn: node-red.0 (2527) 18: 0x11f1269 v8::internal::Runtime_SetKeyedProperty(int, unsigned long*, v8::internal::Isolate*) [node-red]
        2022-12-12 14:58:50.155 - warn: node-red.0 (2527) 19: 0x15da159 [node-red]
        2022-12-12 14:58:50.168 - info: node-red.0 (2527) node-red exited with null
        2022-12-12 14:58:55.168 - info: node-red.0 (2527) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
        2022-12-12 14:58:58.450 - warn: node-red.0 (2527) 12 Dec 14:58:58 - [warn] Projects disabled : editorTheme.projects.enabled=false
        2022-12-12 14:58:58.949 - warn: node-red.0 (2527)
        <--- Last few GCs --->
        [4827:0x6ac1f70] 3718 ms: Mark-sweep 125.1 (133.9) -> 123.5 (134.4) MB, 44.0 / 0.0 ms (average mu = 0.240, current mu = 0.109) allocation failure scavenge might not succeed
        [4827:0x6ac1f70] 3767 ms: Mark-sweep 125.6 (134.4) -> 124.0 (134.9) MB, 43.5 / 0.0 ms (average mu = 0.177, current mu = 0.105) allocation failure scavenge might not succeed
        <--- JS stacktrace --->
        FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
        2022-12-12 14:58:58.951 - warn: node-red.0 (2527) 1: 0xb06730 node::Abort() [node-red]
        2022-12-12 14:58:58.951 - warn: node-red.0 (2527) 2: 0xa1b6d0 [node-red]
        3: 0xce1e60 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node-red]
        2022-12-12 14:58:58.951 - warn: node-red.0 (2527) 4: 0xce2207 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node-red]
        2022-12-12 14:58:58.955 - warn: node-red.0 (2527) 5: 0xe99875 [node-red]
        6: 0xea953d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node-red]
        7: 0xeac23e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node-red]
        8: 0xe6d77a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node-red]
        9: 0x11e64e6 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node-red]
        10: 0x15da159 [node-red]
        2022-12-12 14:58:58.968 - info: node-red.0 (2527) node-red exited with null
        2022-12-12 14:59:00.775 - error: rpi2.0 (2689) Cannot evaluate: Filesystem 1K-blocks Used Available Use% Mounted on
        /dev/loop0 16337788 3655048 11827496 24% /
        /1024
        2022-12-12 14:59:00.776 - error: rpi2.0 (2689) Cannot evaluate: Filesystem 1K-blocks Used Available Use% Mounted on
        /dev/loop0 16337788 3655048 11827496 24% /
        
        mickym 1 Reply Last reply Reply Quote 0
        • mickym
          mickym Most Active @Saranger last edited by

          @saranger hast du mal den speicherbedarf im Node-red Adapter erhöht?

          S 1 Reply Last reply Reply Quote 0
          • S
            Saranger @mickym last edited by

            @mickym nein du meinst den ram wenn ich im iobroker auf den noderedadapter gehe? Wieviel sollte man da geben?

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

              @saranger

              Wie bist du denn da eigentlich insgesamt unterwegs?

              free -ht
              sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
              uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
              
              1 Reply Last reply Reply Quote 0
              • mickym
                mickym Most Active @Saranger last edited by

                @saranger ich glaub Standard ist 128. ich hab 2048 weil ich viele flows habe, aber kannst ja mal mit 512 oder 1024 Testen.

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

                  @thomas-braun said in contrib tts lässt sich nicht installieren:

                  saranger@ioBroker:~$ free -ht
                                 total        used        free      shared  buff/cache   available
                  Mem:           4.0Gi       1.3Gi       2.4Gi       0.0Ki       293Mi       2.7Gi
                  Swap:          512Mi          0B       512Mi
                  Total:         4.5Gi       1.3Gi       2.9Gi
                  saranger@ioBroker:~$ sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
                  [sudo] password for saranger: 
                  Sorry, try again.
                  [sudo] password for saranger: 
                  saranger@ioBroker:~$ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                  x86_64
                  Kein Docker
                  /usr/bin/nodejs
                  /usr/bin/node
                  /usr/bin/npm
                  v16.18.1
                  v16.18.1
                  8.19.2
                  4.0.23
                  saranger
                  saranger sudo iobroker
                  
                  
                  /home/saranger
                  Hit:1 https://deb.nodesource.com/node_16.x jammy InRelease
                  Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease
                  Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
                  Get:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
                  Fetched 224 kB in 1s (228 kB/s)  
                  Reading package lists... Done
                  Building dependency tree... Done
                  Reading state information... Done
                  All packages are up to date.
                  nodejs:
                    Installed: 16.18.1-deb-1nodesource1
                    Candidate: 16.18.1-deb-1nodesource1
                    Version table:
                   *** 16.18.1-deb-1nodesource1 500
                          500 https://deb.nodesource.com/node_16.x jammy/main amd64 Packages
                          100 /var/lib/dpkg/status
                       12.22.9~dfsg-1ubuntu3 500
                          500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
                  saranger@ioBroker:~$ 
                  
                  S 1 Reply Last reply Reply Quote 0
                  • S
                    Saranger @Saranger last edited by

                    @mickym werd ich mal testen, ich muss dazu sagen das Ganze läuft auf Proxmox und ich habe seit dem auch immer probleme beim Deploy, teilweise muss ich 4 mal darauf klicken bis es funktioniert.

                    mickym 1 Reply Last reply Reply Quote 0
                    • mickym
                      mickym Most Active @Saranger last edited by mickym

                      @saranger na dann wird es Zeit, bei 128k, ist das ein Zeichen, dass der Speicher knapp ist und da immer rumgeswapt wird. Ich würde mal 1024 nehmen und wie gesagt ich habe 2048.

                      Das heißt nicht dass soviel gebraucht wird, aber der Speicher für Node-Red wird halt nicht so schnell limitiert.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        Saranger @mickym last edited by

                        @mickym und das war die Lösung des Problems hab es auf 1024 gestellt und jetzt lies sich die Node installieren. Verrückt

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

                          @saranger na nicht verrückt, wenn du das log mit dem Crash eher gepostet hättest, dann wäre man da vielleicht schon früher drauf gekommen. Das arme #node-Red 😁

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

                            @saranger

                            2022-12-12 14:58:46.208 - info: node-red.0 (2527) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
                            
                            [...]
                            <--- JS stacktrace --->
                            
                            FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
                            

                            Soweit so klar.

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

                              @thomas-braun

                              also war hier das einzige Problem nur der zu kleine Ram für nodered? Aber vielen Dank für die Hilfe und den Wink mit dem User.

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

                                @saranger

                                Falscher user und zuwenig aollokierter Arbeitsspeicher.

                                1 Reply Last reply Reply Quote 0
                                • mickym
                                  mickym Most Active @Saranger last edited by mickym

                                  @saranger na ob die package-lock.json noch ein Problem war, weiß ich nicht. Das Hauptproblem war aber sicher der fehlende Speicher. Das Deployen sollte nun auch flüssiger laufen. Über den Palletten- Manager wird wahrscheinlich mit dem user iobroker installiert. Allerdings sollte man selbst halt nie mit Root hantieren. Ich hoffe Du hast Dir mit dem npm install nichts zerschossen- aber das habe ich nicht gesehen, dass du da mit Root rumhantierst.

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    Saranger @mickym last edited by

                                    @mickym also aktuell läuft soweit erstmal alles, ich werde das mal beobachten und jetzt mal die node testen, das wird auch spannend.

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

                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate

                                    807
                                    Online

                                    31.7k
                                    Users

                                    79.8k
                                    Topics

                                    1.3m
                                    Posts

                                    3
                                    36
                                    1233
                                    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