Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Skripten / Logik
  4. Node-Red
  5. contrib tts lässt sich nicht installieren

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    651

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    18
    1
    5.7k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.5k

contrib tts lässt sich nicht installieren

Scheduled Pinned Locked Moved Node-Red
36 Posts 3 Posters 2.5k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Saranger

    @mickym

    ah das hab ich auch nicht auf dem schirm gehabt, ich hab glaube gar keinen anderen user.

    anbei wieder die meldung und nodered geht nicht

    
    -----------------------------------------------------------
    2022-12-12T13:16:47.946Z Installieren : node-red-contrib-tts-ultimate 1.0.52
    
    2022-12-12T13:16:47.964Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-tts-ultimate@1.0.52
    2022-12-12T13:16:48.245Z [err] npm
    2022-12-12T13:16:48.245Z [err]  WARN config production Use `--omit=dev` instead.
    2022-12-12T13:16:57.529Z [err] npm
    2022-12-12T13:16:57.530Z [err]  WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
    
    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    wrote on last edited by
    #15

    @saranger

    Abbrechen, Rechte fixen!

    iob stop 
    iob fix
    

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    S 1 Reply Last reply
    0
    • Thomas BraunT Thomas Braun

      @saranger

      Abbrechen, Rechte fixen!

      iob stop 
      iob fix
      
      S Offline
      S Offline
      Saranger
      wrote on last edited by
      #16

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

      iob fix

      user hab ich jetzt angelegt und die beiden befehle hab ich auch ausgeführt

      Thomas BraunT mickymM 2 Replies Last reply
      0
      • mickymM Offline
        mickymM Offline
        mickym
        Most Active
        wrote on last edited by
        #17

        Ja ich glaube auch, dass da mit den Rechten insgesamt was nicht stimmt. Da übergebe ich lieber an @Thomas-Braun. Ich schau mal, ob ich auf meinem Testsystem die Node installieren kann.

        Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

        1 Reply Last reply
        0
        • S Saranger

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

          iob fix

          user hab ich jetzt angelegt und die beiden befehle hab ich auch ausgeführt

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          wrote on last edited by
          #18

          @saranger

          iob diag
          

          ausführen, die markierten Ausgaben hier wieder rein.

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          S 1 Reply Last reply
          0
          • Thomas BraunT Thomas Braun

            @saranger

            iob diag
            

            ausführen, die markierten Ausgaben hier wieder rein.

            S Offline
            S Offline
            Saranger
            wrote on last edited by
            #19

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

            iob diag

            bash: line 1: syntax error near unexpected token `<'
            bash: line 1: `<!doctype html><html lang="en"><head><meta charset="utf-8"/><link rel="icon" href="/www/favicon.ico"/><meta name="viewport" content="width=device-width,initial-scale=1"/><meta name="theme-color" content="#2196F3"><meta name="description" content="Remote access to personal ioBroker server via ioBroker.cloud"/><link rel="apple-touch-icon" href="/www/logo192.png"/><link rel="manifest" href="/www/manifest.json"/><title>ioBroker Cloud</title><style>#root,body,html{height:100%;width:100%;display:flex;overflow:hidden}</style><script defer="defer" src="/www/static/js/main.ae982c84.js"></script><link href="/www/static/css/main.59da0ebb.css" rel="stylesheet"></head><body><noscript>You need to enable JavaScript to run this app.</noscript><div id="root"></div></body></html>'
            
            S 1 Reply Last reply
            0
            • S Saranger

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

              iob fix

              user hab ich jetzt angelegt und die beiden befehle hab ich auch ausgeführt

              mickymM Offline
              mickymM Offline
              mickym
              Most Active
              wrote on last edited by mickym
              #20

              @saranger Also auf meinem Testsystem konnte ich die Node installieren.

              d9197c27-cc24-40fe-baa4-99f3ee72c01e-image.png

              Die Meldungen ansonsten sind aber normal - habe hier mal das Log über die Installation über den Palletten-Manager:

              -----------------------------------------------------------
              2022-12-12T13:31:52.224Z Installieren : node-red-contrib-tts-ultimate 1.0.52
              
              2022-12-12T13:31:52.226Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-tts-ultimate@1.0.52
              2022-12-12T13:31:52.406Z [err] npm
              2022-12-12T13:31:52.406Z [err]  WARN config production Use `--omit=dev` instead.
              2022-12-12T13:31:53.776Z [err] npm
              2022-12-12T13:31:53.776Z [err]  
              2022-12-12T13:31:53.776Z [err] WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
              2022-12-12T13:31:53.779Z [err] npm
              2022-12-12T13:31:53.779Z [err]  WARN deprecated formidable@1.2.2: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
              2022-12-12T13:31:53.792Z [err] npm
              2022-12-12T13:31:53.792Z [err]  WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
              2022-12-12T13:32:06.791Z [out] 
              2022-12-12T13:32:06.791Z [out] added 169 packages in 14s
              2022-12-12T13:32:06.800Z rc=0
              

              Das heisst diese Math.random Warnung kann man ignorieren.

              Bei Dir fehlt nur die Erfolgsmeldung dass 169 Pakete installiert wurden. Vielleicht Geduld?

              Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

              S 1 Reply Last reply
              0
              • mickymM mickym

                @saranger Also auf meinem Testsystem konnte ich die Node installieren.

                d9197c27-cc24-40fe-baa4-99f3ee72c01e-image.png

                Die Meldungen ansonsten sind aber normal - habe hier mal das Log über die Installation über den Palletten-Manager:

                -----------------------------------------------------------
                2022-12-12T13:31:52.224Z Installieren : node-red-contrib-tts-ultimate 1.0.52
                
                2022-12-12T13:31:52.226Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-tts-ultimate@1.0.52
                2022-12-12T13:31:52.406Z [err] npm
                2022-12-12T13:31:52.406Z [err]  WARN config production Use `--omit=dev` instead.
                2022-12-12T13:31:53.776Z [err] npm
                2022-12-12T13:31:53.776Z [err]  
                2022-12-12T13:31:53.776Z [err] WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                2022-12-12T13:31:53.779Z [err] npm
                2022-12-12T13:31:53.779Z [err]  WARN deprecated formidable@1.2.2: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
                2022-12-12T13:31:53.792Z [err] npm
                2022-12-12T13:31:53.792Z [err]  WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
                2022-12-12T13:32:06.791Z [out] 
                2022-12-12T13:32:06.791Z [out] added 169 packages in 14s
                2022-12-12T13:32:06.800Z rc=0
                

                Das heisst diese Math.random Warnung kann man ignorieren.

                Bei Dir fehlt nur die Erfolgsmeldung dass 169 Pakete installiert wurden. Vielleicht Geduld?

                S Offline
                S Offline
                Saranger
                wrote on last edited by
                #21

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

                danke Dir.

                1 Reply Last reply
                0
                • S Saranger

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

                  iob diag

                  bash: line 1: syntax error near unexpected token `<'
                  bash: line 1: `<!doctype html><html lang="en"><head><meta charset="utf-8"/><link rel="icon" href="/www/favicon.ico"/><meta name="viewport" content="width=device-width,initial-scale=1"/><meta name="theme-color" content="#2196F3"><meta name="description" content="Remote access to personal ioBroker server via ioBroker.cloud"/><link rel="apple-touch-icon" href="/www/logo192.png"/><link rel="manifest" href="/www/manifest.json"/><title>ioBroker Cloud</title><style>#root,body,html{height:100%;width:100%;display:flex;overflow:hidden}</style><script defer="defer" src="/www/static/js/main.ae982c84.js"></script><link href="/www/static/css/main.59da0ebb.css" rel="stylesheet"></head><body><noscript>You need to enable JavaScript to run this app.</noscript><div id="root"></div></body></html>'
                  
                  S Offline
                  S Offline
                  Saranger
                  wrote on last edited by
                  #22

                  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% /
                  
                  mickymM 1 Reply Last reply
                  0
                  • S Saranger

                    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% /
                    
                    mickymM Offline
                    mickymM Offline
                    mickym
                    Most Active
                    wrote on last edited by
                    #23

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

                    Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                    S 1 Reply Last reply
                    0
                    • mickymM mickym

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

                      S Offline
                      S Offline
                      Saranger
                      wrote on last edited by
                      #24

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

                      Thomas BraunT mickymM 2 Replies Last reply
                      0
                      • S Saranger

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

                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        wrote on last edited by
                        #25

                        @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
                        

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Reply Last reply
                        0
                        • S Saranger

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

                          mickymM Offline
                          mickymM Offline
                          mickym
                          Most Active
                          wrote on last edited by
                          #26

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

                          Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                          1 Reply Last reply
                          0
                          • S Offline
                            S Offline
                            Saranger
                            wrote on last edited by
                            #27

                            @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
                            0
                            • S Saranger

                              @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 Offline
                              S Offline
                              Saranger
                              wrote on last edited by
                              #28

                              @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.

                              mickymM 1 Reply Last reply
                              0
                              • S Saranger

                                @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.

                                mickymM Offline
                                mickymM Offline
                                mickym
                                Most Active
                                wrote on last edited by mickym
                                #29

                                @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.

                                Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                                S 1 Reply Last reply
                                0
                                • mickymM 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 Offline
                                  S Offline
                                  Saranger
                                  wrote on last edited by
                                  #30

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

                                  mickymM Thomas BraunT 2 Replies Last reply
                                  0
                                  • S Saranger

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

                                    mickymM Offline
                                    mickymM Offline
                                    mickym
                                    Most Active
                                    wrote on last edited by
                                    #31

                                    @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 :grin:

                                    Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                                    1 Reply Last reply
                                    0
                                    • S Saranger

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

                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      wrote on last edited by
                                      #32

                                      @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.

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      S 1 Reply Last reply
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @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 Offline
                                        S Offline
                                        Saranger
                                        wrote on last edited by
                                        #33

                                        @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 BraunT mickymM 2 Replies Last reply
                                        0
                                        • S Saranger

                                          @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 BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          wrote on last edited by
                                          #34

                                          @saranger

                                          Falscher user und zuwenig aollokierter Arbeitsspeicher.

                                          Linux-Werkzeugkasten:
                                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                          NodeJS Fixer Skript:
                                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                          1 Reply Last reply
                                          0

                                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                          With your input, this post could be even better 💗

                                          Register Login
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          477

                                          Online

                                          32.7k

                                          Users

                                          82.6k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe