Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. IoBroker mach nur noch Probleme

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    IoBroker mach nur noch Probleme

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

      Ich verstehe noch nicht wie das einspielen des alten Backups und npm downgrade das ram Problem lösen soll …

      Ich hätte er den Stand genommen den du hattest und hätte mal mit top weitergemacht und mit die Prozesse nach Speichernutzung sortieren lassen.

      Also ja 1GB wird recht schnell knapp aber wenn da nur der js-Controller läuft sollte der Speicher nicht do verbraucht aussehen.

      Gesendet vom Handy ...

      1 Reply Last reply Reply Quote 0
      • E
        Elektroman last edited by

        Ich habe irgendwie beim updaten des jscontrollers oder so einen Fehler gemacht.

        Jetzt habe ich als erstes alte Images vom Juni wieder auf die SD Karten aufgespielt und mich langsam herangetastet

        Bis jetzt läuft noch alles. Morgen werde ich dann noch die Adapter updaten

        1 Reply Last reply Reply Quote 0
        • E
          Elektroman last edited by

          Hallo,

          was soll ich sagen, die Ram Probleme sind weg.

          Ich habe aber leider weiterhin Adapter die nicht mehr funktionieren u.a. "s7" bzw. Adapter die immer mal wieder neu starten (grün-rot-grün)

          host.raspberrypi	2018-10-11 18:39:59.376	error	instance system.adapter.s7.0 terminated with code 0 (OK)
          host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Module._compile (module.js:577:32)
          host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/lib/node-snap7.js:9:45)
          host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/node_modules/bindings/bindings.js:76:44)
          host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at require (internal/module.js:20:19)
          host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at Module.require (module.js:504:17)
          host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Function.Module._load (module.js:445:3)
          host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at tryModuleLoad (module.js:453:12)
          host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Module.load (module.js:494:32)
          host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:604:18)
          host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Error (native)
          host.raspberrypi	2018-10-11 18:39:59.372	error	Caught by controller[0]: Error: Module version mismatch. Expected 48, got 46.</anonymous>
          
          1 Reply Last reply Reply Quote 0
          • Dutchman
            Dutchman Developer Most Active Administrators last edited by

            Wen deine docker Installation im Eimer ist Spiele nicht lange Rum…

            Backup machen, sicherstellen. Docker Container und Image Weck, neues drauf und Backup einspielen Dan ist dein npm Problem gelöst

            Sent from my iPhone using Tapatalk

            1 Reply Last reply Reply Quote 0
            • E
              Elektroman last edited by

              Hallo Dutchman,

              läuft aber nicht über Docker. Docker gibt es für mein NAS nicht.

              Ich bin nicht der Profi, ich glaube aber das NAS ist nicht mehr mein Problem

              1 Reply Last reply Reply Quote 0
              • E
                Elektroman last edited by

                Platform: linux

                Architecture: arm

                CPUs: 2

                Speed: 0 MHz

                Model: Marvell PJ4Bv7 Processor rev 2 (v7l)

                RAM: 1009.4 MB

                System uptime: 4 T. 08:33:45

                Node.js: v6.12.3

                NPM: 4.6.1

                adapters count: 198

                Uptime: 03:57:02

                1 Reply Last reply Reply Quote 0
                • E
                  Elektroman last edited by

                  Ich komme nicht mehr weiter

                  Es kommen immer neue Fehlermeldungen dazu:

                  m-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                  hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                  hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                  hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.516	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
                  hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
                  hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
                  hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                  hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                  hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                  hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
                  hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
                  hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
                  hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
                  hm-rpc.3	2018-10-11 20:37:24.513	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                  
                  1 Reply Last reply Reply Quote 0
                  • E
                    Elektroman last edited by

                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.429	error	instance system.adapter.web.0 terminated with code 7 (Adapter already running)
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	info	Restart adapter system.adapter.hm-rpc.0 because enabled
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	error	instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.043	info	Restart adapter system.adapter.hm-rega.0 because enabled
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.042	error	instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.197	info	Restart adapter system.adapter.javascript.1 because enabled
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.196	error	instance system.adapter.javascript.1 terminated with code 7 (Adapter already running)
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.648	info	Restart adapter system.adapter.javascript.2 because enabled
                    host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.646	error	instance system.adapter.javascript.2 terminated with code 7 (Adapter already running)
                    
                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 last edited by

                      @Elektroman:

                      Hallo,

                      was soll ich sagen, die Ram Probleme sind weg.

                      Ich habe aber leider weiterhin Adapter die nicht mehr funktionieren u.a. "s7" bzw. Adapter die immer mal wieder neu starten (grün-rot-grün)

                      host.raspberrypi	2018-10-11 18:39:59.376	error	instance system.adapter.s7.0 terminated with code 0 (OK)
                      host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Module._compile (module.js:577:32)
                      host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/lib/node-snap7.js:9:45)
                      host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/node_modules/bindings/bindings.js:76:44)
                      host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at require (internal/module.js:20:19)
                      host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at Module.require (module.js:504:17)
                      host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Function.Module._load (module.js:445:3)
                      host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at tryModuleLoad (module.js:453:12)
                      host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Module.load (module.js:494:32)
                      host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:604:18)
                      host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Error (native)
                      host.raspberrypi	2018-10-11 18:39:59.372	error	Caught by controller[0]: Error: Module version mismatch. Expected 48, got 46.</anonymous>
                      ```` `  
                      

                      Kann es sein das du nodejs Update gemacht hast?

                      Betroffenen Adapter Neu installieren sollte das fixen.

                      Oder in das Verzeichnis des Adapters in node_modules und npm rebuild eingeben.

                      Gesendet vom Handy …

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

                        @Elektroman:

                        Ich komme nicht mehr weiter

                        Es kommen immer neue Fehlermeldungen dazu:

                        m-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                        hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                        hm-rpc.3	2018-10-11 20:37:24.517	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                        hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.517	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.516	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
                        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
                        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","STATE",true] BOOL
                        hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.515	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                        hm-rpc.3	2018-10-11 20:37:24.515	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
                        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
                        hm-rpc.3	2018-10-11 20:37:24.514	error	binrpc -> setValue ["1","STATE",true] BOOL
                        hm-rpc.3	2018-10-11 20:37:24.514	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.513	error	Error: You are sending too fast
                        hm-rpc.3	2018-10-11 20:37:24.513	error	binrpc -> setValue ["1","ON_TIME",30] FLOAT
                        ```` `  
                        

                        Welches deiner Skripte setzt diese States? Dann checke diese Skripte. Scheinbar läuft da was Amok und sendet viel zu schnell Kommandos an hm-rpc.3. Und genau so ein Skript Problem kann die Ursache für „reconnection to dB“ sein.

                        Gesendet vom Handy …

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

                          @Elektroman:

                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.429	error	instance system.adapter.web.0 terminated with code 7 (Adapter already running)
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	info	Restart adapter system.adapter.hm-rpc.0 because enabled
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.167	error	instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.043	info	Restart adapter system.adapter.hm-rega.0 because enabled
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:17.042	error	instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.197	info	Restart adapter system.adapter.javascript.1 because enabled
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:14.196	error	instance system.adapter.javascript.1 terminated with code 7 (Adapter already running)
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.648	info	Restart adapter system.adapter.javascript.2 because enabled
                          host.ioBroker-Pi3-slave-sw	2018-10-11 20:38:16.646	error	instance system.adapter.javascript.2 terminated with code 7 (Adapter already running)
                          ```` `  
                          

                          Siehe letzter Post. Ich tippe darauf das bei dir irgend ein Skript Müll baut und das der verursacher ist.

                          Gesendet vom Handy …

                          1 Reply Last reply Reply Quote 0
                          • E
                            Elektroman last edited by

                            Ok, vielen Dank für die schnelle Hilfe

                            Ich schaue morgen mal weiter.

                            Ich habe für heute die Nase voll. Ich drehe mich jetzt schon seit Wochen im Kreis

                            1 Reply Last reply Reply Quote 0
                            • E
                              Elektroman last edited by

                              @apollon77:

                              @Elektroman:

                              Hallo,

                              was soll ich sagen, die Ram Probleme sind weg.

                              Ich habe aber leider weiterhin Adapter die nicht mehr funktionieren u.a. "s7" bzw. Adapter die immer mal wieder neu starten (grün-rot-grün)

                              host.raspberrypi	2018-10-11 18:39:59.376	error	instance system.adapter.s7.0 terminated with code 0 (OK)
                              host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Module._compile (module.js:577:32)
                              host.raspberrypi	2018-10-11 18:39:59.376	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/lib/node-snap7.js:9:45)
                              host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.s7/node_modules/node-snap7/node_modules/bindings/bindings.js:76:44)
                              host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at require (internal/module.js:20:19)
                              host.raspberrypi	2018-10-11 18:39:59.375	error	Caught by controller[0]: at Module.require (module.js:504:17)
                              host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Function.Module._load (module.js:445:3)
                              host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at tryModuleLoad (module.js:453:12)
                              host.raspberrypi	2018-10-11 18:39:59.374	error	Caught by controller[0]: at Module.load (module.js:494:32)
                              host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:604:18)
                              host.raspberrypi	2018-10-11 18:39:59.373	error	Caught by controller[0]: at Error (native)
                              host.raspberrypi	2018-10-11 18:39:59.372	error	Caught by controller[0]: Error: Module version mismatch. Expected 48, got 46.</anonymous>
                              ```` `  
                              

                              Kann es sein das du nodejs Update gemacht hast?

                              Betroffenen Adapter Neu installieren sollte das fixen.

                              Oder in das Verzeichnis des Adapters in node_modules und npm rebuild eingeben.

                              Gesendet vom Handy … `

                              Beim Master oder bei einem der Slaves?

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

                                Na da Wonder s7 Adapter installiert ist der da meckert …

                                Gesendet vom Handy ...

                                1 Reply Last reply Reply Quote 0
                                • E
                                  Elektroman last edited by

                                  Neuer Tag neues Glück

                                  Hallo,

                                  ich habe beim Master und bei einem der zwei Slave das Verzeichnis "iobroker.s7" vorhanden? Habe es bei beiden es ausgeführt

                                  1 Reply Last reply Reply Quote 0
                                  • E
                                    Elektroman last edited by

                                    Es sind mehrere Adapter 😢

                                    npm rebuild ergab keine Besserung

                                    host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:39.388	info	Restart adapter system.adapter.admin.0 because enabled
                                    host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:39.387	error	instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
                                    host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:38.401	info	Restart adapter system.adapter.hm-rega.0 because enabled
                                    host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:38.401	error	instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
                                    host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:36.886	info	instance system.adapter.hm-rega.0 started with pid 3386
                                    host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:36.439	info	instance system.adapter.admin.0 started with pid 3380
                                    host.ioBroker-Pi3-slave-sw	2018-10-12 18:40:35.691	info	Restart adapter system.adapter.hm-rpc.0 because enabled
                                    
                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 last edited by

                                      npm rebuild von s7 sorgt erstmal nur dafür das s7 wieder tut … alles andere ist was anderes.

                                      Schau Die betroffenen Adapter an die mit error 7 gemeckert werden und kille die prozesse die da laufen oder mach nen reboot

                                      1 Reply Last reply Reply Quote 0
                                      • E
                                        Elektroman last edited by

                                        Ich bin gerade vorsichtig optimistisch. 😉

                                        Habe vor ca. 3 Std einen reboot an allen Hosts durchgeführt, bis jetzt bleibt es ruhig

                                        Hat doch was gebracht, danke dafür

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

                                        Support us

                                        ioBroker
                                        Community Adapters
                                        Donate

                                        478
                                        Online

                                        31.6k
                                        Users

                                        79.5k
                                        Topics

                                        1.3m
                                        Posts

                                        6
                                        46
                                        3409
                                        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