Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • 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. Error/Bug
  4. [gelöst] Nach Docker Umzug keine Updates möglich

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    439

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    5.1k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.4k

[gelöst] Nach Docker Umzug keine Updates möglich

Geplant Angeheftet Gesperrt Verschoben Error/Bug
42 Beiträge 4 Kommentatoren 2.7k Aufrufe 3 Watching
  • Ä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.
  • Z ZoXx

    bin die Kommandos von oben durchgegangen.

    Ohne Erfolg. Fehler bleibt weiterhin.
    Auch das löschen des .bin Ordners bringt keinen Erfolg.

    Z Offline
    Z Offline
    ZoXx
    schrieb am zuletzt editiert von
    #29

    niemand mehr eine Idee? :(

    GlasfaserG 1 Antwort Letzte Antwort
    0
    • Z ZoXx

      niemand mehr eine Idee? :(

      GlasfaserG Offline
      GlasfaserG Offline
      Glasfaser
      schrieb am zuletzt editiert von
      #30

      @zoxx

      Ohne Erfolg. Fehler bleibt weiterhin.

      Welcher Fehler von was ... aber ..

      habe jetzt quer gelesen ..setze ioBroker neu auf und spiele eine Backup rein ist die sauberste Lösung !

      Bringt doch nicht´s wenn du erstmal am anfang mit root gearbeitest hast und jetzt Installationen im falschen Verzeichniss vorhanden sind .

      Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

      Z 1 Antwort Letzte Antwort
      0
      • GlasfaserG Glasfaser

        @zoxx

        Ohne Erfolg. Fehler bleibt weiterhin.

        Welcher Fehler von was ... aber ..

        habe jetzt quer gelesen ..setze ioBroker neu auf und spiele eine Backup rein ist die sauberste Lösung !

        Bringt doch nicht´s wenn du erstmal am anfang mit root gearbeitest hast und jetzt Installationen im falschen Verzeichniss vorhanden sind .

        Z Offline
        Z Offline
        ZoXx
        schrieb am zuletzt editiert von
        #31

        die backups gehen nicht weit genug zurück.

        Z 1 Antwort Letzte Antwort
        0
        • Z ZoXx

          die backups gehen nicht weit genug zurück.

          Z Offline
          Z Offline
          ZoXx
          schrieb am zuletzt editiert von
          #32

          Ich habe noch ein etwas älteres Backup gefunden.

          Damit gibt es aber auch Probleme.

          Sobald ich den iobroker neu aufsetze, läuft alles.
          Spiele ich das Backup via backitup ein, läuft es nicht mehr, spiele ich es via restore beim Docker Start ein, läuft es nicht mehr.

          Kann es damit zusammenhängen, dass ich von dem Docker der Synology auf ein Intel System gewechselt bin?

          GlasfaserG 1 Antwort Letzte Antwort
          0
          • Z ZoXx

            Ich habe noch ein etwas älteres Backup gefunden.

            Damit gibt es aber auch Probleme.

            Sobald ich den iobroker neu aufsetze, läuft alles.
            Spiele ich das Backup via backitup ein, läuft es nicht mehr, spiele ich es via restore beim Docker Start ein, läuft es nicht mehr.

            Kann es damit zusammenhängen, dass ich von dem Docker der Synology auf ein Intel System gewechselt bin?

            GlasfaserG Offline
            GlasfaserG Offline
            Glasfaser
            schrieb am zuletzt editiert von Glasfaser
            #33

            @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

            Spiele ich das Backup via backitup ein, läuft es nicht mehr, spiele ich es via restore beim Docker Start ein, läuft es nicht mehr.

            Was läuft nicht mehr !?
            Welche Fehler kommen .

            Was steht im Log bei :

            iobroker logs --watch
            

            ( Vermutung der Hostname stimmt nicht )

            Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

            Z 1 Antwort Letzte Antwort
            0
            • GlasfaserG Glasfaser

              @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

              Spiele ich das Backup via backitup ein, läuft es nicht mehr, spiele ich es via restore beim Docker Start ein, läuft es nicht mehr.

              Was läuft nicht mehr !?
              Welche Fehler kommen .

              Was steht im Log bei :

              iobroker logs --watch
              

              ( Vermutung der Hostname stimmt nicht )

              Z Offline
              Z Offline
              ZoXx
              schrieb am zuletzt editiert von
              #34

              @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

              Was steht im Log bei :
              iobroker logs --watch

              2022-03-14 13:25:07.061  - info: host.07cbffd7e85a iobroker.js-controller version 4.0.21 js-controller starting
              2022-03-14 13:25:07.064  - info: host.07cbffd7e85a Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
              2022-03-14 13:25:07.064  - info: host.07cbffd7e85a hostname: 07cbffd7e85a, node: v14.19.0
              2022-03-14 13:25:07.064  - info: host.07cbffd7e85a ip addresses: 172.17.0.3
              2022-03-14 13:25:07.251  - info: host.07cbffd7e85a connected to Objects and States
              2022-03-14 13:25:07.264  - info: host.07cbffd7e85a Node.js version has changed from unknown to 14.19.0
              2022-03-14 13:25:07.283  - info: host.07cbffd7e85a added notifications configuration of host
              2022-03-14 13:25:09.374  - info: host.07cbffd7e85a Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
              2022-03-14 13:25:09.382  - info: host.07cbffd7e85a 3 instances found
              2022-03-14 13:25:09.385  - info: host.07cbffd7e85a starting 3 instances
              2022-03-14 13:25:09.431  - info: host.07cbffd7e85a instance system.adapter.admin.0 started with pid 229
              2022-03-14 13:25:09.531  - info: host.07cbffd7e85a Created UUID: 8b601527-da37-485e-b758-c19ee482868b
              2022-03-14 13:25:13.416  - info: host.07cbffd7e85a instance system.adapter.discovery.0 started with pid 236
              2022-03-14 13:25:17.420  - info: host.07cbffd7e85a instance system.adapter.backitup.0 started with pid 247
              2022-03-14 13:25:18.910  - info: admin.0 (229) starting. Version 5.3.1 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.0, js-controller: 4.0.21
              2022-03-14 13:25:18.926  - info: admin.0 (229) requesting all states
              2022-03-14 13:25:18.926  - info: admin.0 (229) requesting all objects
              2022-03-14 13:25:18.964  - info: admin.0 (229) received all objects
              2022-03-14 13:25:19.009  - info: admin.0 (229) http server listening on port 8081
              2022-03-14 13:25:19.010  - info: admin.0 (229) Use link "http://localhost:8081" to configure.
              2022-03-14 13:25:19.195  - warn: admin.0 (229) Repository cannot be read: Active repo - stable
              2022-03-14 13:25:19.195  - warn: admin.0 (229) Active repository "stable cannot be read
              2022-03-14 13:25:21.845  - info: discovery.0 (236) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.19.0, js-controller: 4.0.21
              2022-03-14 13:25:25.350  - info: backitup.0 (247) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21
              2022-03-14 13:25:25.457  - info: backitup.0 (247) [iobroker] backup was activated at 02:40 every 1 day(s)
              2022-03-14 13:27:53.471  - info: host.07cbffd7e85a Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
              2022-03-14 13:28:49.823  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 (force=false, process=true)
              2022-03-14 13:28:49.826  - info: backitup.0 (247) Got terminate signal TERMINATE_YOURSELF
              2022-03-14 13:28:49.826  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 send kill signal
              2022-03-14 13:28:49.826  - info: backitup.0 (247) cleaned everything up...
              2022-03-14 13:28:49.827  - info: backitup.0 (247) terminating
              2022-03-14 13:28:49.827  - info: backitup.0 (247) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-03-14 13:28:50.349  - info: host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-03-14 13:28:52.850  - info: host.07cbffd7e85a instance system.adapter.backitup.0 started with pid 457
              2022-03-14 13:29:00.551  - info: backitup.0 (457) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21
              2022-03-14 13:29:00.657  - info: backitup.0 (457) [iobroker] backup was activated at 02:40 every 1 day(s)
              2022-03-14 13:34:39.611  - info: host.07cbffd7e85a received SIGTERM
              2022-03-14 13:34:39.612  - info: host.07cbffd7e85a stopInstance system.adapter.admin.0 (force=false, process=true)
              2022-03-14 13:34:39.612  - info: host.07cbffd7e85a stopInstance system.adapter.discovery.0 (force=false, process=true)
              2022-03-14 13:34:39.613  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 (force=false, process=true)
              2022-03-14 13:34:39.615  - info: host.07cbffd7e85a stopInstance system.adapter.admin.0 send kill signal
              2022-03-14 13:34:39.615  - info: backitup.0 (457) Got terminate signal TERMINATE_YOURSELF
              2022-03-14 13:34:39.616  - info: host.07cbffd7e85a stopInstance system.adapter.discovery.0 send kill signal
              2022-03-14 13:34:39.616  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 send kill signal
              2022-03-14 13:34:39.615  - info: admin.0 (229) Got terminate signal TERMINATE_YOURSELF
              2022-03-14 13:34:39.615  - info: discovery.0 (236) Got terminate signal TERMINATE_YOURSELF
              2022-03-14 13:34:39.616  - info: backitup.0 (457) cleaned everything up...
              2022-03-14 13:34:39.617  - info: backitup.0 (457) terminating
              2022-03-14 13:34:39.617  - info: backitup.0 (457) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-03-14 13:34:39.616  - info: discovery.0 (236) terminating
              2022-03-14 13:34:39.617  - info: discovery.0 (236) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-03-14 13:34:39.617  - info: admin.0 (229) terminating http server on port 8081
              2022-03-14 13:34:39.618  - info: admin.0 (229) terminating
              2022-03-14 13:34:39.620  - info: admin.0 (229) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-03-14 13:34:40.135  - info: host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-03-14 13:34:40.138  - info: host.07cbffd7e85a instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-03-14 13:34:40.143  - info: host.07cbffd7e85a instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-03-14 13:34:40.143  - info: host.07cbffd7e85a All instances are stopped.
              2022-03-14 13:34:40.242  - info: host.07cbffd7e85a terminated
              2022-03-14 13:37:26.143  - info: host.IoBroker iobroker.js-controller version 4.0.21 js-controller starting
              2022-03-14 13:37:26.145  - info: host.IoBroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
              2022-03-14 13:37:26.145  - info: host.IoBroker hostname: IoBroker, node: v14.19.0
              2022-03-14 13:37:26.145  - info: host.IoBroker ip addresses: 172.17.0.3
              2022-03-14 13:37:26.454  - info: host.IoBroker Sets unsupported
              2022-03-14 13:37:26.576  - info: host.IoBroker connected to Objects and States
              2022-03-14 13:37:26.594  - info: host.IoBroker added notifications configuration of host
              2022-03-14 13:37:26.596  - info: host.IoBroker Node.js version has changed from unknown to 14.19.0
              2022-03-14 13:37:26.618  - info: host.IoBroker Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
              2022-03-14 13:37:28.408  - info: host.IoBroker Delete host system.host.07cbffd7e85a
              2022-03-14 13:37:28.439  - info: host.IoBroker 33 instances found
              2022-03-14 13:37:28.447  - warn: host.IoBroker does not start any instances on this host
              2022-03-14 18:28:41.714  - info: host.IoBroker iobroker.js-controller version 4.0.21 js-controller starting
              2022-03-14 18:28:41.716  - info: host.IoBroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
              2022-03-14 18:28:41.716  - info: host.IoBroker hostname: IoBroker, node: v14.19.0
              2022-03-14 18:28:41.717  - info: host.IoBroker ip addresses: 172.17.0.3
              2022-03-14 18:28:42.199  - info: host.IoBroker connected to Objects and States
              2022-03-14 18:28:42.221  - info: host.IoBroker added notifications configuration of host
              2022-03-14 18:28:44.388  - info: host.IoBroker 33 instances found
              2022-03-14 18:28:44.394  - warn: host.IoBroker does not start any instances on this host
              

              @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

              Was läuft nicht mehr !?
              Welche Fehler kommen .
              Im Browser erscheint nur noch "ERR_EMPTY_RESPONSE"

              HomoranH GlasfaserG 2 Antworten Letzte Antwort
              0
              • Z ZoXx

                @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

                Was steht im Log bei :
                iobroker logs --watch

                2022-03-14 13:25:07.061  - info: host.07cbffd7e85a iobroker.js-controller version 4.0.21 js-controller starting
                2022-03-14 13:25:07.064  - info: host.07cbffd7e85a Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                2022-03-14 13:25:07.064  - info: host.07cbffd7e85a hostname: 07cbffd7e85a, node: v14.19.0
                2022-03-14 13:25:07.064  - info: host.07cbffd7e85a ip addresses: 172.17.0.3
                2022-03-14 13:25:07.251  - info: host.07cbffd7e85a connected to Objects and States
                2022-03-14 13:25:07.264  - info: host.07cbffd7e85a Node.js version has changed from unknown to 14.19.0
                2022-03-14 13:25:07.283  - info: host.07cbffd7e85a added notifications configuration of host
                2022-03-14 13:25:09.374  - info: host.07cbffd7e85a Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
                2022-03-14 13:25:09.382  - info: host.07cbffd7e85a 3 instances found
                2022-03-14 13:25:09.385  - info: host.07cbffd7e85a starting 3 instances
                2022-03-14 13:25:09.431  - info: host.07cbffd7e85a instance system.adapter.admin.0 started with pid 229
                2022-03-14 13:25:09.531  - info: host.07cbffd7e85a Created UUID: 8b601527-da37-485e-b758-c19ee482868b
                2022-03-14 13:25:13.416  - info: host.07cbffd7e85a instance system.adapter.discovery.0 started with pid 236
                2022-03-14 13:25:17.420  - info: host.07cbffd7e85a instance system.adapter.backitup.0 started with pid 247
                2022-03-14 13:25:18.910  - info: admin.0 (229) starting. Version 5.3.1 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.0, js-controller: 4.0.21
                2022-03-14 13:25:18.926  - info: admin.0 (229) requesting all states
                2022-03-14 13:25:18.926  - info: admin.0 (229) requesting all objects
                2022-03-14 13:25:18.964  - info: admin.0 (229) received all objects
                2022-03-14 13:25:19.009  - info: admin.0 (229) http server listening on port 8081
                2022-03-14 13:25:19.010  - info: admin.0 (229) Use link "http://localhost:8081" to configure.
                2022-03-14 13:25:19.195  - warn: admin.0 (229) Repository cannot be read: Active repo - stable
                2022-03-14 13:25:19.195  - warn: admin.0 (229) Active repository "stable cannot be read
                2022-03-14 13:25:21.845  - info: discovery.0 (236) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.19.0, js-controller: 4.0.21
                2022-03-14 13:25:25.350  - info: backitup.0 (247) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21
                2022-03-14 13:25:25.457  - info: backitup.0 (247) [iobroker] backup was activated at 02:40 every 1 day(s)
                2022-03-14 13:27:53.471  - info: host.07cbffd7e85a Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
                2022-03-14 13:28:49.823  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 (force=false, process=true)
                2022-03-14 13:28:49.826  - info: backitup.0 (247) Got terminate signal TERMINATE_YOURSELF
                2022-03-14 13:28:49.826  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 send kill signal
                2022-03-14 13:28:49.826  - info: backitup.0 (247) cleaned everything up...
                2022-03-14 13:28:49.827  - info: backitup.0 (247) terminating
                2022-03-14 13:28:49.827  - info: backitup.0 (247) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-03-14 13:28:50.349  - info: host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-03-14 13:28:52.850  - info: host.07cbffd7e85a instance system.adapter.backitup.0 started with pid 457
                2022-03-14 13:29:00.551  - info: backitup.0 (457) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21
                2022-03-14 13:29:00.657  - info: backitup.0 (457) [iobroker] backup was activated at 02:40 every 1 day(s)
                2022-03-14 13:34:39.611  - info: host.07cbffd7e85a received SIGTERM
                2022-03-14 13:34:39.612  - info: host.07cbffd7e85a stopInstance system.adapter.admin.0 (force=false, process=true)
                2022-03-14 13:34:39.612  - info: host.07cbffd7e85a stopInstance system.adapter.discovery.0 (force=false, process=true)
                2022-03-14 13:34:39.613  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 (force=false, process=true)
                2022-03-14 13:34:39.615  - info: host.07cbffd7e85a stopInstance system.adapter.admin.0 send kill signal
                2022-03-14 13:34:39.615  - info: backitup.0 (457) Got terminate signal TERMINATE_YOURSELF
                2022-03-14 13:34:39.616  - info: host.07cbffd7e85a stopInstance system.adapter.discovery.0 send kill signal
                2022-03-14 13:34:39.616  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 send kill signal
                2022-03-14 13:34:39.615  - info: admin.0 (229) Got terminate signal TERMINATE_YOURSELF
                2022-03-14 13:34:39.615  - info: discovery.0 (236) Got terminate signal TERMINATE_YOURSELF
                2022-03-14 13:34:39.616  - info: backitup.0 (457) cleaned everything up...
                2022-03-14 13:34:39.617  - info: backitup.0 (457) terminating
                2022-03-14 13:34:39.617  - info: backitup.0 (457) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-03-14 13:34:39.616  - info: discovery.0 (236) terminating
                2022-03-14 13:34:39.617  - info: discovery.0 (236) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-03-14 13:34:39.617  - info: admin.0 (229) terminating http server on port 8081
                2022-03-14 13:34:39.618  - info: admin.0 (229) terminating
                2022-03-14 13:34:39.620  - info: admin.0 (229) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2022-03-14 13:34:40.135  - info: host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-03-14 13:34:40.138  - info: host.07cbffd7e85a instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-03-14 13:34:40.143  - info: host.07cbffd7e85a instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                2022-03-14 13:34:40.143  - info: host.07cbffd7e85a All instances are stopped.
                2022-03-14 13:34:40.242  - info: host.07cbffd7e85a terminated
                2022-03-14 13:37:26.143  - info: host.IoBroker iobroker.js-controller version 4.0.21 js-controller starting
                2022-03-14 13:37:26.145  - info: host.IoBroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                2022-03-14 13:37:26.145  - info: host.IoBroker hostname: IoBroker, node: v14.19.0
                2022-03-14 13:37:26.145  - info: host.IoBroker ip addresses: 172.17.0.3
                2022-03-14 13:37:26.454  - info: host.IoBroker Sets unsupported
                2022-03-14 13:37:26.576  - info: host.IoBroker connected to Objects and States
                2022-03-14 13:37:26.594  - info: host.IoBroker added notifications configuration of host
                2022-03-14 13:37:26.596  - info: host.IoBroker Node.js version has changed from unknown to 14.19.0
                2022-03-14 13:37:26.618  - info: host.IoBroker Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
                2022-03-14 13:37:28.408  - info: host.IoBroker Delete host system.host.07cbffd7e85a
                2022-03-14 13:37:28.439  - info: host.IoBroker 33 instances found
                2022-03-14 13:37:28.447  - warn: host.IoBroker does not start any instances on this host
                2022-03-14 18:28:41.714  - info: host.IoBroker iobroker.js-controller version 4.0.21 js-controller starting
                2022-03-14 18:28:41.716  - info: host.IoBroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                2022-03-14 18:28:41.716  - info: host.IoBroker hostname: IoBroker, node: v14.19.0
                2022-03-14 18:28:41.717  - info: host.IoBroker ip addresses: 172.17.0.3
                2022-03-14 18:28:42.199  - info: host.IoBroker connected to Objects and States
                2022-03-14 18:28:42.221  - info: host.IoBroker added notifications configuration of host
                2022-03-14 18:28:44.388  - info: host.IoBroker 33 instances found
                2022-03-14 18:28:44.394  - warn: host.IoBroker does not start any instances on this host
                

                @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

                Was läuft nicht mehr !?
                Welche Fehler kommen .
                Im Browser erscheint nur noch "ERR_EMPTY_RESPONSE"

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

                @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                host.IoBroker does not start any instances on this host

                und wer ist

                @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

                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 im Header. Danke!
                der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                Z 1 Antwort Letzte Antwort
                0
                • Z ZoXx

                  @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

                  Was steht im Log bei :
                  iobroker logs --watch

                  2022-03-14 13:25:07.061  - info: host.07cbffd7e85a iobroker.js-controller version 4.0.21 js-controller starting
                  2022-03-14 13:25:07.064  - info: host.07cbffd7e85a Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                  2022-03-14 13:25:07.064  - info: host.07cbffd7e85a hostname: 07cbffd7e85a, node: v14.19.0
                  2022-03-14 13:25:07.064  - info: host.07cbffd7e85a ip addresses: 172.17.0.3
                  2022-03-14 13:25:07.251  - info: host.07cbffd7e85a connected to Objects and States
                  2022-03-14 13:25:07.264  - info: host.07cbffd7e85a Node.js version has changed from unknown to 14.19.0
                  2022-03-14 13:25:07.283  - info: host.07cbffd7e85a added notifications configuration of host
                  2022-03-14 13:25:09.374  - info: host.07cbffd7e85a Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
                  2022-03-14 13:25:09.382  - info: host.07cbffd7e85a 3 instances found
                  2022-03-14 13:25:09.385  - info: host.07cbffd7e85a starting 3 instances
                  2022-03-14 13:25:09.431  - info: host.07cbffd7e85a instance system.adapter.admin.0 started with pid 229
                  2022-03-14 13:25:09.531  - info: host.07cbffd7e85a Created UUID: 8b601527-da37-485e-b758-c19ee482868b
                  2022-03-14 13:25:13.416  - info: host.07cbffd7e85a instance system.adapter.discovery.0 started with pid 236
                  2022-03-14 13:25:17.420  - info: host.07cbffd7e85a instance system.adapter.backitup.0 started with pid 247
                  2022-03-14 13:25:18.910  - info: admin.0 (229) starting. Version 5.3.1 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.0, js-controller: 4.0.21
                  2022-03-14 13:25:18.926  - info: admin.0 (229) requesting all states
                  2022-03-14 13:25:18.926  - info: admin.0 (229) requesting all objects
                  2022-03-14 13:25:18.964  - info: admin.0 (229) received all objects
                  2022-03-14 13:25:19.009  - info: admin.0 (229) http server listening on port 8081
                  2022-03-14 13:25:19.010  - info: admin.0 (229) Use link "http://localhost:8081" to configure.
                  2022-03-14 13:25:19.195  - warn: admin.0 (229) Repository cannot be read: Active repo - stable
                  2022-03-14 13:25:19.195  - warn: admin.0 (229) Active repository "stable cannot be read
                  2022-03-14 13:25:21.845  - info: discovery.0 (236) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.19.0, js-controller: 4.0.21
                  2022-03-14 13:25:25.350  - info: backitup.0 (247) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21
                  2022-03-14 13:25:25.457  - info: backitup.0 (247) [iobroker] backup was activated at 02:40 every 1 day(s)
                  2022-03-14 13:27:53.471  - info: host.07cbffd7e85a Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
                  2022-03-14 13:28:49.823  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 (force=false, process=true)
                  2022-03-14 13:28:49.826  - info: backitup.0 (247) Got terminate signal TERMINATE_YOURSELF
                  2022-03-14 13:28:49.826  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 send kill signal
                  2022-03-14 13:28:49.826  - info: backitup.0 (247) cleaned everything up...
                  2022-03-14 13:28:49.827  - info: backitup.0 (247) terminating
                  2022-03-14 13:28:49.827  - info: backitup.0 (247) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2022-03-14 13:28:50.349  - info: host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2022-03-14 13:28:52.850  - info: host.07cbffd7e85a instance system.adapter.backitup.0 started with pid 457
                  2022-03-14 13:29:00.551  - info: backitup.0 (457) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21
                  2022-03-14 13:29:00.657  - info: backitup.0 (457) [iobroker] backup was activated at 02:40 every 1 day(s)
                  2022-03-14 13:34:39.611  - info: host.07cbffd7e85a received SIGTERM
                  2022-03-14 13:34:39.612  - info: host.07cbffd7e85a stopInstance system.adapter.admin.0 (force=false, process=true)
                  2022-03-14 13:34:39.612  - info: host.07cbffd7e85a stopInstance system.adapter.discovery.0 (force=false, process=true)
                  2022-03-14 13:34:39.613  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 (force=false, process=true)
                  2022-03-14 13:34:39.615  - info: host.07cbffd7e85a stopInstance system.adapter.admin.0 send kill signal
                  2022-03-14 13:34:39.615  - info: backitup.0 (457) Got terminate signal TERMINATE_YOURSELF
                  2022-03-14 13:34:39.616  - info: host.07cbffd7e85a stopInstance system.adapter.discovery.0 send kill signal
                  2022-03-14 13:34:39.616  - info: host.07cbffd7e85a stopInstance system.adapter.backitup.0 send kill signal
                  2022-03-14 13:34:39.615  - info: admin.0 (229) Got terminate signal TERMINATE_YOURSELF
                  2022-03-14 13:34:39.615  - info: discovery.0 (236) Got terminate signal TERMINATE_YOURSELF
                  2022-03-14 13:34:39.616  - info: backitup.0 (457) cleaned everything up...
                  2022-03-14 13:34:39.617  - info: backitup.0 (457) terminating
                  2022-03-14 13:34:39.617  - info: backitup.0 (457) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2022-03-14 13:34:39.616  - info: discovery.0 (236) terminating
                  2022-03-14 13:34:39.617  - info: discovery.0 (236) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2022-03-14 13:34:39.617  - info: admin.0 (229) terminating http server on port 8081
                  2022-03-14 13:34:39.618  - info: admin.0 (229) terminating
                  2022-03-14 13:34:39.620  - info: admin.0 (229) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2022-03-14 13:34:40.135  - info: host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2022-03-14 13:34:40.138  - info: host.07cbffd7e85a instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2022-03-14 13:34:40.143  - info: host.07cbffd7e85a instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2022-03-14 13:34:40.143  - info: host.07cbffd7e85a All instances are stopped.
                  2022-03-14 13:34:40.242  - info: host.07cbffd7e85a terminated
                  2022-03-14 13:37:26.143  - info: host.IoBroker iobroker.js-controller version 4.0.21 js-controller starting
                  2022-03-14 13:37:26.145  - info: host.IoBroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                  2022-03-14 13:37:26.145  - info: host.IoBroker hostname: IoBroker, node: v14.19.0
                  2022-03-14 13:37:26.145  - info: host.IoBroker ip addresses: 172.17.0.3
                  2022-03-14 13:37:26.454  - info: host.IoBroker Sets unsupported
                  2022-03-14 13:37:26.576  - info: host.IoBroker connected to Objects and States
                  2022-03-14 13:37:26.594  - info: host.IoBroker added notifications configuration of host
                  2022-03-14 13:37:26.596  - info: host.IoBroker Node.js version has changed from unknown to 14.19.0
                  2022-03-14 13:37:26.618  - info: host.IoBroker Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
                  2022-03-14 13:37:28.408  - info: host.IoBroker Delete host system.host.07cbffd7e85a
                  2022-03-14 13:37:28.439  - info: host.IoBroker 33 instances found
                  2022-03-14 13:37:28.447  - warn: host.IoBroker does not start any instances on this host
                  2022-03-14 18:28:41.714  - info: host.IoBroker iobroker.js-controller version 4.0.21 js-controller starting
                  2022-03-14 18:28:41.716  - info: host.IoBroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                  2022-03-14 18:28:41.716  - info: host.IoBroker hostname: IoBroker, node: v14.19.0
                  2022-03-14 18:28:41.717  - info: host.IoBroker ip addresses: 172.17.0.3
                  2022-03-14 18:28:42.199  - info: host.IoBroker connected to Objects and States
                  2022-03-14 18:28:42.221  - info: host.IoBroker added notifications configuration of host
                  2022-03-14 18:28:44.388  - info: host.IoBroker 33 instances found
                  2022-03-14 18:28:44.394  - warn: host.IoBroker does not start any instances on this host
                  

                  @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

                  Was läuft nicht mehr !?
                  Welche Fehler kommen .
                  Im Browser erscheint nur noch "ERR_EMPTY_RESPONSE"

                  GlasfaserG Offline
                  GlasfaserG Offline
                  Glasfaser
                  schrieb am zuletzt editiert von
                  #36

                  @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                  warn: host.IoBroker does not start any instances on this host

                  In der Docker Konsole:

                  pkill -u iobroker
                  iobroker host this
                  

                  Docker anschließend neu starten

                  Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                  1 Antwort Letzte Antwort
                  0
                  • HomoranH Homoran

                    @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                    host.IoBroker does not start any instances on this host

                    und wer ist

                    @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                    host.07cbffd7e85a instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

                    Z Offline
                    Z Offline
                    ZoXx
                    schrieb am zuletzt editiert von
                    #37

                    @homoran said in Nach Docker Umzug keine Updates / Installationen möglich:

                    host.IoBroker does not start any instances on this host
                    das habe ich auch herausgelesen.

                    @homoran said in Nach Docker Umzug keine Updates / Installationen möglich:

                    und wer ist
                    07cbffd7e85a ist der Name des host der auch in Portainer drin steht.

                    @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

                    Docker anschließend neu starten

                    Host "IoBroker" successfully renamed to "07cbffd7e85a".
                    The host for instance "system.adapter.admin.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.discovery.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.backitup.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.alexa2.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.cloud.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.daswetter.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.dwd.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.echarts.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.ecovacs-deebot.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.history.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.ical.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.ical.1" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.icons-mfd-png.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.icons-open-icon-library-png.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.info.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.iot.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.javascript.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.mqtt.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.openweathermap.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.pushover.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.shelly.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.shuttercontrol.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.sonoff.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.trashschedule.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.trashschedule.1" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.vis-fancyswitch.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.vis-icontwo.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.vis-inventwo.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.vis-metro.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.vis-timeandweather.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.vis.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.web.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    The host for instance "system.adapter.zigbee.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                    

                    Änderungen sind anscheinend keine durchgeführt wurden. Fehler bleibt weiterhin vorhanden.

                    HomoranH GlasfaserG 2 Antworten Letzte Antwort
                    0
                    • Z ZoXx

                      @homoran said in Nach Docker Umzug keine Updates / Installationen möglich:

                      host.IoBroker does not start any instances on this host
                      das habe ich auch herausgelesen.

                      @homoran said in Nach Docker Umzug keine Updates / Installationen möglich:

                      und wer ist
                      07cbffd7e85a ist der Name des host der auch in Portainer drin steht.

                      @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

                      Docker anschließend neu starten

                      Host "IoBroker" successfully renamed to "07cbffd7e85a".
                      The host for instance "system.adapter.admin.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.discovery.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.backitup.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.alexa2.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.cloud.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.daswetter.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.dwd.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.echarts.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.ecovacs-deebot.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.history.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.ical.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.ical.1" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.icons-mfd-png.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.icons-open-icon-library-png.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.info.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.iot.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.javascript.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.mqtt.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.openweathermap.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.pushover.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.shelly.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.shuttercontrol.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.sonoff.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.trashschedule.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.trashschedule.1" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.vis-fancyswitch.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.vis-icontwo.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.vis-inventwo.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.vis-metro.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.vis-timeandweather.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.vis.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.web.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      The host for instance "system.adapter.zigbee.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                      

                      Änderungen sind anscheinend keine durchgeführt wurden. Fehler bleibt weiterhin vorhanden.

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

                      @zoxx wie heisst denn dein Host jetzt?
                      laut log gibt es zwei Hostnamen

                      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 im Header. Danke!
                      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                      GlasfaserG 1 Antwort Letzte Antwort
                      0
                      • Z ZoXx

                        @homoran said in Nach Docker Umzug keine Updates / Installationen möglich:

                        host.IoBroker does not start any instances on this host
                        das habe ich auch herausgelesen.

                        @homoran said in Nach Docker Umzug keine Updates / Installationen möglich:

                        und wer ist
                        07cbffd7e85a ist der Name des host der auch in Portainer drin steht.

                        @glasfaser said in Nach Docker Umzug keine Updates / Installationen möglich:

                        Docker anschließend neu starten

                        Host "IoBroker" successfully renamed to "07cbffd7e85a".
                        The host for instance "system.adapter.admin.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.discovery.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.backitup.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.alexa2.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.cloud.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.daswetter.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.dwd.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.echarts.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.ecovacs-deebot.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.history.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.ical.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.ical.1" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.icons-mfd-png.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.icons-open-icon-library-png.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.info.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.iot.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.javascript.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.mqtt.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.openweathermap.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.pushover.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.shelly.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.shuttercontrol.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.sonoff.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.trashschedule.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.trashschedule.1" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.vis-fancyswitch.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.vis-icontwo.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.vis-inventwo.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.vis-metro.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.vis-timeandweather.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.vis.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.web.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        The host for instance "system.adapter.zigbee.0" was changed from "07cbffd7e85a" to "07cbffd7e85a".
                        

                        Änderungen sind anscheinend keine durchgeführt wurden. Fehler bleibt weiterhin vorhanden.

                        GlasfaserG Offline
                        GlasfaserG Offline
                        Glasfaser
                        schrieb am zuletzt editiert von
                        #39

                        @zoxx sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                        ost "IoBroker" successfully renamed to "07cbffd7e85a".

                        ist doch ...

                        Fehler bleibt weiterhin vorhanden.

                        welche Fehler

                        Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                        1 Antwort Letzte Antwort
                        0
                        • HomoranH Homoran

                          @zoxx wie heisst denn dein Host jetzt?
                          laut log gibt es zwei Hostnamen

                          GlasfaserG Offline
                          GlasfaserG Offline
                          Glasfaser
                          schrieb am zuletzt editiert von
                          #40

                          @homoran sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                          laut log gibt es zwei Hostnamen

                          ja ... sehr korrios .... zu unterschiedlichen Uhrzeiten .

                          Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                          Z 1 Antwort Letzte Antwort
                          0
                          • GlasfaserG Glasfaser

                            @homoran sagte in Nach Docker Umzug keine Updates / Installationen möglich:

                            laut log gibt es zwei Hostnamen

                            ja ... sehr korrios .... zu unterschiedlichen Uhrzeiten .

                            Z Offline
                            Z Offline
                            ZoXx
                            schrieb am zuletzt editiert von ZoXx
                            #41

                            @glasfaser ich komme via web nicht auf den iobroker.
                            "ERR_EMPTY_RESPONSE"

                            JETZT KLAPPT ES ! :)
                            Riesen Dank schon einmal an der Stelle, ich schaue später direkt einmal, ob die Fehler von Thread oben im Backup auch vorhanden sind.

                            Z 1 Antwort Letzte Antwort
                            0
                            • Z ZoXx

                              @glasfaser ich komme via web nicht auf den iobroker.
                              "ERR_EMPTY_RESPONSE"

                              JETZT KLAPPT ES ! :)
                              Riesen Dank schon einmal an der Stelle, ich schaue später direkt einmal, ob die Fehler von Thread oben im Backup auch vorhanden sind.

                              Z Offline
                              Z Offline
                              ZoXx
                              schrieb am zuletzt editiert von
                              #42

                              Kurzes Feedback an alle.
                              Backup habe ich auf dem Live System eingespielt und alle Änderungen übertragen.
                              Läuft nun wieder alles wie gewohnt.

                              Vielen vielen Dank!

                              1 Antwort Letzte Antwort
                              0
                              Antworten
                              • In einem neuen Thema antworten
                              Anmelden zum Antworten
                              • Älteste zuerst
                              • Neuste zuerst
                              • Meiste Stimmen


                              Support us

                              ioBroker
                              Community Adapters
                              Donate

                              623

                              Online

                              32.7k

                              Benutzer

                              82.5k

                              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