Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Crash - no connection to states 0.0.0.0:6370[redis]

NEWS

  • Neues YouTube-Video: Visualisierung im Devices-Adapter
    BluefoxB
    Bluefox
    11
    1
    564

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    2.0k

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    11
    1
    869

Crash - no connection to states 0.0.0.0:6370[redis]

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
59 Beiträge 4 Kommentatoren 5.6k Aufrufe 3 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • S Sirfauntleroy

    @thomas-braun

    sorry beschreib grad die SD neu.

    unter iobroker status
    kam nur die gleiche meldung wie zuvor

    iobroker is running on this host.
     
     
    Objects type: file
    States  type: file
    
    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von
    #37

    @sirfauntleroy Dann installiert vor dem rückspielen des Backups redis.

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    1 Antwort Letzte Antwort
    0
    • HomoranH Nicht stören
      HomoranH Nicht stören
      Homoran
      Global Moderator Administrators
      schrieb am zuletzt editiert von
      #38

      @Thomas-Braun

      bis hierhin sah es noch gut aus
      2021-12-20 20:25:06.270 - info: host.raspberrypi received SIGTERM

      Wo kommt da der SIGTERM auf einmal her

      kein Support per PN! - Fragen im Forum stellen -
      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
      Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

      S F 2 Antworten Letzte Antwort
      0
      • HomoranH Homoran

        @Thomas-Braun

        bis hierhin sah es noch gut aus
        2021-12-20 20:25:06.270 - info: host.raspberrypi received SIGTERM

        Wo kommt da der SIGTERM auf einmal her

        S Offline
        S Offline
        Sirfauntleroy
        schrieb am zuletzt editiert von
        #39

        @homoran
        gute Frage
        bekommt er den durch den "iob fix"?

        Thomas BraunT 1 Antwort Letzte Antwort
        0
        • S Sirfauntleroy

          @homoran
          gute Frage
          bekommt er den durch den "iob fix"?

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb am zuletzt editiert von
          #40

          @sirfauntleroy
          Möglich. Vor dem fix stoppt man den iobroker ja. Das wird dann wohl per SIGTERM passieren.

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          HomoranH 1 Antwort Letzte Antwort
          0
          • HomoranH Homoran

            @Thomas-Braun

            bis hierhin sah es noch gut aus
            2021-12-20 20:25:06.270 - info: host.raspberrypi received SIGTERM

            Wo kommt da der SIGTERM auf einmal her

            F Online
            F Online
            fastfoot
            schrieb am zuletzt editiert von
            #41

            @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

            Wo kommt da der SIGTERM auf einmal her

            später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

            iobroker läuft unter Docker auf QNAP TS-451+
            SkriptRecovery: https://forum.iobroker.net/post/930558

            HomoranH 1 Antwort Letzte Antwort
            1
            • Thomas BraunT Thomas Braun

              @sirfauntleroy
              Möglich. Vor dem fix stoppt man den iobroker ja. Das wird dann wohl per SIGTERM passieren.

              HomoranH Nicht stören
              HomoranH Nicht stören
              Homoran
              Global Moderator Administrators
              schrieb am zuletzt editiert von
              #42

              @thomas-braun sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

              Möglich. Vor dem fix stoppt man den iobroker ja. Das wird dann wohl per SIGTERM passieren.

              passt, aber dass er dann nach dem Fixer nicht mehr hochkommt ist schon seltsam

              kein Support per PN! - Fragen im Forum stellen -
              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
              Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

              1 Antwort Letzte Antwort
              0
              • F fastfoot

                @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                Wo kommt da der SIGTERM auf einmal her

                später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

                HomoranH Nicht stören
                HomoranH Nicht stören
                Homoran
                Global Moderator Administrators
                schrieb am zuletzt editiert von
                #43

                @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                Wo kommt da der SIGTERM auf einmal her

                später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

                DANKE!!!

                Schon wieder mal nicht gesehen - gestern erst

                kein Support per PN! - Fragen im Forum stellen -
                Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
                der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                F 1 Antwort Letzte Antwort
                0
                • HomoranH Homoran

                  @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  Wo kommt da der SIGTERM auf einmal her

                  später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

                  DANKE!!!

                  Schon wieder mal nicht gesehen - gestern erst

                  F Online
                  F Online
                  fastfoot
                  schrieb am zuletzt editiert von
                  #44

                  @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                  Wo kommt da der SIGTERM auf einmal her

                  später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

                  DANKE!!!

                  Schon wieder mal nicht gesehen - gestern erst

                  sieht man auch an list instances, die zeigen noch auf raspberrypi

                  iobroker läuft unter Docker auf QNAP TS-451+
                  SkriptRecovery: https://forum.iobroker.net/post/930558

                  HomoranH 1 Antwort Letzte Antwort
                  0
                  • F fastfoot

                    @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                    @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                    @homoran sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                    Wo kommt da der SIGTERM auf einmal her

                    später heisst der host iobroker, die instanzen laufen auf einen anderen hostnamen, deshalb die Meldung host.ioBroker does not start any instances on this host. ein iob host this sollte das bereinigen

                    DANKE!!!

                    Schon wieder mal nicht gesehen - gestern erst

                    sieht man auch an list instances, die zeigen noch auf raspberrypi

                    HomoranH Nicht stören
                    HomoranH Nicht stören
                    Homoran
                    Global Moderator Administrators
                    schrieb am zuletzt editiert von
                    #45

                    @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                    sieht man auch an list instances, die zeigen noch auf raspberrypi

                    ja, die Spalte blende ich immer irgendwie aus 😳 :-(

                    kein Support per PN! - Fragen im Forum stellen -
                    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                    Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
                    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                    S 1 Antwort Letzte Antwort
                    0
                    • HomoranH Homoran

                      @fastfoot sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                      sieht man auch an list instances, die zeigen noch auf raspberrypi

                      ja, die Spalte blende ich immer irgendwie aus 😳 :-(

                      S Offline
                      S Offline
                      Sirfauntleroy
                      schrieb am zuletzt editiert von
                      #46

                      @homoran
                      21f7498b-b4a0-4882-8454-5033b71f6c02-image.png
                      das Fenster bleibt jetzt so, bis alles wiederhergestellt ist?

                      einfach mal so laufen lassen. ... kommen da zwischen drin neue Zeilen, dass man sieht, das was passiert?

                      HomoranH Thomas BraunT 2 Antworten Letzte Antwort
                      0
                      • S Sirfauntleroy

                        @homoran
                        21f7498b-b4a0-4882-8454-5033b71f6c02-image.png
                        das Fenster bleibt jetzt so, bis alles wiederhergestellt ist?

                        einfach mal so laufen lassen. ... kommen da zwischen drin neue Zeilen, dass man sieht, das was passiert?

                        HomoranH Nicht stören
                        HomoranH Nicht stören
                        Homoran
                        Global Moderator Administrators
                        schrieb am zuletzt editiert von Homoran
                        #47

                        @sirfauntleroy sagte in Crash - no connection to states 0.0.0.0:6370[redis]:

                        kommen da zwischen drin neue Zeilen, dass man sieht, das was passiert?

                        iobroker logs --watch zeigt dir die Aktivitäten

                        kein Support per PN! - Fragen im Forum stellen -
                        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
                        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                        1 Antwort Letzte Antwort
                        0
                        • S Sirfauntleroy

                          @homoran
                          21f7498b-b4a0-4882-8454-5033b71f6c02-image.png
                          das Fenster bleibt jetzt so, bis alles wiederhergestellt ist?

                          einfach mal so laufen lassen. ... kommen da zwischen drin neue Zeilen, dass man sieht, das was passiert?

                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #48

                          @sirfauntleroy
                          Konsole auf, per

                          iobroker logs --watch
                          

                          den Fortgang beobachten

                          Linux-Werkzeugkasten:
                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                          NodeJS Fixer Skript:
                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                          S 1 Antwort Letzte Antwort
                          1
                          • Thomas BraunT Thomas Braun

                            @sirfauntleroy
                            Konsole auf, per

                            iobroker logs --watch
                            

                            den Fortgang beobachten

                            S Offline
                            S Offline
                            Sirfauntleroy
                            schrieb am zuletzt editiert von
                            #49

                            will nicht ungeduldig sein, aber ist es normal, dass der Start des Backup-Resores nicht im log steht?

                            iobroker logs --watch
                            2021-12-20 21:04:34.397  - info: host.raspberrypi iobroker.js-controller version 3.3.21 js-controller starting
                            2021-12-20 21:04:34.403  - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                            2021-12-20 21:04:34.404  - info: host.raspberrypi hostname: raspberrypi, node: v14.18.2
                            2021-12-20 21:04:34.404  - info: host.raspberrypi ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                            2021-12-20 21:04:34.601  - info: host.raspberrypi connected to Objects and States
                            2021-12-20 21:04:34.667  - info: host.raspberrypi added notifications configuration of host
                            2021-12-20 21:04:34.987  - info: host.raspberrypi 3 instances found
                            2021-12-20 21:04:34.999  - info: host.raspberrypi starting 3 instances
                            2021-12-20 21:04:35.052  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 7454
                            2021-12-20 21:04:37.005  - info: admin.0 (7454) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:04:37.054  - info: admin.0 (7454) requesting all states
                            2021-12-20 21:04:37.055  - info: admin.0 (7454) requesting all objects
                            2021-12-20 21:04:37.135  - info: admin.0 (7454) received all objects
                            2021-12-20 21:04:37.231  - info: admin.0 (7454) http server listening on port 8081
                            2021-12-20 21:04:37.231  - info: admin.0 (7454) Use link "http://localhost:8081" to configure.
                            2021-12-20 21:04:37.268  - info: admin.0 (7454) State value to set for "admin.0.info.lastUpdateCheck" has to be type "number" but received type "string"
                            2021-12-20 21:04:37.274  - warn: admin.0 (7454) Repository cannot be read
                            2021-12-20 21:04:39.056  - info: host.raspberrypi instance system.adapter.discovery.0 started with pid 7505
                            2021-12-20 21:04:40.515  - info: discovery.0 (7505) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:04:43.039  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7520
                            2021-12-20 21:04:44.601  - info: backitup.0 (7520) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:04:44.662  - info: backitup.0 (7520) [iobroker] backup was activated at 02:40 every 1 day(s)
                            2021-12-20 21:05:13.492  - info: host.raspberrypi Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
                            2021-12-20 21:07:29.728  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                            2021-12-20 21:07:29.743  - info: backitup.0 (7520) Got terminate signal TERMINATE_YOURSELF
                            2021-12-20 21:07:29.744  - info: backitup.0 (7520) cleaned everything up...
                            2021-12-20 21:07:29.745  - info: backitup.0 (7520) terminating
                            2021-12-20 21:07:29.746  - info: backitup.0 (7520) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2021-12-20 21:07:29.752  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                            2021-12-20 21:07:30.293  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2021-12-20 21:07:32.829  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7933
                            2021-12-20 21:07:34.369  - info: backitup.0 (7933) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:07:34.432  - info: backitup.0 (7933) [iobroker] backup was activated at 02:40 every 1 day(s)
                            2021-12-20 21:08:09.386  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                            2021-12-20 21:08:09.398  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                            2021-12-20 21:08:09.398  - info: backitup.0 (7933) Got terminate signal TERMINATE_YOURSELF
                            2021-12-20 21:08:09.401  - info: backitup.0 (7933) cleaned everything up...
                            2021-12-20 21:08:09.402  - info: backitup.0 (7933) terminating
                            2021-12-20 21:08:09.405  - info: backitup.0 (7933) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2021-12-20 21:08:09.993  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2021-12-20 21:08:12.439  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7984
                            2021-12-20 21:08:14.006  - info: backitup.0 (7984) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:08:14.074  - info: backitup.0 (7984) [iobroker] backup was activated at 02:40 every 1 day(s)
                            2021-12-20 21:09:05.300  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                            2021-12-20 21:09:05.316  - info: backitup.0 (7984) Got terminate signal TERMINATE_YOURSELF
                            2021-12-20 21:09:05.320  - info: backitup.0 (7984) cleaned everything up...
                            2021-12-20 21:09:05.322  - info: backitup.0 (7984) terminating
                            2021-12-20 21:09:05.325  - info: backitup.0 (7984) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2021-12-20 21:09:05.358  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                            2021-12-20 21:09:05.861  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                            2021-12-20 21:09:08.399  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 8013
                            2021-12-20 21:09:09.926  - info: backitup.0 (8013) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                            2021-12-20 21:09:09.989  - info: backitup.0 (8013) [iobroker] backup was activated at 02:40 every 1 day(s)
                            
                            
                            
                            S 1 Antwort Letzte Antwort
                            0
                            • S Sirfauntleroy

                              will nicht ungeduldig sein, aber ist es normal, dass der Start des Backup-Resores nicht im log steht?

                              iobroker logs --watch
                              2021-12-20 21:04:34.397  - info: host.raspberrypi iobroker.js-controller version 3.3.21 js-controller starting
                              2021-12-20 21:04:34.403  - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                              2021-12-20 21:04:34.404  - info: host.raspberrypi hostname: raspberrypi, node: v14.18.2
                              2021-12-20 21:04:34.404  - info: host.raspberrypi ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                              2021-12-20 21:04:34.601  - info: host.raspberrypi connected to Objects and States
                              2021-12-20 21:04:34.667  - info: host.raspberrypi added notifications configuration of host
                              2021-12-20 21:04:34.987  - info: host.raspberrypi 3 instances found
                              2021-12-20 21:04:34.999  - info: host.raspberrypi starting 3 instances
                              2021-12-20 21:04:35.052  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 7454
                              2021-12-20 21:04:37.005  - info: admin.0 (7454) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.2, js-controller: 3.3.21
                              2021-12-20 21:04:37.054  - info: admin.0 (7454) requesting all states
                              2021-12-20 21:04:37.055  - info: admin.0 (7454) requesting all objects
                              2021-12-20 21:04:37.135  - info: admin.0 (7454) received all objects
                              2021-12-20 21:04:37.231  - info: admin.0 (7454) http server listening on port 8081
                              2021-12-20 21:04:37.231  - info: admin.0 (7454) Use link "http://localhost:8081" to configure.
                              2021-12-20 21:04:37.268  - info: admin.0 (7454) State value to set for "admin.0.info.lastUpdateCheck" has to be type "number" but received type "string"
                              2021-12-20 21:04:37.274  - warn: admin.0 (7454) Repository cannot be read
                              2021-12-20 21:04:39.056  - info: host.raspberrypi instance system.adapter.discovery.0 started with pid 7505
                              2021-12-20 21:04:40.515  - info: discovery.0 (7505) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.2, js-controller: 3.3.21
                              2021-12-20 21:04:43.039  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7520
                              2021-12-20 21:04:44.601  - info: backitup.0 (7520) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                              2021-12-20 21:04:44.662  - info: backitup.0 (7520) [iobroker] backup was activated at 02:40 every 1 day(s)
                              2021-12-20 21:05:13.492  - info: host.raspberrypi Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
                              2021-12-20 21:07:29.728  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                              2021-12-20 21:07:29.743  - info: backitup.0 (7520) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:07:29.744  - info: backitup.0 (7520) cleaned everything up...
                              2021-12-20 21:07:29.745  - info: backitup.0 (7520) terminating
                              2021-12-20 21:07:29.746  - info: backitup.0 (7520) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              2021-12-20 21:07:29.752  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                              2021-12-20 21:07:30.293  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              2021-12-20 21:07:32.829  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7933
                              2021-12-20 21:07:34.369  - info: backitup.0 (7933) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                              2021-12-20 21:07:34.432  - info: backitup.0 (7933) [iobroker] backup was activated at 02:40 every 1 day(s)
                              2021-12-20 21:08:09.386  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                              2021-12-20 21:08:09.398  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                              2021-12-20 21:08:09.398  - info: backitup.0 (7933) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:08:09.401  - info: backitup.0 (7933) cleaned everything up...
                              2021-12-20 21:08:09.402  - info: backitup.0 (7933) terminating
                              2021-12-20 21:08:09.405  - info: backitup.0 (7933) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              2021-12-20 21:08:09.993  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              2021-12-20 21:08:12.439  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 7984
                              2021-12-20 21:08:14.006  - info: backitup.0 (7984) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                              2021-12-20 21:08:14.074  - info: backitup.0 (7984) [iobroker] backup was activated at 02:40 every 1 day(s)
                              2021-12-20 21:09:05.300  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                              2021-12-20 21:09:05.316  - info: backitup.0 (7984) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:09:05.320  - info: backitup.0 (7984) cleaned everything up...
                              2021-12-20 21:09:05.322  - info: backitup.0 (7984) terminating
                              2021-12-20 21:09:05.325  - info: backitup.0 (7984) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                              2021-12-20 21:09:05.358  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                              2021-12-20 21:09:05.861  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                              2021-12-20 21:09:08.399  - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 8013
                              2021-12-20 21:09:09.926  - info: backitup.0 (8013) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.2, js-controller: 3.3.21
                              2021-12-20 21:09:09.989  - info: backitup.0 (8013) [iobroker] backup was activated at 02:40 every 1 day(s)
                              
                              
                              
                              S Offline
                              S Offline
                              Sirfauntleroy
                              schrieb am zuletzt editiert von
                              #50

                              Fand die datei nicht.. nochmal ausgewählt: und es tut sich was

                              2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                              2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                              2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                              2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                              2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                              2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                              2021-12-20 21:18:40.641  - info: backitup.0 (8013) cleaned everything up...
                              2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                              2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                              2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                              2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                              2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                              2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                              2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                              2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                              2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                              2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                              2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                              2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                              2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                              2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                              2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                              2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                              2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                              2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                              2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                              2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                              2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                              2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                              2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                              2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                              2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                              2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                              2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                              2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                              2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                              
                              
                              Thomas BraunT F 2 Antworten Letzte Antwort
                              0
                              • S Sirfauntleroy

                                Fand die datei nicht.. nochmal ausgewählt: und es tut sich was

                                2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                                2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                                2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                                2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                                2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                                2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                                2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                                2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                                2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                                2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                                2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                                2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                                2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                                2021-12-20 21:18:40.641  - info: backitup.0 (8013) cleaned everything up...
                                2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                                2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                                2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                                2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                                2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                                2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                                2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                                2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                                2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                                2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                                2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                                2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                                2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                                2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                                2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                                2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                                2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                                2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                                2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                                2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                                2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                                2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                                2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                                2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                                2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                                2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                                2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                                2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                                2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                                2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                                2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                                
                                
                                Thomas BraunT Online
                                Thomas BraunT Online
                                Thomas Braun
                                Most Active
                                schrieb am zuletzt editiert von
                                #51

                                @sirfauntleroy
                                Du hast die Lokalisierung / lokale Zeitzone nicht angepasst .

                                Linux-Werkzeugkasten:
                                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                NodeJS Fixer Skript:
                                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                1 Antwort Letzte Antwort
                                0
                                • S Sirfauntleroy

                                  Fand die datei nicht.. nochmal ausgewählt: und es tut sich was

                                  2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                                  2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                                  2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                                  2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                                  2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                                  2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                                  2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                                  2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                                  2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                                  2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                                  2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                                  2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                  2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                  2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                  2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                                  2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                                  2021-12-20 21:18:40.641  - info: backitup.0 (8013) cleaned everything up...
                                  2021-12-20 21:18:40.643  - info: admin.0 (7454) terminating http server on port 8081
                                  2021-12-20 21:18:40.642  - info: host.raspberrypi received SIGTERM
                                  2021-12-20 21:18:40.653  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
                                  2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
                                  2021-12-20 21:18:40.654  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
                                  2021-12-20 21:18:40.671  - info: admin.0 (7454) Got terminate signal TERMINATE_YOURSELF
                                  2021-12-20 21:18:40.672  - info: discovery.0 (7505) Got terminate signal TERMINATE_YOURSELF
                                  2021-12-20 21:18:40.673  - info: backitup.0 (8013) Got terminate signal TERMINATE_YOURSELF
                                  2021-12-20 21:18:40.677  - info: discovery.0 (7505) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2021-12-20 21:18:40.677  - info: backitup.0 (8013) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2021-12-20 21:18:40.679  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
                                  2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
                                  2021-12-20 21:18:40.683  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
                                  2021-12-20 21:18:40.689  - info: admin.0 (7454) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2021-12-20 21:18:41.240  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                  2021-12-20 21:18:41.258  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                  2021-12-20 21:18:41.261  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
                                  2021-12-20 21:18:41.262  - info: host.raspberrypi All instances are stopped.
                                  2021-12-20 21:18:41.285  - info: host.raspberrypi terminated
                                  2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                                  2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                                  2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                                  2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                                  2021-12-20 21:19:43.964  - info: host.ioBroker iobroker.js-controller version 3.3.21 js-controller starting
                                  2021-12-20 21:19:43.970  - info: host.ioBroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                                  2021-12-20 21:19:43.971  - info: host.ioBroker hostname: ioBroker, node: v14.18.2
                                  2021-12-20 21:19:43.972  - info: host.ioBroker ip addresses: 192.168.10.11 fe80::1c60:4643:360d:88a7
                                  2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                                  2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                                  2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                                  2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                                  2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                                  2021-12-20 21:19:45.163  - info: host.ioBroker connected to Objects and States
                                  2021-12-20 21:19:45.191  - info: host.ioBroker added notifications configuration of host
                                  2021-12-20 21:19:45.688  - info: host.ioBroker Delete host system.host.raspberrypi
                                  2021-12-20 21:19:45.836  - info: host.ioBroker 76 instances found
                                  2021-12-20 21:19:45.897  - warn: host.ioBroker does not start any instances on this host
                                  
                                  
                                  F Online
                                  F Online
                                  fastfoot
                                  schrieb am zuletzt editiert von
                                  #52

                                  @sirfauntleroy da ist immer noch der hostname falschiob stop, iob host this, iob start. Gestern hiess es noch dass backitup das macht :-)

                                  iobroker läuft unter Docker auf QNAP TS-451+
                                  SkriptRecovery: https://forum.iobroker.net/post/930558

                                  S HomoranH 2 Antworten Letzte Antwort
                                  1
                                  • F fastfoot

                                    @sirfauntleroy da ist immer noch der hostname falschiob stop, iob host this, iob start. Gestern hiess es noch dass backitup das macht :-)

                                    S Offline
                                    S Offline
                                    Sirfauntleroy
                                    schrieb am zuletzt editiert von
                                    #53

                                    @fastfoot

                                    jetzt rattert im log so einiges durch..
                                    geduldig abwarten...

                                    S 1 Antwort Letzte Antwort
                                    0
                                    • S Sirfauntleroy

                                      @fastfoot

                                      jetzt rattert im log so einiges durch..
                                      geduldig abwarten...

                                      S Offline
                                      S Offline
                                      Sirfauntleroy
                                      schrieb am zuletzt editiert von
                                      #54

                                      Das Backup ist durchgelaufen.
                                      nun folgendes Problem ...

                                      Error: Cannot find module '../encodings'
                                      Require stack:
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/read.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/types/json.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/express/lib/express.js
                                      - /opt/iobroker/node_modules/iobroker.admin/node_modules/express/index.js
                                      - /opt/iobroker/node_modules/iobroker.admin/lib/web.js
                                      - /opt/iobroker/node_modules/iobroker.admin/main.js
                                          at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
                                          at Function.Module._load (internal/modules/cjs/loader.js:746:27)
                                          at Module.require (internal/modules/cjs/loader.js:974:19)
                                          at require (internal/modules/cjs/helpers.js:93:18)
                                          at Object.getCodec (/opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js:65:27)
                                          at Object.getDecoder (/opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js:127:23)
                                          at getDecoder (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:45:18)
                                          at readStream (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:180:15)
                                          at getRawBody (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:108:12)
                                          at read (/opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/read.js:77:3)
                                      
                                      Thomas BraunT 1 Antwort Letzte Antwort
                                      0
                                      • S Sirfauntleroy

                                        Das Backup ist durchgelaufen.
                                        nun folgendes Problem ...

                                        Error: Cannot find module '../encodings'
                                        Require stack:
                                        - /opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js
                                        - /opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js
                                        - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/read.js
                                        - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/types/json.js
                                        - /opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/index.js
                                        - /opt/iobroker/node_modules/iobroker.admin/node_modules/express/lib/express.js
                                        - /opt/iobroker/node_modules/iobroker.admin/node_modules/express/index.js
                                        - /opt/iobroker/node_modules/iobroker.admin/lib/web.js
                                        - /opt/iobroker/node_modules/iobroker.admin/main.js
                                            at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
                                            at Function.Module._load (internal/modules/cjs/loader.js:746:27)
                                            at Module.require (internal/modules/cjs/loader.js:974:19)
                                            at require (internal/modules/cjs/helpers.js:93:18)
                                            at Object.getCodec (/opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js:65:27)
                                            at Object.getDecoder (/opt/iobroker/node_modules/iobroker.admin/node_modules/iconv-lite/lib/index.js:127:23)
                                            at getDecoder (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:45:18)
                                            at readStream (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:180:15)
                                            at getRawBody (/opt/iobroker/node_modules/iobroker.admin/node_modules/raw-body/index.js:108:12)
                                            at read (/opt/iobroker/node_modules/iobroker.admin/node_modules/body-parser/lib/read.js:77:3)
                                        
                                        Thomas BraunT Online
                                        Thomas BraunT Online
                                        Thomas Braun
                                        Most Active
                                        schrieb am zuletzt editiert von
                                        #55

                                        @sirfauntleroy

                                        nodeJS ist sauber, nehme ich an?

                                        Linux-Werkzeugkasten:
                                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                        NodeJS Fixer Skript:
                                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                        S 1 Antwort Letzte Antwort
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @sirfauntleroy

                                          nodeJS ist sauber, nehme ich an?

                                          S Offline
                                          S Offline
                                          Sirfauntleroy
                                          schrieb am zuletzt editiert von
                                          #56

                                          @thomas-braun

                                          nach einem Reboot gehts es jetzt soweit..

                                          eieiei..

                                          Irgendwie wäre die Idee mit dem schnellen wiederherstellen per .iso ja doch verlockend gewesen...

                                          Herzlichen Dank bisher an euch alle!!!!!!

                                          S 1 Antwort Letzte Antwort
                                          0

                                          Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                                          Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                                          Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                                          Registrieren Anmelden
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          406

                                          Online

                                          32.9k

                                          Benutzer

                                          83.0k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe