Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. ioBroker startet in Endlosschleife

    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

    SOLVED ioBroker startet in Endlosschleife

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

      Hallo,
      ich bräuchte mal Hilfe von Experten...

      Der ioBroker lief eigentlich ziemlich stabil, doch nach einem Neustart verfängt er sich in einer Endlosschleife und so ist auch kein Zugriff auf den Admin möglich.

      per Tail -f habe ich mir die Aktivitäten angeschaut und folgendes wird ins Log geschrieben:

      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19456": 1
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "killall.sh": 123
      Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Starting daemon iobroker...
      Mon Dec 02 2019 10:16:23 GMT+0100 (CET)Daemon iobroker started
      Mon Dec 02 2019 10:16:24 GMT+0100 (CET)Restarting iobroker...
      Mon Dec 02 2019 10:16:24 GMT+0100 (CET)Stopping daemon iobroker...
      Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19521": 1
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "killall.sh": 123
      Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Starting daemon iobroker...
      Mon Dec 02 2019 10:16:31 GMT+0100 (CET)Daemon iobroker started
      Mon Dec 02 2019 10:16:32 GMT+0100 (CET)Restarting iobroker...
      Mon Dec 02 2019 10:16:32 GMT+0100 (CET)Stopping daemon iobroker...
      
      

      list instances zeigt folgendes an:

      pi@io_broker:/opt/iobroker $ iobroker list instances
      system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
      system.adapter.alexa2.0                : alexa2      -  enabled
      system.adapter.amazon-dash.0           : amazon-dash -  enabled
      system.adapter.backitup.0              : backitup    -  enabled
      system.adapter.cloud.0                 : cloud       -  enabled
      system.adapter.discovery.0             : discovery   - disabled
      system.adapter.flot.0                  : flot        -  enabled
      system.adapter.fritzdect.0             : fritzdect   -  enabled
      system.adapter.harmony.0               : harmony     - disabled
      system.adapter.hue.0                   : hue         - disabled, port: 80
      system.adapter.icons-mfd-png.0         : icons-mfd-png -  enabled
      system.adapter.icons-mfd-svg.0         : icons-mfd-svg -  enabled
      system.adapter.info.0                  : info        -  enabled
      system.adapter.javascript.0            : javascript  -  enabled
      system.adapter.mihome-vacuum.0         : mihome-vacuum -  enabled, port: 54321
      system.adapter.mqtt.0                  : mqtt        - disabled, port: 1883
      system.adapter.node-red.0              : node-red    - disabled, port: 1880, bind: 0.0.0.0
      system.adapter.parser.0                : parser      -  enabled
      system.adapter.scenes.0                : scenes      -  enabled
      system.adapter.sql.0                   : sql         -  enabled, port: 0
      system.adapter.telegram.0              : telegram    - disabled, port: 8443, bind: 0.0.0.0
      system.adapter.text2command.0          : text2command -  enabled
      system.adapter.tr-064.0                : tr-064      - disabled
      system.adapter.vis-colorpicker.0       : vis-colorpicker -  enabled
      system.adapter.vis-hqwidgets.0         : vis-hqwidgets -  enabled
      system.adapter.vis-jqui-mfd.0          : vis-jqui-mfd -  enabled
      system.adapter.vis.0                   : vis         -  enabled
      system.adapter.web.0                   : web         -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      
      

      Wo kann ich ansetzen?

      Info zu Versionen:

      pi@io_broker:/opt/iobroker $ npm -v
      6.4.1
      pi@io_broker:/opt/iobroker $ node -v
      v8.15.0
      pi@io_broker:/opt/iobroker $ nodejs -v
      v8.15.0
      
      

      Adapter Versionen:

      pi@io_broker:/opt/iobroker $ iobroker list adapters
      system.adapter.admin                   : admin       - 3.6.2
      system.adapter.discovery               : discovery   - 1.2.1
      system.adapter.mihome-vacuum           : mihome-vacuum - 1.1.5
      system.adapter.cloud                   : cloud       - 2.6.2
      system.adapter.web                     : web         - 2.4.1
      system.adapter.sql                     : sql         - 1.9.2
      system.adapter.flot                    : flot        - 1.9.2
      system.adapter.node-red                : node-red    - 1.7.1
      system.adapter.harmony                 : harmony     - 1.0.0
      system.adapter.hue                     : hue         - 1.1.0
      system.adapter.tr-064                  : tr-064      - 0.4.18
      system.adapter.backitup                : backitup    - 0.4.2
      system.adapter.mqtt                    : mqtt        - 2.0.4
      system.adapter.telegram                : telegram    - 1.3.6
      system.adapter.text2command            : text2command - 1.2.4
      system.adapter.scenes                  : scenes      - 1.1.0
      system.adapter.alexa2                  : alexa2      - 2.6.4
      system.adapter.parser                  : parser      - 1.0.7
      system.adapter.javascript              : javascript  - 4.0.5
      system.adapter.fritzdect               : fritzdect   - 0.1.4
      system.adapter.vis                     : vis         - 1.1.10
      system.adapter.yahka                   : yahka       - 0.8.2
      system.adapter.vis-hqwidgets           : vis-hqwidgets - 1.1.2
      system.adapter.vis-colorpicker         : vis-colorpicker - 1.1.1
      system.adapter.vis-jqui-mfd            : vis-jqui-mfd - 1.0.12
      system.adapter.icons-mfd-svg           : icons-mfd-svg - 1.0.2
      system.adapter.icons-mfd-png           : icons-mfd-png - 1.0.2
      system.adapter.amazon-dash             : amazon-dash - 0.3.1
      system.adapter.info                    : info        - 1.4.1
      
      

      Vielen Dank!

      Homoran 1 Reply Last reply Reply Quote 0
      • J.A.R.V.I.S.
        J.A.R.V.I.S. Developer last edited by J.A.R.V.I.S.

        Probier mal den Fixer aus. Wenn du den ioBroker vor über einem Jahr installiert hast, dann kann dir der Beitrag vielleicht helfen. Aber bitte vorher sichern!!

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

          @Kaldi sagte in ioBroker startet in Endlosschleife:

          nach einem Neustart

          Der Neustart wurde nicht etwa gemacht, weil etwas upgedatet wurde?

          K 1 Reply Last reply Reply Quote 0
          • K
            Kaldi @Homoran last edited by Kaldi

            @Homoran sagte in ioBroker startet in Endlosschleife:

            @Kaldi sagte in ioBroker startet in Endlosschleife:

            nach einem Neustart

            Der Neustart wurde nicht etwa gemacht, weil etwas upgedatet wurde?

            Nicht, dass ich wüsste. Also nicht aktiv - wobei mich die Versionsnummer des "admin" etwas verwundert. Installiert wurde der ioBroker vor etwas über einem Jahr.

            1 Reply Last reply Reply Quote 0
            • J.A.R.V.I.S.
              J.A.R.V.I.S. Developer last edited by

              @Kaldi hast du schon versucht, den Loop zu unterbrechen und den ioBroker manuell zu starten?

              K 1 Reply Last reply Reply Quote 0
              • K
                Kaldi @J.A.R.V.I.S. last edited by

                @J-A-R-V-I-S sagte in ioBroker startet in Endlosschleife:

                @Kaldi hast du schon versucht, den Loop zu unterbrechen und den ioBroker manuell zu starten?

                Ja. ioBroker mit "iobroker stop" angehalten und mit "iobroker start" und alternativ auch mit "iobroker restart" wieder versucht zu starten.

                Gibt es noch ein Log, welches mir evtl. Detailinformationen geben könnte?

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

                  @Kaldi /opt/iobroker/log/Datum _des_Tages

                  K 1 Reply Last reply Reply Quote 0
                  • K
                    Kaldi @Homoran last edited by

                    @Homoran sagte in ioBroker startet in Endlosschleife:

                    @Kaldi /opt/iobroker/log/Datum _des_Tages

                    Danke. Problem ist, dass ioBroker nicht startet und somit nur das "restart.log" existiert. Das andere sind alte logs bis zum 03.11.2019. Das ist das Datum seitdem er nicht mehr läuft... ich schau nochmal in das letzte Log - vielleicht finde ich noch was

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      Kaldi @Kaldi last edited by Kaldi

                      Ich habe jetzt mal in das letzte Log geschaut und da kommt folgender Block immer wiederkehrend, bis um 14:16:17 Ende war (hab mal 3 Blöcke drin gelassen):

                      2019-11-03 14:01:07.438  - info: iobroker _restart
                      2019-11-03 14:01:07.574  - info: admin.0 https server listening on port 8081
                      2019-11-03 14:01:07.575  - info: admin.0 Use link "https://localhost:8081" to configure.
                      2019-11-03 14:01:07.808  - info: admin.0 Repository received successfully.
                      2019-11-03 14:01:07.819  - info: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
                      2019-11-03 14:01:07.836  - info: mihome-vacuum.0 Expert mode disabled, states deleded
                      2019-11-03 14:01:07.838  - info: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
                      2019-11-03 14:01:08.082  - info: iobroker Starting node restart.js
                      2019-11-03 14:01:08.103  - info: iobroker exit 0
                      2019-11-03 14:01:08.429  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:13.435  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:19.701  - info: host.io_broker iobroker.js-controller version 1.4.2 js-controller starting
                      2019-11-03 14:01:19.708  - info: host.io_broker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
                      2019-11-03 14:01:19.709  - info: host.io_broker hostname: io_broker, node: v8.15.0
                      2019-11-03 14:01:19.713  - info: host.io_broker ip addresses: 192.168.0.XXX XXXXXXX
                      2019-11-03 14:01:19.857  - info: host.io_broker  inMem-states listening on port 9000
                      2019-11-03 14:01:20.113  - info: host.io_broker  inMem-objects listening on port 9001
                      2019-11-03 14:01:20.131  - info: host.io_broker InMemoryDB connected
                      2019-11-03 14:01:20.160  - info: host.io_broker 28 instances found
                      2019-11-03 14:01:20.189  - info: host.io_broker starting 18 instances
                      2019-11-03 14:01:20.241  - info: host.io_broker instance system.adapter.admin.0 started with pid 4704
                      2019-11-03 14:01:22.432  - error: admin.0 setObject id missing!!
                      2019-11-03 14:01:22.454  - info: admin.0 starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0
                      2019-11-03 14:01:22.509  - info: admin.0 Request actual repository...
                      2019-11-03 14:01:22.518  - info: admin.0 requesting all states
                      2019-11-03 14:01:22.521  - info: admin.0 requesting all objects
                      2019-11-03 14:01:23.068  - info: host.io_broker Update repository "default" under "http://download.iobroker.net/sources-dist.json"
                      2019-11-03 14:01:24.152  - info: admin.0 received all states
                      2019-11-03 14:01:24.206  - info: host.io_broker instance system.adapter.mihome-vacuum.0 started with pid 4714
                      2019-11-03 14:01:24.954  - info: admin.0 received all objects
                      2019-11-03 14:01:25.156  - error: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
                      2019-11-03 14:01:25.161  - error: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
                          at Object.fs.openSync (fs.js:646:18)
                          at Object.fs.writeFileSync (fs.js:1299:33)
                          at Timeout.saveConfig [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1897:16)
                          at ontimeout (timers.js:498:11)
                          at tryOnTimeout (timers.js:323:5)
                          at Timer.listOnTimeout (timers.js:290:5)
                      2019-11-03 14:01:25.163  - info: iobroker _restart
                      2019-11-03 14:01:25.269  - info: admin.0 https server listening on port 8081
                      2019-11-03 14:01:25.269  - info: admin.0 Use link "https://localhost:8081" to configure.
                      2019-11-03 14:01:25.522  - info: admin.0 Repository received successfully.
                      2019-11-03 14:01:25.639  - info: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
                      2019-11-03 14:01:25.657  - info: mihome-vacuum.0 Expert mode disabled, states deleded
                      2019-11-03 14:01:25.659  - info: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
                      2019-11-03 14:01:25.860  - info: iobroker Starting node restart.js
                      2019-11-03 14:01:25.884  - info: iobroker exit 0
                      2019-11-03 14:01:26.217  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:31.227  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:37.445  - info: host.io_broker iobroker.js-controller version 1.4.2 js-controller starting
                      2019-11-03 14:01:37.452  - info: host.io_broker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
                      2019-11-03 14:01:37.452  - info: host.io_broker hostname: io_broker, node: v8.15.0
                      2019-11-03 14:01:37.456  - info: host.io_broker ip addresses: 192.168.0.XXX XXXXXXXX
                      2019-11-03 14:01:37.599  - info: host.io_broker  inMem-states listening on port 9000
                      2019-11-03 14:01:37.855  - info: host.io_broker  inMem-objects listening on port 9001
                      2019-11-03 14:01:37.872  - info: host.io_broker InMemoryDB connected
                      2019-11-03 14:01:37.901  - info: host.io_broker 28 instances found
                      2019-11-03 14:01:37.931  - info: host.io_broker starting 18 instances
                      2019-11-03 14:01:37.983  - info: host.io_broker instance system.adapter.admin.0 started with pid 4780
                      2019-11-03 14:01:40.165  - error: admin.0 setObject id missing!!
                      2019-11-03 14:01:40.187  - info: admin.0 starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0
                      2019-11-03 14:01:40.242  - info: admin.0 Request actual repository...
                      2019-11-03 14:01:40.250  - info: admin.0 requesting all states
                      2019-11-03 14:01:40.253  - info: admin.0 requesting all objects
                      2019-11-03 14:01:40.792  - info: host.io_broker Update repository "default" under "http://download.iobroker.net/sources-dist.json"
                      2019-11-03 14:01:41.893  - info: admin.0 received all states
                      2019-11-03 14:01:41.946  - info: host.io_broker instance system.adapter.mihome-vacuum.0 started with pid 4790
                      2019-11-03 14:01:42.656  - info: admin.0 received all objects
                      2019-11-03 14:01:42.896  - error: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
                      2019-11-03 14:01:42.901  - error: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
                          at Object.fs.openSync (fs.js:646:18)
                          at Object.fs.writeFileSync (fs.js:1299:33)
                          at Timeout.saveConfig [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1897:16)
                          at ontimeout (timers.js:498:11)
                          at tryOnTimeout (timers.js:323:5)
                          at Timer.listOnTimeout (timers.js:290:5)
                      2019-11-03 14:01:42.903  - info: iobroker _restart
                      2019-11-03 14:01:42.965  - info: admin.0 https server listening on port 8081
                      2019-11-03 14:01:42.965  - info: admin.0 Use link "https://localhost:8081" to configure.
                      2019-11-03 14:01:43.203  - info: admin.0 Repository received successfully.
                      2019-11-03 14:01:43.344  - info: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
                      2019-11-03 14:01:43.362  - info: mihome-vacuum.0 Expert mode disabled, states deleded
                      2019-11-03 14:01:43.364  - info: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
                      2019-11-03 14:01:43.552  - info: iobroker Starting node restart.js
                      2019-11-03 14:01:43.575  - info: iobroker exit 0
                      2019-11-03 14:01:43.908  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:46.152  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:48.918  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:52.163  - info: host.io_broker received SIGTERM
                      2019-11-03 14:01:55.136  - info: host.io_broker iobroker.js-controller version 1.4.2 js-controller starting
                      2019-11-03 14:01:55.142  - info: host.io_broker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
                      2019-11-03 14:01:55.143  - info: host.io_broker hostname: io_broker, node: v8.15.0
                      2019-11-03 14:01:55.147  - info: host.io_broker ip addresses: 192.168.0.XXX XXXXXXXXXX
                      2019-11-03 14:01:55.289  - info: host.io_broker  inMem-states listening on port 9000
                      2019-11-03 14:01:55.542  - info: host.io_broker  inMem-objects listening on port 9001
                      2019-11-03 14:01:55.559  - info: host.io_broker InMemoryDB connected
                      2019-11-03 14:01:55.588  - info: host.io_broker 28 instances found
                      2019-11-03 14:01:55.617  - info: host.io_broker starting 18 instances
                      2019-11-03 14:01:55.669  - info: host.io_broker instance system.adapter.admin.0 started with pid 4863
                      2019-11-03 14:01:57.884  - error: admin.0 setObject id missing!!
                      2019-11-03 14:01:57.906  - info: admin.0 starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0
                      2019-11-03 14:01:57.961  - info: admin.0 Request actual repository...
                      2019-11-03 14:01:57.968  - info: admin.0 requesting all states
                      2019-11-03 14:01:57.971  - info: admin.0 requesting all objects
                      2019-11-03 14:01:58.535  - info: host.io_broker Update repository "default" under "http://download.iobroker.net/sources-dist.json"
                      2019-11-03 14:01:59.599  - info: admin.0 received all states
                      2019-11-03 14:01:59.634  - info: host.io_broker instance system.adapter.mihome-vacuum.0 started with pid 4879
                      2019-11-03 14:02:00.427  - info: admin.0 received all objects
                      2019-11-03 14:02:00.584  - error: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
                      2019-11-03 14:02:00.589  - error: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
                          at Object.fs.openSync (fs.js:646:18)
                          at Object.fs.writeFileSync (fs.js:1299:33)
                          at Timeout.saveConfig [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1897:16)
                          at ontimeout (timers.js:498:11)
                          at tryOnTimeout (timers.js:323:5)
                          at Timer.listOnTimeout (timers.js:290:5)
                      2019-11-03 14:02:00.591  - info: iobroker _restart
                      2019-11-03 14:02:00.753  - info: admin.0 https server listening on port 8081
                      2019-11-03 14:02:00.754  - info: admin.0 Use link "https://localhost:8081" to configure.
                      2019-11-03 14:02:01.005  - info: admin.0 Repository received successfully.
                      2019-11-03 14:02:00.996  - info: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
                      2019-11-03 14:02:01.016  - info: mihome-vacuum.0 Expert mode disabled, states deleded
                      2019-11-03 14:02:01.018  - info: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
                      2019-11-03 14:02:01.245  - info: iobroker Starting node restart.js
                      2019-11-03 14:02:01.265  - info: iobroker exit 0
                      2019-11-03 14:02:51.260  - info: mihome-vacuum.0 New generation or new fw detected, create new states
                      2019-11-03 14:06:17.625  - info: admin.0 terminating https server on port 8081
                      
                      1 Reply Last reply Reply Quote 0
                      • J.A.R.V.I.S.
                        J.A.R.V.I.S. Developer last edited by

                        Das sieht aus, als wären da irgendwelche Rechte auf eine Datei nicht vorhanden.

                        1 Reply Last reply Reply Quote 0
                        • J.A.R.V.I.S.
                          J.A.R.V.I.S. Developer last edited by J.A.R.V.I.S.

                          Probier mal den Fixer aus. Wenn du den ioBroker vor über einem Jahr installiert hast, dann kann dir der Beitrag vielleicht helfen. Aber bitte vorher sichern!!

                          K 1 Reply Last reply Reply Quote 0
                          • K
                            Kaldi @J.A.R.V.I.S. last edited by

                            @J-A-R-V-I-S sagte in ioBroker startet in Endlosschleife:

                            Probier mal den Fixer aus. Wenn du den ioBroker vor über einem Jahr installiert hast, dann kann dir der Beitrag vielleicht helfen. Aber bitte vorher sichern!!

                            DAS WAR'S!
                            System läuft wieder... Vielen Dank an Euch. 👍

                            Bei der Gelegenheit gleich eine andere Frage. Ich habe noch ein MultihostSystem mit 3 RPi. Kann ich das da auch gefahrlos drüberlaufen lassen - quasi vorbeugend, oder sollte das bei Multihost nicht gemacht werden?

                            1 Reply Last reply Reply Quote 0
                            • J.A.R.V.I.S.
                              J.A.R.V.I.S. Developer last edited by J.A.R.V.I.S.

                              @Kaldi sagte in ioBroker startet in Endlosschleife:

                              Bitte diesen Beitrag löschen. Wollte einen anderen Beitrag zitieren. Muss mich erst an das neue Layout des Forums gewöhnen...

                              Du kannst den Beitrag über die drei Punkte unten rechts selber löschen.

                              @Kaldi schön, dass es wieder funktioniert. Zu deiner anderen Frage kann ich leider keine sichere Aussage treffen, da ich noch nicht mit einem Multihostsystem gearbeitet habe. Ich würde aber mal vermuten, dass das bei denen auch kein Problem sein sollte, da er, laut dem Beitrag, nichts an irgendwelchen Adpatern/Node/JS-Controllern ändert, sondern nur die Berechtigungen gerade biegt.

                              Sollte bei deinem Multihostsystem aber noch alles in Ordnung sein, würde ich dort ersmal nicht zwingend eingreifen.

                              sigi234 1 Reply Last reply Reply Quote 0
                              • sigi234
                                sigi234 Forum Testing Most Active @J.A.R.V.I.S. last edited by

                                @J-A-R-V-I-S sagte in ioBroker startet in Endlosschleife:

                                Du kannst den Beitrag über die drei Punkte unten rechts selber löschen.

                                Nein, man kann keine Beiträge selber löschen.

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

                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                804
                                Online

                                31.9k
                                Users

                                80.1k
                                Topics

                                1.3m
                                Posts

                                endlosschleife
                                4
                                13
                                666
                                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