Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Diverse Fehler, von mir nicht einschätzbar

    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

    UNSOLVED Diverse Fehler, von mir nicht einschätzbar

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

      Hallo zusammen,

      eigentlich war ich nur auf der Suche, weshalb ich heute teils minütlich eine Info über Telegram erhalten habe, ohne das "Triggerwort" zu senden, da habe ich diverse Fehler im Log gesehen.

      Einige Fehler habe ich bereits gesucht, entweder nichts dazu gefunden oder es gab hier keine Lösung.

      Die Fehler laut Log:

      2019-07-24 02:02:19.375 - error: homee.0 uncaught exception: Cannot read property 'send' of null
      2019-07-24 02:02:19.375 - error: homee.0 TypeError: Cannot read property 'send' of null
      2019-07-24 02:02:19.380 - warn: homee.0 Exception: TypeError: Cannot read property 'send' of null
      2019-07-24 02:02:22.031 - error: Caught by controller[0]: at Homee.send (/opt/iobroker/node_modules/homee-api/homee.js:184:18)
      2019-07-24 02:02:22.031 - error: Caught by controller[0]: at createHomeegram (/opt/iobroker/node_modules/iobroker.homee/main.js:190:11)
      2019-07-24 02:02:22.031 - error: Caught by controller[0]: at Socket.adapter.extendObject (/opt/iobroker/node_modules/iobroker.homee/main.js:146:43)
      2019-07-24 02:02:22.031 - error: Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
      2019-07-24 02:02:22.032 - error: Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
      2019-07-24 02:02:22.032 - error: Caught by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
      2019-07-24 02:02:22.032 - error: Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
      2019-07-24 02:02:22.032 - error: Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
      2019-07-24 02:02:22.032 - error: Caught by controller[0]: at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
      2019-07-24 02:02:22.032 - error: Caught by controller[0]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
      2019-07-24 02:02:22.032 - error: host.ioBroker-Pi instance system.adapter.homee.0 terminated with code 6 (uncaught exception)
      2019-07-24 02:02:23.856 - error: web.0 port 8082 already in use
      2019-07-24 02:02:24.820 - error: host.ioBroker-Pi instance system.adapter.web.0 terminated with code 1 ()
      2019-07-24 02:02:25.883 - warn: ping.0 please update js-controller to at least 1.2.0
      2019-07-24 02:02:25.903 - warn: ping.0 please update js-controller to at least 1.2.0
      2019-07-24 02:07:06.323 - error: tr-064-community.0 forEachConfiguredDevice: in GetSpecificHostEntry 0(Samsung-Galaxy-S7/AC:5F:3E:36:74:02):Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: - {"code":""}
      2019-07-24 02:07:06.638 - error: ping.0 uncaught exception: spawn ENOMEM
      2019-07-24 02:07:06.639 - error: ping.0 Error: spawn ENOMEM
      2019-07-24 02:07:09.698 - warn: host.ioBroker-Pi instance system.adapter.admin.0 terminated due to SIGKILL
      2019-07-24 02:07:09.699 - error: host.ioBroker-Pi instance system.adapter.admin.0 terminated with code null ()
      2019-07-24 02:07:09.726 - error: Caught by controller[0]: { Error: spawn ENOMEM
      2019-07-24 02:07:09.726 - error: Caught by controller[0]: at ChildProcess.spawn (internal/child_process.js:313:11)
      2019-07-24 02:07:09.726 - error: Caught by controller[0]: at Object.exports.spawn (child_process.js:508:9)
      2019-07-24 02:07:09.727 - error: Caught by controller[0]: at Object.probe (/opt/iobroker/node_modules/iobroker.ping/lib/ping.js:35:17)
      2019-07-24 02:07:09.727 - error: Caught by controller[0]: at pingAll (/opt/iobroker/node_modules/iobroker.ping/main.js:98:10)
      2019-07-24 02:07:09.727 - error: Caught by controller[0]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.ping/main.js:107:17)
      2019-07-24 02:07:09.728 - error: Caught by controller[0]: at ontimeout (timers.js:498:11)
      2019-07-24 02:07:09.728 - error: Caught by controller[0]: at tryOnTimeout (timers.js:323:5)
      2019-07-24 02:07:09.728 - error: Caught by controller[0]: at Timer.listOnTimeout (timers.js:290:5) errno: 'ENOMEM', code: 'ENOMEM', syscall: 'spawn' }
      2019-07-24 02:07:09.729 - error: host.ioBroker-Pi instance system.adapter.ping.0 terminated with code 6 (uncaught exception)
      2019-07-24 02:07:09.849 - warn: backitup.0 Reconnection to DB.
      2019-07-24 02:07:09.864 - warn: scenes.0 Reconnection to DB.
      2019-07-24 02:07:09.861 - warn: sayit.0 Reconnection to DB.
      2019-07-24 02:07:09.868 - warn: history.0 Reconnection to DB.
      2019-07-24 02:07:09.891 - warn: virtualpowermeter.0 Reconnection to DB.
      2019-07-24 02:07:09.972 - warn: history.0 Reconnection to DB.
      2019-07-24 02:07:09.974 - warn: sayit.0 Reconnection to DB.
      2019-07-24 02:07:09.988 - warn: backitup.0 Reconnection to DB.
      2019-07-24 02:07:09.999 - warn: virtualpowermeter.0 Reconnection to DB.
      2019-07-24 02:07:09.998 - warn: scenes.0 Reconnection to DB.
      2019-07-24 02:07:10.094 - error: sayit.0 already running
      2019-07-24 02:07:10.125 - error: backitup.0 already running
      2019-07-24 02:07:10.138 - error: scenes.0 already running
      2019-07-24 02:07:10.191 - error: host.ioBroker-Pi instance system.adapter.scenes.0 terminated with code 7 (Adapter already running)
      2019-07-24 02:07:10.579 - warn: telegram.0 Reconnection to DB.
      2019-07-24 02:07:10.591 - warn: text2command.0 Reconnection to DB.
      2019-07-24 02:07:10.697 - warn: telegram.0 Reconnection to DB.
      2019-07-24 02:07:10.703 - warn: text2command.0 Reconnection to DB.
      2019-07-24 02:07:10.762 - warn: tr-064-community.0 Reconnection to DB.
      2019-07-24 02:07:19.217 - error: tr-064-community.0 timeout - "timeout"
      2019-07-24 02:07:19.219 - error: tr-064-community.0 ~
      2019-07-24 02:07:19.219 - error: tr-064-community.0 ~~ Fatal error. Can not connect to your FritzBox.
      2019-07-24 02:07:19.220 - error: tr-064-community.0 ~~ If configuration, networt, IP address, etc. ok, try to restart your FritzBox
      2019-07-24 02:07:19.220 - error: tr-064-community.0 ~
      2019-07-24 02:07:20.107 - error: tr-064-community.0 timeout - "timeout"
      2019-07-24 02:07:20.108 - error: tr-064-community.0 ~
      2019-07-24 02:07:20.109 - error: tr-064-community.0 ~~ Fatal error. Can not connect to your FritzBox.
      2019-07-24 02:07:20.109 - error: tr-064-community.0 ~~ If configuration, networt, IP address, etc. ok, try to restart your FritzBox
      2019-07-24 02:07:20.109 - error: tr-064-community.0 ~
      
      

      Der Fehler, der wohl das minütliche Senden bei Telegram ausgelöst hat, ist wohl

      2019-07-24 05:07:00.142 - error: host.ioBroker-Pi instance system.adapter.homee.0 terminated with code 156 ()
      

      denn dieser erscheint zur selben Zeit minütlich.

      Zudem ist mir aufgefallen, dass ich seit heute beim Raspberry das Passwort doppelt eingeben muss:

      login as: pi
      pi@192.168.178.66's password:
      Linux ioBroker-Pi 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l
      
      The programs included with the Debian GNU/Linux system are free software;
      the exact distribution terms for each program are described in the
      individual files in /usr/share/doc/*/copyright.
      
      Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      permitted by applicable law.
      Last login: Mon Jul 22 22:51:44 2019 from 192.168.178.3x
      
      SSH is enabled and the default password for the 'pi' user has not been changed.
      This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password.
      
      pi@ioBroker-Pi:~ $ sudo reboot
      [sudo] Passwort für pi:
      
      

      Ich kann diese Nachrichten leider alle nicht einschätzen. Muss ich mir Gedanken machen? bzw. kann ich mein System verbessern?

      Ich habe die letzten Wochen täglich Fehlermeldungen gegooglt, da mir immer wieder welche aufgefallen sind. Nun ist es extrem komprimiert.

      Danke für jeden Hinweis...

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

        du hast mehrere Probleme

        @PatrickFro sagte in Diverse Fehler, von mir nicht einschätzbar:

        please update js-controller to at least 1.2.0

        bissel alt dein system was.... 1.5.13 ist das akutelle.. also erstmal update.. vergiss den admin nicht upzudaten

        web.0 port 8082 already in use
        
        host.ioBroker-Pi instance system.adapter.scenes.0 terminated with code 7 (Adapter already running)
        
        1 Reply Last reply Reply Quote 0
        • P
          PatrickFro last edited by

          pi@ioBroker-Pi:/opt/iobroker $ sudo iobroker stop
          [sudo] Passwort für pi:
          pi@ioBroker-Pi:/opt/iobroker $ sudo npm install iobroker.js-controller
          [..................] | loadIdealTree:loadAllDepsIntoIdealTree: sill install loadIdealTree
          pi@ioBroker-Pi:/opt/iobroker $ sudo npm install iobroker.js-controller
          [..................] - rollbackFailedOptional: verb npm-session 476e776ccda2fc6e
          
          > iobroker.js-controller@1.5.14 preinstall /opt/iobroker/node_modules/iobroker.js-controller
          > node lib/preinstallCheck.js
          
          NPM version: 6.10.1
          npm version >= 5: disabling package-lock
          
          > diskusage@1.1.3 install /opt/iobroker/node_modules/diskusage
          > node-gyp rebuild
          
          gyp WARN EACCES user "pi" does not have permission to access the dev dir "/root/.cache/node-gyp/8.15.0"
          gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
          gyp ERR! configure error
          gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/diskusage/build'
          gyp ERR! System Linux 4.14.79-v7+
          gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
          gyp ERR! cwd /opt/iobroker/node_modules/diskusage
          gyp ERR! node -v v8.15.0
          gyp ERR! node-gyp -v v5.0.2
          gyp ERR! not ok
          
          > iobroker.js-controller@1.5.14 install /opt/iobroker/node_modules/iobroker.js-controller
          > node iobroker.js setup first
          
          Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-cont                                      roller/lib/setup/../../_service_iobroker.bat'
          Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-cont                                      roller/lib/setup/../../iobroker.bat'
          fs.js:885
            return binding.mkdir(pathModule._makeLong(path),
                           ^
          
          Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../tmp'
              at Object.fs.mkdirSync (fs.js:885:18)
              at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:189:58)
              at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:653:27
              at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:691:15)
              at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3193:5)
              at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:100)
              at Module._compile (module.js:653:30)
              at Object.Module._extensions..js (module.js:664:10)
              at Module.load (module.js:566:32)
              at tryModuleLoad (module.js:506:12)
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: diskusage@1.1.3 (node_modules/diskusage):
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: diskusage@1.1.3 install: `node-gyp rebuild`
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
          
          npm ERR! code ELIFECYCLE
          npm ERR! errno 1
          npm ERR! iobroker.js-controller@1.5.14 install: `node iobroker.js setup first`
          npm ERR! Exit status 1
          npm ERR!
          npm ERR! Failed at the iobroker.js-controller@1.5.14 install script.
          npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /root/.npm/_logs/2019-07-25T06_21_51_148Z-debug.log
          pi@ioBroker-Pi:/opt/iobroker $
          
          pi@ioBroker-Pi:/opt/iobroker $ sudo iobroker start
          
          

          Dieses ist nun leider das Ergebnis, dazu kommt, dass IoBroker wohl nicht mehr startet... HILFE... Neustart Raspi habe ich gemacht, keine Besserung

          1 Reply Last reply Reply Quote 0
          • sigi234
            sigi234 Forum Testing Most Active last edited by Negalein

            Hast du den Fixer schon mal gemacht?

            curl -sL https://iobroker.net/fix.sh | bash -
            
            1 Reply Last reply Reply Quote 0
            • P
              PatrickFro last edited by

              ja. ist schon 3 Mal gelaufen, zuletzt vor wenigen Tagen

              sigi234 1 Reply Last reply Reply Quote 0
              • sigi234
                sigi234 Forum Testing Most Active @PatrickFro last edited by Negalein

                @PatrickFro sagte in Diverse Fehler, von mir nicht einschätzbar:

                ja. ist schon 3 Mal gelaufen, zuletzt vor wenigen Tagen

                Was kommt bei:

                cd /opt/iobroker
                iobroker list instances
                
                1 Reply Last reply Reply Quote 0
                • P
                  PatrickFro last edited by

                  Du bist mein Held, gerade nochmal laufen lassen, die Installation nochmal angestoßen und nun läuft es scheinbar wieder

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

                  Support us

                  ioBroker
                  Community Adapters
                  Donate

                  947
                  Online

                  31.9k
                  Users

                  80.2k
                  Topics

                  1.3m
                  Posts

                  error
                  3
                  7
                  381
                  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