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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Slave-Installation - reassign instance falsch [SOLVED]

NEWS

  • Neues YouTube-Video: Visualisierung im Devices-Adapter
    BluefoxB
    Bluefox
    13
    1
    629

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

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

Slave-Installation - reassign instance falsch [SOLVED]

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
34 Beiträge 5 Kommentatoren 1.3k Aufrufe 4 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • Thomas BraunT Thomas Braun

    @dennis-b
    npm 8.1.4 ist zu hoch.
    Installier das für node14 vorgesehene npm6.

    Dennis.BD Offline
    Dennis.BD Offline
    Dennis.B
    schrieb am zuletzt editiert von
    #6

    @thomas-braun

    Ok alles neu aufgesetzt und npm6 gelassen.

    Leider passiert wieder genau das gleiche.

    pi.png
    pi2.png
    pi-multi.png
    pi2_multi.png
    pi_down.png

    pi1 logs

        ioBroker was installed successfully
        Open http://192.168.101.99 172.17.0.1 169.254.186.48:8081 in a browser and start configuring!
    
    ==========================================================================
    
    
    You need to re-login before doing anything else on the console!
    
    pi@pi:~ $ iobroker multihost enable
    Multihost discovery server activated on this host. If iobroker is currently not running please start befeore trying to discover this host.
    Important: Multihost discovery works with UDP packets. Make sure they are routed correctly in your network. If you use Docker you also need to configure this correctly.
    Multihost discovery will be automatically deactivated after 15 minutes. If you want to activate it permanently use the --persist flag
    Discovery authentication activated.
    Enter secret phrase for connection: 
    Repeat secret phrase for connection: 
    Changing objects server to accept connections on all IP addresses.
    Changing states server to accept connections on all IP addresses.
    Please restart ioBroker for the changes to take effect: "iobroker restart"
    
    
    Multihost discovery server: enabled
    Discovery authentication:   enabled
    Persistent activation:      disabled
    Objects:                    file on 0.0.0.0
    States:                     file on 0.0.0.0
    pi@pi:~ $ iobroker restart
    pi@pi:~ $ iobroker logs
    2021-11-24 09:37:44.729  - info: host.pi iobroker.js-controller version 3.3.19 js-controller starting
    2021-11-24 09:37:44.745  - info: host.pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
    2021-11-24 09:37:44.747  - info: host.pi hostname: pi, node: v14.18.1
    2021-11-24 09:37:44.748  - info: host.pi ip addresses: 192.168.101.99 fe80::9ca0:7208:2eb7:69f7 172.17.0.1 fe80::42:beff:fe1c:774b 169.254.186.48 fe80::94c5:3eff:fe7f:8e0d
    2021-11-24 09:37:45.118  - info: host.pi connected to Objects and States
    2021-11-24 09:37:45.269  - info: host.pi added notifications configuration of host
    2021-11-24 09:37:46.207  - info: host.pi 3 instances found
    2021-11-24 09:37:46.236  - info: host.pi starting 3 instances
    2021-11-24 09:37:46.356  - info: host.pi instance system.adapter.admin.0 started with pid 23768
    2021-11-24 09:37:50.364  - info: host.pi instance system.adapter.discovery.0 started with pid 23779
    2021-11-24 09:37:51.559  - info: admin.0 (23768) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:37:51.684  - info: admin.0 (23768) requesting all states
    2021-11-24 09:37:51.686  - info: admin.0 (23768) requesting all objects
    2021-11-24 09:37:51.912  - info: admin.0 (23768) received all objects
    2021-11-24 09:37:52.606  - info: admin.0 (23768) http server listening on port 8081
    2021-11-24 09:37:52.608  - info: admin.0 (23768) Use link "http://localhost:8081" to configure.
    2021-11-24 09:37:52.699  - info: admin.0 (23768) State value to set for "admin.0.info.lastUpdateCheck" has to be type "number" but received type "string" 
    2021-11-24 09:37:52.780  - warn: admin.0 (23768) Repository cannot be read
    2021-11-24 09:37:53.942  - info: discovery.0 (23779) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:37:54.266  - info: host.pi instance system.adapter.backitup.0 started with pid 23798
    2021-11-24 09:37:57.733  - info: backitup.0 (23798) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:37:57.867  - info: backitup.0 (23798) [iobroker] backup was activated at 02:40 every 1 day(s)
    2021-11-24 09:38:01.721  - info: host.pi Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
    2021-11-24 09:41:25.198  - info: host.pi Multi-host discovery server: service started on 0.0.0.0:50005
    2021-11-24 09:41:53.577  - info: host.pi received SIGTERM
    2021-11-24 09:41:53.575  - info: backitup.0 (23798) cleaned everything up...
    2021-11-24 09:41:53.588  - info: admin.0 (23768) terminating http server on port 8081
    2021-11-24 09:41:53.587  - info: host.pi stopInstance system.adapter.admin.0 (force=false, process=true)
    2021-11-24 09:41:53.589  - info: host.pi stopInstance system.adapter.discovery.0 (force=false, process=true)
    2021-11-24 09:41:53.590  - info: host.pi stopInstance system.adapter.backitup.0 (force=false, process=true)
    2021-11-24 09:41:53.632  - info: admin.0 (23768) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:41:53.636  - info: discovery.0 (23779) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:41:53.639  - info: backitup.0 (23798) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:41:53.649  - info: discovery.0 (23779) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:41:53.652  - info: backitup.0 (23798) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:41:53.662  - info: admin.0 (23768) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:41:53.669  - info: host.pi stopInstance system.adapter.admin.0 send kill signal
    2021-11-24 09:41:53.679  - info: host.pi stopInstance system.adapter.discovery.0 send kill signal
    2021-11-24 09:41:53.681  - info: host.pi stopInstance system.adapter.backitup.0 send kill signal
    2021-11-24 09:41:54.321  - info: host.pi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:41:54.324  - info: host.pi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:41:54.361  - info: host.pi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:41:54.362  - info: host.pi All instances are stopped.
    2021-11-24 09:41:54.434  - info: host.pi terminated
    2021-11-24 09:41:57.868  - info: host.pi iobroker.js-controller version 3.3.19 js-controller starting
    2021-11-24 09:41:57.880  - info: host.pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
    2021-11-24 09:41:57.882  - info: host.pi hostname: pi, node: v14.18.1
    2021-11-24 09:41:57.883  - info: host.pi ip addresses: 192.168.101.99 fe80::9ca0:7208:2eb7:69f7 172.17.0.1 fe80::42:beff:fe1c:774b 169.254.186.48 fe80::94c5:3eff:fe7f:8e0d
    2021-11-24 09:41:58.496  - info: host.pi connected to Objects and States
    2021-11-24 09:41:58.551  - info: host.pi added notifications configuration of host
    2021-11-24 09:41:59.274  - info: host.pi Multi-host discovery server: service started on 0.0.0.0:50005
    2021-11-24 09:41:59.313  - info: host.pi 3 instances found
    2021-11-24 09:41:59.342  - info: host.pi starting 3 instances
    2021-11-24 09:41:59.448  - info: host.pi instance system.adapter.admin.0 started with pid 23890
    2021-11-24 09:42:03.406  - info: host.pi instance system.adapter.discovery.0 started with pid 23902
    2021-11-24 09:42:04.852  - info: admin.0 (23890) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:42:04.965  - info: admin.0 (23890) requesting all states
    2021-11-24 09:42:04.967  - info: admin.0 (23890) requesting all objects
    2021-11-24 09:42:05.702  - info: admin.0 (23890) received all objects
    2021-11-24 09:42:06.302  - info: admin.0 (23890) http server listening on port 8081
    2021-11-24 09:42:06.303  - info: admin.0 (23890) Use link "http://localhost:8081" to configure.
    2021-11-24 09:42:07.391  - info: host.pi instance system.adapter.backitup.0 started with pid 23917
    2021-11-24 09:42:07.404  - info: discovery.0 (23902) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:42:11.202  - info: backitup.0 (23917) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:42:11.335  - info: backitup.0 (23917) [iobroker] backup was activated at 02:40 every 1 day(s)
    2021-11-24 09:43:26.187  - info: host.pi stopInstance system.adapter.admin.0 (force=false, process=true)
    2021-11-24 09:43:26.210  - info: admin.0 (23890) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:43:26.216  - info: admin.0 (23890) terminating http server on port 8081
    2021-11-24 09:43:26.218  - info: admin.0 (23890) terminating
    2021-11-24 09:43:26.222  - info: admin.0 (23890) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2021-11-24 09:43:26.232  - info: host.pi stopInstance system.adapter.admin.0 send kill signal
    2021-11-24 09:43:26.289  - info: host.pi stopInstance system.adapter.discovery.0 (force=false, process=true)
    2021-11-24 09:43:26.308  - info: discovery.0 (23902) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:43:26.314  - info: discovery.0 (23902) terminating
    2021-11-24 09:43:26.321  - info: discovery.0 (23902) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2021-11-24 09:43:26.357  - info: host.pi stopInstance system.adapter.backitup.0 (force=false, process=true)
    2021-11-24 09:43:26.367  - info: host.pi stopInstance system.adapter.discovery.0 send kill signal
    2021-11-24 09:43:26.385  - info: backitup.0 (23917) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:43:26.389  - info: host.pi stopInstance system.adapter.backitup.0 send kill signal
    2021-11-24 09:43:26.389  - info: backitup.0 (23917) cleaned everything up...
    2021-11-24 09:43:26.392  - info: backitup.0 (23917) terminating
    2021-11-24 09:43:26.397  - info: backitup.0 (23917) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    2021-11-24 09:43:26.840  - error: host.pi instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
    2021-11-24 09:43:26.842  - info: host.pi Do not restart adapter system.adapter.admin.0 because desired by instance
    2021-11-24 09:43:26.943  - error: host.pi instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
    2021-11-24 09:43:26.944  - info: host.pi Do not restart adapter system.adapter.discovery.0 because desired by instance
    2021-11-24 09:43:27.012  - error: host.pi instance system.adapter.backitup.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
    2021-11-24 09:43:27.014  - info: host.pi Do not restart adapter system.adapter.backitup.0 because desired by instance
    

    pi2 logs

    pi@rp-surveillance:~ $ iobroker multihost connect
    1 |      192.168.101.99 |  host |      192.168.101.99 | "authentication required"
    Please select host [1]: 1
    Enter secret phrase for connection: ***********
    
    Config ok. Please restart ioBroker: "iobroker restart"
    pi@rp-surveillance:~ $ iobroker restart
    pi@rp-surveillance:~ $ iobroker logs
    2021-11-24 09:35:26.074  - info: host.rp-survaillance iobroker.js-controller version 3.3.19 js-controller starting
    2021-11-24 09:35:26.085  - info: host.rp-survaillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
    2021-11-24 09:35:26.086  - info: host.rp-survaillance hostname: rp-survaillance, node: v14.18.1
    2021-11-24 09:35:26.086  - info: host.rp-survaillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7 172.17.0.1 fe80::42:6cff:feb5:dee0 169.254.17.77 fe80::94a3:ecff:fe48:98f9 169.254.212.103 fe80::bd7c:7396:e9d7:5bdd 169.254.233.85 fe80::a889:ee1:f988:9fda 169.254.220.121 fe80::103f:92ff:fedb:c25b 169.254.6.58 fe80::7144:b9be:46bf:ad97
    2021-11-24 09:35:26.439  - info: host.rp-survaillance connected to Objects and States
    2021-11-24 09:35:26.544  - info: host.rp-survaillance added notifications configuration of host
    2021-11-24 09:35:27.254  - info: host.rp-survaillance 3 instances found
    2021-11-24 09:35:27.285  - info: host.rp-survaillance starting 3 instances
    2021-11-24 09:35:27.388  - info: host.rp-survaillance instance system.adapter.admin.0 started with pid 19235
    2021-11-24 09:35:30.879  - info: admin.0 (19235) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:35:30.947  - info: admin.0 (19235) requesting all states
    2021-11-24 09:35:30.949  - info: admin.0 (19235) requesting all objects
    2021-11-24 09:35:31.135  - info: admin.0 (19235) received all objects
    2021-11-24 09:35:31.342  - info: host.rp-survaillance instance system.adapter.discovery.0 started with pid 19251
    2021-11-24 09:35:31.466  - info: admin.0 (19235) http server listening on port 8081
    2021-11-24 09:35:31.467  - info: admin.0 (19235) Use link "http://localhost:8081" to configure.
    2021-11-24 09:35:31.712  - info: admin.0 (19235) State value to set for "admin.0.info.lastUpdateCheck" has to be type "number" but received type "string" 
    2021-11-24 09:35:31.724  - warn: admin.0 (19235) Repository cannot be read
    2021-11-24 09:35:32.870  - info: host.rp-survaillance Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
    2021-11-24 09:35:36.289  - info: discovery.0 (19251) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:35:36.396  - info: host.rp-survaillance instance system.adapter.backitup.0 started with pid 19264
    2021-11-24 09:35:40.315  - info: backitup.0 (19264) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:35:40.473  - info: backitup.0 (19264) [iobroker] backup was activated at 02:40 every 1 day(s)
    2021-11-24 09:37:54.196  - info: host.rp-survaillance received SIGTERM
    2021-11-24 09:37:54.204  - info: backitup.0 (19264) cleaned everything up...
    2021-11-24 09:37:54.225  - info: host.rp-survaillance stopInstance system.adapter.admin.0 (force=false, process=true)
    2021-11-24 09:37:54.226  - info: host.rp-survaillance stopInstance system.adapter.discovery.0 (force=false, process=true)
    2021-11-24 09:37:54.227  - info: host.rp-survaillance stopInstance system.adapter.backitup.0 (force=false, process=true)
    2021-11-24 09:37:54.217  - info: admin.0 (19235) terminating http server on port 8081
    2021-11-24 09:37:54.359  - info: discovery.0 (19251) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:37:54.378  - info: backitup.0 (19264) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:37:54.372  - info: discovery.0 (19251) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:37:54.387  - info: host.rp-survaillance stopInstance system.adapter.admin.0 send kill signal
    2021-11-24 09:37:54.400  - info: host.rp-survaillance stopInstance system.adapter.discovery.0 send kill signal
    2021-11-24 09:37:54.402  - info: host.rp-survaillance stopInstance system.adapter.backitup.0 send kill signal
    2021-11-24 09:37:54.428  - info: admin.0 (19235) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:37:54.413  - info: backitup.0 (19264) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:37:54.495  - info: admin.0 (19235) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:37:54.991  - info: host.rp-survaillance instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:37:55.042  - info: host.rp-survaillance instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:37:55.123  - info: host.rp-survaillance instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:37:55.127  - info: host.rp-survaillance All instances are stopped.
    2021-11-24 09:37:55.257  - info: host.rp-survaillance terminated
    2021-11-24 09:38:34.396  - info: host.rp-surveillance iobroker.js-controller version 3.3.19 js-controller starting
    2021-11-24 09:38:34.408  - info: host.rp-surveillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
    2021-11-24 09:38:34.410  - info: host.rp-surveillance hostname: rp-surveillance, node: v14.18.1
    2021-11-24 09:38:34.411  - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7
    2021-11-24 09:38:34.864  - info: host.rp-surveillance connected to Objects and States
    2021-11-24 09:38:34.985  - info: host.rp-surveillance added notifications configuration of host
    2021-11-24 09:38:35.476  - info: host.rp-surveillance Reassign instance admin.0 from rp-survaillance to rp-surveillance
    2021-11-24 09:38:35.499  - info: host.rp-surveillance Reassign instance discovery.0 from rp-survaillance to rp-surveillance
    2021-11-24 09:38:35.601  - info: host.rp-surveillance Reassign instance backitup.0 from rp-survaillance to rp-surveillance
    2021-11-24 09:38:35.645  - info: host.rp-surveillance Delete host system.host.rp-survaillance
    2021-11-24 09:38:35.669  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.notifications.system"
    2021-11-24 09:38:35.680  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.plugins.sentry.enabled"
    2021-11-24 09:38:35.694  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.compactModeEnabled"
    2021-11-24 09:38:35.707  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.compactgroupProcesses"
    2021-11-24 09:38:35.729  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.instancesAsProcess"
    2021-11-24 09:38:35.746  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.instancesAsCompact"
    2021-11-24 09:38:35.755  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.cpu"
    2021-11-24 09:38:35.769  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.cputime"
    2021-11-24 09:38:35.784  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.mem"
    2021-11-24 09:38:35.795  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memHeapUsed"
    2021-11-24 09:38:35.813  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memAvailable"
    2021-11-24 09:38:35.822  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memHeapTotal"
    2021-11-24 09:38:35.830  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memRss"
    2021-11-24 09:38:35.837  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.uptime"
    2021-11-24 09:38:35.856  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.load"
    2021-11-24 09:38:35.865  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.alive"
    2021-11-24 09:38:35.877  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.freemem"
    2021-11-24 09:38:35.886  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.inputCount"
    2021-11-24 09:38:35.907  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.outputCount"
    2021-11-24 09:38:35.916  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.eventLoopLag"
    2021-11-24 09:38:35.929  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.logLevel"
    2021-11-24 09:38:35.943  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.diskSize"
    2021-11-24 09:38:35.953  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.diskFree"
    2021-11-24 09:38:35.961  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.diskWarning"
    2021-11-24 09:38:35.997  - info: host.rp-surveillance 3 instances found
    2021-11-24 09:38:36.012  - info: host.rp-surveillance starting 3 instances
    2021-11-24 09:38:36.095  - info: host.rp-surveillance instance system.adapter.admin.0 started with pid 928
    2021-11-24 09:38:40.442  - info: host.rp-surveillance instance system.adapter.discovery.0 started with pid 1664
    2021-11-24 09:38:41.497  - info: admin.0 (928) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:38:41.662  - info: admin.0 (928) requesting all states
    2021-11-24 09:38:41.683  - info: admin.0 (928) requesting all objects
    2021-11-24 09:38:42.357  - info: admin.0 (928) received all objects
    2021-11-24 09:39:06.544  - info: admin.0 (928) http server listening on port 8081
    2021-11-24 09:39:06.544  - info: admin.0 (928) Use link "http://localhost:8081" to configure.
    2021-11-24 09:39:07.161  - info: discovery.0 (1664) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:39:07.464  - info: host.rp-surveillance instance system.adapter.backitup.0 started with pid 1725
    2021-11-24 09:39:09.659  - info: backitup.0 (1725) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:39:09.733  - info: backitup.0 (1725) [iobroker] backup was activated at 02:40 every 1 day(s)
    2021-11-24 09:43:22.110  - info: backitup.0 (1725) cleaned everything up...
    2021-11-24 09:43:22.111  - info: admin.0 (928) terminating http server on port 8081
    2021-11-24 09:43:22.111  - info: host.rp-surveillance received SIGTERM
    2021-11-24 09:43:22.123  - info: host.rp-surveillance stopInstance system.adapter.admin.0 (force=false, process=true)
    2021-11-24 09:43:22.124  - info: host.rp-surveillance stopInstance system.adapter.discovery.0 (force=false, process=true)
    2021-11-24 09:43:22.125  - info: host.rp-surveillance stopInstance system.adapter.backitup.0 (force=false, process=true)
    2021-11-24 09:43:22.145  - info: admin.0 (928) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:43:22.147  - info: discovery.0 (1664) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:43:22.152  - info: backitup.0 (1725) Got terminate signal TERMINATE_YOURSELF
    2021-11-24 09:43:22.156  - info: discovery.0 (1664) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:43:22.162  - info: backitup.0 (1725) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:43:22.179  - info: host.rp-surveillance stopInstance system.adapter.admin.0 send kill signal
    2021-11-24 09:43:22.181  - info: admin.0 (928) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2021-11-24 09:43:22.190  - info: host.rp-surveillance stopInstance system.adapter.discovery.0 send kill signal
    2021-11-24 09:43:22.192  - info: host.rp-surveillance stopInstance system.adapter.backitup.0 send kill signal
    2021-11-24 09:43:22.751  - info: host.rp-surveillance instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:43:22.752  - info: host.rp-surveillance instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:43:22.795  - info: host.rp-surveillance instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
    2021-11-24 09:43:22.796  - info: host.rp-surveillance All instances are stopped.
    2021-11-24 09:43:22.969  - info: host.rp-surveillance terminated
    2021-11-24 09:43:25.401  - info: host.rp-surveillance iobroker.js-controller version 3.3.19 js-controller starting
    2021-11-24 09:43:25.408  - info: host.rp-surveillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
    2021-11-24 09:43:25.410  - info: host.rp-surveillance hostname: rp-surveillance, node: v14.18.1
    2021-11-24 09:43:25.410  - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7 172.17.0.1 fe80::42:46ff:fea6:f5de 169.254.148.77 fe80::4f0:aeff:fe74:35d1 169.254.156.19 fe80::666e:6e01:d771:ea1d 169.254.204.15 fe80::c0e3:1fff:fe5f:d8c9 169.254.243.197 fe80::14c1:43ff:fece:39ea 169.254.157.190 fe80::f87c:c7aa:db66:c818
    2021-11-24 09:43:25.601  - info: host.rp-surveillance connected to Objects and States
    2021-11-24 09:43:25.696  - info: host.rp-surveillance added notifications configuration of host
    2021-11-24 09:43:26.135  - info: host.rp-surveillance Reassign instance admin.0 from pi to rp-surveillance
    2021-11-24 09:43:26.208  - info: host.rp-surveillance Reassign instance discovery.0 from pi to rp-surveillance
    2021-11-24 09:43:26.301  - info: host.rp-surveillance Reassign instance backitup.0 from pi to rp-surveillance
    2021-11-24 09:43:26.370  - info: host.rp-surveillance Delete host system.host.pi
    2021-11-24 09:43:26.414  - info: host.rp-surveillance Delete state "system.host.pi.notifications.system"
    2021-11-24 09:43:26.489  - info: host.rp-surveillance Delete state "system.host.pi.plugins.sentry.enabled"
    2021-11-24 09:43:26.514  - info: host.rp-surveillance Delete state "system.host.pi.compactModeEnabled"
    2021-11-24 09:43:26.547  - info: host.rp-surveillance Delete state "system.host.pi.compactgroupProcesses"
    2021-11-24 09:43:26.567  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsProcess"
    2021-11-24 09:43:26.636  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsCompact"
    2021-11-24 09:43:26.662  - info: host.rp-surveillance Delete state "system.host.pi.cpu"
    2021-11-24 09:43:26.725  - info: host.rp-surveillance Delete state "system.host.pi.cputime"
    2021-11-24 09:43:26.770  - info: host.rp-surveillance Delete state "system.host.pi.mem"
    2021-11-24 09:43:26.868  - info: host.rp-surveillance Delete state "system.host.pi.memHeapUsed"
    2021-11-24 09:43:26.892  - info: host.rp-surveillance Delete state "system.host.pi.memAvailable"
    2021-11-24 09:43:26.934  - info: host.rp-surveillance Delete state "system.host.pi.memHeapTotal"
    2021-11-24 09:43:27.032  - info: host.rp-surveillance Delete state "system.host.pi.memRss"
    2021-11-24 09:43:27.052  - info: host.rp-surveillance Delete state "system.host.pi.uptime"
    2021-11-24 09:43:27.076  - info: host.rp-surveillance Delete state "system.host.pi.load"
    2021-11-24 09:43:27.093  - info: host.rp-surveillance Delete state "system.host.pi.alive"
    2021-11-24 09:43:27.109  - info: host.rp-surveillance Delete state "system.host.pi.freemem"
    2021-11-24 09:43:27.125  - info: host.rp-surveillance Delete state "system.host.pi.inputCount"
    2021-11-24 09:43:27.186  - info: host.rp-surveillance Delete state "system.host.pi.outputCount"
    2021-11-24 09:43:27.203  - info: host.rp-surveillance Delete state "system.host.pi.eventLoopLag"
    2021-11-24 09:43:27.219  - info: host.rp-surveillance Delete state "system.host.pi.logLevel"
    2021-11-24 09:43:27.285  - info: host.rp-surveillance Delete state "system.host.pi.diskSize"
    2021-11-24 09:43:27.304  - info: host.rp-surveillance Delete state "system.host.pi.diskFree"
    2021-11-24 09:43:27.321  - info: host.rp-surveillance Delete state "system.host.pi.diskWarning"
    2021-11-24 09:43:27.422  - info: host.rp-surveillance 3 instances found
    2021-11-24 09:43:27.437  - info: host.rp-surveillance starting 3 instances
    2021-11-24 09:43:27.527  - info: host.rp-surveillance instance system.adapter.admin.0 started with pid 2201
    2021-11-24 09:43:30.850  - info: admin.0 (2201) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:43:31.004  - info: admin.0 (2201) requesting all states
    2021-11-24 09:43:31.005  - info: admin.0 (2201) requesting all objects
    2021-11-24 09:43:31.541  - info: host.rp-surveillance instance system.adapter.discovery.0 started with pid 2216
    2021-11-24 09:43:31.764  - info: admin.0 (2201) received all objects
    2021-11-24 09:43:32.185  - info: admin.0 (2201) http server listening on port 8081
    2021-11-24 09:43:32.186  - info: admin.0 (2201) Use link "http://localhost:8081" to configure.
    2021-11-24 09:43:34.106  - info: discovery.0 (2216) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:43:35.472  - info: host.rp-surveillance instance system.adapter.backitup.0 started with pid 2231
    2021-11-24 09:43:38.176  - info: backitup.0 (2231) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
    2021-11-24 09:43:38.263  - info: backitup.0 (2231) [iobroker] backup was activated at 02:40 every 1 day(s)
    
    HomoranH 1 Antwort Letzte Antwort
    0
    • Dennis.BD Dennis.B

      @thomas-braun

      Ok alles neu aufgesetzt und npm6 gelassen.

      Leider passiert wieder genau das gleiche.

      pi.png
      pi2.png
      pi-multi.png
      pi2_multi.png
      pi_down.png

      pi1 logs

          ioBroker was installed successfully
          Open http://192.168.101.99 172.17.0.1 169.254.186.48:8081 in a browser and start configuring!
      
      ==========================================================================
      
      
      You need to re-login before doing anything else on the console!
      
      pi@pi:~ $ iobroker multihost enable
      Multihost discovery server activated on this host. If iobroker is currently not running please start befeore trying to discover this host.
      Important: Multihost discovery works with UDP packets. Make sure they are routed correctly in your network. If you use Docker you also need to configure this correctly.
      Multihost discovery will be automatically deactivated after 15 minutes. If you want to activate it permanently use the --persist flag
      Discovery authentication activated.
      Enter secret phrase for connection: 
      Repeat secret phrase for connection: 
      Changing objects server to accept connections on all IP addresses.
      Changing states server to accept connections on all IP addresses.
      Please restart ioBroker for the changes to take effect: "iobroker restart"
      
      
      Multihost discovery server: enabled
      Discovery authentication:   enabled
      Persistent activation:      disabled
      Objects:                    file on 0.0.0.0
      States:                     file on 0.0.0.0
      pi@pi:~ $ iobroker restart
      pi@pi:~ $ iobroker logs
      2021-11-24 09:37:44.729  - info: host.pi iobroker.js-controller version 3.3.19 js-controller starting
      2021-11-24 09:37:44.745  - info: host.pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
      2021-11-24 09:37:44.747  - info: host.pi hostname: pi, node: v14.18.1
      2021-11-24 09:37:44.748  - info: host.pi ip addresses: 192.168.101.99 fe80::9ca0:7208:2eb7:69f7 172.17.0.1 fe80::42:beff:fe1c:774b 169.254.186.48 fe80::94c5:3eff:fe7f:8e0d
      2021-11-24 09:37:45.118  - info: host.pi connected to Objects and States
      2021-11-24 09:37:45.269  - info: host.pi added notifications configuration of host
      2021-11-24 09:37:46.207  - info: host.pi 3 instances found
      2021-11-24 09:37:46.236  - info: host.pi starting 3 instances
      2021-11-24 09:37:46.356  - info: host.pi instance system.adapter.admin.0 started with pid 23768
      2021-11-24 09:37:50.364  - info: host.pi instance system.adapter.discovery.0 started with pid 23779
      2021-11-24 09:37:51.559  - info: admin.0 (23768) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:37:51.684  - info: admin.0 (23768) requesting all states
      2021-11-24 09:37:51.686  - info: admin.0 (23768) requesting all objects
      2021-11-24 09:37:51.912  - info: admin.0 (23768) received all objects
      2021-11-24 09:37:52.606  - info: admin.0 (23768) http server listening on port 8081
      2021-11-24 09:37:52.608  - info: admin.0 (23768) Use link "http://localhost:8081" to configure.
      2021-11-24 09:37:52.699  - info: admin.0 (23768) State value to set for "admin.0.info.lastUpdateCheck" has to be type "number" but received type "string" 
      2021-11-24 09:37:52.780  - warn: admin.0 (23768) Repository cannot be read
      2021-11-24 09:37:53.942  - info: discovery.0 (23779) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:37:54.266  - info: host.pi instance system.adapter.backitup.0 started with pid 23798
      2021-11-24 09:37:57.733  - info: backitup.0 (23798) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:37:57.867  - info: backitup.0 (23798) [iobroker] backup was activated at 02:40 every 1 day(s)
      2021-11-24 09:38:01.721  - info: host.pi Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
      2021-11-24 09:41:25.198  - info: host.pi Multi-host discovery server: service started on 0.0.0.0:50005
      2021-11-24 09:41:53.577  - info: host.pi received SIGTERM
      2021-11-24 09:41:53.575  - info: backitup.0 (23798) cleaned everything up...
      2021-11-24 09:41:53.588  - info: admin.0 (23768) terminating http server on port 8081
      2021-11-24 09:41:53.587  - info: host.pi stopInstance system.adapter.admin.0 (force=false, process=true)
      2021-11-24 09:41:53.589  - info: host.pi stopInstance system.adapter.discovery.0 (force=false, process=true)
      2021-11-24 09:41:53.590  - info: host.pi stopInstance system.adapter.backitup.0 (force=false, process=true)
      2021-11-24 09:41:53.632  - info: admin.0 (23768) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:41:53.636  - info: discovery.0 (23779) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:41:53.639  - info: backitup.0 (23798) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:41:53.649  - info: discovery.0 (23779) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:41:53.652  - info: backitup.0 (23798) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:41:53.662  - info: admin.0 (23768) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:41:53.669  - info: host.pi stopInstance system.adapter.admin.0 send kill signal
      2021-11-24 09:41:53.679  - info: host.pi stopInstance system.adapter.discovery.0 send kill signal
      2021-11-24 09:41:53.681  - info: host.pi stopInstance system.adapter.backitup.0 send kill signal
      2021-11-24 09:41:54.321  - info: host.pi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:41:54.324  - info: host.pi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:41:54.361  - info: host.pi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:41:54.362  - info: host.pi All instances are stopped.
      2021-11-24 09:41:54.434  - info: host.pi terminated
      2021-11-24 09:41:57.868  - info: host.pi iobroker.js-controller version 3.3.19 js-controller starting
      2021-11-24 09:41:57.880  - info: host.pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
      2021-11-24 09:41:57.882  - info: host.pi hostname: pi, node: v14.18.1
      2021-11-24 09:41:57.883  - info: host.pi ip addresses: 192.168.101.99 fe80::9ca0:7208:2eb7:69f7 172.17.0.1 fe80::42:beff:fe1c:774b 169.254.186.48 fe80::94c5:3eff:fe7f:8e0d
      2021-11-24 09:41:58.496  - info: host.pi connected to Objects and States
      2021-11-24 09:41:58.551  - info: host.pi added notifications configuration of host
      2021-11-24 09:41:59.274  - info: host.pi Multi-host discovery server: service started on 0.0.0.0:50005
      2021-11-24 09:41:59.313  - info: host.pi 3 instances found
      2021-11-24 09:41:59.342  - info: host.pi starting 3 instances
      2021-11-24 09:41:59.448  - info: host.pi instance system.adapter.admin.0 started with pid 23890
      2021-11-24 09:42:03.406  - info: host.pi instance system.adapter.discovery.0 started with pid 23902
      2021-11-24 09:42:04.852  - info: admin.0 (23890) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:42:04.965  - info: admin.0 (23890) requesting all states
      2021-11-24 09:42:04.967  - info: admin.0 (23890) requesting all objects
      2021-11-24 09:42:05.702  - info: admin.0 (23890) received all objects
      2021-11-24 09:42:06.302  - info: admin.0 (23890) http server listening on port 8081
      2021-11-24 09:42:06.303  - info: admin.0 (23890) Use link "http://localhost:8081" to configure.
      2021-11-24 09:42:07.391  - info: host.pi instance system.adapter.backitup.0 started with pid 23917
      2021-11-24 09:42:07.404  - info: discovery.0 (23902) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:42:11.202  - info: backitup.0 (23917) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:42:11.335  - info: backitup.0 (23917) [iobroker] backup was activated at 02:40 every 1 day(s)
      2021-11-24 09:43:26.187  - info: host.pi stopInstance system.adapter.admin.0 (force=false, process=true)
      2021-11-24 09:43:26.210  - info: admin.0 (23890) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:43:26.216  - info: admin.0 (23890) terminating http server on port 8081
      2021-11-24 09:43:26.218  - info: admin.0 (23890) terminating
      2021-11-24 09:43:26.222  - info: admin.0 (23890) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2021-11-24 09:43:26.232  - info: host.pi stopInstance system.adapter.admin.0 send kill signal
      2021-11-24 09:43:26.289  - info: host.pi stopInstance system.adapter.discovery.0 (force=false, process=true)
      2021-11-24 09:43:26.308  - info: discovery.0 (23902) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:43:26.314  - info: discovery.0 (23902) terminating
      2021-11-24 09:43:26.321  - info: discovery.0 (23902) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2021-11-24 09:43:26.357  - info: host.pi stopInstance system.adapter.backitup.0 (force=false, process=true)
      2021-11-24 09:43:26.367  - info: host.pi stopInstance system.adapter.discovery.0 send kill signal
      2021-11-24 09:43:26.385  - info: backitup.0 (23917) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:43:26.389  - info: host.pi stopInstance system.adapter.backitup.0 send kill signal
      2021-11-24 09:43:26.389  - info: backitup.0 (23917) cleaned everything up...
      2021-11-24 09:43:26.392  - info: backitup.0 (23917) terminating
      2021-11-24 09:43:26.397  - info: backitup.0 (23917) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2021-11-24 09:43:26.840  - error: host.pi instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
      2021-11-24 09:43:26.842  - info: host.pi Do not restart adapter system.adapter.admin.0 because desired by instance
      2021-11-24 09:43:26.943  - error: host.pi instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
      2021-11-24 09:43:26.944  - info: host.pi Do not restart adapter system.adapter.discovery.0 because desired by instance
      2021-11-24 09:43:27.012  - error: host.pi instance system.adapter.backitup.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
      2021-11-24 09:43:27.014  - info: host.pi Do not restart adapter system.adapter.backitup.0 because desired by instance
      

      pi2 logs

      pi@rp-surveillance:~ $ iobroker multihost connect
      1 |      192.168.101.99 |  host |      192.168.101.99 | "authentication required"
      Please select host [1]: 1
      Enter secret phrase for connection: ***********
      
      Config ok. Please restart ioBroker: "iobroker restart"
      pi@rp-surveillance:~ $ iobroker restart
      pi@rp-surveillance:~ $ iobroker logs
      2021-11-24 09:35:26.074  - info: host.rp-survaillance iobroker.js-controller version 3.3.19 js-controller starting
      2021-11-24 09:35:26.085  - info: host.rp-survaillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
      2021-11-24 09:35:26.086  - info: host.rp-survaillance hostname: rp-survaillance, node: v14.18.1
      2021-11-24 09:35:26.086  - info: host.rp-survaillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7 172.17.0.1 fe80::42:6cff:feb5:dee0 169.254.17.77 fe80::94a3:ecff:fe48:98f9 169.254.212.103 fe80::bd7c:7396:e9d7:5bdd 169.254.233.85 fe80::a889:ee1:f988:9fda 169.254.220.121 fe80::103f:92ff:fedb:c25b 169.254.6.58 fe80::7144:b9be:46bf:ad97
      2021-11-24 09:35:26.439  - info: host.rp-survaillance connected to Objects and States
      2021-11-24 09:35:26.544  - info: host.rp-survaillance added notifications configuration of host
      2021-11-24 09:35:27.254  - info: host.rp-survaillance 3 instances found
      2021-11-24 09:35:27.285  - info: host.rp-survaillance starting 3 instances
      2021-11-24 09:35:27.388  - info: host.rp-survaillance instance system.adapter.admin.0 started with pid 19235
      2021-11-24 09:35:30.879  - info: admin.0 (19235) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:35:30.947  - info: admin.0 (19235) requesting all states
      2021-11-24 09:35:30.949  - info: admin.0 (19235) requesting all objects
      2021-11-24 09:35:31.135  - info: admin.0 (19235) received all objects
      2021-11-24 09:35:31.342  - info: host.rp-survaillance instance system.adapter.discovery.0 started with pid 19251
      2021-11-24 09:35:31.466  - info: admin.0 (19235) http server listening on port 8081
      2021-11-24 09:35:31.467  - info: admin.0 (19235) Use link "http://localhost:8081" to configure.
      2021-11-24 09:35:31.712  - info: admin.0 (19235) State value to set for "admin.0.info.lastUpdateCheck" has to be type "number" but received type "string" 
      2021-11-24 09:35:31.724  - warn: admin.0 (19235) Repository cannot be read
      2021-11-24 09:35:32.870  - info: host.rp-survaillance Updating repository "default" under "http://download.iobroker.net/sources-dist.json"
      2021-11-24 09:35:36.289  - info: discovery.0 (19251) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:35:36.396  - info: host.rp-survaillance instance system.adapter.backitup.0 started with pid 19264
      2021-11-24 09:35:40.315  - info: backitup.0 (19264) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:35:40.473  - info: backitup.0 (19264) [iobroker] backup was activated at 02:40 every 1 day(s)
      2021-11-24 09:37:54.196  - info: host.rp-survaillance received SIGTERM
      2021-11-24 09:37:54.204  - info: backitup.0 (19264) cleaned everything up...
      2021-11-24 09:37:54.225  - info: host.rp-survaillance stopInstance system.adapter.admin.0 (force=false, process=true)
      2021-11-24 09:37:54.226  - info: host.rp-survaillance stopInstance system.adapter.discovery.0 (force=false, process=true)
      2021-11-24 09:37:54.227  - info: host.rp-survaillance stopInstance system.adapter.backitup.0 (force=false, process=true)
      2021-11-24 09:37:54.217  - info: admin.0 (19235) terminating http server on port 8081
      2021-11-24 09:37:54.359  - info: discovery.0 (19251) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:37:54.378  - info: backitup.0 (19264) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:37:54.372  - info: discovery.0 (19251) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:37:54.387  - info: host.rp-survaillance stopInstance system.adapter.admin.0 send kill signal
      2021-11-24 09:37:54.400  - info: host.rp-survaillance stopInstance system.adapter.discovery.0 send kill signal
      2021-11-24 09:37:54.402  - info: host.rp-survaillance stopInstance system.adapter.backitup.0 send kill signal
      2021-11-24 09:37:54.428  - info: admin.0 (19235) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:37:54.413  - info: backitup.0 (19264) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:37:54.495  - info: admin.0 (19235) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:37:54.991  - info: host.rp-survaillance instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:37:55.042  - info: host.rp-survaillance instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:37:55.123  - info: host.rp-survaillance instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:37:55.127  - info: host.rp-survaillance All instances are stopped.
      2021-11-24 09:37:55.257  - info: host.rp-survaillance terminated
      2021-11-24 09:38:34.396  - info: host.rp-surveillance iobroker.js-controller version 3.3.19 js-controller starting
      2021-11-24 09:38:34.408  - info: host.rp-surveillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
      2021-11-24 09:38:34.410  - info: host.rp-surveillance hostname: rp-surveillance, node: v14.18.1
      2021-11-24 09:38:34.411  - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7
      2021-11-24 09:38:34.864  - info: host.rp-surveillance connected to Objects and States
      2021-11-24 09:38:34.985  - info: host.rp-surveillance added notifications configuration of host
      2021-11-24 09:38:35.476  - info: host.rp-surveillance Reassign instance admin.0 from rp-survaillance to rp-surveillance
      2021-11-24 09:38:35.499  - info: host.rp-surveillance Reassign instance discovery.0 from rp-survaillance to rp-surveillance
      2021-11-24 09:38:35.601  - info: host.rp-surveillance Reassign instance backitup.0 from rp-survaillance to rp-surveillance
      2021-11-24 09:38:35.645  - info: host.rp-surveillance Delete host system.host.rp-survaillance
      2021-11-24 09:38:35.669  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.notifications.system"
      2021-11-24 09:38:35.680  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.plugins.sentry.enabled"
      2021-11-24 09:38:35.694  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.compactModeEnabled"
      2021-11-24 09:38:35.707  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.compactgroupProcesses"
      2021-11-24 09:38:35.729  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.instancesAsProcess"
      2021-11-24 09:38:35.746  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.instancesAsCompact"
      2021-11-24 09:38:35.755  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.cpu"
      2021-11-24 09:38:35.769  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.cputime"
      2021-11-24 09:38:35.784  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.mem"
      2021-11-24 09:38:35.795  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memHeapUsed"
      2021-11-24 09:38:35.813  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memAvailable"
      2021-11-24 09:38:35.822  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memHeapTotal"
      2021-11-24 09:38:35.830  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.memRss"
      2021-11-24 09:38:35.837  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.uptime"
      2021-11-24 09:38:35.856  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.load"
      2021-11-24 09:38:35.865  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.alive"
      2021-11-24 09:38:35.877  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.freemem"
      2021-11-24 09:38:35.886  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.inputCount"
      2021-11-24 09:38:35.907  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.outputCount"
      2021-11-24 09:38:35.916  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.eventLoopLag"
      2021-11-24 09:38:35.929  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.logLevel"
      2021-11-24 09:38:35.943  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.diskSize"
      2021-11-24 09:38:35.953  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.diskFree"
      2021-11-24 09:38:35.961  - info: host.rp-surveillance Delete state "system.host.rp-survaillance.diskWarning"
      2021-11-24 09:38:35.997  - info: host.rp-surveillance 3 instances found
      2021-11-24 09:38:36.012  - info: host.rp-surveillance starting 3 instances
      2021-11-24 09:38:36.095  - info: host.rp-surveillance instance system.adapter.admin.0 started with pid 928
      2021-11-24 09:38:40.442  - info: host.rp-surveillance instance system.adapter.discovery.0 started with pid 1664
      2021-11-24 09:38:41.497  - info: admin.0 (928) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:38:41.662  - info: admin.0 (928) requesting all states
      2021-11-24 09:38:41.683  - info: admin.0 (928) requesting all objects
      2021-11-24 09:38:42.357  - info: admin.0 (928) received all objects
      2021-11-24 09:39:06.544  - info: admin.0 (928) http server listening on port 8081
      2021-11-24 09:39:06.544  - info: admin.0 (928) Use link "http://localhost:8081" to configure.
      2021-11-24 09:39:07.161  - info: discovery.0 (1664) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:39:07.464  - info: host.rp-surveillance instance system.adapter.backitup.0 started with pid 1725
      2021-11-24 09:39:09.659  - info: backitup.0 (1725) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:39:09.733  - info: backitup.0 (1725) [iobroker] backup was activated at 02:40 every 1 day(s)
      2021-11-24 09:43:22.110  - info: backitup.0 (1725) cleaned everything up...
      2021-11-24 09:43:22.111  - info: admin.0 (928) terminating http server on port 8081
      2021-11-24 09:43:22.111  - info: host.rp-surveillance received SIGTERM
      2021-11-24 09:43:22.123  - info: host.rp-surveillance stopInstance system.adapter.admin.0 (force=false, process=true)
      2021-11-24 09:43:22.124  - info: host.rp-surveillance stopInstance system.adapter.discovery.0 (force=false, process=true)
      2021-11-24 09:43:22.125  - info: host.rp-surveillance stopInstance system.adapter.backitup.0 (force=false, process=true)
      2021-11-24 09:43:22.145  - info: admin.0 (928) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:43:22.147  - info: discovery.0 (1664) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:43:22.152  - info: backitup.0 (1725) Got terminate signal TERMINATE_YOURSELF
      2021-11-24 09:43:22.156  - info: discovery.0 (1664) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:43:22.162  - info: backitup.0 (1725) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:43:22.179  - info: host.rp-surveillance stopInstance system.adapter.admin.0 send kill signal
      2021-11-24 09:43:22.181  - info: admin.0 (928) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-11-24 09:43:22.190  - info: host.rp-surveillance stopInstance system.adapter.discovery.0 send kill signal
      2021-11-24 09:43:22.192  - info: host.rp-surveillance stopInstance system.adapter.backitup.0 send kill signal
      2021-11-24 09:43:22.751  - info: host.rp-surveillance instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:43:22.752  - info: host.rp-surveillance instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:43:22.795  - info: host.rp-surveillance instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
      2021-11-24 09:43:22.796  - info: host.rp-surveillance All instances are stopped.
      2021-11-24 09:43:22.969  - info: host.rp-surveillance terminated
      2021-11-24 09:43:25.401  - info: host.rp-surveillance iobroker.js-controller version 3.3.19 js-controller starting
      2021-11-24 09:43:25.408  - info: host.rp-surveillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
      2021-11-24 09:43:25.410  - info: host.rp-surveillance hostname: rp-surveillance, node: v14.18.1
      2021-11-24 09:43:25.410  - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7 172.17.0.1 fe80::42:46ff:fea6:f5de 169.254.148.77 fe80::4f0:aeff:fe74:35d1 169.254.156.19 fe80::666e:6e01:d771:ea1d 169.254.204.15 fe80::c0e3:1fff:fe5f:d8c9 169.254.243.197 fe80::14c1:43ff:fece:39ea 169.254.157.190 fe80::f87c:c7aa:db66:c818
      2021-11-24 09:43:25.601  - info: host.rp-surveillance connected to Objects and States
      2021-11-24 09:43:25.696  - info: host.rp-surveillance added notifications configuration of host
      2021-11-24 09:43:26.135  - info: host.rp-surveillance Reassign instance admin.0 from pi to rp-surveillance
      2021-11-24 09:43:26.208  - info: host.rp-surveillance Reassign instance discovery.0 from pi to rp-surveillance
      2021-11-24 09:43:26.301  - info: host.rp-surveillance Reassign instance backitup.0 from pi to rp-surveillance
      2021-11-24 09:43:26.370  - info: host.rp-surveillance Delete host system.host.pi
      2021-11-24 09:43:26.414  - info: host.rp-surveillance Delete state "system.host.pi.notifications.system"
      2021-11-24 09:43:26.489  - info: host.rp-surveillance Delete state "system.host.pi.plugins.sentry.enabled"
      2021-11-24 09:43:26.514  - info: host.rp-surveillance Delete state "system.host.pi.compactModeEnabled"
      2021-11-24 09:43:26.547  - info: host.rp-surveillance Delete state "system.host.pi.compactgroupProcesses"
      2021-11-24 09:43:26.567  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsProcess"
      2021-11-24 09:43:26.636  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsCompact"
      2021-11-24 09:43:26.662  - info: host.rp-surveillance Delete state "system.host.pi.cpu"
      2021-11-24 09:43:26.725  - info: host.rp-surveillance Delete state "system.host.pi.cputime"
      2021-11-24 09:43:26.770  - info: host.rp-surveillance Delete state "system.host.pi.mem"
      2021-11-24 09:43:26.868  - info: host.rp-surveillance Delete state "system.host.pi.memHeapUsed"
      2021-11-24 09:43:26.892  - info: host.rp-surveillance Delete state "system.host.pi.memAvailable"
      2021-11-24 09:43:26.934  - info: host.rp-surveillance Delete state "system.host.pi.memHeapTotal"
      2021-11-24 09:43:27.032  - info: host.rp-surveillance Delete state "system.host.pi.memRss"
      2021-11-24 09:43:27.052  - info: host.rp-surveillance Delete state "system.host.pi.uptime"
      2021-11-24 09:43:27.076  - info: host.rp-surveillance Delete state "system.host.pi.load"
      2021-11-24 09:43:27.093  - info: host.rp-surveillance Delete state "system.host.pi.alive"
      2021-11-24 09:43:27.109  - info: host.rp-surveillance Delete state "system.host.pi.freemem"
      2021-11-24 09:43:27.125  - info: host.rp-surveillance Delete state "system.host.pi.inputCount"
      2021-11-24 09:43:27.186  - info: host.rp-surveillance Delete state "system.host.pi.outputCount"
      2021-11-24 09:43:27.203  - info: host.rp-surveillance Delete state "system.host.pi.eventLoopLag"
      2021-11-24 09:43:27.219  - info: host.rp-surveillance Delete state "system.host.pi.logLevel"
      2021-11-24 09:43:27.285  - info: host.rp-surveillance Delete state "system.host.pi.diskSize"
      2021-11-24 09:43:27.304  - info: host.rp-surveillance Delete state "system.host.pi.diskFree"
      2021-11-24 09:43:27.321  - info: host.rp-surveillance Delete state "system.host.pi.diskWarning"
      2021-11-24 09:43:27.422  - info: host.rp-surveillance 3 instances found
      2021-11-24 09:43:27.437  - info: host.rp-surveillance starting 3 instances
      2021-11-24 09:43:27.527  - info: host.rp-surveillance instance system.adapter.admin.0 started with pid 2201
      2021-11-24 09:43:30.850  - info: admin.0 (2201) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:43:31.004  - info: admin.0 (2201) requesting all states
      2021-11-24 09:43:31.005  - info: admin.0 (2201) requesting all objects
      2021-11-24 09:43:31.541  - info: host.rp-surveillance instance system.adapter.discovery.0 started with pid 2216
      2021-11-24 09:43:31.764  - info: admin.0 (2201) received all objects
      2021-11-24 09:43:32.185  - info: admin.0 (2201) http server listening on port 8081
      2021-11-24 09:43:32.186  - info: admin.0 (2201) Use link "http://localhost:8081" to configure.
      2021-11-24 09:43:34.106  - info: discovery.0 (2216) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:43:35.472  - info: host.rp-surveillance instance system.adapter.backitup.0 started with pid 2231
      2021-11-24 09:43:38.176  - info: backitup.0 (2231) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
      2021-11-24 09:43:38.263  - info: backitup.0 (2231) [iobroker] backup was activated at 02:40 every 1 day(s)
      
      HomoranH Nicht stören
      HomoranH Nicht stören
      Homoran
      Global Moderator Administrators
      schrieb am zuletzt editiert von
      #7

      @dennis-b sagte in Slave-Installation - reassign instance falsch:

      You need to re-login before doing anything else on the console!

      did you do that?

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

      Dennis.BD 1 Antwort Letzte Antwort
      0
      • HomoranH Homoran

        @dennis-b sagte in Slave-Installation - reassign instance falsch:

        You need to re-login before doing anything else on the console!

        did you do that?

        Dennis.BD Offline
        Dennis.BD Offline
        Dennis.B
        schrieb am zuletzt editiert von
        #8

        @homoran yea i have tried that before but it does not really do anything if you do re-login.... I only grabbed 2 new pi's because i have the same issue with my debian server and that the server might have an issue but it might be something else here.

        HomoranH 1 Antwort Letzte Antwort
        0
        • Dennis.BD Dennis.B

          @homoran yea i have tried that before but it does not really do anything if you do re-login.... I only grabbed 2 new pi's because i have the same issue with my debian server and that the server might have an issue but it might be something else here.

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

          @dennis-b OK - dann bitte manuell konfigurieren über iobroker setup custom (kein enable oder discover nutzen)
          Anschließende Neustarts der beiden Hosts

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

          Dennis.BD 1 Antwort Letzte Antwort
          0
          • HomoranH Homoran

            @dennis-b OK - dann bitte manuell konfigurieren über iobroker setup custom (kein enable oder discover nutzen)
            Anschließende Neustarts der beiden Hosts

            Dennis.BD Offline
            Dennis.BD Offline
            Dennis.B
            schrieb am zuletzt editiert von
            #10

            @homoran

            pi@pi:~ $ iobroker setup custom
            Current configuration:
            - Objects database:
              - Type: file
              - Host/Unix Socket: 0.0.0.0
              - Port: 9001
            - States database:
              - Type: file
              - Host/Unix Socket: 0.0.0.0
              - Port: 9000
            - Data Directory: ../../iobroker-data/
            
            Type of objects DB [(f)ile, (r)edis, ...], default [file]: file
            Host / Unix Socket of objects DB(file), default[0.0.0.0]: 0.0.0.0
            Port of objects DB(file), default[9001]: 9001
            Type of states DB [(f)file, (r)edis, ...], default [file]: file
            Host / Unix Socket of states DB (file), default[0.0.0.0]: 0.0.0.0
            Port of states DB (file), default[9000]: 9000
            Data directory (file), default[../../iobroker-data/]: 
            Host name of this machine [pi]: pi
            updating conf/iobroker.json
            pi@pi:~ $ sudo reboot now
            Connection to pi closed by remote host.
            Connection to pi closed.
            
            pi@rp-surveillance:~ $ iobroker setup custom
            Current configuration:
            - Objects database:
              - Type: file
              - Host/Unix Socket: 192.168.101.99
              - Port: 9001
            - States database:
              - Type: file
              - Host/Unix Socket: 192.168.101.99
              - Port: 9000
            - Data Directory: ../../iobroker-data/
            
            Type of objects DB [(f)ile, (r)edis, ...], default [file]: file
            Host / Unix Socket of objects DB(file), default[192.168.101.99]: 192.168.101.99
            Port of objects DB(file), default[9001]: 9001
            Type of states DB [(f)file, (r)edis, ...], default [file]: file
            Host / Unix Socket of states DB (file), default[192.168.101.99]: 192.168.101.99
            Port of states DB (file), default[9000]: 9000
            Host name of this machine [rp-surveillance]: rp-surveillance
            updating conf/iobroker.json
            pi@rp-surveillance:~ $ sudo reboot now
            Connection to rp-surveillance closed by remote host.
            Connection to rp-surveillance closed.
            

            nach neustart beider hosts geht es leider immer noch nicht.

            pi1

            2021-11-24 10:08:37.364  - info: host.pi iobroker.js-controller version 3.3.19 js-controller starting
            2021-11-24 10:08:37.381  - info: host.pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
            2021-11-24 10:08:37.383  - info: host.pi hostname: pi, node: v14.18.1
            2021-11-24 10:08:37.385  - info: host.pi ip addresses: fe80::9ca0:7208:2eb7:69f7
            2021-11-24 10:08:38.466  - info: host.pi connected to Objects and States
            2021-11-24 10:08:38.538  - info: host.pi added notifications configuration of host
            2021-11-24 10:08:41.434  - info: host.pi 3 instances found
            2021-11-24 10:08:41.462  - info: host.pi starting 3 instances
            2021-11-24 10:08:41.601  - info: host.pi instance system.adapter.admin.0 started with pid 956
            2021-11-24 10:08:45.573  - info: host.pi instance system.adapter.discovery.0 started with pid 1014
            2021-11-24 10:08:49.559  - info: host.pi instance system.adapter.backitup.0 started with pid 1075
            2021-11-24 10:08:49.922  - info: discovery.0 (1014) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
            2021-11-24 10:09:02.964  - info: admin.0 (956) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
            2021-11-24 10:09:03.131  - info: admin.0 (956) requesting all states
            2021-11-24 10:09:03.136  - info: admin.0 (956) requesting all objects
            2021-11-24 10:09:04.510  - info: admin.0 (956) received all objects
            2021-11-24 10:09:05.848  - info: admin.0 (956) http server listening on port 8081
            2021-11-24 10:09:05.863  - info: admin.0 (956) Use link "http://localhost:8081" to configure.
            2021-11-24 10:09:07.848  - info: backitup.0 (1075) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
            2021-11-24 10:09:08.046  - info: backitup.0 (1075) [iobroker] backup was activated at 02:40 every 1 day(s)
            2021-11-24 10:10:11.726  - info: host.pi stopInstance system.adapter.admin.0 (force=false, process=true)
            2021-11-24 10:10:11.765  - info: admin.0 (956) Got terminate signal TERMINATE_YOURSELF
            2021-11-24 10:10:11.769  - info: admin.0 (956) terminating http server on port 8081
            2021-11-24 10:10:11.772  - info: admin.0 (956) terminating
            2021-11-24 10:10:11.775  - info: admin.0 (956) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
            2021-11-24 10:10:11.800  - info: host.pi stopInstance system.adapter.admin.0 send kill signal
            2021-11-24 10:10:11.812  - info: host.pi stopInstance system.adapter.discovery.0 (force=false, process=true)
            2021-11-24 10:10:11.835  - info: discovery.0 (1014) Got terminate signal TERMINATE_YOURSELF
            2021-11-24 10:10:11.839  - info: discovery.0 (1014) terminating
            2021-11-24 10:10:11.842  - info: discovery.0 (1014) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
            2021-11-24 10:10:11.886  - info: host.pi stopInstance system.adapter.backitup.0 (force=false, process=true)
            2021-11-24 10:10:11.894  - info: host.pi stopInstance system.adapter.discovery.0 send kill signal
            2021-11-24 10:10:11.903  - info: backitup.0 (1075) Got terminate signal TERMINATE_YOURSELF
            2021-11-24 10:10:11.907  - info: host.pi stopInstance system.adapter.backitup.0 send kill signal
            2021-11-24 10:10:11.907  - info: backitup.0 (1075) cleaned everything up...
            2021-11-24 10:10:11.909  - info: backitup.0 (1075) terminating
            2021-11-24 10:10:11.912  - info: backitup.0 (1075) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
            2021-11-24 10:10:12.369  - error: host.pi instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
            2021-11-24 10:10:12.370  - info: host.pi Do not restart adapter system.adapter.admin.0 because desired by instance
            2021-11-24 10:10:12.440  - error: host.pi instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
            2021-11-24 10:10:12.442  - info: host.pi Do not restart adapter system.adapter.discovery.0 because desired by instance
            2021-11-24 10:10:12.508  - error: host.pi instance system.adapter.backitup.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
            2021-11-24 10:10:12.509  - info: host.pi Do not restart adapter system.adapter.backitup.0 because desired by instance
            

            pi2

            2021-11-24 10:09:54.486  - info: host.rp-surveillance iobroker.js-controller version 3.3.19 js-controller starting
            2021-11-24 10:09:54.495  - info: host.rp-surveillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
            2021-11-24 10:09:54.496  - info: host.rp-surveillance hostname: rp-surveillance, node: v14.18.1
            2021-11-24 10:09:54.497  - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7
            2021-11-24 10:09:54.794  - info: host.rp-surveillance connected to Objects and States
            2021-11-24 10:09:54.891  - info: host.rp-surveillance added notifications configuration of host
            2021-11-24 10:09:55.528  - info: host.rp-surveillance Reassign instance admin.0 from pi to rp-surveillance
            2021-11-24 10:09:55.616  - info: host.rp-surveillance Reassign instance discovery.0 from pi to rp-surveillance
            2021-11-24 10:09:55.695  - info: host.rp-surveillance Reassign instance backitup.0 from pi to rp-surveillance
            2021-11-24 10:09:55.762  - info: host.rp-surveillance Delete host system.host.pi
            2021-11-24 10:09:55.803  - info: host.rp-surveillance Delete state "system.host.pi.notifications.system"
            2021-11-24 10:09:55.826  - info: host.rp-surveillance Delete state "system.host.pi.plugins.sentry.enabled"
            2021-11-24 10:09:55.892  - info: host.rp-surveillance Delete state "system.host.pi.compactModeEnabled"
            2021-11-24 10:09:55.912  - info: host.rp-surveillance Delete state "system.host.pi.compactgroupProcesses"
            2021-11-24 10:09:55.931  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsProcess"
            2021-11-24 10:09:55.954  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsCompact"
            2021-11-24 10:09:56.025  - info: host.rp-surveillance Delete state "system.host.pi.cpu"
            2021-11-24 10:09:56.047  - info: host.rp-surveillance Delete state "system.host.pi.cputime"
            2021-11-24 10:09:56.114  - info: host.rp-surveillance Delete state "system.host.pi.mem"
            2021-11-24 10:09:56.143  - info: host.rp-surveillance Delete state "system.host.pi.memHeapUsed"
            2021-11-24 10:09:56.179  - info: host.rp-surveillance Delete state "system.host.pi.memAvailable"
            2021-11-24 10:09:56.264  - info: host.rp-surveillance Delete state "system.host.pi.memHeapTotal"
            2021-11-24 10:09:56.306  - info: host.rp-surveillance Delete state "system.host.pi.memRss"
            2021-11-24 10:09:56.384  - info: host.rp-surveillance Delete state "system.host.pi.uptime"
            2021-11-24 10:09:56.404  - info: host.rp-surveillance Delete state "system.host.pi.load"
            2021-11-24 10:09:56.419  - info: host.rp-surveillance Delete state "system.host.pi.alive"
            2021-11-24 10:09:56.481  - info: host.rp-surveillance Delete state "system.host.pi.freemem"
            2021-11-24 10:09:56.496  - info: host.rp-surveillance Delete state "system.host.pi.inputCount"
            2021-11-24 10:09:56.511  - info: host.rp-surveillance Delete state "system.host.pi.outputCount"
            2021-11-24 10:09:56.526  - info: host.rp-surveillance Delete state "system.host.pi.eventLoopLag"
            2021-11-24 10:09:56.543  - info: host.rp-surveillance Delete state "system.host.pi.logLevel"
            2021-11-24 10:09:56.601  - info: host.rp-surveillance Delete state "system.host.pi.diskSize"
            2021-11-24 10:09:56.620  - info: host.rp-surveillance Delete state "system.host.pi.diskFree"
            2021-11-24 10:09:56.637  - info: host.rp-surveillance Delete state "system.host.pi.diskWarning"
            2021-11-24 10:09:56.686  - info: host.rp-surveillance 3 instances found
            2021-11-24 10:09:56.706  - info: host.rp-surveillance starting 3 instances
            2021-11-24 10:09:56.824  - info: host.rp-surveillance instance system.adapter.admin.0 started with pid 1111
            2021-11-24 10:10:00.815  - info: host.rp-surveillance instance system.adapter.discovery.0 started with pid 1693
            2021-11-24 10:10:01.942  - info: admin.0 (1111) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
            2021-11-24 10:10:02.138  - info: admin.0 (1111) requesting all states
            2021-11-24 10:10:02.139  - info: admin.0 (1111) requesting all objects
            2021-11-24 10:10:02.835  - info: admin.0 (1111) received all objects
            2021-11-24 10:10:03.350  - info: admin.0 (1111) http server listening on port 8081
            2021-11-24 10:10:03.351  - info: admin.0 (1111) Use link "http://localhost:8081" to configure.
            2021-11-24 10:10:19.816  - info: discovery.0 (1693) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
            2021-11-24 10:10:20.874  - info: host.rp-surveillance instance system.adapter.backitup.0 started with pid 1762
            2021-11-24 10:10:23.378  - info: backitup.0 (1762) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
            2021-11-24 10:10:23.485  - info: backitup.0 (1762) [iobroker] backup was activated at 02:40 every 1 day(s)
            
            HomoranH Thomas BraunT 2 Antworten Letzte Antwort
            0
            • Dennis.BD Dennis.B

              @homoran

              pi@pi:~ $ iobroker setup custom
              Current configuration:
              - Objects database:
                - Type: file
                - Host/Unix Socket: 0.0.0.0
                - Port: 9001
              - States database:
                - Type: file
                - Host/Unix Socket: 0.0.0.0
                - Port: 9000
              - Data Directory: ../../iobroker-data/
              
              Type of objects DB [(f)ile, (r)edis, ...], default [file]: file
              Host / Unix Socket of objects DB(file), default[0.0.0.0]: 0.0.0.0
              Port of objects DB(file), default[9001]: 9001
              Type of states DB [(f)file, (r)edis, ...], default [file]: file
              Host / Unix Socket of states DB (file), default[0.0.0.0]: 0.0.0.0
              Port of states DB (file), default[9000]: 9000
              Data directory (file), default[../../iobroker-data/]: 
              Host name of this machine [pi]: pi
              updating conf/iobroker.json
              pi@pi:~ $ sudo reboot now
              Connection to pi closed by remote host.
              Connection to pi closed.
              
              pi@rp-surveillance:~ $ iobroker setup custom
              Current configuration:
              - Objects database:
                - Type: file
                - Host/Unix Socket: 192.168.101.99
                - Port: 9001
              - States database:
                - Type: file
                - Host/Unix Socket: 192.168.101.99
                - Port: 9000
              - Data Directory: ../../iobroker-data/
              
              Type of objects DB [(f)ile, (r)edis, ...], default [file]: file
              Host / Unix Socket of objects DB(file), default[192.168.101.99]: 192.168.101.99
              Port of objects DB(file), default[9001]: 9001
              Type of states DB [(f)file, (r)edis, ...], default [file]: file
              Host / Unix Socket of states DB (file), default[192.168.101.99]: 192.168.101.99
              Port of states DB (file), default[9000]: 9000
              Host name of this machine [rp-surveillance]: rp-surveillance
              updating conf/iobroker.json
              pi@rp-surveillance:~ $ sudo reboot now
              Connection to rp-surveillance closed by remote host.
              Connection to rp-surveillance closed.
              

              nach neustart beider hosts geht es leider immer noch nicht.

              pi1

              2021-11-24 10:08:37.364  - info: host.pi iobroker.js-controller version 3.3.19 js-controller starting
              2021-11-24 10:08:37.381  - info: host.pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
              2021-11-24 10:08:37.383  - info: host.pi hostname: pi, node: v14.18.1
              2021-11-24 10:08:37.385  - info: host.pi ip addresses: fe80::9ca0:7208:2eb7:69f7
              2021-11-24 10:08:38.466  - info: host.pi connected to Objects and States
              2021-11-24 10:08:38.538  - info: host.pi added notifications configuration of host
              2021-11-24 10:08:41.434  - info: host.pi 3 instances found
              2021-11-24 10:08:41.462  - info: host.pi starting 3 instances
              2021-11-24 10:08:41.601  - info: host.pi instance system.adapter.admin.0 started with pid 956
              2021-11-24 10:08:45.573  - info: host.pi instance system.adapter.discovery.0 started with pid 1014
              2021-11-24 10:08:49.559  - info: host.pi instance system.adapter.backitup.0 started with pid 1075
              2021-11-24 10:08:49.922  - info: discovery.0 (1014) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
              2021-11-24 10:09:02.964  - info: admin.0 (956) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
              2021-11-24 10:09:03.131  - info: admin.0 (956) requesting all states
              2021-11-24 10:09:03.136  - info: admin.0 (956) requesting all objects
              2021-11-24 10:09:04.510  - info: admin.0 (956) received all objects
              2021-11-24 10:09:05.848  - info: admin.0 (956) http server listening on port 8081
              2021-11-24 10:09:05.863  - info: admin.0 (956) Use link "http://localhost:8081" to configure.
              2021-11-24 10:09:07.848  - info: backitup.0 (1075) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
              2021-11-24 10:09:08.046  - info: backitup.0 (1075) [iobroker] backup was activated at 02:40 every 1 day(s)
              2021-11-24 10:10:11.726  - info: host.pi stopInstance system.adapter.admin.0 (force=false, process=true)
              2021-11-24 10:10:11.765  - info: admin.0 (956) Got terminate signal TERMINATE_YOURSELF
              2021-11-24 10:10:11.769  - info: admin.0 (956) terminating http server on port 8081
              2021-11-24 10:10:11.772  - info: admin.0 (956) terminating
              2021-11-24 10:10:11.775  - info: admin.0 (956) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2021-11-24 10:10:11.800  - info: host.pi stopInstance system.adapter.admin.0 send kill signal
              2021-11-24 10:10:11.812  - info: host.pi stopInstance system.adapter.discovery.0 (force=false, process=true)
              2021-11-24 10:10:11.835  - info: discovery.0 (1014) Got terminate signal TERMINATE_YOURSELF
              2021-11-24 10:10:11.839  - info: discovery.0 (1014) terminating
              2021-11-24 10:10:11.842  - info: discovery.0 (1014) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2021-11-24 10:10:11.886  - info: host.pi stopInstance system.adapter.backitup.0 (force=false, process=true)
              2021-11-24 10:10:11.894  - info: host.pi stopInstance system.adapter.discovery.0 send kill signal
              2021-11-24 10:10:11.903  - info: backitup.0 (1075) Got terminate signal TERMINATE_YOURSELF
              2021-11-24 10:10:11.907  - info: host.pi stopInstance system.adapter.backitup.0 send kill signal
              2021-11-24 10:10:11.907  - info: backitup.0 (1075) cleaned everything up...
              2021-11-24 10:10:11.909  - info: backitup.0 (1075) terminating
              2021-11-24 10:10:11.912  - info: backitup.0 (1075) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2021-11-24 10:10:12.369  - error: host.pi instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
              2021-11-24 10:10:12.370  - info: host.pi Do not restart adapter system.adapter.admin.0 because desired by instance
              2021-11-24 10:10:12.440  - error: host.pi instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
              2021-11-24 10:10:12.442  - info: host.pi Do not restart adapter system.adapter.discovery.0 because desired by instance
              2021-11-24 10:10:12.508  - error: host.pi instance system.adapter.backitup.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
              2021-11-24 10:10:12.509  - info: host.pi Do not restart adapter system.adapter.backitup.0 because desired by instance
              

              pi2

              2021-11-24 10:09:54.486  - info: host.rp-surveillance iobroker.js-controller version 3.3.19 js-controller starting
              2021-11-24 10:09:54.495  - info: host.rp-surveillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
              2021-11-24 10:09:54.496  - info: host.rp-surveillance hostname: rp-surveillance, node: v14.18.1
              2021-11-24 10:09:54.497  - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7
              2021-11-24 10:09:54.794  - info: host.rp-surveillance connected to Objects and States
              2021-11-24 10:09:54.891  - info: host.rp-surveillance added notifications configuration of host
              2021-11-24 10:09:55.528  - info: host.rp-surveillance Reassign instance admin.0 from pi to rp-surveillance
              2021-11-24 10:09:55.616  - info: host.rp-surveillance Reassign instance discovery.0 from pi to rp-surveillance
              2021-11-24 10:09:55.695  - info: host.rp-surveillance Reassign instance backitup.0 from pi to rp-surveillance
              2021-11-24 10:09:55.762  - info: host.rp-surveillance Delete host system.host.pi
              2021-11-24 10:09:55.803  - info: host.rp-surveillance Delete state "system.host.pi.notifications.system"
              2021-11-24 10:09:55.826  - info: host.rp-surveillance Delete state "system.host.pi.plugins.sentry.enabled"
              2021-11-24 10:09:55.892  - info: host.rp-surveillance Delete state "system.host.pi.compactModeEnabled"
              2021-11-24 10:09:55.912  - info: host.rp-surveillance Delete state "system.host.pi.compactgroupProcesses"
              2021-11-24 10:09:55.931  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsProcess"
              2021-11-24 10:09:55.954  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsCompact"
              2021-11-24 10:09:56.025  - info: host.rp-surveillance Delete state "system.host.pi.cpu"
              2021-11-24 10:09:56.047  - info: host.rp-surveillance Delete state "system.host.pi.cputime"
              2021-11-24 10:09:56.114  - info: host.rp-surveillance Delete state "system.host.pi.mem"
              2021-11-24 10:09:56.143  - info: host.rp-surveillance Delete state "system.host.pi.memHeapUsed"
              2021-11-24 10:09:56.179  - info: host.rp-surveillance Delete state "system.host.pi.memAvailable"
              2021-11-24 10:09:56.264  - info: host.rp-surveillance Delete state "system.host.pi.memHeapTotal"
              2021-11-24 10:09:56.306  - info: host.rp-surveillance Delete state "system.host.pi.memRss"
              2021-11-24 10:09:56.384  - info: host.rp-surveillance Delete state "system.host.pi.uptime"
              2021-11-24 10:09:56.404  - info: host.rp-surveillance Delete state "system.host.pi.load"
              2021-11-24 10:09:56.419  - info: host.rp-surveillance Delete state "system.host.pi.alive"
              2021-11-24 10:09:56.481  - info: host.rp-surveillance Delete state "system.host.pi.freemem"
              2021-11-24 10:09:56.496  - info: host.rp-surveillance Delete state "system.host.pi.inputCount"
              2021-11-24 10:09:56.511  - info: host.rp-surveillance Delete state "system.host.pi.outputCount"
              2021-11-24 10:09:56.526  - info: host.rp-surveillance Delete state "system.host.pi.eventLoopLag"
              2021-11-24 10:09:56.543  - info: host.rp-surveillance Delete state "system.host.pi.logLevel"
              2021-11-24 10:09:56.601  - info: host.rp-surveillance Delete state "system.host.pi.diskSize"
              2021-11-24 10:09:56.620  - info: host.rp-surveillance Delete state "system.host.pi.diskFree"
              2021-11-24 10:09:56.637  - info: host.rp-surveillance Delete state "system.host.pi.diskWarning"
              2021-11-24 10:09:56.686  - info: host.rp-surveillance 3 instances found
              2021-11-24 10:09:56.706  - info: host.rp-surveillance starting 3 instances
              2021-11-24 10:09:56.824  - info: host.rp-surveillance instance system.adapter.admin.0 started with pid 1111
              2021-11-24 10:10:00.815  - info: host.rp-surveillance instance system.adapter.discovery.0 started with pid 1693
              2021-11-24 10:10:01.942  - info: admin.0 (1111) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
              2021-11-24 10:10:02.138  - info: admin.0 (1111) requesting all states
              2021-11-24 10:10:02.139  - info: admin.0 (1111) requesting all objects
              2021-11-24 10:10:02.835  - info: admin.0 (1111) received all objects
              2021-11-24 10:10:03.350  - info: admin.0 (1111) http server listening on port 8081
              2021-11-24 10:10:03.351  - info: admin.0 (1111) Use link "http://localhost:8081" to configure.
              2021-11-24 10:10:19.816  - info: discovery.0 (1693) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
              2021-11-24 10:10:20.874  - info: host.rp-surveillance instance system.adapter.backitup.0 started with pid 1762
              2021-11-24 10:10:23.378  - info: backitup.0 (1762) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
              2021-11-24 10:10:23.485  - info: backitup.0 (1762) [iobroker] backup was activated at 02:40 every 1 day(s)
              
              HomoranH Nicht stören
              HomoranH Nicht stören
              Homoran
              Global Moderator Administrators
              schrieb am zuletzt editiert von Homoran
              #11

              @dennis-b sagte in Slave-Installation - reassign instance falsch:

              2021-11-24 10:08:37.385 - info: host.pi ip addresses: fe80::9ca0:7208:2eb7:69f7

              ist das der Master?

              @dennis-b sagte in Slave-Installation - reassign instance falsch:

              2021-11-24 10:09:54.497 - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7

              und das der slave?

              Beim Master kein IPv4?

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

              Dennis.BD 1 Antwort Letzte Antwort
              0
              • Dennis.BD Dennis.B

                @homoran

                pi@pi:~ $ iobroker setup custom
                Current configuration:
                - Objects database:
                  - Type: file
                  - Host/Unix Socket: 0.0.0.0
                  - Port: 9001
                - States database:
                  - Type: file
                  - Host/Unix Socket: 0.0.0.0
                  - Port: 9000
                - Data Directory: ../../iobroker-data/
                
                Type of objects DB [(f)ile, (r)edis, ...], default [file]: file
                Host / Unix Socket of objects DB(file), default[0.0.0.0]: 0.0.0.0
                Port of objects DB(file), default[9001]: 9001
                Type of states DB [(f)file, (r)edis, ...], default [file]: file
                Host / Unix Socket of states DB (file), default[0.0.0.0]: 0.0.0.0
                Port of states DB (file), default[9000]: 9000
                Data directory (file), default[../../iobroker-data/]: 
                Host name of this machine [pi]: pi
                updating conf/iobroker.json
                pi@pi:~ $ sudo reboot now
                Connection to pi closed by remote host.
                Connection to pi closed.
                
                pi@rp-surveillance:~ $ iobroker setup custom
                Current configuration:
                - Objects database:
                  - Type: file
                  - Host/Unix Socket: 192.168.101.99
                  - Port: 9001
                - States database:
                  - Type: file
                  - Host/Unix Socket: 192.168.101.99
                  - Port: 9000
                - Data Directory: ../../iobroker-data/
                
                Type of objects DB [(f)ile, (r)edis, ...], default [file]: file
                Host / Unix Socket of objects DB(file), default[192.168.101.99]: 192.168.101.99
                Port of objects DB(file), default[9001]: 9001
                Type of states DB [(f)file, (r)edis, ...], default [file]: file
                Host / Unix Socket of states DB (file), default[192.168.101.99]: 192.168.101.99
                Port of states DB (file), default[9000]: 9000
                Host name of this machine [rp-surveillance]: rp-surveillance
                updating conf/iobroker.json
                pi@rp-surveillance:~ $ sudo reboot now
                Connection to rp-surveillance closed by remote host.
                Connection to rp-surveillance closed.
                

                nach neustart beider hosts geht es leider immer noch nicht.

                pi1

                2021-11-24 10:08:37.364  - info: host.pi iobroker.js-controller version 3.3.19 js-controller starting
                2021-11-24 10:08:37.381  - info: host.pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                2021-11-24 10:08:37.383  - info: host.pi hostname: pi, node: v14.18.1
                2021-11-24 10:08:37.385  - info: host.pi ip addresses: fe80::9ca0:7208:2eb7:69f7
                2021-11-24 10:08:38.466  - info: host.pi connected to Objects and States
                2021-11-24 10:08:38.538  - info: host.pi added notifications configuration of host
                2021-11-24 10:08:41.434  - info: host.pi 3 instances found
                2021-11-24 10:08:41.462  - info: host.pi starting 3 instances
                2021-11-24 10:08:41.601  - info: host.pi instance system.adapter.admin.0 started with pid 956
                2021-11-24 10:08:45.573  - info: host.pi instance system.adapter.discovery.0 started with pid 1014
                2021-11-24 10:08:49.559  - info: host.pi instance system.adapter.backitup.0 started with pid 1075
                2021-11-24 10:08:49.922  - info: discovery.0 (1014) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
                2021-11-24 10:09:02.964  - info: admin.0 (956) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
                2021-11-24 10:09:03.131  - info: admin.0 (956) requesting all states
                2021-11-24 10:09:03.136  - info: admin.0 (956) requesting all objects
                2021-11-24 10:09:04.510  - info: admin.0 (956) received all objects
                2021-11-24 10:09:05.848  - info: admin.0 (956) http server listening on port 8081
                2021-11-24 10:09:05.863  - info: admin.0 (956) Use link "http://localhost:8081" to configure.
                2021-11-24 10:09:07.848  - info: backitup.0 (1075) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
                2021-11-24 10:09:08.046  - info: backitup.0 (1075) [iobroker] backup was activated at 02:40 every 1 day(s)
                2021-11-24 10:10:11.726  - info: host.pi stopInstance system.adapter.admin.0 (force=false, process=true)
                2021-11-24 10:10:11.765  - info: admin.0 (956) Got terminate signal TERMINATE_YOURSELF
                2021-11-24 10:10:11.769  - info: admin.0 (956) terminating http server on port 8081
                2021-11-24 10:10:11.772  - info: admin.0 (956) terminating
                2021-11-24 10:10:11.775  - info: admin.0 (956) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2021-11-24 10:10:11.800  - info: host.pi stopInstance system.adapter.admin.0 send kill signal
                2021-11-24 10:10:11.812  - info: host.pi stopInstance system.adapter.discovery.0 (force=false, process=true)
                2021-11-24 10:10:11.835  - info: discovery.0 (1014) Got terminate signal TERMINATE_YOURSELF
                2021-11-24 10:10:11.839  - info: discovery.0 (1014) terminating
                2021-11-24 10:10:11.842  - info: discovery.0 (1014) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2021-11-24 10:10:11.886  - info: host.pi stopInstance system.adapter.backitup.0 (force=false, process=true)
                2021-11-24 10:10:11.894  - info: host.pi stopInstance system.adapter.discovery.0 send kill signal
                2021-11-24 10:10:11.903  - info: backitup.0 (1075) Got terminate signal TERMINATE_YOURSELF
                2021-11-24 10:10:11.907  - info: host.pi stopInstance system.adapter.backitup.0 send kill signal
                2021-11-24 10:10:11.907  - info: backitup.0 (1075) cleaned everything up...
                2021-11-24 10:10:11.909  - info: backitup.0 (1075) terminating
                2021-11-24 10:10:11.912  - info: backitup.0 (1075) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                2021-11-24 10:10:12.369  - error: host.pi instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
                2021-11-24 10:10:12.370  - info: host.pi Do not restart adapter system.adapter.admin.0 because desired by instance
                2021-11-24 10:10:12.440  - error: host.pi instance system.adapter.discovery.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
                2021-11-24 10:10:12.442  - info: host.pi Do not restart adapter system.adapter.discovery.0 because desired by instance
                2021-11-24 10:10:12.508  - error: host.pi instance system.adapter.backitup.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
                2021-11-24 10:10:12.509  - info: host.pi Do not restart adapter system.adapter.backitup.0 because desired by instance
                

                pi2

                2021-11-24 10:09:54.486  - info: host.rp-surveillance iobroker.js-controller version 3.3.19 js-controller starting
                2021-11-24 10:09:54.495  - info: host.rp-surveillance Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                2021-11-24 10:09:54.496  - info: host.rp-surveillance hostname: rp-surveillance, node: v14.18.1
                2021-11-24 10:09:54.497  - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7
                2021-11-24 10:09:54.794  - info: host.rp-surveillance connected to Objects and States
                2021-11-24 10:09:54.891  - info: host.rp-surveillance added notifications configuration of host
                2021-11-24 10:09:55.528  - info: host.rp-surveillance Reassign instance admin.0 from pi to rp-surveillance
                2021-11-24 10:09:55.616  - info: host.rp-surveillance Reassign instance discovery.0 from pi to rp-surveillance
                2021-11-24 10:09:55.695  - info: host.rp-surveillance Reassign instance backitup.0 from pi to rp-surveillance
                2021-11-24 10:09:55.762  - info: host.rp-surveillance Delete host system.host.pi
                2021-11-24 10:09:55.803  - info: host.rp-surveillance Delete state "system.host.pi.notifications.system"
                2021-11-24 10:09:55.826  - info: host.rp-surveillance Delete state "system.host.pi.plugins.sentry.enabled"
                2021-11-24 10:09:55.892  - info: host.rp-surveillance Delete state "system.host.pi.compactModeEnabled"
                2021-11-24 10:09:55.912  - info: host.rp-surveillance Delete state "system.host.pi.compactgroupProcesses"
                2021-11-24 10:09:55.931  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsProcess"
                2021-11-24 10:09:55.954  - info: host.rp-surveillance Delete state "system.host.pi.instancesAsCompact"
                2021-11-24 10:09:56.025  - info: host.rp-surveillance Delete state "system.host.pi.cpu"
                2021-11-24 10:09:56.047  - info: host.rp-surveillance Delete state "system.host.pi.cputime"
                2021-11-24 10:09:56.114  - info: host.rp-surveillance Delete state "system.host.pi.mem"
                2021-11-24 10:09:56.143  - info: host.rp-surveillance Delete state "system.host.pi.memHeapUsed"
                2021-11-24 10:09:56.179  - info: host.rp-surveillance Delete state "system.host.pi.memAvailable"
                2021-11-24 10:09:56.264  - info: host.rp-surveillance Delete state "system.host.pi.memHeapTotal"
                2021-11-24 10:09:56.306  - info: host.rp-surveillance Delete state "system.host.pi.memRss"
                2021-11-24 10:09:56.384  - info: host.rp-surveillance Delete state "system.host.pi.uptime"
                2021-11-24 10:09:56.404  - info: host.rp-surveillance Delete state "system.host.pi.load"
                2021-11-24 10:09:56.419  - info: host.rp-surveillance Delete state "system.host.pi.alive"
                2021-11-24 10:09:56.481  - info: host.rp-surveillance Delete state "system.host.pi.freemem"
                2021-11-24 10:09:56.496  - info: host.rp-surveillance Delete state "system.host.pi.inputCount"
                2021-11-24 10:09:56.511  - info: host.rp-surveillance Delete state "system.host.pi.outputCount"
                2021-11-24 10:09:56.526  - info: host.rp-surveillance Delete state "system.host.pi.eventLoopLag"
                2021-11-24 10:09:56.543  - info: host.rp-surveillance Delete state "system.host.pi.logLevel"
                2021-11-24 10:09:56.601  - info: host.rp-surveillance Delete state "system.host.pi.diskSize"
                2021-11-24 10:09:56.620  - info: host.rp-surveillance Delete state "system.host.pi.diskFree"
                2021-11-24 10:09:56.637  - info: host.rp-surveillance Delete state "system.host.pi.diskWarning"
                2021-11-24 10:09:56.686  - info: host.rp-surveillance 3 instances found
                2021-11-24 10:09:56.706  - info: host.rp-surveillance starting 3 instances
                2021-11-24 10:09:56.824  - info: host.rp-surveillance instance system.adapter.admin.0 started with pid 1111
                2021-11-24 10:10:00.815  - info: host.rp-surveillance instance system.adapter.discovery.0 started with pid 1693
                2021-11-24 10:10:01.942  - info: admin.0 (1111) starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.18.1, js-controller: 3.3.19
                2021-11-24 10:10:02.138  - info: admin.0 (1111) requesting all states
                2021-11-24 10:10:02.139  - info: admin.0 (1111) requesting all objects
                2021-11-24 10:10:02.835  - info: admin.0 (1111) received all objects
                2021-11-24 10:10:03.350  - info: admin.0 (1111) http server listening on port 8081
                2021-11-24 10:10:03.351  - info: admin.0 (1111) Use link "http://localhost:8081" to configure.
                2021-11-24 10:10:19.816  - info: discovery.0 (1693) starting. Version 2.7.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 3.3.19
                2021-11-24 10:10:20.874  - info: host.rp-surveillance instance system.adapter.backitup.0 started with pid 1762
                2021-11-24 10:10:23.378  - info: backitup.0 (1762) starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.1, js-controller: 3.3.19
                2021-11-24 10:10:23.485  - info: backitup.0 (1762) [iobroker] backup was activated at 02:40 every 1 day(s)
                
                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #12

                @dennis-b
                Die Kisten der und in unterschiedlichen Netzen? Wird UDP da geroutet?

                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

                Dennis.BD 1 Antwort Letzte Antwort
                0
                • HomoranH Homoran

                  @dennis-b sagte in Slave-Installation - reassign instance falsch:

                  2021-11-24 10:08:37.385 - info: host.pi ip addresses: fe80::9ca0:7208:2eb7:69f7

                  ist das der Master?

                  @dennis-b sagte in Slave-Installation - reassign instance falsch:

                  2021-11-24 10:09:54.497 - info: host.rp-surveillance ip addresses: 192.168.102.188 fe80::865:3498:6aae:1eb7

                  und das der slave?

                  Beim Master kein IPv4?

                  Dennis.BD Offline
                  Dennis.BD Offline
                  Dennis.B
                  schrieb am zuletzt editiert von
                  #13

                  @homoran

                  beide gurkern haben ipv4 und sind im selben netz. Habe nur range 192.168.100.x bis 192.168.103.x

                  pi1

                  eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
                          ether b8:27:eb:5a:93:30  txqueuelen 1000  (Ethernet)
                          RX packets 0  bytes 0 (0.0 B)
                          RX errors 0  dropped 0  overruns 0  frame 0
                          TX packets 0  bytes 0 (0.0 B)
                          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                  
                  lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
                          inet 127.0.0.1  netmask 255.0.0.0
                          inet6 ::1  prefixlen 128  scopeid 0x10<host>
                          loop  txqueuelen 1000  (Local Loopback)
                          RX packets 7431  bytes 6954458 (6.6 MiB)
                          RX errors 0  dropped 0  overruns 0  frame 0
                          TX packets 7431  bytes 6954458 (6.6 MiB)
                          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                  
                  wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
                          inet 192.168.101.99  netmask 255.255.252.0  broadcast 192.168.103.255
                          inet6 fe80::9ca0:7208:2eb7:69f7  prefixlen 64  scopeid 0x20<link>
                          ether b8:27:eb:0f:c6:65  txqueuelen 1000  (Ethernet)
                          RX packets 24241  bytes 14846082 (14.1 MiB)
                          RX errors 0  dropped 1  overruns 0  frame 0
                          TX packets 22505  bytes 20633425 (19.6 MiB)
                          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                  
                  

                  pi2

                  eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
                          inet 192.168.102.188  netmask 255.255.252.0  broadcast 192.168.103.255
                          inet6 fe80::865:3498:6aae:1eb7  prefixlen 64  scopeid 0x20<link>
                          ether e4:5f:01:05:49:07  txqueuelen 1000  (Ethernet)
                          RX packets 759645  bytes 717546600 (684.3 MiB)
                          RX errors 0  dropped 3  overruns 0  frame 0
                          TX packets 446798  bytes 35770471 (34.1 MiB)
                          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                  
                  lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
                          inet 127.0.0.1  netmask 255.0.0.0
                          inet6 ::1  prefixlen 128  scopeid 0x10<host>
                          loop  txqueuelen 1000  (Local Loopback)
                          RX packets 193  bytes 10190 (9.9 KiB)
                          RX errors 0  dropped 0  overruns 0  frame 0
                          TX packets 193  bytes 10190 (9.9 KiB)
                          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                  
                  HomoranH 2 Antworten Letzte Antwort
                  0
                  • Dennis.BD Dennis.B

                    @homoran

                    beide gurkern haben ipv4 und sind im selben netz. Habe nur range 192.168.100.x bis 192.168.103.x

                    pi1

                    eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
                            ether b8:27:eb:5a:93:30  txqueuelen 1000  (Ethernet)
                            RX packets 0  bytes 0 (0.0 B)
                            RX errors 0  dropped 0  overruns 0  frame 0
                            TX packets 0  bytes 0 (0.0 B)
                            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                    
                    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
                            inet 127.0.0.1  netmask 255.0.0.0
                            inet6 ::1  prefixlen 128  scopeid 0x10<host>
                            loop  txqueuelen 1000  (Local Loopback)
                            RX packets 7431  bytes 6954458 (6.6 MiB)
                            RX errors 0  dropped 0  overruns 0  frame 0
                            TX packets 7431  bytes 6954458 (6.6 MiB)
                            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                    
                    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
                            inet 192.168.101.99  netmask 255.255.252.0  broadcast 192.168.103.255
                            inet6 fe80::9ca0:7208:2eb7:69f7  prefixlen 64  scopeid 0x20<link>
                            ether b8:27:eb:0f:c6:65  txqueuelen 1000  (Ethernet)
                            RX packets 24241  bytes 14846082 (14.1 MiB)
                            RX errors 0  dropped 1  overruns 0  frame 0
                            TX packets 22505  bytes 20633425 (19.6 MiB)
                            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                    
                    

                    pi2

                    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
                            inet 192.168.102.188  netmask 255.255.252.0  broadcast 192.168.103.255
                            inet6 fe80::865:3498:6aae:1eb7  prefixlen 64  scopeid 0x20<link>
                            ether e4:5f:01:05:49:07  txqueuelen 1000  (Ethernet)
                            RX packets 759645  bytes 717546600 (684.3 MiB)
                            RX errors 0  dropped 3  overruns 0  frame 0
                            TX packets 446798  bytes 35770471 (34.1 MiB)
                            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                    
                    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
                            inet 127.0.0.1  netmask 255.0.0.0
                            inet6 ::1  prefixlen 128  scopeid 0x10<host>
                            loop  txqueuelen 1000  (Local Loopback)
                            RX packets 193  bytes 10190 (9.9 KiB)
                            RX errors 0  dropped 0  overruns 0  frame 0
                            TX packets 193  bytes 10190 (9.9 KiB)
                            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                    
                    HomoranH Nicht stören
                    HomoranH Nicht stören
                    Homoran
                    Global Moderator Administrators
                    schrieb am zuletzt editiert von
                    #14

                    @dennis-b sagte in Slave-Installation - reassign instance falsch:

                    ether b8:27:eb:5a:93:30 txqueuelen 1000 (Ethernet)

                    LAN hat keine IPv4 Adresse - nur im WLAN

                    @dennis-b sagte in Slave-Installation - reassign instance falsch:

                    inet 192.168.101.99 netmask 255.255.252.0 broadcast 192.168.103.255

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

                    Dennis.BD 1 Antwort Letzte Antwort
                    0
                    • HomoranH Homoran

                      @dennis-b sagte in Slave-Installation - reassign instance falsch:

                      ether b8:27:eb:5a:93:30 txqueuelen 1000 (Ethernet)

                      LAN hat keine IPv4 Adresse - nur im WLAN

                      @dennis-b sagte in Slave-Installation - reassign instance falsch:

                      inet 192.168.101.99 netmask 255.255.252.0 broadcast 192.168.103.255

                      Dennis.BD Offline
                      Dennis.BD Offline
                      Dennis.B
                      schrieb am zuletzt editiert von
                      #15

                      @homoran

                      LAN ist nicht verbunden

                      HomoranH 1 Antwort Letzte Antwort
                      0
                      • Dennis.BD Dennis.B

                        @homoran

                        beide gurkern haben ipv4 und sind im selben netz. Habe nur range 192.168.100.x bis 192.168.103.x

                        pi1

                        eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
                                ether b8:27:eb:5a:93:30  txqueuelen 1000  (Ethernet)
                                RX packets 0  bytes 0 (0.0 B)
                                RX errors 0  dropped 0  overruns 0  frame 0
                                TX packets 0  bytes 0 (0.0 B)
                                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                        
                        lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
                                inet 127.0.0.1  netmask 255.0.0.0
                                inet6 ::1  prefixlen 128  scopeid 0x10<host>
                                loop  txqueuelen 1000  (Local Loopback)
                                RX packets 7431  bytes 6954458 (6.6 MiB)
                                RX errors 0  dropped 0  overruns 0  frame 0
                                TX packets 7431  bytes 6954458 (6.6 MiB)
                                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                        
                        wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
                                inet 192.168.101.99  netmask 255.255.252.0  broadcast 192.168.103.255
                                inet6 fe80::9ca0:7208:2eb7:69f7  prefixlen 64  scopeid 0x20<link>
                                ether b8:27:eb:0f:c6:65  txqueuelen 1000  (Ethernet)
                                RX packets 24241  bytes 14846082 (14.1 MiB)
                                RX errors 0  dropped 1  overruns 0  frame 0
                                TX packets 22505  bytes 20633425 (19.6 MiB)
                                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                        
                        

                        pi2

                        eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
                                inet 192.168.102.188  netmask 255.255.252.0  broadcast 192.168.103.255
                                inet6 fe80::865:3498:6aae:1eb7  prefixlen 64  scopeid 0x20<link>
                                ether e4:5f:01:05:49:07  txqueuelen 1000  (Ethernet)
                                RX packets 759645  bytes 717546600 (684.3 MiB)
                                RX errors 0  dropped 3  overruns 0  frame 0
                                TX packets 446798  bytes 35770471 (34.1 MiB)
                                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                        
                        lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
                                inet 127.0.0.1  netmask 255.0.0.0
                                inet6 ::1  prefixlen 128  scopeid 0x10<host>
                                loop  txqueuelen 1000  (Local Loopback)
                                RX packets 193  bytes 10190 (9.9 KiB)
                                RX errors 0  dropped 0  overruns 0  frame 0
                                TX packets 193  bytes 10190 (9.9 KiB)
                                TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
                        
                        HomoranH Nicht stören
                        HomoranH Nicht stören
                        Homoran
                        Global Moderator Administrators
                        schrieb am zuletzt editiert von Homoran
                        #16

                        @dennis-b sagte in Slave-Installation - reassign instance falsch:

                        LAN ist nicht verbunden

                        passt
                        im log wird versucht mit @dennis-b sagte in Slave-Installation - reassign instance falsch:

                        inet6 fe80::9ca0:7208:2eb7:69f7

                        zu verbinden, das ist die WLAN-Adresse. Aber IPv6

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

                        Dennis.BD 1 Antwort Letzte Antwort
                        0
                        • HomoranH Homoran

                          @dennis-b sagte in Slave-Installation - reassign instance falsch:

                          LAN ist nicht verbunden

                          passt
                          im log wird versucht mit @dennis-b sagte in Slave-Installation - reassign instance falsch:

                          inet6 fe80::9ca0:7208:2eb7:69f7

                          zu verbinden, das ist die WLAN-Adresse. Aber IPv6

                          Dennis.BD Offline
                          Dennis.BD Offline
                          Dennis.B
                          schrieb am zuletzt editiert von
                          #17

                          @homoran

                          ich habe ipv6 jetzt auf beiden deaktiviert und neu gestartet, leider immer noch das Problem.

                          sobald der slave zum master connected kommt das hier:

                          2021-11-24 10:09:54.794  - info: host.rp-surveillance connected to Objects and States
                          2021-11-24 10:09:54.891  - info: host.rp-surveillance added notifications configuration of host
                          2021-11-24 10:09:55.528  - info: host.rp-surveillance Reassign instance admin.0 from pi to rp-surveillance
                          2021-11-24 10:09:55.616  - info: host.rp-surveillance Reassign instance discovery.0 from pi to rp-surveillance
                          2021-11-24 10:09:55.695  - info: host.rp-surveillance Reassign instance backitup.0 from pi to rp-surveillance
                          
                          HomoranH 1 Antwort Letzte Antwort
                          0
                          • Dennis.BD Dennis.B

                            @homoran

                            LAN ist nicht verbunden

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

                            @dennis-b wir hatten letztens erst einen seltsamen Fehler in dieser Art
                            https://forum.iobroker.net/topic/49496/slave-installation-master-unter-slave-adresse-erreichbar/20?_=1637743925119

                            Auch mit "komischer" Netmask

                            Allerdings hatte dort ein iobroker fix geholfen - warum auch immer

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

                            Dennis.BD 1 Antwort Letzte Antwort
                            0
                            • HomoranH Homoran

                              @dennis-b wir hatten letztens erst einen seltsamen Fehler in dieser Art
                              https://forum.iobroker.net/topic/49496/slave-installation-master-unter-slave-adresse-erreichbar/20?_=1637743925119

                              Auch mit "komischer" Netmask

                              Allerdings hatte dort ein iobroker fix geholfen - warum auch immer

                              Dennis.BD Offline
                              Dennis.BD Offline
                              Dennis.B
                              schrieb am zuletzt editiert von
                              #19

                              @homoran said in Slave-Installation - reassign instance falsch:

                              iobroker fix

                              Ja das hatte ich auch schon gesehen und ausprobiert, leider ohne Erfolg.

                              1 Antwort Letzte Antwort
                              0
                              • Dennis.BD Dennis.B

                                @homoran

                                ich habe ipv6 jetzt auf beiden deaktiviert und neu gestartet, leider immer noch das Problem.

                                sobald der slave zum master connected kommt das hier:

                                2021-11-24 10:09:54.794  - info: host.rp-surveillance connected to Objects and States
                                2021-11-24 10:09:54.891  - info: host.rp-surveillance added notifications configuration of host
                                2021-11-24 10:09:55.528  - info: host.rp-surveillance Reassign instance admin.0 from pi to rp-surveillance
                                2021-11-24 10:09:55.616  - info: host.rp-surveillance Reassign instance discovery.0 from pi to rp-surveillance
                                2021-11-24 10:09:55.695  - info: host.rp-surveillance Reassign instance backitup.0 from pi to rp-surveillance
                                
                                HomoranH Nicht stören
                                HomoranH Nicht stören
                                Homoran
                                Global Moderator Administrators
                                schrieb am zuletzt editiert von
                                #20

                                @dennis-b sagte in Slave-Installation - reassign instance falsch:

                                ch habe ipv6 jetzt auf beiden deaktiviert und neu gestartet

                                auch nochmal mit iobroker setup custom reingesehen?

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

                                Dennis.BD 1 Antwort Letzte Antwort
                                0
                                • HomoranH Homoran

                                  @dennis-b sagte in Slave-Installation - reassign instance falsch:

                                  ch habe ipv6 jetzt auf beiden deaktiviert und neu gestartet

                                  auch nochmal mit iobroker setup custom reingesehen?

                                  Dennis.BD Offline
                                  Dennis.BD Offline
                                  Dennis.B
                                  schrieb am zuletzt editiert von
                                  #21

                                  @homoran said in Slave-Installation - reassign instance falsch:

                                  iobroker setup custom

                                  jo - sieht auch gut aus

                                  pi@pi:~ $ iobroker setup custom
                                  Current configuration:
                                  - Objects database:
                                    - Type: file
                                    - Host/Unix Socket: 0.0.0.0
                                    - Port: 9001
                                  - States database:
                                    - Type: file
                                    - Host/Unix Socket: 0.0.0.0
                                    - Port: 9000
                                  - Data Directory: ../../iobroker-data/
                                  - Host name: pi
                                  
                                  
                                  pi@rp-surveillance:~ $ iobroker setup custom
                                  Current configuration:
                                  - Objects database:
                                    - Type: file
                                    - Host/Unix Socket: 192.168.101.99
                                    - Port: 9001
                                  - States database:
                                    - Type: file
                                    - Host/Unix Socket: 192.168.101.99
                                    - Port: 9000
                                  - Data Directory: ../../iobroker-data/
                                  - Host name: rp-surveillance
                                  
                                  
                                  HomoranH 1 Antwort Letzte Antwort
                                  0
                                  • Dennis.BD Dennis.B

                                    @homoran said in Slave-Installation - reassign instance falsch:

                                    iobroker setup custom

                                    jo - sieht auch gut aus

                                    pi@pi:~ $ iobroker setup custom
                                    Current configuration:
                                    - Objects database:
                                      - Type: file
                                      - Host/Unix Socket: 0.0.0.0
                                      - Port: 9001
                                    - States database:
                                      - Type: file
                                      - Host/Unix Socket: 0.0.0.0
                                      - Port: 9000
                                    - Data Directory: ../../iobroker-data/
                                    - Host name: pi
                                    
                                    
                                    pi@rp-surveillance:~ $ iobroker setup custom
                                    Current configuration:
                                    - Objects database:
                                      - Type: file
                                      - Host/Unix Socket: 192.168.101.99
                                      - Port: 9001
                                    - States database:
                                      - Type: file
                                      - Host/Unix Socket: 192.168.101.99
                                      - Port: 9000
                                    - Data Directory: ../../iobroker-data/
                                    - Host name: rp-surveillance
                                    
                                    
                                    HomoranH Nicht stören
                                    HomoranH Nicht stören
                                    Homoran
                                    Global Moderator Administrators
                                    schrieb am zuletzt editiert von
                                    #22

                                    @dennis-b Dann bin ich am Ende mit meinem Latein.

                                    Hast du die Frage von @Thomas-Braun geprüft und beantwortet?

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

                                    W 1 Antwort Letzte Antwort
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @dennis-b
                                      Die Kisten der und in unterschiedlichen Netzen? Wird UDP da geroutet?

                                      Dennis.BD Offline
                                      Dennis.BD Offline
                                      Dennis.B
                                      schrieb am zuletzt editiert von
                                      #23

                                      @thomas-braun
                                      @Homoran

                                      UDP geht.

                                      pi@pi:~ $ nc -ul 6111
                                      test
                                      test
                                      test
                                      test
                                      ^C
                                      pi@pi:~ $ 
                                      
                                      pi@rp-surveillance:~ $ nc -u pi 6111
                                      test
                                      test
                                      test
                                      test
                                      ^C
                                      pi@rp-surveillance:~ $ 
                                      
                                      
                                      HomoranH 1 Antwort Letzte Antwort
                                      0
                                      • Dennis.BD Dennis.B

                                        @thomas-braun
                                        @Homoran

                                        UDP geht.

                                        pi@pi:~ $ nc -ul 6111
                                        test
                                        test
                                        test
                                        test
                                        ^C
                                        pi@pi:~ $ 
                                        
                                        pi@rp-surveillance:~ $ nc -u pi 6111
                                        test
                                        test
                                        test
                                        test
                                        ^C
                                        pi@rp-surveillance:~ $ 
                                        
                                        
                                        HomoranH Nicht stören
                                        HomoranH Nicht stören
                                        Homoran
                                        Global Moderator Administrators
                                        schrieb am zuletzt editiert von
                                        #24

                                        @dennis-b sagte in Slave-Installation - reassign instance falsch:

                                        UDP geht.

                                        steht denn jetzt die IPv4 im log bei Verbindungstversuch (Slave neustart über Admin des Masters?)

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

                                        Dennis.BD 1 Antwort Letzte Antwort
                                        0
                                        • HomoranH Homoran

                                          @dennis-b Dann bin ich am Ende mit meinem Latein.

                                          Hast du die Frage von @Thomas-Braun geprüft und beantwortet?

                                          W Offline
                                          W Offline
                                          wackl
                                          schrieb am zuletzt editiert von wackl
                                          #25

                                          Ich kämpfe seit 2 Tagen mit dem selben Problem.
                                          Habe schon 2 Raspis aufgesetzt, gleiches verhalten,
                                          dann 2 ct am Proxmox, auch kein Erfolg.

                                          Downgrade vom js-controller auf 3.2.16 -> multihost geht sofort

                                          Ab welcher Version das nicht mehr funktioniert wäre auszutesten...

                                          1 Antwort Letzte Antwort
                                          1

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

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

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

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


                                          Support us

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

                                          556

                                          Online

                                          32.9k

                                          Benutzer

                                          83.0k

                                          Themen

                                          1.3m

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

                                          • Du hast noch kein Konto? Registrieren

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