Probleme nach einem Restore
-
ip a -
@thomas-braun ```
berges01@Strommix-Smart:/opt/iobroker$ ^C
berges01@Strommix-Smart:/opt/iobroker$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 74:fe:48:29:76:f1 brd ff:ff:ff:ff:ff:ff
3: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 74:fe:48:29:76:f2 brd ff:ff:ff:ff:ff:ff
4: enp8s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether c4:00:ad:01:e5:11 brd ff:ff:ff:ff:ff:ff
5: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether c4:00:ad:01:e5:10 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.50/24 brd 192.168.2.255 scope global dynamic eno1
valid_lft 740330sec preferred_lft 740330sec
inet6 2003:f0:3f19:7b00:c600:adff:fe01:e510/64 scope global dynamic mngtmpaddr
valid_lft 6828sec preferred_lft 971sec
inet6 fe80::c600:adff:fe01:e510/64 scope link
valid_lft forever preferred_lft forever
berges01@Strommix-Smart:/opt/iobroker$ -
@berges01 sagte in Probleme nach einem Restore:
probiere mal https://192.168.2.50:8081/
also mit Verschlüsselung - wobei in dem Fall die Fehlermeldung bei mir anders aussieht wenn man http Zugriff auf https probiert (EMPTY RESPONSE) -
-
ufw statuswürde anzeigen ob die Linux-Firewall aktiv ist
Selbes Ergebiss dürfte eigentlich nicht sein, da könnte es sein das es vorher schon geblockt wird
-
@bananajoe said in Probleme nach einem Restore:
ufw status
berges01@Strommix-Smart:/opt/iobroker$ ufw status -bash: ufw: Kommando nicht gefunden. berges01@Strommix-Smart:/opt/iobroker$ -
@bananajoe
Das ist aber kein default-Service.ufw status -bash: ufw: command not found -
Mal eine Dumme Frage, muss der web.0 nicht enabled sein ?
-
-
@thomas-braun said in Probleme nach einem Restore:
iobroker start admin
berges01@Strommix-Smart:/opt/iobroker$ ^C berges01@Strommix-Smart:/opt/iobroker$ iobroker start web The adapter "web.0" was started. berges01@Strommix-Smart:/opt/iobroker$ iobroker start admin berges01@Strommix-Smart:/opt/iobroker$ iobroker status iobroker is running on this host. Objects type: file States type: file berges01@Strommix-Smart:/opt/iobroker$Nein geht immer noch nicht !
berges01@Strommix-Smart:/opt/iobroker$ ^C berges01@Strommix-Smart:/opt/iobroker$ iobroker list instances system.adapter.admin.0 : admin : Strommix-Smart - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : Strommix-Smart - disabled system.adapter.backitup.0 : backitup : Strommix-Smart - enabled system.adapter.cloud.0 : cloud : Strommix-Smart - disabled system.adapter.devices.0 : devices : Strommix-Smart - disabled system.adapter.info.0 : info : Strommix-Smart - disabled system.adapter.iot.0 : iot : Strommix-Smart - disabled system.adapter.javascript.0 : javascript : Strommix-Smart - disabled system.adapter.netatmo.0 : netatmo : Strommix-Smart - disabled system.adapter.ping.0 : ping : Strommix-Smart - disabled system.adapter.socketio.0 : socketio : Strommix-Smart - disabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.tr-064.0 : tr-064 : Strommix-Smart - disabled system.adapter.vis.0 : vis : Strommix-Smart - disabled system.adapter.web.0 : web : Strommix-Smart - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.whatsapp-cmb.0 : whatsapp-cmb : Strommix-Smart - disabled system.adapter.zwave2.0 : zwave2 : Strommix-Smart - disabled + instance is alive berges01@Strommix-Smart:/opt/iobroker$ -
iobroker start all -
@thomas-braun said in Probleme nach einem Restore:
iobroker start all
berges01@Strommix-Smart:/opt/iobroker$ ^C berges01@Strommix-Smart:/opt/iobroker$ iobroker start all The adapter "alexa2.0" was started. The adapter "cloud.0" was started. The adapter "devices.0" was started. The adapter "info.0" was started. The adapter "iot.0" was started. The adapter "javascript.0" was started. The adapter "netatmo.0" was started. The adapter "ping.0" was started. The adapter "socketio.0" was started. The adapter "tr-064.0" was started. The adapter "vis.0" was started. The adapter "whatsapp-cmb.0" was started. The adapter "zwave2.0" was started. berges01@Strommix-Smart:/opt/iobroker$ iobroker list instances system.adapter.admin.0 : admin : Strommix-Smart - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : Strommix-Smart - enabled system.adapter.backitup.0 : backitup : Strommix-Smart - enabled system.adapter.cloud.0 : cloud : Strommix-Smart - enabled system.adapter.devices.0 : devices : Strommix-Smart - enabled system.adapter.info.0 : info : Strommix-Smart - enabled system.adapter.iot.0 : iot : Strommix-Smart - enabled system.adapter.javascript.0 : javascript : Strommix-Smart - enabled system.adapter.netatmo.0 : netatmo : Strommix-Smart - enabled system.adapter.ping.0 : ping : Strommix-Smart - enabled system.adapter.socketio.0 : socketio : Strommix-Smart - enabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.tr-064.0 : tr-064 : Strommix-Smart - enabled system.adapter.vis.0 : vis : Strommix-Smart - enabled system.adapter.web.0 : web : Strommix-Smart - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.whatsapp-cmb.0 : whatsapp-cmb : Strommix-Smart - enabled system.adapter.zwave2.0 : zwave2 : Strommix-Smart - enabled + instance is alive berges01@Strommix-Smart:/opt/iobroker$Nein immer noch nicht
-
@berges01
Komme in 30min wieder -
So in der Zwischenzeit den Debian runter gefahren und neu gestartet.
Angepingt geht.
per Putty angemeldet geht.berges01@Strommix-Smart:~$ iobroker status iobroker is running on this host. Objects type: file States type: file berges01@Strommix-Smart:~$ iobroker list instances system.adapter.admin.0 : admin : Strommix-Smart - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : Strommix-Smart - enabled system.adapter.backitup.0 : backitup : Strommix-Smart - enabled system.adapter.cloud.0 : cloud : Strommix-Smart - enabled system.adapter.devices.0 : devices : Strommix-Smart - enabled system.adapter.info.0 : info : Strommix-Smart - enabled system.adapter.iot.0 : iot : Strommix-Smart - enabled system.adapter.javascript.0 : javascript : Strommix-Smart - enabled system.adapter.netatmo.0 : netatmo : Strommix-Smart - enabled system.adapter.ping.0 : ping : Strommix-Smart - enabled system.adapter.socketio.0 : socketio : Strommix-Smart - enabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.tr-064.0 : tr-064 : Strommix-Smart - enabled system.adapter.vis.0 : vis : Strommix-Smart - enabled system.adapter.web.0 : web : Strommix-Smart - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.whatsapp-cmb.0 : whatsapp-cmb : Strommix-Smart - enabled system.adapter.zwave2.0 : zwave2 : Strommix-Smart - enabled + instance is alive berges01@Strommix-Smart:~$
Mal mit Chrom angemeldet selbes Ergebnis
-
-
Keine Ahnung warum die Instanzen nicht starten.
Füg mal eine weitere hinzu:iobroker add admin -
@thomas-braun said in Probleme nach einem Restore:
iobroker add admin
berges01@Strommix-Smart:~$ ^C berges01@Strommix-Smart:~$ iobroker add admin host.DESKTOP-61ND8BH(SmartHome) create instance admin host.DESKTOP-61ND8BH(SmartHome) object admin.1.info.updatesList created host.DESKTOP-61ND8BH(SmartHome) object admin.1.info.newsLastId created host.DESKTOP-61ND8BH(SmartHome) object admin.1.info.newsETag created host.DESKTOP-61ND8BH(SmartHome) object admin.1.info.newsFeed created host.DESKTOP-61ND8BH(SmartHome) object admin.1.info.connection created host.DESKTOP-61ND8BH(SmartHome) object admin.1 created host.DESKTOP-61ND8BH(SmartHome) object admin.1.info created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.upload created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.logLevel created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.sigKill created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.eventLoopLag created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.outputCount created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.inputCount created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.uptime created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.memRss created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.memHeapTotal created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.memHeapUsed created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.cputime created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.cpu created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.compactMode created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.connected created host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1.alive created host.DESKTOP-61ND8BH(SmartHome) Set default value of admin.1.info.updatesList: host.DESKTOP-61ND8BH(SmartHome) Set default value of admin.1.info.connection: host.DESKTOP-61ND8BH(SmartHome) object system.adapter.admin.1 created berges01@Strommix-Smart:~$ -
So jetzt ist der Zugang da !
-
berges01@Strommix-Smart:~$ iobroker list instances system.adapter.admin.0 : admin : Strommix-Smart - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.admin.1 : admin : DESKTOP-61ND8BH(SmartHome) - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : Strommix-Smart - enabled system.adapter.backitup.0 : backitup : Strommix-Smart - enabled system.adapter.cloud.0 : cloud : Strommix-Smart - enabled system.adapter.devices.0 : devices : Strommix-Smart - enabled system.adapter.info.0 : info : Strommix-Smart - enabled system.adapter.iot.0 : iot : Strommix-Smart - enabled system.adapter.javascript.0 : javascript : Strommix-Smart - enabled system.adapter.netatmo.0 : netatmo : Strommix-Smart - enabled system.adapter.ping.0 : ping : Strommix-Smart - enabled system.adapter.socketio.0 : socketio : Strommix-Smart - enabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.tr-064.0 : tr-064 : Strommix-Smart - enabled system.adapter.vis.0 : vis : Strommix-Smart - enabled system.adapter.web.0 : web : Strommix-Smart - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.whatsapp-cmb.0 : whatsapp-cmb : Strommix-Smart - enabled system.adapter.zwave2.0 : zwave2 : Strommix-Smart - enabled + instance is alive berges01@Strommix-Smart:~$ -
@berges01 sagte in Probleme nach einem Restore:
So jetzt ist der Zugang da !
und beide admin-Instanzen auf dem selben Port
das kann nicht gutgehenAndererseits dürfte das zeigen, dass der :8081 nich bereits verwendet wurde
