Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller läuft auf Volllast

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    js-controller läuft auf Volllast

    This topic has been deleted. Only users with topic management privileges can see it.
    • crunchip
      crunchip Forum Testing Most Active @Th3RockYeah last edited by

      @th3rockyeah sagte in js-controller 4.0 jetzt im BETA/LATEST!:

      non-npm

      @apollon77 kann es sein das da mit npm etwas nicht passt?

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

        @crunchip Ne das sind GitHub installs ... aber habs nur für email und weatherunderground gesehen, da sollte es eher irrelevant sein ... Javascript 5.4 wäre eher ein Kandidat weil der Ordner anlegt, aber bei den 5 Skripten sollte das fast egal sein

        Denke man muss jetzt mal strukturiert rangehen weil ausser dem controller nichts irklich auffällig ist

        1 Reply Last reply Reply Quote 0
        • T
          Th3RockYeah @apollon77 last edited by

          @apollon77
          Ok, mach ich. ich starte nach und nach die Adapter und schaue, ob etwas auffällig ist.

          Den MQTT Adapter nutze ich nicht, nur Shelly.

          Nun hat sich der JS-Controller beruhigt und ich kann den IOBroker wieder normal nutzen. Das hier waren die letzten Fehler im Log:

          	Zeit
warn
Nachricht

zigbee.0
2022-03-21 11:49:59.635	warn	DeviceAvailability:Failed to ping 0x000d6ffffe2e4a54 TRADFRI signal repeater

zigbee.0
2022-03-21 11:45:23.370	warn	State value to set for "zigbee.0.00158d00042176ed.pressure" has value "95992" greater than max "10000"

radar2.0
2022-03-21 11:34:11.290	warn	State "radar2.0._uIPs.SonosZP_xxx-xxx-xxx-xxx" has no existing object, this might lead to an error in future versions

...

radar2.0
2022-03-21 11:34:11.273	warn	State "radar2.0._uIPs.SonosZP_xxx-xxx-xxx-xxx" has no existing object, this might lead to an error in future versions

radar2.0
2022-03-21 11:34:11.119	warn	State "radar2.0._uIPs.shellyplug-s-DE15FC_xxx-xxx--xxx-xx" has no existing object, this might lead to an error in future versions

...

radar2.0
2022-03-21 11:34:11.040	warn	State "radar2.0._uIPs.shellyplug-s-DE15FC_xxx-xxx-xxx-xxx" has no existing object, this might lead to an error in future versions

radar2.0
2022-03-21 11:34:10.070	warn	State "radar2.0._uIPs.HDot_xxx-xxx-xxx-xxx" has no existing object, this might lead to an error in future versions

....

radar2.0
2022-03-21 11:34:10.034	warn	State "radar2.0._uIPs.HDot_xxx-xxx-xxx-xxx" has no existing object, this might lead to an error in future versions

radar2.0
2022-03-21 11:34:10.032	warn	State "radar2.0._uIPs.HDot_xxx-xxx-xxx-xxx" has no existing object, this might lead to an error in future versions

zigbee.0
2022-03-21 11:25:12.257	warn	DeviceAvailability:Stopping to ping 0x680ae2fffe9c8577 TRADFRI Signal Repeater after 4 ping attempts

zigbee.0
2022-03-21 11:19:39.577	warn	State value to set for "zigbee.0.00158d000464c66d.pressure" has value "96079" greater than max "10000"

radar2.0
2022-03-21 11:12:30.875	warn	scanDelay increased to 71.119 seconds, delayAway to 2 minutes!
host.raspberrypi
2022-03-21 11:07:54.826	error	instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

radar2.0
2022-03-21 11:07:54.333	warn	Error {} is setState for _uIPs with {"val":"[]","ack":true,"from":"system.adapter.radar2.0","user":"system.user.admin"}

radar2.0
2022-03-21 11:07:54.330	warn	get state error: Connection is closed.

radar2.0
2022-03-21 11:07:54.329	warn	Could not perform strict object check of state radar2.0._uIPs: DB closed

radar2.0
2022-03-21 11:07:53.861	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.860	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.859	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62)

radar2.0
2022-03-21 11:07:53.858	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.857	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.854	warn	redis get radar2.0._uIPs.192-168-170-210, error - Connection is closed.

radar2.0
2022-03-21 11:07:53.853	warn	Error {} is setState for radar2.0._uIPs.xxx-xxx-xxx-xxx with {"val":"{ ipAddress: 'xxx.xxx.xxxx.xxxx', macAddress: '8:33:4d:ca', by: 'arp', hosts: [], getMacVendor: 'N/A'\n}","ack":true,"from":"system.adapter.radar2.0","user":"system.user.admin"}

radar2.0
2022-03-21 11:07:53.852	warn	get state error: Connection is closed.

radar2.0
2022-03-21 11:07:53.851	warn	Error {} is setState for info.connection with {"val":false,"ack":true,"from":"system.adapter.radar2.0","user":"system.user.admin"}

radar2.0
2022-03-21 11:07:53.850	warn	get state error: Connection is closed.

radar2.0
2022-03-21 11:07:53.652	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.651	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.650	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62)

radar2.0
2022-03-21 11:07:53.650	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.649	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.647	warn	redis get radar2.0._uIPs.xxx-xxx-xxx-xxx, error - Connection is closed.

radar2.0
2022-03-21 11:07:53.646	warn	Error {} is setState for _uIPs.xxx-xxx-xxx-xxx with {"val":"{ ipAddress: 'xxx.xxx.xxx.xxx', macAddress: '33:4d:ca', by: 'arp', hosts: [], getMacVendor: 'N/A'\n}","ack":true,"from":"system.adapter.radar2.0","user":"system.user.admin"}

radar2.0
2022-03-21 11:07:53.645	warn	get state error: Connection is closed.

radar2.0
2022-03-21 11:07:53.332	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.331	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.331	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62)

radar2.0
2022-03-21 11:07:53.330	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.329	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.320	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.320	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.319	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)

radar2.0
2022-03-21 11:07:53.319	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.318	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.316	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.315	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.315	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)

radar2.0
2022-03-21 11:07:53.314	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.313	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.311	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.289	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.288	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)

radar2.0
2022-03-21 11:07:53.287	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.286	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.283	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.281	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.279	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)

radar2.0
2022-03-21 11:07:53.278	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.277	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.275	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.275	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.274	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)

radar2.0
2022-03-21 11:07:53.273	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.272	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.270	warn	Unhandled rejection at

radar2.0
2022-03-21 11:07:53.269	error	Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.268	error	TypeError: Cannot read property 'hosts' of undefined at Timeout.scanAll (/opt/iobroker/node_modules/iobroker.radar2/radar2.js:447:62) at runNextTicks (internal/process/task_queues.js:60:5) at processImmediate (internal/timers.js:437:9)

radar2.0
2022-03-21 11:07:53.268	error	unhandled promise rejection: Cannot read property 'hosts' of undefined

radar2.0
2022-03-21 11:07:53.267	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

radar2.0
2022-03-21 11:07:53.264	warn	redis get radar2.0._uIPs.XXX-XXX-XXX-XXX, error - Connection is closed.

          Nur damit ich es gefragt habe, weil es mich nicht "loslässt". Kann die SD-Card kaputt sein?

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

            @th3rockyeah sagte in js-controller 4.0 jetzt im BETA/LATEST!:

            Kann die SD-Card kaputt sein?

            Möglich. Die eine Karte, die mir mal verreckt ist hat sich in den Logfiles sang- und klanglos verabschiedet.
            Schau mal mit

            dmesg -T | grep -i ext4

            danach.

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

              @thomas-braun
              Das kommt als Antwort. Was bedeutet das?

              [Mo Mär 21 10:52:17 2022]  ext4_filemap_fault+0x3c/0x818
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Th3RockYeah last edited by

                @th3rockyeah

                Nur die eine Zeile?
                Da muss mehr kommen.
                Aber ext4_filemap_fault ist schon mal schlecht, das sollte nicht kommen.

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

                  @thomas-braun
                  Ja nur die eine Zeile:
                  fc4f4761-adf3-4212-9a01-091bccfe5d04-image.png

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

                    @th3rockyeah

                    Dann würde ich sagen, die Karte/das Dateisystem ist fehlerhaft.

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

                      @thomas-braun Ok, dann setze ich hier einmal ebenfalls an.
                      Was müsste denn dort normalerweise stehen, wenn die SD-Card OK wäre?

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

                        @th3rockyeah

                        Da tauchen dann 4 Zeilen auf.
                        Ich komme gerade an mein System nicht ran, sonst hätte ich es gezeigt.

                        Aus deinem obigen Log:

                        ping invoked oom-killer: gfp_mask=0x400dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO), order=0, oom_score_adj=0

                        gfp_mask ist auch nah am System/RAM/Dateisystem. Ich würde sagen, das Ding schwimmt schon nicht mehr, das ist abgesoffen.

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

                          @thomas-braun ok, danke dir! Ich habe jetzt auch mehrere Zeilen bei dem Aufruf in der Console.

                          Ich habe nun den IoBroker auf einem USB Stick neu aufgesetzt und aktuell läuft er total smooth. Ich beobachte es noch eine Weile, aber nach einem Iobroker restart ist das Verhalten normal, der js-controller läuft ohne starke CPU oder Memory last.
                          Es scheint die SD-Card gewesen zu sein #fingercrossed.

                          @apollon77 , @thomas-braun, @Diginix , @crunchip: DANKE für euren Support!!! Kudos to you all! 🙂

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

                            @th3rockyeah sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                            Ich habe jetzt auch mehrere Zeilen bei dem Aufruf in der Console.

                            Welche?

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

                              @thomas-braun
                              diese hier:

                              pi@raspberrypiNew:~ $ dmesg -T | grep -i ext4
[Mon Mar 21 15:27:04 2022] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=DC:A6:32:4F:DD:06 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=ttyS0,115200 console=tty1 root=PARTUUID=dc01fa95-02 rootfstype=ext4 fsck.repair=yes rootwait
[Mon Mar 21 15:27:07 2022] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[Mon Mar 21 15:27:07 2022] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[Mon Mar 21 15:27:08 2022] EXT4-fs (sda2): re-mounted. Opts: (null)
pi@raspberrypiNew:~ $
                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Th3RockYeah last edited by

                                @th3rockyeah

                                Ja, so muss das aussehen.

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

                                  @thomas-braun Yihaa! Danke 🙂

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

                                    @th3rockyeah Interessant ...

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

                                      Ich habe diesen Thread mal aus dem controller4.0-Thread herausgelöst.

                                      @Th3RockYeah
                                      Bitte meinen provisorisch gewählten Threadtitel noch anpassen. Ich habe nicht alles gelesen

                                      T 1 Reply Last reply Reply Quote 0
                                      • T
                                        Th3RockYeah @Homoran last edited by Th3RockYeah

                                        @homoran done. 🙂

                                        Für alle: Bei mir sind seit dem Umzug auf den USB Stick alle Probleme weg, die ich in der letzten Zeit hatte. Angefangen von langsamer Performance bis hinzu, dass Zigbee einige Message verschluckt hat. Ich wollte dies nur noch mal als Ergänzung schreiben, da eine sterbende SD-Card nicht offensichtlich ist.

                                        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

                                        982
                                        Online

                                        31.8k
                                        Users

                                        80.0k
                                        Topics

                                        1.3m
                                        Posts

                                        6
                                        42
                                        1447
                                        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