Skip to content
  • 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
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Probleme mit admin nach restore

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.1k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

Probleme mit admin nach restore

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
55 Beiträge 3 Kommentatoren 5.3k Aufrufe 2 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.
  • JB_SullivanJ JB_Sullivan

    @homoran

    Wieso, da steht doch run as admin

    Wie komme ich an das LOG ohne laufenden Admin? Wie gesagt ist Linux und ich habe Null Ahnung (von Linux) wo und wie man da im Dateisystem die Logdatei finden und öffnen kann.

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

    @jb_sullivan

    Hat doch mit Linux nix zu tun. Die Kommandos sind vom iobroker und auf jeder Plattform gleich.

    iobroker logs
    

    sagt?

    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

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

      @jb_sullivan sagte in Test Adapter ioBroker.backitup v2.5.x:

      Wieso, da steht doch run as admin

      das heisst, dass er wenn er läuft unter dem User admin läuft.

      Die Erklärung steht in der fehlenden letzten Zeile.

      @jb_sullivan sagte in Test Adapter ioBroker.backitup v2.5.x:

      Wie komme ich an das LOG ohne laufenden Admin? Wie gesagt ist Linux und ich habe Null Ahnung (von Linux) wo und wie man da im Dateisystem die Logdatei finden und öffnen kann.

      unter /opt/iobroker/logs

      oder zweite putty session aufmachen, dort iobroker logs --watch starten und in der ersten nochmals iobroker start admin eingeben

      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

      1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @jb_sullivan

        Hat doch mit Linux nix zu tun. Die Kommandos sind vom iobroker und auf jeder Plattform gleich.

        iobroker logs
        

        sagt?

        JB_SullivanJ Offline
        JB_SullivanJ Offline
        JB_Sullivan
        schrieb am zuletzt editiert von
        #12

        @thomas-braun

        Ok - naja wenn man mit Windows arbeitet, brauche ich viele der iobroker Kommandos nicht. Da gehe ich in die Dateistruktur und öffne die LOG Datei mit dem Texteditor.

        Hier nun das Log

        
        sully@ioBrokerNUC:~$ iobroker logs
        2022-12-29 10:31:14.990  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
        2022-12-29 10:31:44.995  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
        2022-12-29 10:31:48.334  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
        2022-12-29 10:40:26.924  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 10:41:06.878  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 10:44:01.886  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
        2022-12-29 10:44:14.689  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
        2022-12-29 10:44:25.011  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 12:47:02.750  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 12:47:15.689  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
        2022-12-29 13:21:15.006  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
        2022-12-29 13:21:45.008  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
        2022-12-29 13:21:47.992  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
        2022-12-29 13:54:51.219  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 13:55:05.561  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
        2022-12-29 13:55:25.563  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 13:55:52.524  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
        2022-12-29 14:10:57.617  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 14:10:59.105  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
        2022-12-29 14:11:05.947  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
        2022-12-29 14:11:15.009  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
        2022-12-29 14:11:45.011  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
        2022-12-29 14:11:47.986  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
        2022-12-29 15:01:15.015  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
        2022-12-29 15:01:45.016  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
        2022-12-29 15:01:47.981  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
        2022-12-29 18:27:29.310  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:28:47.331  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:29:26.256  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:29:30.850  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:31:06.727  - info: host.ioBrokerNUC "system.adapter.backitup.0" enabled
        2022-12-29 18:31:06.768  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 1336
        2022-12-29 18:31:07.979  - info: backitup.0 (1336) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:31:08.067  - info: backitup.0 (1336) [iobroker] backup was activated at 02:40 every 1 day(s)
        2022-12-29 18:31:48.051  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 (force=false, process=true)
        2022-12-29 18:31:48.056  - info: backitup.0 (1336) Got terminate signal TERMINATE_YOURSELF
        2022-12-29 18:31:48.057  - info: backitup.0 (1336) cleaned everything up...
        2022-12-29 18:31:48.058  - info: backitup.0 (1336) terminating
        2022-12-29 18:31:48.059  - info: backitup.0 (1336) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2022-12-29 18:31:48.097  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 send kill signal
        2022-12-29 18:31:48.601  - info: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2022-12-29 18:31:50.601  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:31:51.011  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:31:51.126  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 1351
        2022-12-29 18:31:52.377  - info: backitup.0 (1351) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:31:52.454  - info: backitup.0 (1351) [iobroker] backup was activated at  every 1 day(s)
        2022-12-29 18:36:02.842  - info: proxmox.0 (646) Detected new VM/storage "VM 501" - restarting instance
        2022-12-29 18:36:02.848  - warn: proxmox.0 (646) Restart initiated
        2022-12-29 18:36:02.852  - info: proxmox.0 (646) cleaned everything up...
        2022-12-29 18:36:02.876  - info: proxmox.0 (646) terminating
        2022-12-29 18:36:02.877  - info: proxmox.0 (646) Terminated (NO_ERROR): Without reason
        2022-12-29 18:36:03.417  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 0 (NO_ERROR)
        2022-12-29 18:36:03.418  - info: host.ioBrokerNUC Restart adapter system.adapter.proxmox.0 because enabled
        2022-12-29 18:36:33.444  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 1380
        2022-12-29 18:36:34.950  - info: proxmox.0 (1380) starting. Version 1.3.5 in /opt/iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:43:28.411  - info: host.ioBrokerNUC iobroker.js-controller version 4.0.24 js-controller starting
        2022-12-29 18:43:28.419  - info: host.ioBrokerNUC Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
        2022-12-29 18:43:28.419  - info: host.ioBrokerNUC hostname: ioBrokerNUC, node: v14.21.1
        2022-12-29 18:43:28.420  - info: host.ioBrokerNUC ip addresses: 10.122.60.127 2a02:8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
        2022-12-29 18:43:29.917  - info: host.ioBrokerNUC connected to Objects and States
        2022-12-29 18:43:29.936  - info: host.ioBrokerNUC added notifications configuration of host
        2022-12-29 18:43:30.327  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeCurrent"
        2022-12-29 18:43:30.333  - info: host.ioBrokerNUC 7 instances found
        2022-12-29 18:43:30.353  - info: host.ioBrokerNUC starting 6 instances
        2022-12-29 18:43:30.409  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeNewest"
        2022-12-29 18:43:30.471  - info: host.ioBrokerNUC instance system.adapter.admin.0 started with pid 466
        2022-12-29 18:43:30.482  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeNewestNext"
        2022-12-29 18:43:30.537  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmCurrent"
        2022-12-29 18:43:30.587  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmNewest"
        2022-12-29 18:43:30.639  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmNewestNext"
        2022-12-29 18:43:30.699  - info: host.ioBrokerNUC Some obsolete host states deleted.
        2022-12-29 18:43:32.039  - error: admin.0 (466) admin.0 already running
        2022-12-29 18:43:32.041  - warn: admin.0 (466) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
        2022-12-29 18:43:32.602  - error: host.ioBrokerNUC instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
        2022-12-29 18:43:32.605  - info: host.ioBrokerNUC Restart adapter system.adapter.admin.0 because enabled
        2022-12-29 18:43:34.384  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 started with pid 477
        2022-12-29 18:43:36.039  - error: innogy-smarthome.0 (477) innogy-smarthome.0 already running
        2022-12-29 18:43:36.041  - warn: innogy-smarthome.0 (477) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
        2022-12-29 18:43:36.578  - error: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
        2022-12-29 18:43:36.579  - info: host.ioBrokerNUC Restart adapter system.adapter.innogy-smarthome.0 because enabled
        2022-12-29 18:43:38.387  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 488
        2022-12-29 18:43:39.414  - error: backitup.0 (488) backitup.0 already running
        2022-12-29 18:43:39.417  - warn: backitup.0 (488) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
        2022-12-29 18:43:39.949  - error: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
        2022-12-29 18:43:39.949  - info: host.ioBrokerNUC Restart adapter system.adapter.backitup.0 because enabled
        2022-12-29 18:43:42.390  - info: host.ioBrokerNUC instance system.adapter.info.0 started with pid 499
        2022-12-29 18:43:44.075  - error: info.0 (499) info.0 already running
        2022-12-29 18:43:44.077  - warn: info.0 (499) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
        2022-12-29 18:43:44.611  - error: host.ioBrokerNUC instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
        2022-12-29 18:43:44.612  - info: host.ioBrokerNUC Restart adapter system.adapter.info.0 because enabled
        2022-12-29 18:43:46.386  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 518
        2022-12-29 18:43:47.586  - error: proxmox.0 (518) proxmox.0 already running
        2022-12-29 18:43:47.589  - warn: proxmox.0 (518) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
        2022-12-29 18:43:48.129  - error: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
        2022-12-29 18:43:48.129  - info: host.ioBrokerNUC Restart adapter system.adapter.proxmox.0 because enabled
        2022-12-29 18:43:50.385  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 started with pid 529
        2022-12-29 18:43:51.458  - error: device-watcher.0 (529) device-watcher.0 already running
        2022-12-29 18:43:51.460  - warn: device-watcher.0 (529) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
        2022-12-29 18:43:52.000  - error: host.ioBrokerNUC instance system.adapter.device-watcher.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
        2022-12-29 18:43:52.000  - info: host.ioBrokerNUC Restart adapter system.adapter.device-watcher.0 because enabled
        2022-12-29 18:44:02.628  - info: host.ioBrokerNUC instance system.adapter.admin.0 started with pid 540
        2022-12-29 18:44:04.144  - info: admin.0 (540) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:44:04.185  - info: admin.0 (540) requesting all states
        2022-12-29 18:44:04.186  - info: admin.0 (540) requesting all objects
        2022-12-29 18:44:05.064  - info: admin.0 (540) received all objects
        2022-12-29 18:44:05.311  - info: admin.0 (540) Request actual repository...
        2022-12-29 18:44:05.374  - info: admin.0 (540) http server listening on port 8081
        2022-12-29 18:44:05.375  - info: admin.0 (540) Use link "http://localhost:8081" to configure.
        2022-12-29 18:44:05.397  - info: admin.0 (540) socket.io server listening on port 8081
        2022-12-29 18:44:05.885  - info: host.ioBrokerNUC Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
        2022-12-29 18:44:08.187  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 started with pid 563
        2022-12-29 18:44:08.412  - info: admin.0 (540) Repository received successfully.
        2022-12-29 18:44:09.985  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 574
        2022-12-29 18:44:10.032  - info: innogy-smarthome.0 (563) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.innogy-smarthome, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:44:10.092  - info: innogy-smarthome.0 (563) Trying to use local smarthome connection! SHC generation: 2
        2022-12-29 18:44:11.329  - info: backitup.0 (574) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:44:11.425  - info: backitup.0 (574) [iobroker] backup was activated at  every 1 day(s)
        2022-12-29 18:44:13.476  - info: innogy-smarthome.0 (563) Initialization sequence completed: found 62 devices
        2022-12-29 18:44:14.641  - info: host.ioBrokerNUC instance system.adapter.info.0 started with pid 593
        2022-12-29 18:44:17.371  - info: info.0 (593) starting. Version 1.9.24 in /opt/iobroker/node_modules/iobroker.info, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:44:17.452  - info: info.0 (593) Reading/updating systemdata.
        2022-12-29 18:44:18.036  - info: info.0 (593) cpu Temp res = {"main":null,"cores":[],"max":null,"socket":[],"chipset":null}
        2022-12-29 18:44:18.156  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 677
        2022-12-29 18:44:19.818  - info: proxmox.0 (677) starting. Version 1.3.5 in /opt/iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:44:22.038  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 started with pid 994
        2022-12-29 18:44:23.434  - info: device-watcher.0 (994) starting. Version 2.2.1 in /opt/iobroker/node_modules/iobroker.device-watcher, node: v14.21.1, js-controller: 4.0.24
        2022-12-29 18:44:23.480  - info: device-watcher.0 (994) Number of selected adapters: 1. Loading data from: Innogy ...
        2022-12-29 18:44:24.590  - info: proxmox.0 (677) Deleted old VM/storage "qemu_VM 501"
        2022-12-29 18:44:39.129  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:44:41.732  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:44:45.976  - info: admin.0 (540) <== Disconnect system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:44:57.277  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
        2022-12-29 18:45:42.153  - info: admin.0 (540) terminating http server on port 8081
        2022-12-29 18:45:42.151  - info: host.ioBrokerNUC received SIGTERM
        2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.admin.0 (force=false, process=true)
        2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.influxdb.0 (force=false, process=false)
        2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.innogy-smarthome.0 (force=false, process=true)
        2022-12-29 18:45:42.157  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 (force=false, process=true)
        2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.info.0 (force=false, process=true)
        2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.proxmox.0 (force=false, process=true)
        2022-12-29 18:45:42.159  - info: host.ioBrokerNUC stopInstance system.adapter.device-watcher.0 (force=false, process=true)
        2022-12-29 18:45:42.162  - info: innogy-smarthome.0 (563) cleaned everything up...
        2022-12-29 18:45:42.165  - info: backitup.0 (574) cleaned everything up...
        2022-12-29 18:45:42.168  - info: info.0 (593) cleaned everything up...
        2022-12-29 18:45:42.171  - info: proxmox.0 (677) cleaned everything up...
        2022-12-29 18:45:42.173  - info: device-watcher.0 (994) cleaned everything up...
        2022-12-29 18:45:42.190  - info: backitup.0 (574) Got terminate signal TERMINATE_YOURSELF
        2022-12-29 18:45:42.192  - info: admin.0 (540) Got terminate signal TERMINATE_YOURSELF
        2022-12-29 18:45:42.193  - info: innogy-smarthome.0 (563) Got terminate signal TERMINATE_YOURSELF
        2022-12-29 18:45:42.194  - info: info.0 (593) Got terminate signal TERMINATE_YOURSELF
        2022-12-29 18:45:42.195  - info: proxmox.0 (677) Got terminate signal TERMINATE_YOURSELF
        2022-12-29 18:45:42.197  - info: device-watcher.0 (994) Got terminate signal TERMINATE_YOURSELF
        2022-12-29 18:45:42.209  - info: innogy-smarthome.0 (563) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
        2022-12-29 18:45:42.210  - info: admin.0 (540) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
        2022-12-29 18:45:42.226  - info: host.ioBrokerNUC stopInstance system.adapter.admin.0 send kill signal
        2022-12-29 18:45:42.229  - info: host.ioBrokerNUC stopInstance system.adapter.innogy-smarthome.0 send kill signal
        2022-12-29 18:45:42.230  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 send kill signal
        2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.info.0 send kill signal
        2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.proxmox.0 send kill signal
        2022-12-29 18:45:42.232  - info: host.ioBrokerNUC stopInstance system.adapter.device-watcher.0 send kill signal
        2022-12-29 18:45:42.245  - info: info.0 (593) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
        2022-12-29 18:45:42.245  - info: backitup.0 (574) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
        2022-12-29 18:45:42.248  - info: proxmox.0 (677) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
        2022-12-29 18:45:42.253  - info: device-watcher.0 (994) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
        2022-12-29 18:45:42.810  - info: host.ioBrokerNUC instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
        2022-12-29 18:45:42.811  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
        2022-12-29 18:45:42.872  - info: host.ioBrokerNUC instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
        2022-12-29 18:45:42.873  - info: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
        2022-12-29 18:45:42.893  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
        2022-12-29 18:45:42.894  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
        2022-12-29 18:45:42.894  - info: host.ioBrokerNUC All instances are stopped.
        2022-12-29 18:45:42.992  - info: host.ioBrokerNUC terminated
        2022-12-29 18:48:34.791  - info: host.GLT(GLT) iobroker.js-controller version 4.0.24 js-controller starting
        2022-12-29 18:48:34.796  - info: host.GLT(GLT) Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
        2022-12-29 18:48:34.797  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.21.1
        2022-12-29 18:48:34.797  - info: host.GLT(GLT) ip addresses: 10.122.60.127 2a02:8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
        2022-12-29 18:48:37.068  - info: host.GLT(GLT) connected to Objects and States
        2022-12-29 18:48:37.174  - info: host.GLT(GLT) added notifications configuration of host
        2022-12-29 18:48:37.176  - info: host.GLT(GLT) Node.js version has changed from 14.16.0 to 14.21.1
        2022-12-29 18:48:37.218  - info: host.GLT(GLT) Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
        2022-12-29 18:48:38.008  - info: host.GLT(GLT) Delete host system.host.ioBrokerNUC
        2022-12-29 18:48:38.200  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeCurrent"
        2022-12-29 18:48:38.201  - info: host.GLT(GLT) 68 instances found
        2022-12-29 18:48:38.246  - warn: host.GLT(GLT) does not start any instances on this host
        2022-12-29 18:48:38.302  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeNewest"
        2022-12-29 18:48:38.353  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeNewestNext"
        2022-12-29 18:48:38.406  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmCurrent"
        2022-12-29 18:48:38.455  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmNewest"
        2022-12-29 18:48:38.508  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmNewestNext"
        2022-12-29 18:48:38.558  - info: host.GLT(GLT) Some obsolete host states deleted.
        
        

        ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

        HomoranH Thomas BraunT 2 Antworten Letzte Antwort
        0
        • JB_SullivanJ JB_Sullivan

          @thomas-braun

          Ok - naja wenn man mit Windows arbeitet, brauche ich viele der iobroker Kommandos nicht. Da gehe ich in die Dateistruktur und öffne die LOG Datei mit dem Texteditor.

          Hier nun das Log

          
          sully@ioBrokerNUC:~$ iobroker logs
          2022-12-29 10:31:14.990  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
          2022-12-29 10:31:44.995  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
          2022-12-29 10:31:48.334  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
          2022-12-29 10:40:26.924  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 10:41:06.878  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 10:44:01.886  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
          2022-12-29 10:44:14.689  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
          2022-12-29 10:44:25.011  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 12:47:02.750  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 12:47:15.689  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
          2022-12-29 13:21:15.006  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
          2022-12-29 13:21:45.008  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
          2022-12-29 13:21:47.992  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
          2022-12-29 13:54:51.219  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 13:55:05.561  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
          2022-12-29 13:55:25.563  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 13:55:52.524  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
          2022-12-29 14:10:57.617  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 14:10:59.105  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
          2022-12-29 14:11:05.947  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
          2022-12-29 14:11:15.009  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
          2022-12-29 14:11:45.011  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
          2022-12-29 14:11:47.986  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
          2022-12-29 15:01:15.015  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
          2022-12-29 15:01:45.016  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
          2022-12-29 15:01:47.981  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
          2022-12-29 18:27:29.310  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:28:47.331  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:29:26.256  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:29:30.850  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:31:06.727  - info: host.ioBrokerNUC "system.adapter.backitup.0" enabled
          2022-12-29 18:31:06.768  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 1336
          2022-12-29 18:31:07.979  - info: backitup.0 (1336) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:31:08.067  - info: backitup.0 (1336) [iobroker] backup was activated at 02:40 every 1 day(s)
          2022-12-29 18:31:48.051  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 (force=false, process=true)
          2022-12-29 18:31:48.056  - info: backitup.0 (1336) Got terminate signal TERMINATE_YOURSELF
          2022-12-29 18:31:48.057  - info: backitup.0 (1336) cleaned everything up...
          2022-12-29 18:31:48.058  - info: backitup.0 (1336) terminating
          2022-12-29 18:31:48.059  - info: backitup.0 (1336) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2022-12-29 18:31:48.097  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 send kill signal
          2022-12-29 18:31:48.601  - info: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          2022-12-29 18:31:50.601  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:31:51.011  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:31:51.126  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 1351
          2022-12-29 18:31:52.377  - info: backitup.0 (1351) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:31:52.454  - info: backitup.0 (1351) [iobroker] backup was activated at  every 1 day(s)
          2022-12-29 18:36:02.842  - info: proxmox.0 (646) Detected new VM/storage "VM 501" - restarting instance
          2022-12-29 18:36:02.848  - warn: proxmox.0 (646) Restart initiated
          2022-12-29 18:36:02.852  - info: proxmox.0 (646) cleaned everything up...
          2022-12-29 18:36:02.876  - info: proxmox.0 (646) terminating
          2022-12-29 18:36:02.877  - info: proxmox.0 (646) Terminated (NO_ERROR): Without reason
          2022-12-29 18:36:03.417  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 0 (NO_ERROR)
          2022-12-29 18:36:03.418  - info: host.ioBrokerNUC Restart adapter system.adapter.proxmox.0 because enabled
          2022-12-29 18:36:33.444  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 1380
          2022-12-29 18:36:34.950  - info: proxmox.0 (1380) starting. Version 1.3.5 in /opt/iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:43:28.411  - info: host.ioBrokerNUC iobroker.js-controller version 4.0.24 js-controller starting
          2022-12-29 18:43:28.419  - info: host.ioBrokerNUC Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
          2022-12-29 18:43:28.419  - info: host.ioBrokerNUC hostname: ioBrokerNUC, node: v14.21.1
          2022-12-29 18:43:28.420  - info: host.ioBrokerNUC ip addresses: 10.122.60.127 2a02:8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
          2022-12-29 18:43:29.917  - info: host.ioBrokerNUC connected to Objects and States
          2022-12-29 18:43:29.936  - info: host.ioBrokerNUC added notifications configuration of host
          2022-12-29 18:43:30.327  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeCurrent"
          2022-12-29 18:43:30.333  - info: host.ioBrokerNUC 7 instances found
          2022-12-29 18:43:30.353  - info: host.ioBrokerNUC starting 6 instances
          2022-12-29 18:43:30.409  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeNewest"
          2022-12-29 18:43:30.471  - info: host.ioBrokerNUC instance system.adapter.admin.0 started with pid 466
          2022-12-29 18:43:30.482  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeNewestNext"
          2022-12-29 18:43:30.537  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmCurrent"
          2022-12-29 18:43:30.587  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmNewest"
          2022-12-29 18:43:30.639  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmNewestNext"
          2022-12-29 18:43:30.699  - info: host.ioBrokerNUC Some obsolete host states deleted.
          2022-12-29 18:43:32.039  - error: admin.0 (466) admin.0 already running
          2022-12-29 18:43:32.041  - warn: admin.0 (466) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
          2022-12-29 18:43:32.602  - error: host.ioBrokerNUC instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
          2022-12-29 18:43:32.605  - info: host.ioBrokerNUC Restart adapter system.adapter.admin.0 because enabled
          2022-12-29 18:43:34.384  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 started with pid 477
          2022-12-29 18:43:36.039  - error: innogy-smarthome.0 (477) innogy-smarthome.0 already running
          2022-12-29 18:43:36.041  - warn: innogy-smarthome.0 (477) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
          2022-12-29 18:43:36.578  - error: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
          2022-12-29 18:43:36.579  - info: host.ioBrokerNUC Restart adapter system.adapter.innogy-smarthome.0 because enabled
          2022-12-29 18:43:38.387  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 488
          2022-12-29 18:43:39.414  - error: backitup.0 (488) backitup.0 already running
          2022-12-29 18:43:39.417  - warn: backitup.0 (488) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
          2022-12-29 18:43:39.949  - error: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
          2022-12-29 18:43:39.949  - info: host.ioBrokerNUC Restart adapter system.adapter.backitup.0 because enabled
          2022-12-29 18:43:42.390  - info: host.ioBrokerNUC instance system.adapter.info.0 started with pid 499
          2022-12-29 18:43:44.075  - error: info.0 (499) info.0 already running
          2022-12-29 18:43:44.077  - warn: info.0 (499) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
          2022-12-29 18:43:44.611  - error: host.ioBrokerNUC instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
          2022-12-29 18:43:44.612  - info: host.ioBrokerNUC Restart adapter system.adapter.info.0 because enabled
          2022-12-29 18:43:46.386  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 518
          2022-12-29 18:43:47.586  - error: proxmox.0 (518) proxmox.0 already running
          2022-12-29 18:43:47.589  - warn: proxmox.0 (518) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
          2022-12-29 18:43:48.129  - error: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
          2022-12-29 18:43:48.129  - info: host.ioBrokerNUC Restart adapter system.adapter.proxmox.0 because enabled
          2022-12-29 18:43:50.385  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 started with pid 529
          2022-12-29 18:43:51.458  - error: device-watcher.0 (529) device-watcher.0 already running
          2022-12-29 18:43:51.460  - warn: device-watcher.0 (529) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
          2022-12-29 18:43:52.000  - error: host.ioBrokerNUC instance system.adapter.device-watcher.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
          2022-12-29 18:43:52.000  - info: host.ioBrokerNUC Restart adapter system.adapter.device-watcher.0 because enabled
          2022-12-29 18:44:02.628  - info: host.ioBrokerNUC instance system.adapter.admin.0 started with pid 540
          2022-12-29 18:44:04.144  - info: admin.0 (540) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:44:04.185  - info: admin.0 (540) requesting all states
          2022-12-29 18:44:04.186  - info: admin.0 (540) requesting all objects
          2022-12-29 18:44:05.064  - info: admin.0 (540) received all objects
          2022-12-29 18:44:05.311  - info: admin.0 (540) Request actual repository...
          2022-12-29 18:44:05.374  - info: admin.0 (540) http server listening on port 8081
          2022-12-29 18:44:05.375  - info: admin.0 (540) Use link "http://localhost:8081" to configure.
          2022-12-29 18:44:05.397  - info: admin.0 (540) socket.io server listening on port 8081
          2022-12-29 18:44:05.885  - info: host.ioBrokerNUC Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
          2022-12-29 18:44:08.187  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 started with pid 563
          2022-12-29 18:44:08.412  - info: admin.0 (540) Repository received successfully.
          2022-12-29 18:44:09.985  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 574
          2022-12-29 18:44:10.032  - info: innogy-smarthome.0 (563) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.innogy-smarthome, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:44:10.092  - info: innogy-smarthome.0 (563) Trying to use local smarthome connection! SHC generation: 2
          2022-12-29 18:44:11.329  - info: backitup.0 (574) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:44:11.425  - info: backitup.0 (574) [iobroker] backup was activated at  every 1 day(s)
          2022-12-29 18:44:13.476  - info: innogy-smarthome.0 (563) Initialization sequence completed: found 62 devices
          2022-12-29 18:44:14.641  - info: host.ioBrokerNUC instance system.adapter.info.0 started with pid 593
          2022-12-29 18:44:17.371  - info: info.0 (593) starting. Version 1.9.24 in /opt/iobroker/node_modules/iobroker.info, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:44:17.452  - info: info.0 (593) Reading/updating systemdata.
          2022-12-29 18:44:18.036  - info: info.0 (593) cpu Temp res = {"main":null,"cores":[],"max":null,"socket":[],"chipset":null}
          2022-12-29 18:44:18.156  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 677
          2022-12-29 18:44:19.818  - info: proxmox.0 (677) starting. Version 1.3.5 in /opt/iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:44:22.038  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 started with pid 994
          2022-12-29 18:44:23.434  - info: device-watcher.0 (994) starting. Version 2.2.1 in /opt/iobroker/node_modules/iobroker.device-watcher, node: v14.21.1, js-controller: 4.0.24
          2022-12-29 18:44:23.480  - info: device-watcher.0 (994) Number of selected adapters: 1. Loading data from: Innogy ...
          2022-12-29 18:44:24.590  - info: proxmox.0 (677) Deleted old VM/storage "qemu_VM 501"
          2022-12-29 18:44:39.129  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:44:41.732  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:44:45.976  - info: admin.0 (540) <== Disconnect system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:44:57.277  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
          2022-12-29 18:45:42.153  - info: admin.0 (540) terminating http server on port 8081
          2022-12-29 18:45:42.151  - info: host.ioBrokerNUC received SIGTERM
          2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.admin.0 (force=false, process=true)
          2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.influxdb.0 (force=false, process=false)
          2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.innogy-smarthome.0 (force=false, process=true)
          2022-12-29 18:45:42.157  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 (force=false, process=true)
          2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.info.0 (force=false, process=true)
          2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.proxmox.0 (force=false, process=true)
          2022-12-29 18:45:42.159  - info: host.ioBrokerNUC stopInstance system.adapter.device-watcher.0 (force=false, process=true)
          2022-12-29 18:45:42.162  - info: innogy-smarthome.0 (563) cleaned everything up...
          2022-12-29 18:45:42.165  - info: backitup.0 (574) cleaned everything up...
          2022-12-29 18:45:42.168  - info: info.0 (593) cleaned everything up...
          2022-12-29 18:45:42.171  - info: proxmox.0 (677) cleaned everything up...
          2022-12-29 18:45:42.173  - info: device-watcher.0 (994) cleaned everything up...
          2022-12-29 18:45:42.190  - info: backitup.0 (574) Got terminate signal TERMINATE_YOURSELF
          2022-12-29 18:45:42.192  - info: admin.0 (540) Got terminate signal TERMINATE_YOURSELF
          2022-12-29 18:45:42.193  - info: innogy-smarthome.0 (563) Got terminate signal TERMINATE_YOURSELF
          2022-12-29 18:45:42.194  - info: info.0 (593) Got terminate signal TERMINATE_YOURSELF
          2022-12-29 18:45:42.195  - info: proxmox.0 (677) Got terminate signal TERMINATE_YOURSELF
          2022-12-29 18:45:42.197  - info: device-watcher.0 (994) Got terminate signal TERMINATE_YOURSELF
          2022-12-29 18:45:42.209  - info: innogy-smarthome.0 (563) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-12-29 18:45:42.210  - info: admin.0 (540) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-12-29 18:45:42.226  - info: host.ioBrokerNUC stopInstance system.adapter.admin.0 send kill signal
          2022-12-29 18:45:42.229  - info: host.ioBrokerNUC stopInstance system.adapter.innogy-smarthome.0 send kill signal
          2022-12-29 18:45:42.230  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 send kill signal
          2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.info.0 send kill signal
          2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.proxmox.0 send kill signal
          2022-12-29 18:45:42.232  - info: host.ioBrokerNUC stopInstance system.adapter.device-watcher.0 send kill signal
          2022-12-29 18:45:42.245  - info: info.0 (593) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-12-29 18:45:42.245  - info: backitup.0 (574) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-12-29 18:45:42.248  - info: proxmox.0 (677) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-12-29 18:45:42.253  - info: device-watcher.0 (994) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
          2022-12-29 18:45:42.810  - info: host.ioBrokerNUC instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
          2022-12-29 18:45:42.811  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
          2022-12-29 18:45:42.872  - info: host.ioBrokerNUC instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
          2022-12-29 18:45:42.873  - info: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
          2022-12-29 18:45:42.893  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
          2022-12-29 18:45:42.894  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
          2022-12-29 18:45:42.894  - info: host.ioBrokerNUC All instances are stopped.
          2022-12-29 18:45:42.992  - info: host.ioBrokerNUC terminated
          2022-12-29 18:48:34.791  - info: host.GLT(GLT) iobroker.js-controller version 4.0.24 js-controller starting
          2022-12-29 18:48:34.796  - info: host.GLT(GLT) Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
          2022-12-29 18:48:34.797  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.21.1
          2022-12-29 18:48:34.797  - info: host.GLT(GLT) ip addresses: 10.122.60.127 2a02:8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
          2022-12-29 18:48:37.068  - info: host.GLT(GLT) connected to Objects and States
          2022-12-29 18:48:37.174  - info: host.GLT(GLT) added notifications configuration of host
          2022-12-29 18:48:37.176  - info: host.GLT(GLT) Node.js version has changed from 14.16.0 to 14.21.1
          2022-12-29 18:48:37.218  - info: host.GLT(GLT) Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
          2022-12-29 18:48:38.008  - info: host.GLT(GLT) Delete host system.host.ioBrokerNUC
          2022-12-29 18:48:38.200  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeCurrent"
          2022-12-29 18:48:38.201  - info: host.GLT(GLT) 68 instances found
          2022-12-29 18:48:38.246  - warn: host.GLT(GLT) does not start any instances on this host
          2022-12-29 18:48:38.302  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeNewest"
          2022-12-29 18:48:38.353  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeNewestNext"
          2022-12-29 18:48:38.406  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmCurrent"
          2022-12-29 18:48:38.455  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmNewest"
          2022-12-29 18:48:38.508  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmNewestNext"
          2022-12-29 18:48:38.558  - info: host.GLT(GLT) Some obsolete host states deleted.
          
          
          HomoranH Nicht stören
          HomoranH Nicht stören
          Homoran
          Global Moderator Administrators
          schrieb am zuletzt editiert von
          #13

          @jb_sullivan sagte in Test Adapter ioBroker.backitup v2.5.x:

          terminated with code 7

          da laufen mehrere Prozesse vom admin.
          mqch mal reboot

          kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

          der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

          JB_SullivanJ 1 Antwort Letzte Antwort
          0
          • HomoranH Homoran

            @jb_sullivan sagte in Test Adapter ioBroker.backitup v2.5.x:

            terminated with code 7

            da laufen mehrere Prozesse vom admin.
            mqch mal reboot

            JB_SullivanJ Offline
            JB_SullivanJ Offline
            JB_Sullivan
            schrieb am zuletzt editiert von
            #14

            @homoran Reboot hat nichts geändert - Admin Seite ist immer noch nicht erreichbar.

            login as: sully
            sully@10.122.60.127's password:
            Linux ioBrokerNUC 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64
            
            The programs included with the Debian GNU/Linux system are free software;
            the exact distribution terms for each program are described in the
            individual files in /usr/share/doc/*/copyright.
            
            Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
            permitted by applicable law.
            Last login: Thu Dec 29 19:58:41 2022 from 10.122.60.92
            sully@ioBrokerNUC:~$ iobroker logs --watch
            2022-12-29 10:31:14.990  - warn: innogy-smarthome.0 (1020) Adapter is not connec                                          ted ... Will recheck in 30 seconds!
            2022-12-29 10:31:44.995  - warn: innogy-smarthome.0 (1020) Adapter is still not                                           connected to the Innogy API, restarting!
            2022-12-29 10:31:48.334  - info: innogy-smarthome.0 (1020) Initialization sequen                                          ce completed: found 62 devices
            2022-12-29 10:40:26.924  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 10:41:06.878  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 10:44:01.886  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.87
            2022-12-29 10:44:14.689  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.87
            2022-12-29 10:44:25.011  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 12:47:02.750  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 12:47:15.689  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.87
            2022-12-29 13:21:15.006  - warn: innogy-smarthome.0 (1020) Adapter is not connec                                          ted ... Will recheck in 30 seconds!
            2022-12-29 13:21:45.008  - warn: innogy-smarthome.0 (1020) Adapter is still not                                           connected to the Innogy API, restarting!
            2022-12-29 13:21:47.992  - info: innogy-smarthome.0 (1020) Initialization sequen                                          ce completed: found 62 devices
            2022-12-29 13:54:51.219  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 13:55:05.561  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.87
            2022-12-29 13:55:25.563  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 13:55:52.524  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.87
            2022-12-29 14:10:57.617  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 14:10:59.105  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.87
            2022-12-29 14:11:05.947  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.87 admin
            2022-12-29 14:11:15.009  - warn: innogy-smarthome.0 (1020) Adapter is not connec                                          ted ... Will recheck in 30 seconds!
            2022-12-29 14:11:45.011  - warn: innogy-smarthome.0 (1020) Adapter is still not                                           connected to the Innogy API, restarting!
            2022-12-29 14:11:47.986  - info: innogy-smarthome.0 (1020) Initialization sequen                                          ce completed: found 62 devices
            2022-12-29 15:01:15.015  - warn: innogy-smarthome.0 (1020) Adapter is not connec                                          ted ... Will recheck in 30 seconds!
            2022-12-29 15:01:45.016  - warn: innogy-smarthome.0 (1020) Adapter is still not                                           connected to the Innogy API, restarting!
            2022-12-29 15:01:47.981  - info: innogy-smarthome.0 (1020) Initialization sequen                                          ce completed: found 62 devices
            2022-12-29 18:27:29.310  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.92
            2022-12-29 18:28:47.331  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.92
            2022-12-29 18:29:26.256  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.92
            2022-12-29 18:29:30.850  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.92
            2022-12-29 18:31:06.727  - info: host.ioBrokerNUC "system.adapter.backitup.0" en                                          abled
            2022-12-29 18:31:06.768  - info: host.ioBrokerNUC instance system.adapter.backit                                          up.0 started with pid 1336
            2022-12-29 18:31:07.979  - info: backitup.0 (1336) starting. Version 2.5.9 in /o                                          pt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.2                                          4
            2022-12-29 18:31:08.067  - info: backitup.0 (1336) [iobroker] backup was activat                                          ed at 02:40 every 1 day(s)
            2022-12-29 18:31:48.051  - info: host.ioBrokerNUC stopInstance system.adapter.ba                                          ckitup.0 (force=false, process=true)
            2022-12-29 18:31:48.056  - info: backitup.0 (1336) Got terminate signal TERMINAT                                          E_YOURSELF
            2022-12-29 18:31:48.057  - info: backitup.0 (1336) cleaned everything up...
            2022-12-29 18:31:48.058  - info: backitup.0 (1336) terminating
            2022-12-29 18:31:48.059  - info: backitup.0 (1336) Terminated (ADAPTER_REQUESTED                                          _TERMINATION): Without reason
            2022-12-29 18:31:48.097  - info: host.ioBrokerNUC stopInstance system.adapter.ba                                          ckitup.0 send kill signal
            2022-12-29 18:31:48.601  - info: host.ioBrokerNUC instance system.adapter.backit                                          up.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
            2022-12-29 18:31:50.601  - info: admin.0 (467) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.92
            2022-12-29 18:31:51.011  - info: admin.0 (467) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.92
            2022-12-29 18:31:51.126  - info: host.ioBrokerNUC instance system.adapter.backit                                          up.0 started with pid 1351
            2022-12-29 18:31:52.377  - info: backitup.0 (1351) starting. Version 2.5.9 in /o                                          pt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.2                                          4
            2022-12-29 18:31:52.454  - info: backitup.0 (1351) [iobroker] backup was activat                                          ed at  every 1 day(s)
            2022-12-29 18:36:02.842  - info: proxmox.0 (646) Detected new VM/storage "VM 501                                          " - restarting instance
            2022-12-29 18:36:02.848  - warn: proxmox.0 (646) Restart initiated
            2022-12-29 18:36:02.852  - info: proxmox.0 (646) cleaned everything up...
            2022-12-29 18:36:02.876  - info: proxmox.0 (646) terminating
            2022-12-29 18:36:02.877  - info: proxmox.0 (646) Terminated (NO_ERROR): Without                                           reason
            2022-12-29 18:36:03.417  - info: host.ioBrokerNUC instance system.adapter.proxmo                                          x.0 terminated with code 0 (NO_ERROR)
            2022-12-29 18:36:03.418  - info: host.ioBrokerNUC Restart adapter system.adapter                                          .proxmox.0 because enabled
            2022-12-29 18:36:33.444  - info: host.ioBrokerNUC instance system.adapter.proxmo                                          x.0 started with pid 1380
            2022-12-29 18:36:34.950  - info: proxmox.0 (1380) starting. Version 1.3.5 in /op                                          t/iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
            2022-12-29 18:43:28.411  - info: host.ioBrokerNUC iobroker.js-controller version                                           4.0.24 js-controller starting
            2022-12-29 18:43:28.419  - info: host.ioBrokerNUC Copyright (c) 2014-2022 bluefo                                          x, 2014 hobbyquaker
            2022-12-29 18:43:28.419  - info: host.ioBrokerNUC hostname: ioBrokerNUC, node: v                                          14.21.1
            2022-12-29 18:43:28.420  - info: host.ioBrokerNUC ip addresses: 10.122.60.127 2a                                          02:8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
            2022-12-29 18:43:29.917  - info: host.ioBrokerNUC connected to Objects and State                                          s
            2022-12-29 18:43:29.936  - info: host.ioBrokerNUC added notifications configurat                                          ion of host
            2022-12-29 18:43:30.327  - info: host.ioBrokerNUC Delete state "system.host.ioBr                                          okerNUC.versions.nodeCurrent"
            2022-12-29 18:43:30.333  - info: host.ioBrokerNUC 7 instances found
            2022-12-29 18:43:30.353  - info: host.ioBrokerNUC starting 6 instances
            2022-12-29 18:43:30.409  - info: host.ioBrokerNUC Delete state "system.host.ioBr                                          okerNUC.versions.nodeNewest"
            2022-12-29 18:43:30.471  - info: host.ioBrokerNUC instance system.adapter.admin.                                          0 started with pid 466
            2022-12-29 18:43:30.482  - info: host.ioBrokerNUC Delete state "system.host.ioBr                                          okerNUC.versions.nodeNewestNext"
            2022-12-29 18:43:30.537  - info: host.ioBrokerNUC Delete state "system.host.ioBr                                          okerNUC.versions.npmCurrent"
            2022-12-29 18:43:30.587  - info: host.ioBrokerNUC Delete state "system.host.ioBr                                          okerNUC.versions.npmNewest"
            2022-12-29 18:43:30.639  - info: host.ioBrokerNUC Delete state "system.host.ioBr                                          okerNUC.versions.npmNewestNext"
            2022-12-29 18:43:30.699  - info: host.ioBrokerNUC Some obsolete host states dele                                          ted.
            2022-12-29 18:43:32.039  - error: admin.0 (466) admin.0 already running
            2022-12-29 18:43:32.041  - warn: admin.0 (466) Terminated (ADAPTER_ALREADY_RUNNI                                          NG): Without reason
            2022-12-29 18:43:32.602  - error: host.ioBrokerNUC instance system.adapter.admin                                          .0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
            2022-12-29 18:43:32.605  - info: host.ioBrokerNUC Restart adapter system.adapter                                          .admin.0 because enabled
            2022-12-29 18:43:34.384  - info: host.ioBrokerNUC instance system.adapter.innogy                                          -smarthome.0 started with pid 477
            2022-12-29 18:43:36.039  - error: innogy-smarthome.0 (477) innogy-smarthome.0 al                                          ready running
            2022-12-29 18:43:36.041  - warn: innogy-smarthome.0 (477) Terminated (ADAPTER_AL                                          READY_RUNNING): Without reason
            2022-12-29 18:43:36.578  - error: host.ioBrokerNUC instance system.adapter.innog                                          y-smarthome.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
            2022-12-29 18:43:36.579  - info: host.ioBrokerNUC Restart adapter system.adapter                                          .innogy-smarthome.0 because enabled
            2022-12-29 18:43:38.387  - info: host.ioBrokerNUC instance system.adapter.backit                                          up.0 started with pid 488
            2022-12-29 18:43:39.414  - error: backitup.0 (488) backitup.0 already running
            2022-12-29 18:43:39.417  - warn: backitup.0 (488) Terminated (ADAPTER_ALREADY_RU                                          NNING): Without reason
            2022-12-29 18:43:39.949  - error: host.ioBrokerNUC instance system.adapter.backi                                          tup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
            2022-12-29 18:43:39.949  - info: host.ioBrokerNUC Restart adapter system.adapter                                          .backitup.0 because enabled
            2022-12-29 18:43:42.390  - info: host.ioBrokerNUC instance system.adapter.info.0                                           started with pid 499
            2022-12-29 18:43:44.075  - error: info.0 (499) info.0 already running
            2022-12-29 18:43:44.077  - warn: info.0 (499) Terminated (ADAPTER_ALREADY_RUNNIN                                          G): Without reason
            2022-12-29 18:43:44.611  - error: host.ioBrokerNUC instance system.adapter.info.                                          0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
            2022-12-29 18:43:44.612  - info: host.ioBrokerNUC Restart adapter system.adapter                                          .info.0 because enabled
            2022-12-29 18:43:46.386  - info: host.ioBrokerNUC instance system.adapter.proxmo                                          x.0 started with pid 518
            2022-12-29 18:43:47.586  - error: proxmox.0 (518) proxmox.0 already running
            2022-12-29 18:43:47.589  - warn: proxmox.0 (518) Terminated (ADAPTER_ALREADY_RUN                                          NING): Without reason
            2022-12-29 18:43:48.129  - error: host.ioBrokerNUC instance system.adapter.proxm                                          ox.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
            2022-12-29 18:43:48.129  - info: host.ioBrokerNUC Restart adapter system.adapter                                          .proxmox.0 because enabled
            2022-12-29 18:43:50.385  - info: host.ioBrokerNUC instance system.adapter.device                                          -watcher.0 started with pid 529
            2022-12-29 18:43:51.458  - error: device-watcher.0 (529) device-watcher.0 alread                                          y running
            2022-12-29 18:43:51.460  - warn: device-watcher.0 (529) Terminated (ADAPTER_ALRE                                          ADY_RUNNING): Without reason
            2022-12-29 18:43:52.000  - error: host.ioBrokerNUC instance system.adapter.devic                                          e-watcher.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
            2022-12-29 18:43:52.000  - info: host.ioBrokerNUC Restart adapter system.adapter                                          .device-watcher.0 because enabled
            2022-12-29 18:44:02.628  - info: host.ioBrokerNUC instance system.adapter.admin.                                          0 started with pid 540
            2022-12-29 18:44:04.144  - info: admin.0 (540) starting. Version 6.3.5 in /opt/i                                          obroker/node_modules/iobroker.admin, node: v14.21.1, js-controller: 4.0.24
            2022-12-29 18:44:04.185  - info: admin.0 (540) requesting all states
            2022-12-29 18:44:04.186  - info: admin.0 (540) requesting all objects
            2022-12-29 18:44:05.064  - info: admin.0 (540) received all objects
            2022-12-29 18:44:05.311  - info: admin.0 (540) Request actual repository...
            2022-12-29 18:44:05.374  - info: admin.0 (540) http server listening on port 808                                          1
            2022-12-29 18:44:05.375  - info: admin.0 (540) Use link "http://localhost:8081"                                           to configure.
            2022-12-29 18:44:05.397  - info: admin.0 (540) socket.io server listening on por                                          t 8081
            2022-12-29 18:44:05.885  - info: host.ioBrokerNUC Updating repository "beta" und                                          er "http://download.iobroker.net/sources-dist-latest.json"
            2022-12-29 18:44:08.187  - info: host.ioBrokerNUC instance system.adapter.innogy                                          -smarthome.0 started with pid 563
            2022-12-29 18:44:08.412  - info: admin.0 (540) Repository received successfully.
            2022-12-29 18:44:09.985  - info: host.ioBrokerNUC instance system.adapter.backit                                          up.0 started with pid 574
            2022-12-29 18:44:10.032  - info: innogy-smarthome.0 (563) starting. Version 1.1.                                          1 in /opt/iobroker/node_modules/iobroker.innogy-smarthome, node: v14.21.1, js-co                                          ntroller: 4.0.24
            2022-12-29 18:44:10.092  - info: innogy-smarthome.0 (563) Trying to use local sm                                          arthome connection! SHC generation: 2
            2022-12-29 18:44:11.329  - info: backitup.0 (574) starting. Version 2.5.9 in /op                                          t/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
            2022-12-29 18:44:11.425  - info: backitup.0 (574) [iobroker] backup was activate                                          d at  every 1 day(s)
            2022-12-29 18:44:13.476  - info: innogy-smarthome.0 (563) Initialization sequenc                                          e completed: found 62 devices
            2022-12-29 18:44:14.641  - info: host.ioBrokerNUC instance system.adapter.info.0                                           started with pid 593
            2022-12-29 18:44:17.371  - info: info.0 (593) starting. Version 1.9.24 in /opt/i                                          obroker/node_modules/iobroker.info, node: v14.21.1, js-controller: 4.0.24
            2022-12-29 18:44:17.452  - info: info.0 (593) Reading/updating systemdata.
            2022-12-29 18:44:18.036  - info: info.0 (593) cpu Temp res = {"main":null,"cores                                          ":[],"max":null,"socket":[],"chipset":null}
            2022-12-29 18:44:18.156  - info: host.ioBrokerNUC instance system.adapter.proxmo                                          x.0 started with pid 677
            2022-12-29 18:44:19.818  - info: proxmox.0 (677) starting. Version 1.3.5 in /opt                                          /iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
            2022-12-29 18:44:22.038  - info: host.ioBrokerNUC instance system.adapter.device                                          -watcher.0 started with pid 994
            2022-12-29 18:44:23.434  - info: device-watcher.0 (994) starting. Version 2.2.1                                           in /opt/iobroker/node_modules/iobroker.device-watcher, node: v14.21.1, js-contro                                          ller: 4.0.24
            2022-12-29 18:44:23.480  - info: device-watcher.0 (994) Number of selected adapt                                          ers: 1. Loading data from: Innogy ...
            2022-12-29 18:44:24.590  - info: proxmox.0 (677) Deleted old VM/storage "qemu_VM                                           501"
            2022-12-29 18:44:39.129  - info: admin.0 (540) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.92
            2022-12-29 18:44:41.732  - info: admin.0 (540) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.92
            2022-12-29 18:44:45.976  - info: admin.0 (540) <== Disconnect system.user.admin                                           from ::ffff:10.122.60.92
            2022-12-29 18:44:57.277  - info: admin.0 (540) ==> Connected system.user.admin f                                          rom ::ffff:10.122.60.92
            2022-12-29 18:45:42.153  - info: admin.0 (540) terminating http server on port 8                                          081
            2022-12-29 18:45:42.151  - info: host.ioBrokerNUC received SIGTERM
            2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.ad                                          min.0 (force=false, process=true)
            2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.in                                          fluxdb.0 (force=false, process=false)
            2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.in                                          nogy-smarthome.0 (force=false, process=true)
            2022-12-29 18:45:42.157  - info: host.ioBrokerNUC stopInstance system.adapter.ba                                          ckitup.0 (force=false, process=true)
            2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.in                                          fo.0 (force=false, process=true)
            2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.pr                                          oxmox.0 (force=false, process=true)
            2022-12-29 18:45:42.159  - info: host.ioBrokerNUC stopInstance system.adapter.de                                          vice-watcher.0 (force=false, process=true)
            2022-12-29 18:45:42.162  - info: innogy-smarthome.0 (563) cleaned everything up.                                          ..
            2022-12-29 18:45:42.165  - info: backitup.0 (574) cleaned everything up...
            2022-12-29 18:45:42.168  - info: info.0 (593) cleaned everything up...
            2022-12-29 18:45:42.171  - info: proxmox.0 (677) cleaned everything up...
            2022-12-29 18:45:42.173  - info: device-watcher.0 (994) cleaned everything up...
            2022-12-29 18:45:42.190  - info: backitup.0 (574) Got terminate signal TERMINATE                                          _YOURSELF
            2022-12-29 18:45:42.192  - info: admin.0 (540) Got terminate signal TERMINATE_YO                                          URSELF
            2022-12-29 18:45:42.193  - info: innogy-smarthome.0 (563) Got terminate signal T                                          ERMINATE_YOURSELF
            2022-12-29 18:45:42.194  - info: info.0 (593) Got terminate signal TERMINATE_YOU                                          RSELF
            2022-12-29 18:45:42.195  - info: proxmox.0 (677) Got terminate signal TERMINATE_                                          YOURSELF
            2022-12-29 18:45:42.197  - info: device-watcher.0 (994) Got terminate signal TER                                          MINATE_YOURSELF
            2022-12-29 18:45:42.209  - info: innogy-smarthome.0 (563) Terminated (START_IMME                                          DIATELY_AFTER_STOP): Without reason
            2022-12-29 18:45:42.210  - info: admin.0 (540) Terminated (START_IMMEDIATELY_AFT                                          ER_STOP): Without reason
            2022-12-29 18:45:42.226  - info: host.ioBrokerNUC stopInstance system.adapter.ad                                          min.0 send kill signal
            2022-12-29 18:45:42.229  - info: host.ioBrokerNUC stopInstance system.adapter.in                                          nogy-smarthome.0 send kill signal
            2022-12-29 18:45:42.230  - info: host.ioBrokerNUC stopInstance system.adapter.ba                                          ckitup.0 send kill signal
            2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.in                                          fo.0 send kill signal
            2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.pr                                          oxmox.0 send kill signal
            2022-12-29 18:45:42.232  - info: host.ioBrokerNUC stopInstance system.adapter.de                                          vice-watcher.0 send kill signal
            2022-12-29 18:45:42.245  - info: info.0 (593) Terminated (START_IMMEDIATELY_AFTE                                          R_STOP): Without reason
            2022-12-29 18:45:42.245  - info: backitup.0 (574) Terminated (START_IMMEDIATELY_                                          AFTER_STOP): Without reason
            2022-12-29 18:45:42.248  - info: proxmox.0 (677) Terminated (START_IMMEDIATELY_A                                          FTER_STOP): Without reason
            2022-12-29 18:45:42.253  - info: device-watcher.0 (994) Terminated (START_IMMEDI                                          ATELY_AFTER_STOP): Without reason
            2022-12-29 18:45:42.810  - info: host.ioBrokerNUC instance system.adapter.admin.                                          0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            2022-12-29 18:45:42.811  - info: host.ioBrokerNUC instance system.adapter.innogy                                          -smarthome.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            2022-12-29 18:45:42.872  - info: host.ioBrokerNUC instance system.adapter.info.0                                           terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            2022-12-29 18:45:42.873  - info: host.ioBrokerNUC instance system.adapter.backit                                          up.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            2022-12-29 18:45:42.893  - info: host.ioBrokerNUC instance system.adapter.proxmo                                          x.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            2022-12-29 18:45:42.894  - info: host.ioBrokerNUC instance system.adapter.device                                          -watcher.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
            2022-12-29 18:45:42.894  - info: host.ioBrokerNUC All instances are stopped.
            2022-12-29 18:45:42.992  - info: host.ioBrokerNUC terminated
            2022-12-29 18:48:34.791  - info: host.GLT(GLT) iobroker.js-controller version 4.                                          0.24 js-controller starting
            2022-12-29 18:48:34.796  - info: host.GLT(GLT) Copyright (c) 2014-2022 bluefox,                                           2014 hobbyquaker
            2022-12-29 18:48:34.797  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.21.                                          1
            2022-12-29 18:48:34.797  - info: host.GLT(GLT) ip addresses: 10.122.60.127 2a02:                                          8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
            2022-12-29 18:48:37.068  - info: host.GLT(GLT) connected to Objects and States
            2022-12-29 18:48:37.174  - info: host.GLT(GLT) added notifications configuration                                           of host
            2022-12-29 18:48:37.176  - info: host.GLT(GLT) Node.js version has changed from                                           14.16.0 to 14.21.1
            2022-12-29 18:48:37.218  - info: host.GLT(GLT) Successfully updated capabilities                                           "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
            2022-12-29 18:48:38.008  - info: host.GLT(GLT) Delete host system.host.ioBrokerN                                          UC
            2022-12-29 18:48:38.200  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT                                          ).versions.nodeCurrent"
            2022-12-29 18:48:38.201  - info: host.GLT(GLT) 68 instances found
            2022-12-29 18:48:38.246  - warn: host.GLT(GLT) does not start any instances on t                                          his host
            2022-12-29 18:48:38.302  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT                                          ).versions.nodeNewest"
            2022-12-29 18:48:38.353  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT                                          ).versions.nodeNewestNext"
            2022-12-29 18:48:38.406  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT                                          ).versions.npmCurrent"
            2022-12-29 18:48:38.455  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT                                          ).versions.npmNewest"
            2022-12-29 18:48:38.508  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT                                          ).versions.npmNewestNext"
            2022-12-29 18:48:38.558  - info: host.GLT(GLT) Some obsolete host states deleted                                          .
            2022-12-29 20:17:57.398  - info: host.GLT(GLT) received SIGTERM
            2022-12-29 20:17:57.468  - info: host.GLT(GLT) terminated
            2022-12-29 20:18:21.124  - info: host.GLT(GLT) iobroker.js-controller version 4.                                          0.24 js-controller starting
            2022-12-29 20:18:21.132  - info: host.GLT(GLT) Copyright (c) 2014-2022 bluefox,                                           2014 hobbyquaker
            2022-12-29 20:18:21.133  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.21.                                          1
            2022-12-29 20:18:21.134  - info: host.GLT(GLT) ip addresses: 10.122.60.127 2a02:                                          8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
            2022-12-29 20:18:23.631  - info: host.GLT(GLT) connected to Objects and States
            2022-12-29 20:18:23.694  - info: host.GLT(GLT) added notifications configuration                                           of host
            2022-12-29 20:18:24.653  - info: host.GLT(GLT) 68 instances found
            2022-12-29 20:18:24.673  - warn: host.GLT(GLT) does not start any instances on t                                          his host
            
            

            ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

            1 Antwort Letzte Antwort
            0
            • JB_SullivanJ JB_Sullivan

              @thomas-braun

              Ok - naja wenn man mit Windows arbeitet, brauche ich viele der iobroker Kommandos nicht. Da gehe ich in die Dateistruktur und öffne die LOG Datei mit dem Texteditor.

              Hier nun das Log

              
              sully@ioBrokerNUC:~$ iobroker logs
              2022-12-29 10:31:14.990  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
              2022-12-29 10:31:44.995  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
              2022-12-29 10:31:48.334  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
              2022-12-29 10:40:26.924  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 10:41:06.878  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 10:44:01.886  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
              2022-12-29 10:44:14.689  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
              2022-12-29 10:44:25.011  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 12:47:02.750  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 12:47:15.689  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
              2022-12-29 13:21:15.006  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
              2022-12-29 13:21:45.008  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
              2022-12-29 13:21:47.992  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
              2022-12-29 13:54:51.219  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 13:55:05.561  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
              2022-12-29 13:55:25.563  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 13:55:52.524  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
              2022-12-29 14:10:57.617  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 14:10:59.105  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.87
              2022-12-29 14:11:05.947  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.87 admin
              2022-12-29 14:11:15.009  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
              2022-12-29 14:11:45.011  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
              2022-12-29 14:11:47.986  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
              2022-12-29 15:01:15.015  - warn: innogy-smarthome.0 (1020) Adapter is not connected ... Will recheck in 30 seconds!
              2022-12-29 15:01:45.016  - warn: innogy-smarthome.0 (1020) Adapter is still not connected to the Innogy API, restarting!
              2022-12-29 15:01:47.981  - info: innogy-smarthome.0 (1020) Initialization sequence completed: found 62 devices
              2022-12-29 18:27:29.310  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:28:47.331  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:29:26.256  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:29:30.850  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:31:06.727  - info: host.ioBrokerNUC "system.adapter.backitup.0" enabled
              2022-12-29 18:31:06.768  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 1336
              2022-12-29 18:31:07.979  - info: backitup.0 (1336) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:31:08.067  - info: backitup.0 (1336) [iobroker] backup was activated at 02:40 every 1 day(s)
              2022-12-29 18:31:48.051  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 (force=false, process=true)
              2022-12-29 18:31:48.056  - info: backitup.0 (1336) Got terminate signal TERMINATE_YOURSELF
              2022-12-29 18:31:48.057  - info: backitup.0 (1336) cleaned everything up...
              2022-12-29 18:31:48.058  - info: backitup.0 (1336) terminating
              2022-12-29 18:31:48.059  - info: backitup.0 (1336) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2022-12-29 18:31:48.097  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 send kill signal
              2022-12-29 18:31:48.601  - info: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2022-12-29 18:31:50.601  - info: admin.0 (467) <== Disconnect system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:31:51.011  - info: admin.0 (467) ==> Connected system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:31:51.126  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 1351
              2022-12-29 18:31:52.377  - info: backitup.0 (1351) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:31:52.454  - info: backitup.0 (1351) [iobroker] backup was activated at  every 1 day(s)
              2022-12-29 18:36:02.842  - info: proxmox.0 (646) Detected new VM/storage "VM 501" - restarting instance
              2022-12-29 18:36:02.848  - warn: proxmox.0 (646) Restart initiated
              2022-12-29 18:36:02.852  - info: proxmox.0 (646) cleaned everything up...
              2022-12-29 18:36:02.876  - info: proxmox.0 (646) terminating
              2022-12-29 18:36:02.877  - info: proxmox.0 (646) Terminated (NO_ERROR): Without reason
              2022-12-29 18:36:03.417  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 0 (NO_ERROR)
              2022-12-29 18:36:03.418  - info: host.ioBrokerNUC Restart adapter system.adapter.proxmox.0 because enabled
              2022-12-29 18:36:33.444  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 1380
              2022-12-29 18:36:34.950  - info: proxmox.0 (1380) starting. Version 1.3.5 in /opt/iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:43:28.411  - info: host.ioBrokerNUC iobroker.js-controller version 4.0.24 js-controller starting
              2022-12-29 18:43:28.419  - info: host.ioBrokerNUC Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
              2022-12-29 18:43:28.419  - info: host.ioBrokerNUC hostname: ioBrokerNUC, node: v14.21.1
              2022-12-29 18:43:28.420  - info: host.ioBrokerNUC ip addresses: 10.122.60.127 2a02:8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
              2022-12-29 18:43:29.917  - info: host.ioBrokerNUC connected to Objects and States
              2022-12-29 18:43:29.936  - info: host.ioBrokerNUC added notifications configuration of host
              2022-12-29 18:43:30.327  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeCurrent"
              2022-12-29 18:43:30.333  - info: host.ioBrokerNUC 7 instances found
              2022-12-29 18:43:30.353  - info: host.ioBrokerNUC starting 6 instances
              2022-12-29 18:43:30.409  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeNewest"
              2022-12-29 18:43:30.471  - info: host.ioBrokerNUC instance system.adapter.admin.0 started with pid 466
              2022-12-29 18:43:30.482  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.nodeNewestNext"
              2022-12-29 18:43:30.537  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmCurrent"
              2022-12-29 18:43:30.587  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmNewest"
              2022-12-29 18:43:30.639  - info: host.ioBrokerNUC Delete state "system.host.ioBrokerNUC.versions.npmNewestNext"
              2022-12-29 18:43:30.699  - info: host.ioBrokerNUC Some obsolete host states deleted.
              2022-12-29 18:43:32.039  - error: admin.0 (466) admin.0 already running
              2022-12-29 18:43:32.041  - warn: admin.0 (466) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
              2022-12-29 18:43:32.602  - error: host.ioBrokerNUC instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
              2022-12-29 18:43:32.605  - info: host.ioBrokerNUC Restart adapter system.adapter.admin.0 because enabled
              2022-12-29 18:43:34.384  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 started with pid 477
              2022-12-29 18:43:36.039  - error: innogy-smarthome.0 (477) innogy-smarthome.0 already running
              2022-12-29 18:43:36.041  - warn: innogy-smarthome.0 (477) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
              2022-12-29 18:43:36.578  - error: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
              2022-12-29 18:43:36.579  - info: host.ioBrokerNUC Restart adapter system.adapter.innogy-smarthome.0 because enabled
              2022-12-29 18:43:38.387  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 488
              2022-12-29 18:43:39.414  - error: backitup.0 (488) backitup.0 already running
              2022-12-29 18:43:39.417  - warn: backitup.0 (488) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
              2022-12-29 18:43:39.949  - error: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
              2022-12-29 18:43:39.949  - info: host.ioBrokerNUC Restart adapter system.adapter.backitup.0 because enabled
              2022-12-29 18:43:42.390  - info: host.ioBrokerNUC instance system.adapter.info.0 started with pid 499
              2022-12-29 18:43:44.075  - error: info.0 (499) info.0 already running
              2022-12-29 18:43:44.077  - warn: info.0 (499) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
              2022-12-29 18:43:44.611  - error: host.ioBrokerNUC instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
              2022-12-29 18:43:44.612  - info: host.ioBrokerNUC Restart adapter system.adapter.info.0 because enabled
              2022-12-29 18:43:46.386  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 518
              2022-12-29 18:43:47.586  - error: proxmox.0 (518) proxmox.0 already running
              2022-12-29 18:43:47.589  - warn: proxmox.0 (518) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
              2022-12-29 18:43:48.129  - error: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
              2022-12-29 18:43:48.129  - info: host.ioBrokerNUC Restart adapter system.adapter.proxmox.0 because enabled
              2022-12-29 18:43:50.385  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 started with pid 529
              2022-12-29 18:43:51.458  - error: device-watcher.0 (529) device-watcher.0 already running
              2022-12-29 18:43:51.460  - warn: device-watcher.0 (529) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
              2022-12-29 18:43:52.000  - error: host.ioBrokerNUC instance system.adapter.device-watcher.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
              2022-12-29 18:43:52.000  - info: host.ioBrokerNUC Restart adapter system.adapter.device-watcher.0 because enabled
              2022-12-29 18:44:02.628  - info: host.ioBrokerNUC instance system.adapter.admin.0 started with pid 540
              2022-12-29 18:44:04.144  - info: admin.0 (540) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:44:04.185  - info: admin.0 (540) requesting all states
              2022-12-29 18:44:04.186  - info: admin.0 (540) requesting all objects
              2022-12-29 18:44:05.064  - info: admin.0 (540) received all objects
              2022-12-29 18:44:05.311  - info: admin.0 (540) Request actual repository...
              2022-12-29 18:44:05.374  - info: admin.0 (540) http server listening on port 8081
              2022-12-29 18:44:05.375  - info: admin.0 (540) Use link "http://localhost:8081" to configure.
              2022-12-29 18:44:05.397  - info: admin.0 (540) socket.io server listening on port 8081
              2022-12-29 18:44:05.885  - info: host.ioBrokerNUC Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
              2022-12-29 18:44:08.187  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 started with pid 563
              2022-12-29 18:44:08.412  - info: admin.0 (540) Repository received successfully.
              2022-12-29 18:44:09.985  - info: host.ioBrokerNUC instance system.adapter.backitup.0 started with pid 574
              2022-12-29 18:44:10.032  - info: innogy-smarthome.0 (563) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.innogy-smarthome, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:44:10.092  - info: innogy-smarthome.0 (563) Trying to use local smarthome connection! SHC generation: 2
              2022-12-29 18:44:11.329  - info: backitup.0 (574) starting. Version 2.5.9 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:44:11.425  - info: backitup.0 (574) [iobroker] backup was activated at  every 1 day(s)
              2022-12-29 18:44:13.476  - info: innogy-smarthome.0 (563) Initialization sequence completed: found 62 devices
              2022-12-29 18:44:14.641  - info: host.ioBrokerNUC instance system.adapter.info.0 started with pid 593
              2022-12-29 18:44:17.371  - info: info.0 (593) starting. Version 1.9.24 in /opt/iobroker/node_modules/iobroker.info, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:44:17.452  - info: info.0 (593) Reading/updating systemdata.
              2022-12-29 18:44:18.036  - info: info.0 (593) cpu Temp res = {"main":null,"cores":[],"max":null,"socket":[],"chipset":null}
              2022-12-29 18:44:18.156  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 started with pid 677
              2022-12-29 18:44:19.818  - info: proxmox.0 (677) starting. Version 1.3.5 in /opt/iobroker/node_modules/iobroker.proxmox, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:44:22.038  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 started with pid 994
              2022-12-29 18:44:23.434  - info: device-watcher.0 (994) starting. Version 2.2.1 in /opt/iobroker/node_modules/iobroker.device-watcher, node: v14.21.1, js-controller: 4.0.24
              2022-12-29 18:44:23.480  - info: device-watcher.0 (994) Number of selected adapters: 1. Loading data from: Innogy ...
              2022-12-29 18:44:24.590  - info: proxmox.0 (677) Deleted old VM/storage "qemu_VM 501"
              2022-12-29 18:44:39.129  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:44:41.732  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:44:45.976  - info: admin.0 (540) <== Disconnect system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:44:57.277  - info: admin.0 (540) ==> Connected system.user.admin from ::ffff:10.122.60.92
              2022-12-29 18:45:42.153  - info: admin.0 (540) terminating http server on port 8081
              2022-12-29 18:45:42.151  - info: host.ioBrokerNUC received SIGTERM
              2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.admin.0 (force=false, process=true)
              2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.influxdb.0 (force=false, process=false)
              2022-12-29 18:45:42.156  - info: host.ioBrokerNUC stopInstance system.adapter.innogy-smarthome.0 (force=false, process=true)
              2022-12-29 18:45:42.157  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 (force=false, process=true)
              2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.info.0 (force=false, process=true)
              2022-12-29 18:45:42.158  - info: host.ioBrokerNUC stopInstance system.adapter.proxmox.0 (force=false, process=true)
              2022-12-29 18:45:42.159  - info: host.ioBrokerNUC stopInstance system.adapter.device-watcher.0 (force=false, process=true)
              2022-12-29 18:45:42.162  - info: innogy-smarthome.0 (563) cleaned everything up...
              2022-12-29 18:45:42.165  - info: backitup.0 (574) cleaned everything up...
              2022-12-29 18:45:42.168  - info: info.0 (593) cleaned everything up...
              2022-12-29 18:45:42.171  - info: proxmox.0 (677) cleaned everything up...
              2022-12-29 18:45:42.173  - info: device-watcher.0 (994) cleaned everything up...
              2022-12-29 18:45:42.190  - info: backitup.0 (574) Got terminate signal TERMINATE_YOURSELF
              2022-12-29 18:45:42.192  - info: admin.0 (540) Got terminate signal TERMINATE_YOURSELF
              2022-12-29 18:45:42.193  - info: innogy-smarthome.0 (563) Got terminate signal TERMINATE_YOURSELF
              2022-12-29 18:45:42.194  - info: info.0 (593) Got terminate signal TERMINATE_YOURSELF
              2022-12-29 18:45:42.195  - info: proxmox.0 (677) Got terminate signal TERMINATE_YOURSELF
              2022-12-29 18:45:42.197  - info: device-watcher.0 (994) Got terminate signal TERMINATE_YOURSELF
              2022-12-29 18:45:42.209  - info: innogy-smarthome.0 (563) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
              2022-12-29 18:45:42.210  - info: admin.0 (540) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
              2022-12-29 18:45:42.226  - info: host.ioBrokerNUC stopInstance system.adapter.admin.0 send kill signal
              2022-12-29 18:45:42.229  - info: host.ioBrokerNUC stopInstance system.adapter.innogy-smarthome.0 send kill signal
              2022-12-29 18:45:42.230  - info: host.ioBrokerNUC stopInstance system.adapter.backitup.0 send kill signal
              2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.info.0 send kill signal
              2022-12-29 18:45:42.231  - info: host.ioBrokerNUC stopInstance system.adapter.proxmox.0 send kill signal
              2022-12-29 18:45:42.232  - info: host.ioBrokerNUC stopInstance system.adapter.device-watcher.0 send kill signal
              2022-12-29 18:45:42.245  - info: info.0 (593) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
              2022-12-29 18:45:42.245  - info: backitup.0 (574) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
              2022-12-29 18:45:42.248  - info: proxmox.0 (677) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
              2022-12-29 18:45:42.253  - info: device-watcher.0 (994) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
              2022-12-29 18:45:42.810  - info: host.ioBrokerNUC instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
              2022-12-29 18:45:42.811  - info: host.ioBrokerNUC instance system.adapter.innogy-smarthome.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
              2022-12-29 18:45:42.872  - info: host.ioBrokerNUC instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
              2022-12-29 18:45:42.873  - info: host.ioBrokerNUC instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
              2022-12-29 18:45:42.893  - info: host.ioBrokerNUC instance system.adapter.proxmox.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
              2022-12-29 18:45:42.894  - info: host.ioBrokerNUC instance system.adapter.device-watcher.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
              2022-12-29 18:45:42.894  - info: host.ioBrokerNUC All instances are stopped.
              2022-12-29 18:45:42.992  - info: host.ioBrokerNUC terminated
              2022-12-29 18:48:34.791  - info: host.GLT(GLT) iobroker.js-controller version 4.0.24 js-controller starting
              2022-12-29 18:48:34.796  - info: host.GLT(GLT) Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
              2022-12-29 18:48:34.797  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.21.1
              2022-12-29 18:48:34.797  - info: host.GLT(GLT) ip addresses: 10.122.60.127 2a02:8108:9440:50e4:80a8:fdff:fe23:2344 fe80::80a8:fdff:fe23:2344
              2022-12-29 18:48:37.068  - info: host.GLT(GLT) connected to Objects and States
              2022-12-29 18:48:37.174  - info: host.GLT(GLT) added notifications configuration of host
              2022-12-29 18:48:37.176  - info: host.GLT(GLT) Node.js version has changed from 14.16.0 to 14.21.1
              2022-12-29 18:48:37.218  - info: host.GLT(GLT) Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
              2022-12-29 18:48:38.008  - info: host.GLT(GLT) Delete host system.host.ioBrokerNUC
              2022-12-29 18:48:38.200  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeCurrent"
              2022-12-29 18:48:38.201  - info: host.GLT(GLT) 68 instances found
              2022-12-29 18:48:38.246  - warn: host.GLT(GLT) does not start any instances on this host
              2022-12-29 18:48:38.302  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeNewest"
              2022-12-29 18:48:38.353  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.nodeNewestNext"
              2022-12-29 18:48:38.406  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmCurrent"
              2022-12-29 18:48:38.455  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmNewest"
              2022-12-29 18:48:38.508  - info: host.GLT(GLT) Delete state "system.host.GLT(GLT).versions.npmNewestNext"
              2022-12-29 18:48:38.558  - info: host.GLT(GLT) Some obsolete host states deleted.
              
              
              Thomas BraunT Online
              Thomas BraunT Online
              Thomas Braun
              Most Active
              schrieb am zuletzt editiert von
              #15

              @jb_sullivan sagte in Test Adapter ioBroker.backitup v2.5.x:

              2022-12-29 18:45:42.992  - info: host.ioBrokerNUC terminated
              2022-12-29 18:48:34.791  - info: host.GLT(GLT)
              

              Und warum ändert sich da der host?

              iobroker host this
              

              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

              JB_SullivanJ 1 Antwort Letzte Antwort
              0
              • Thomas BraunT Thomas Braun

                @jb_sullivan sagte in Test Adapter ioBroker.backitup v2.5.x:

                2022-12-29 18:45:42.992  - info: host.ioBrokerNUC terminated
                2022-12-29 18:48:34.791  - info: host.GLT(GLT)
                

                Und warum ändert sich da der host?

                iobroker host this
                
                JB_SullivanJ Offline
                JB_SullivanJ Offline
                JB_Sullivan
                schrieb am zuletzt editiert von
                #16

                @thomas-braun

                Ist das Problem evtl. das im gleichen Netzwerk laufende Produktivsystem vom welchem das Backup stammt? Sind aber zwei unterschiedliche IP Adressen und beim Produktivsystem läuft alles und ich komme dort auch auf den Admin.

                sully@ioBrokerNUC:~$ iobroker host this
                Cannot execute changes on running system. Stop iobroker first.
                sully@ioBrokerNUC:~$
                

                ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • JB_SullivanJ JB_Sullivan

                  @thomas-braun

                  Ist das Problem evtl. das im gleichen Netzwerk laufende Produktivsystem vom welchem das Backup stammt? Sind aber zwei unterschiedliche IP Adressen und beim Produktivsystem läuft alles und ich komme dort auch auf den Admin.

                  sully@ioBrokerNUC:~$ iobroker host this
                  Cannot execute changes on running system. Stop iobroker first.
                  sully@ioBrokerNUC:~$
                  
                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #17

                  @jb_sullivan

                  iob stop 
                  iobroker host this
                  iob start
                  

                  Ist das Problem evtl. das im gleichen Netzwerk laufende Produktivsystem vom welchem das Backup stammt?

                  Na klar. Hostnames müssen eindeutig sein.

                  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

                  JB_SullivanJ 1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT Thomas Braun

                    @jb_sullivan

                    iob stop 
                    iobroker host this
                    iob start
                    

                    Ist das Problem evtl. das im gleichen Netzwerk laufende Produktivsystem vom welchem das Backup stammt?

                    Na klar. Hostnames müssen eindeutig sein.

                    JB_SullivanJ Offline
                    JB_SullivanJ Offline
                    JB_Sullivan
                    schrieb am zuletzt editiert von
                    #18

                    @thomas-braun sagte in Test Adapter ioBroker.backitup v2.5.x:

                    iob stop iobroker host this iob start

                    Was passiert dann mit dem Produktivsystem, wenn ich das hier ausführe?

                    ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                    Thomas BraunT 1 Antwort Letzte Antwort
                    0
                    • JB_SullivanJ JB_Sullivan

                      @thomas-braun sagte in Test Adapter ioBroker.backitup v2.5.x:

                      iob stop iobroker host this iob start

                      Was passiert dann mit dem Produktivsystem, wenn ich das hier ausführe?

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

                      @jb_sullivan

                      Nix. Wie auch?

                      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

                      JB_SullivanJ 1 Antwort Letzte Antwort
                      0
                      • Thomas BraunT Thomas Braun

                        @jb_sullivan

                        Nix. Wie auch?

                        JB_SullivanJ Offline
                        JB_SullivanJ Offline
                        JB_Sullivan
                        schrieb am zuletzt editiert von
                        #20

                        @thomas-braun

                        OK, habe ich gemacht, mit anschließendem Reboot - nun läuft der Admin wieder und der Host wurde umbenannt.

                        Macht der Backitup Adapter keine Prüfung ob ggf. zwei gleiche Hostnamen im Netzwerk am werkeln sind? Wenn er das prüfen würde, könnte der Adapter ggf. gleich fragen, ob man dem Restore Host einen anderen Namen geben möchte - nur so für den Fall, das noch mehr Dödels so wie ich beim Restore aggieren 👀👀

                        Produktivsystem
                        afdea239-3587-47bb-bc2d-a271eb79d50c-image.png

                        Testsystem nach host this

                        410e260c-a18c-45a8-807b-ad2966600703-image.png

                        ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                        HomoranH Thomas BraunT 2 Antworten Letzte Antwort
                        0
                        • JB_SullivanJ JB_Sullivan

                          @thomas-braun

                          OK, habe ich gemacht, mit anschließendem Reboot - nun läuft der Admin wieder und der Host wurde umbenannt.

                          Macht der Backitup Adapter keine Prüfung ob ggf. zwei gleiche Hostnamen im Netzwerk am werkeln sind? Wenn er das prüfen würde, könnte der Adapter ggf. gleich fragen, ob man dem Restore Host einen anderen Namen geben möchte - nur so für den Fall, das noch mehr Dödels so wie ich beim Restore aggieren 👀👀

                          Produktivsystem
                          afdea239-3587-47bb-bc2d-a271eb79d50c-image.png

                          Testsystem nach host this

                          410e260c-a18c-45a8-807b-ad2966600703-image.png

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

                          @jb_sullivan sagte in Probleme mit admin nach restore:

                          Macht der Backitup Adapter keine Prüfung ob ggf. zwei gleiche Hostnamen im Netzwerk am werkeln sind?

                          Das Netzwerk ist dem egal.
                          Aber Backitup führt standardmäßig den iobroker host this aus um die Einstellungen und Rechte auf das neue System anzupassen.

                          Warum das bei dir nicht geklappt hat ist nicht bekannt.

                          kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                          der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                          1 Antwort Letzte Antwort
                          0
                          • JB_SullivanJ JB_Sullivan

                            @thomas-braun

                            OK, habe ich gemacht, mit anschließendem Reboot - nun läuft der Admin wieder und der Host wurde umbenannt.

                            Macht der Backitup Adapter keine Prüfung ob ggf. zwei gleiche Hostnamen im Netzwerk am werkeln sind? Wenn er das prüfen würde, könnte der Adapter ggf. gleich fragen, ob man dem Restore Host einen anderen Namen geben möchte - nur so für den Fall, das noch mehr Dödels so wie ich beim Restore aggieren 👀👀

                            Produktivsystem
                            afdea239-3587-47bb-bc2d-a271eb79d50c-image.png

                            Testsystem nach host this

                            410e260c-a18c-45a8-807b-ad2966600703-image.png

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

                            @jb_sullivan

                            Der Backitup-Adapter führt während eines Restores immer auch ein
                            iobroker host this aus, soweit ich das weiß. Hattest du den nicht verwendet?

                            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

                            JB_SullivanJ 1 Antwort Letzte Antwort
                            0
                            • Thomas BraunT Thomas Braun

                              @jb_sullivan

                              Der Backitup-Adapter führt während eines Restores immer auch ein
                              iobroker host this aus, soweit ich das weiß. Hattest du den nicht verwendet?

                              JB_SullivanJ Offline
                              JB_SullivanJ Offline
                              JB_Sullivan
                              schrieb am zuletzt editiert von
                              #23

                              @thomas-braun sagte in Probleme mit admin nach restore:

                              Hattest du den nicht verwendet?

                              Was hatte ich nicht verwendet?

                              ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                              Thomas BraunT 1 Antwort Letzte Antwort
                              0
                              • JB_SullivanJ JB_Sullivan

                                @thomas-braun sagte in Probleme mit admin nach restore:

                                Hattest du den nicht verwendet?

                                Was hatte ich nicht verwendet?

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

                                @jb_sullivan

                                Den Backitup-Adapter.

                                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

                                JB_SullivanJ 1 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @jb_sullivan

                                  Den Backitup-Adapter.

                                  JB_SullivanJ Offline
                                  JB_SullivanJ Offline
                                  JB_Sullivan
                                  schrieb am zuletzt editiert von
                                  #25

                                  @thomas-braun sagte in Probleme mit admin nach restore:

                                  Den Backitup-Adapter.

                                  Natürlich - darum habe ich ja auch im BackitUp Thread meine Frage gestellt und der Screenshot in Beitrag #1 hier im neuen Thread ist ja auch vom BackitUp Adapter.

                                  ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                                  Thomas BraunT 1 Antwort Letzte Antwort
                                  0
                                  • JB_SullivanJ JB_Sullivan

                                    @thomas-braun sagte in Probleme mit admin nach restore:

                                    Den Backitup-Adapter.

                                    Natürlich - darum habe ich ja auch im BackitUp Thread meine Frage gestellt und der Screenshot in Beitrag #1 hier im neuen Thread ist ja auch vom BackitUp Adapter.

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

                                    @jb_sullivan sagte in Probleme mit admin nach restore:

                                    Screenshot

                                    Die schau ich in der Regel nicht an. Steht meist eh nix verwertbares drin.

                                    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

                                    JB_SullivanJ 1 Antwort Letzte Antwort
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @jb_sullivan sagte in Probleme mit admin nach restore:

                                      Screenshot

                                      Die schau ich in der Regel nicht an. Steht meist eh nix verwertbares drin.

                                      JB_SullivanJ Offline
                                      JB_SullivanJ Offline
                                      JB_Sullivan
                                      schrieb am zuletzt editiert von
                                      #27

                                      @thomas-braun
                                      Das einzige was jetzt noch komisch ist, das auf dem geupdateten System nur 26 Adapter angezeigt werden, obwohl die Sicherung von einem System stammt was 67 Adapter installiert hat.

                                      Diese 67 Adapter Namen tauchen auf dem neuen System aber bei den Instanzen auf - nur eben nicht bei den Adaptern ?!?!

                                      ioBroker auf Intel Core i3-5005U NUC und Windwos10 Pro

                                      Thomas BraunT 1 Antwort Letzte Antwort
                                      0
                                      • JB_SullivanJ JB_Sullivan

                                        @thomas-braun
                                        Das einzige was jetzt noch komisch ist, das auf dem geupdateten System nur 26 Adapter angezeigt werden, obwohl die Sicherung von einem System stammt was 67 Adapter installiert hat.

                                        Diese 67 Adapter Namen tauchen auf dem neuen System aber bei den Instanzen auf - nur eben nicht bei den Adaptern ?!?!

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

                                        @jb_sullivan

                                        iobroker list adapters && iobroker list adapters | wc -l
                                        iobroker list instances
                                        

                                        Läuft das Restore vielleicht noch?
                                        Das kann ja geraume Zeit dauern.

                                        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
                                        • Thomas BraunT Thomas Braun

                                          @jb_sullivan

                                          iobroker list adapters && iobroker list adapters | wc -l
                                          iobroker list instances
                                          

                                          Läuft das Restore vielleicht noch?
                                          Das kann ja geraume Zeit dauern.

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

                                          @thomas-braun sagte in Probleme mit admin nach restore:

                                          Läuft das Restore vielleicht noch?

                                          davon gehe ich aus.
                                          Oder dieser Vorgang wurde viel zu früh gestört, was für mich auch den Fehler mit dem Hostnamen erklären könnte.

                                          kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                                          Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                          der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                          JB_SullivanJ 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
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          563

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

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

                                          • Du hast noch kein Konto? Registrieren

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