Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Error Log Controller Iobroker *GELÖST*

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    Error Log Controller Iobroker *GELÖST*

    This topic has been deleted. Only users with topic management privileges can see it.
    • Nicoloma
      Nicoloma @arteck last edited by

      @arteck doch, ich habe den den Adapter sogar schon komplett deaktiviert, die Meldung bleibt gleich.

      1 Reply Last reply Reply Quote 0
      • Nicoloma
        Nicoloma @arteck last edited by Nicoloma

        @arteck

        host.iobroker
2024-01-03 12:15:34.137	warn	instance system.adapter.trashschedule.0 terminated due to SIGABRT
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[11]: 10: 0x170deb9 [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[10]: 9: 0x12e0bcf v8::internal::Runtime_StackGuardWithGap(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[9]: 8: 0xee014f v8::internal::StackGuard::HandleInterrupts() [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[8]: 7: 0xf61ff5 v8::internal::Heap::HandleGCRequest() [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[7]: 6: 0xf5f08d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[6]: 5: 0xf4cba5 [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[5]: 4: 0xd6f697 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[4]: 3: 0xd6f2f0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[3]: 2: 0xa9a7f8 [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[2]: 1: 0xb95b60 node::Abort() [/usr/bin/node]
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[1]: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[1]: <--- JS stacktrace --->
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[0]: nc[269268:0x6440870] 24816 ms: Mark-sweep (reduce) 18.9 (21.3) -> 18.7 (21.3) MB, 6.7 / 0.0 ms (+ 0.1 ms in 2 steps since start of marking, biggest step 0.1 ms, walltime since start of marking 52 ms) (average mu = 0.937, current mu = 0.874) finalize inc[269268:0x6440870] 24903 ms: Mark-sweep (reduce) 19.0 (21.3) -> 18.8 (21.6) MB, 5.9 / 0.0 ms (+ 0.1 ms in 2 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 86 ms) (average mu = 0.934, current mu = 0.931) finalize inc
host.iobroker
2024-01-03 12:15:34.137	error	Caught by controller[0]: <--- Last few GCs --->

javascript.0
2024-01-03 12:15:03.964	info	terminating

javascript.0
2024-01-03 12:15:03.469	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

javascript.0
2024-01-03 12:15:03.468	info	terminating

javascript.0
2024-01-03 12:15:03.467	info	Stop script script.js.common.Heizung.PV-Heizstab_aktiv

javascript.0
2024-01-03 12:15:03.467	info	Stop script script.js.common.Heizung.Fußboden

javascript.0
2024-01-03 12:15:03.467	info	Stop script script.js.common.PV.aquarium_per_pv

javascript.0
2024-01-03 12:15:03.467	info	Stop script script.js.common.telegramm1

javascript.0
2024-01-03 12:15:03.467	info	Stop script script.js.common.nullsteller

javascript.0
2024-01-03 12:15:03.467	info	Stop script script.js.common.PV.überschuss1_b

javascript.0
2024-01-03 12:15:03.466	info	Stop script script.js.common.Ordner_1.Spreiz_OG

javascript.0
2024-01-03 12:15:03.466	info	Stop script script.js.common.Ordner_1.Spreiz_Fb

javascript.0
2024-01-03 12:15:03.466	info	Stop script script.js.common.Gas.gaszahler

javascript.0
2024-01-03 12:15:03.466	info	Stop script script.js.common.Gas.gasslbst

javascript.0
2024-01-03 12:15:03.466	info	Stop script script.js.common.Gas.gaskhwverbrauch

javascript.0
2024-01-03 12:15:03.466	info	Stop script script.js.common.Gas.Gas_kwheuro

javascript.0
2024-01-03 12:15:03.466	info	Stop script script.js.common.Alexa.Müllrausbringen

javascript.0
2024-01-03 12:15:03.465	info	Stop script script.js.Skript_1ss

javascript.0
2024-01-03 12:15:03.463	info	Got terminate signal TERMINATE_YOURSELF
        1 Reply Last reply Reply Quote 0
        • Nicoloma
          Nicoloma last edited by

          LÖSUNG: DOWNGRADE VON Node.js18 auf NODE 16...

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

            @nicoloma

            Das ist keine Lösung, nodejs@16 ist im Upstream abgekündigt.

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

              @thomas-braun Ja, aber ich kann es nicht lösen und keiner von euch weiß weiter.

              Nicoloma 1 Reply Last reply Reply Quote 0
              • Nicoloma
                Nicoloma @Nicoloma last edited by

                War doch keine lösung habe wieder auf 18 upgedatet!

                arteck 1 Reply Last reply Reply Quote 0
                • arteck
                  arteck Developer Most Active @Nicoloma last edited by

                  @nicoloma setzt die kiste mal neu auf...

                  wechsel auf debian.. probeweise..warum auch immer

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

                    @arteck sagte in Error Log Controller Iobroker:

                    setzt die kiste mal neu auf...
                    wechsel auf debian.. probeweise..warum auch immer

                    Den exakt gleichen Gedanken hatte ich auch! 🙂

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

                      @thomas-braun
                      Kann man mit den Fehlermeldungen den nichts anfangen?

                      host.iobroker
2024-01-04 10:36:18.491	warn	instance system.adapter.trashschedule.0 terminated due to SIGABRT
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[10]: 10: 0x170deb9 [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[9]: 9: 0x12e0a65 v8::internal::Runtime_StackGuard(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[8]: 8: 0xee014f v8::internal::StackGuard::HandleInterrupts() [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[7]: 7: 0xf61ff5 v8::internal::Heap::HandleGCRequest() [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[6]: 6: 0xf5f08d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[5]: 5: 0xf4cba5 [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[4]: 4: 0xd6f697 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[3]: 3: 0xd6f2f0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[2]: 2: 0xa9a7f8 [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[1]: 1: 0xb95b60 node::Abort() [/usr/bin/node]
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[0]: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
host.iobroker
2024-01-04 10:36:18.491	error	Caught by controller[0]: <--- JS stacktrace --->
host.iobroker
2024-01-04 10:36:18.490	error	Caught by controller[0]: nc[269575:0x689a870] 693 ms: Mark-sweep (reduce) 18.9 (21.3) -> 18.3 (21.3) MB, 2.9 / 0.0 ms (+ 0.4 ms in 9 steps since start of marking, biggest step 0.1 ms, walltime since start of marking 10 ms) (average mu = 0.772, current mu = 0.708) allocation f[269575:0x689a870] 714 ms: Mark-sweep (reduce) 19.7 (21.6) -> 19.1 (22.1) MB, 5.9 / 0.0 ms (+ 0.7 ms in 12 steps since start of marking, biggest step 0.1 ms, walltime since start of marking 19 ms) (average mu = 0.717, current mu = 0.681) finalize in
host.iobroker
2024-01-04 10:36:18.490	error	Caught by controller[0]: <--- Last few GCs --->

                      Boah das system neu aufzusetzten ist, da stecken für mich LAIE, ewig viel Arbeit....

                      influx.. die ganzen config.... 😕

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

                        @nicoloma sagte in Error Log Controller Iobroker:

                        Kann man mit den Fehlermeldungen den nichts anfangen?

                        Ich nicht. Ich sehe da nur, das 'irgendwas' den Speicher im Heap auffrisst.
                        Kannst ja mal durch deine Skripte gehen.

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

                          @thomas-braun
                          Ich bin dir für jeden Vorschlag dankbar! Aber wenn ich den Javascript-Adapter stoppe sollen doch alle Skripte auch nicht mehr laufen?
                          Oder laufen Sie vielleicht im Hintergrund weiter?

                          Nicoloma 1 Reply Last reply Reply Quote 0
                          • Nicoloma
                            Nicoloma @Nicoloma last edited by

                            Ich habe schon den Node Option auf

                            Node: -max_old_space_size=8192 erhöt.

                            dan habe ich

                            npm install -g increase-memory-limit

                            durchgeführt..

                            Hat auch nichts gebraucht

                            @Thomas-Braun kennst du eine gute Anleitung für einen evetuellen Umzug?

                            Nicoloma 1 Reply Last reply Reply Quote 0
                            • Nicoloma
                              Nicoloma @Nicoloma last edited by

                              OCH LEUTE * Ich bin stink sauer*
                              Ich glaube ich habe es jetzt.

                              Aus unerklärlichen Gründen, hatte der Trashsheduleadapater eine limitierung von 20MB!

                              51a2501d-2141-429e-9475-5ed884cfbc12-image.png

                              JUHU!!!!!

                              Trotzdem allen vielen dank. Jetzt muss ich nur noch schauen, warum VIS bei mir nicht funktioniert!

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

                              Support us

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

                              638
                              Online

                              32.0k
                              Users

                              80.5k
                              Topics

                              1.3m
                              Posts

                              3
                              32
                              1246
                              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