Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Probleme mit multihost slave nach node.js update

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Probleme mit multihost slave nach node.js update

    This topic has been deleted. Only users with topic management privileges can see it.
    • Mr. Qi
      Mr. Qi @wendy2702 last edited by Mr. Qi

      @wendy2702
      log aus dem admin die errors der adapter hangen mit der fehlenden multihost verbindung zusammen.

      2021-04-09 20:14:23.749 - warn: javascript.0 (1070) getState "tado.0.526573.Rooms.5.Actual_Temperature" not found (3) states[id]=null
      2021-04-09 20:14:23.780 - warn: javascript.0 (1070) at Object. (script.js.meineSkripte.VIS.Temperatur.TempKorri:8:37)
      2021-04-09 20:14:23.781 - warn: javascript.0 (1070) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1075:38)
      2021-04-09 20:14:23.781 - warn: javascript.0 (1070) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:502:29)
      2021-04-09 20:14:23.782 - warn: javascript.0 (1070) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5555:41)
      2021-04-09 20:14:23.782 - warn: javascript.0 (1070) at processImmediate (internal/timers.js:461:21)
      2021-04-09 20:14:24.063 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
      2021-04-09 20:14:25.154 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
      2021-04-09 20:14:25.211 - info: tado.0 (1071) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
      2021-04-09 20:14:30.715 - warn: host.IobrokerMaster "system.host.IobrokerSlave" is offline
      2021-04-09 20:14:44.076 - info: alexa2.0 (1171) Subscribing to states...
      2021-04-09 20:14:44.081 - info: alexa2.0 (1171) Deleting the following states: ["Echo-Devices.G0W19D04019407VG.Alarm","Echo-Devices.G0W19D04019407VG.Timer","Echo-Devices.G0W19D04019407VG.Alarm.New","Echo-Devices.G0W19D04019407VG.Timer.triggered"]
      2021-04-09 20:15:50.053 - info: web.0 (1170) <==Disconnect system.user.admin from ::ffff:192.168.178.190 vis.0
      2021-04-09 20:15:50.067 - info: web.0 (1170) <==Disconnect system.user.admin from ::ffff:192.168.178.190 vis.0
      2021-04-09 20:17:51.443 - info: tado.0 (1071) Temperature changed for room : 8 in home : 526573 to API with : 23
      2021-04-09 20:17:55.527 - info: tado.0 (1071) Overlay cleared for room : 8 in home : 526573
      2021-04-09 20:18:02.670 - info: tado.0 (1071) Temperature changed for room : 1 in home : 526573 to API with : 23
      2021-04-09 20:21:09.792 - error: host.IobrokerMaster-Server Cannot save backup file /opt/iobroker/iobroker-data/objects.json.bak: ENOENT: no such file or directory, rename '/opt/iobroker/iobroker-data/objects.json' -> '/opt/iobroker/iobroker-data/objects.json.bak'
      2021-04-09 20:24:37.063 - info: host.IobrokerMaster Multihost discovery server stopped after 15 minutes, because only temporarily activated
      2021-04-09 20:30:00.083 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 1888
      2021-04-09 20:30:02.133 - info: ical.0 (1888) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 20:30:02.515 - info: ical.0 (1888) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
      2021-04-09 20:30:07.604 - info: ical.0 (1888) Terminated (NO_ERROR): Without reason
      2021-04-09 20:30:08.129 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
      2021-04-09 20:44:39.006 - info: tado.0 (1071) Temperature changed for room : 5 in home : 526573 to API with : 23
      2021-04-09 21:00:00.032 - info: tado.0 (1071) Scheduled restart.
      2021-04-09 21:00:00.036 - info: tado.0 (1071) cleaned everything up...
      2021-04-09 21:00:00.042 - info: tado.0 (1071) terminating
      2021-04-09 21:00:00.048 - info: tado.0 (1071) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 21:00:00.101 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2041
      2021-04-09 21:00:00.684 - info: host.IobrokerMaster instance system.adapter.tado.0 scheduled normal terminated and will be restarted on schedule.
      2021-04-09 21:00:00.685 - info: host.IobrokerMaster Restart adapter system.adapter.tado.0 because enabled
      2021-04-09 21:00:01.713 - info: host.IobrokerMaster instance system.adapter.tado.0 started with pid 2052
      2021-04-09 21:00:02.206 - info: ical.0 (2041) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 21:00:02.574 - info: ical.0 (2041) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
      2021-04-09 21:00:03.635 - info: tado.0 (2052) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.tado, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 21:00:04.312 - info: tado.0 (2052) Connected to Tado cloud, initialyzing ...
      2021-04-09 21:00:07.676 - info: ical.0 (2041) Terminated (NO_ERROR): Without reason
      2021-04-09 21:00:08.203 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
      2021-04-09 21:00:10.671 - info: tado.0 (2052) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
      2021-04-09 21:06:53.760 - info: web.0 (1170) <==Disconnect system.user.admin from ::ffff:192.168.178.23 vis.0
      2021-04-09 21:20:00.034 - info: tado.0 (2052) Scheduled restart.
      2021-04-09 21:20:00.041 - info: tado.0 (2052) cleaned everything up...
      2021-04-09 21:20:00.045 - info: tado.0 (2052) terminating
      2021-04-09 21:20:00.049 - info: tado.0 (2052) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 21:20:00.648 - info: host.IobrokerMaster instance system.adapter.tado.0 scheduled normal terminated and will be restarted on schedule.
      2021-04-09 21:20:00.653 - info: host.IobrokerMaster Restart adapter system.adapter.tado.0 because enabled
      2021-04-09 21:20:01.717 - info: host.IobrokerMaster instance system.adapter.tado.0 started with pid 2154
      2021-04-09 21:20:03.592 - info: tado.0 (2154) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.tado, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 21:20:04.236 - info: tado.0 (2154) Connected to Tado cloud, initialyzing ...
      2021-04-09 21:20:10.219 - info: tado.0 (2154) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
      2021-04-09 21:30:00.044 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2211
      2021-04-09 21:30:02.214 - info: ical.0 (2211) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 21:30:02.587 - info: ical.0 (2211) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
      2021-04-09 21:30:07.683 - info: ical.0 (2211) Terminated (NO_ERROR): Without reason
      2021-04-09 21:30:08.234 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
      2021-04-09 21:40:00.037 - info: tado.0 (2154) Scheduled restart.
      2021-04-09 21:40:00.045 - info: tado.0 (2154) cleaned everything up...
      2021-04-09 21:40:00.051 - info: tado.0 (2154) terminating
      2021-04-09 21:40:00.055 - info: tado.0 (2154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 21:40:00.926 - info: host.IobrokerMaster instance system.adapter.tado.0 scheduled normal terminated and will be restarted on schedule.
      2021-04-09 21:40:00.930 - info: host.IobrokerMaster Restart adapter system.adapter.tado.0 because enabled
      2021-04-09 21:40:01.989 - info: host.IobrokerMaster instance system.adapter.tado.0 started with pid 2357
      2021-04-09 21:40:03.743 - info: tado.0 (2357) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.tado, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 21:40:04.328 - info: tado.0 (2357) Connected to Tado cloud, initialyzing ...
      2021-04-09 21:40:10.237 - info: tado.0 (2357) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
      2021-04-09 21:48:21.492 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.23
      2021-04-09 21:48:43.697 - info: tado.0 (2357) Overlay cleared for room : 1 in home : 526573
      2021-04-09 21:59:36.091 - info: tado.0 (2357) Overlay cleared for room : 5 in home : 526573
      2021-04-09 22:00:00.046 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2474
      2021-04-09 22:00:02.741 - info: ical.0 (2474) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 22:00:03.089 - info: ical.0 (2474) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
      2021-04-09 22:00:08.181 - info: ical.0 (2474) Terminated (NO_ERROR): Without reason
      2021-04-09 22:00:08.705 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
      2021-04-09 22:30:00.044 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2683
      2021-04-09 22:30:02.058 - info: ical.0 (2683) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 22:30:02.279 - info: ical.0 (2683) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
      2021-04-09 22:30:02.295 - error: trashschedule.0 (1109) no events found in iCal instance - check configuration and restart adapter
      2021-04-09 22:30:07.301 - info: ical.0 (2683) Terminated (NO_ERROR): Without reason
      2021-04-09 22:30:07.853 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
      2021-04-09 23:00:00.135 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2813
      2021-04-09 23:00:02.178 - info: ical.0 (2813) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 23:00:02.516 - info: ical.0 (2813) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
      2021-04-09 23:00:07.605 - info: ical.0 (2813) Terminated (NO_ERROR): Without reason
      2021-04-09 23:00:08.155 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
      2021-04-09 23:30:00.226 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 3033
      2021-04-09 23:30:02.241 - info: ical.0 (3033) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
      2021-04-09 23:30:02.590 - info: ical.0 (3033) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
      2021-04-09 23:30:07.679 - info: ical.0 (3033) Terminated (NO_ERROR): Without reason
      2021-04-09 23:30:08.231 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
      2021-04-09 23:46:19.669 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
      2021-04-09 23:46:21.987 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
      2021-04-09 23:46:22.585 - warn: host.IobrokerMaster "system.host.IobrokerSlave" is offline
      2021-04-09 23:50:01.672 - error: tr-064.1 (1085) States database error: read ECONNRESET
      2021-04-09 23:50:01.684 - error: lgtv.0 (992) States database error: read ECONNRESET
      2021-04-09 23:50:01.686 - error: fritzdect.0 (1045) States database error: read ECONNRESET
      2021-04-09 23:50:01.689 - error: alexa2.0 (1171) States database error: read ECONNRESET
      2021-04-09 23:50:01.693 - error: trashschedule.0 (1109) States database error: read ECONNRESET
      2021-04-09 23:50:01.699 - error: history.0 (1052) States database error: read ECONNRESET
      2021-04-09 23:50:01.670 - error: info.0 (1053) States database error: read ECONNRESET
      2021-04-09 23:50:01.694 - error: tr-064.2 (1086) States database error: read ECONNRESET
      2021-04-09 23:50:01.678 - error: backitup.0 (978) States database error: read ECONNRESET
      2021-04-09 23:50:01.714 - error: javascript.0 (1070) States database error: read ECONNRESET
      2021-04-09 23:50:01.677 - error: web.0 (1170) States database error: read ECONNRESET
      2021-04-09 23:50:01.723 - error: asuswrt.0 (971) States database error: read ECONNRESET
      2021-04-09 23:50:01.705 - error: admin.0 (1014) States database error: read ECONNRESET
      2021-04-09 23:50:01.732 - error: echarts.0 (985) States database error: read ECONNRESET
      2021-04-09 23:50:01.704 - error: host.IobrokerMaster States database error: read ECONNRESET
      2021-04-09 23:50:01.713 - error: upnp.0 (995) States database error: read ECONNRESET
      2021-04-09 23:50:01.716 - error: tr-064.0 (1084) States database error: read ECONNRESET
      2021-04-09 23:50:01.727 - error: vis-inventwo.0 (1120) States database error: read ECONNRESET
      2021-04-09 23:50:06.696 - info: lgtv.0 (992) Objects database successfully reconnected
      2021-04-09 23:50:06.697 - info: fritzdect.0 (1045) Objects database successfully reconnected
      2021-04-09 23:50:06.714 - info: trashschedule.0 (1109) Objects database successfully reconnected
      2021-04-09 23:50:06.733 - info: asuswrt.0 (971) Objects database successfully reconnected
      2021-04-09 23:50:06.744 - info: tr-064.2 (1086) Objects database successfully reconnected
      2021-04-09 23:50:06.751 - info: web.0 (1170) Objects database successfully reconnected
      2021-04-09 23:50:06.744 - info: vis-inventwo.0 (1120) Objects database successfully reconnected
      2021-04-09 23:50:06.751 - info: history.0 (1052) Objects database successfully reconnected
      2021-04-09 23:50:06.751 - info: echarts.0 (985) Objects database successfully reconnected
      2021-04-09 23:50:06.758 - info: alexa2.0 (1171) Objects database successfully reconnected
      2021-04-09 23:50:06.773 - info: javascript.0 (1070) Objects database successfully reconnected
      2021-04-09 23:50:06.775 - info: info.0 (1053) Objects database successfully reconnected
      2021-04-09 23:50:06.727 - info: backitup.0 (978) Objects database successfully reconnected
      2021-04-09 23:50:06.781 - info: tr-064.1 (1085) Objects database successfully reconnected
      2021-04-09 23:50:06.787 - info: upnp.0 (995) Objects database successfully reconnected
      2021-04-09 23:50:06.794 - info: admin.0 (1014) Objects database successfully reconnected
      2021-04-09 23:50:06.802 - info: host.IobrokerMaster Objects database successfully reconnected
      2021-04-09 23:50:06.790 - info: tr-064.0 (1084) Objects database successfully reconnected
      2021-04-09 23:54:45.811 - info: backitup.0 (978) cleaned everything up...
      2021-04-09 23:54:45.810 - info: fritzdect.0 (1045) cleaned everything up...
      2021-04-09 23:54:45.819 - info: vis-inventwo.0 (1120) cleaned everything up...
      2021-04-09 23:54:45.825 - info: vis-inventwo.0 (1120) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.815 - info: fritzdect.0 (1045) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.826 - info: tr-064.1 (1085) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.830 - info: info.0 (1053) cleaned everything up...
      2021-04-09 23:54:45.832 - info: upnp.0 (995) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.836 - info: trashschedule.0 (1109) cleaned everything up...
      2021-04-09 23:54:45.844 - info: alexa2.0 (1171) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.845 - info: lgtv.0 (992) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.827 - info: asuswrt.0 (971) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.835 - info: tr-064.2 (1086) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.849 - info: admin.0 (1014) terminating http server on port 8081
      2021-04-09 23:54:45.850 - info: javascript.0 (1070) Stop script script.js.meineSkripte.VIS.Heizung.Heizung_Auto_Manuel
      2021-04-09 23:54:45.851 - info: lgtv.1 (993) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.850 - info: info.0 (1053) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.856 - info: trashschedule.0 (1109) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.840 - info: web.0 (1170) terminated http server on port 8082
      2021-04-09 23:54:45.857 - info: admin.0 (1014) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      2021-04-09 23:54:45.856 - info: backitup.0 (978) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
      
      Mr. Qi 1 Reply Last reply Reply Quote 0
      • Mr. Qi
        Mr. Qi @Mr. Qi last edited by

        @wendy2702
        so oben war der Log auszug aus dem Admin vom Master

        nach kurzem überlegen bin ich endlich auch mal drauf gekommen mir mal das log vom Slave anzuschauen ich bin noch nicht zur Auswertung gekommen vielleicht bis du schneller.
        Hier ist das Gegenstück vom Slave und interesant was der so ausspuckt?!

        master.admin@IobrokerSlave:~ $ iobroker logs
        
        2021-04-10 22:20:08.939  - info: host.IobrokerSlave iobroker.js-controller version 3.2.16 js-controller starting
        2021-04-10 22:20:08.947  - info: host.IobrokerSlave Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
        2021-04-10 22:20:08.948  - info: host.IobrokerSlave hostname: IobrokerSlave, node: v12.22.1
        2021-04-10 22:20:08.949  - info: host.IobrokerSlave ip addresses: 192.168.178.29 2001:4dd4:1f53:0:b759:2505:bb8b:2763 fe80::ebd8:7d12:20c5:ad6e 192.168.178.36 2001:4dd4:1f53:0:2403:815c:196b:b0c fe80::3249:f072:1cc:e47
        2021-04-10 22:20:09.145  - info: host.IobrokerSlave connected to Objects and States
        2021-04-10 22:20:09.177  - info: host.IobrokerSlave added notifications configuration of host
        2021-04-10 22:20:09.746  - error: host.IobrokerSlave uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
        2021-04-10 22:20:09.747  - error: host.IobrokerSlave Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
            at Decipheriv.final (internal/crypto/cipher.js:172:29)
            at Object.decrypt (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:1867:79)
            at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:202:46)
            at processImmediate (internal/timers.js:463:21)
        2021-04-10 22:20:09.760  - info: host.IobrokerSlave iobroker _restart
        2021-04-10 22:20:09.806  - warn: host.IobrokerSlave Cannot get view: Connection is closed.
        2021-04-10 22:20:09.807  - warn: host.IobrokerSlave Cannot get view: Connection is closed.
        2021-04-10 22:20:09.819  - info: host.IobrokerSlave no instances found
        2021-04-10 22:20:09.824  - error: host.IobrokerSlave Cannot write host object:Error: DB closed
        2021-04-10 22:20:09.827  - info: host.IobrokerSlave terminated
        2021-04-10 22:20:11.708  - info: host.IobrokerSlave iobroker.js-controller version 3.2.16 js-controller starting
        2021-04-10 22:20:11.716  - info: host.IobrokerSlave Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
        2021-04-10 22:20:11.717  - info: host.IobrokerSlave hostname: IobrokerSlave, node: v12.22.1
        2021-04-10 22:20:11.718  - info: host.IobrokerSlave ip addresses: 192.168.178.29 2001:4dd4:1f53:0:b759:2505:bb8b:2763 fe80::ebd8:7d12:20c5:ad6e 192.168.178.36 2001:4dd4:1f53:0:2403:815c:196b:b0c fe80::3249:f072:1cc:e47
        2021-04-10 22:20:11.909  - info: host.IobrokerSlave connected to Objects and States
        2021-04-10 22:20:11.942  - info: host.IobrokerSlave added notifications configuration of host
        2021-04-10 22:20:12.565  - error: host.IobrokerSlave uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
        2021-04-10 22:20:12.567  - error: host.IobrokerSlave Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
            at Decipheriv.final (internal/crypto/cipher.js:172:29)
            at Object.decrypt (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:1867:79)
            at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:202:46)
            at processImmediate (internal/timers.js:463:21)
        

        wenn man sich zulange auf etwas fixiert ist man nicht mehr Konstruktive.

        Ein angezeigter Error (Angezeigte Straftat) kommt Logischerweise aus einem Melder Logs vom iobroker Master / Admin (Zeugenaussage und Anzeige). Aber folglich gibt es auch eine zweite aussage von den Logs des iobroker Slave (Gegendarstellung vermeintlicher Täteraussage). Die zwei Seiten der Geschichte XD wenn ich zu Biografisch werde sollte ich ins Bett gehen. Hoffe ihr seht was, was ich noch nicht sehe.😵 😁

        wendy2702 1 Reply Last reply Reply Quote 0
        • wendy2702
          wendy2702 @Mr. Qi last edited by

          @mr-qi Mit den Befehlen im EIngangspost hat du auch den JS-Controller upgedated. Hierbei wäre die Reihenfolge zu beachten gewesen.

          Wo hast du ein Backup eingespielt damit es wieder ging?

          Ist der Ping zwischen Master und Slave stabil?

          was kommt bei Master und Slave bei

          iobroker status
          

          Mal auf dem Slave das ausgeführt:

          iobroker setup custom
          

          Und geschaut ob da alles richtig ist.

          1 Reply Last reply Reply Quote 0
          • Mr. Qi
            Mr. Qi @Mr. Qi last edited by Mr. Qi

            @mr-qi sagte in Probleme mit multihost slave nach node.js update:

            Brauch mal Hilfe bei der Suche nach dem Fehler:

            Aufbau RPI 4 (Master) UND 3B (Slave) multihost system.
            beide in der selben sub Netz domene. Beide vollständig ab to date bislang keine Probleme.

            Ereignis: Update auf node.js 12.22.1 nach Anleitung
            (groß und Kleinschreibung dint nur der Darstellung in der console habe ich alles kleingeschrieben)

            cd /opt/iobroker
            iobroker stop
            cd 
            sudo apt-get update & & sudo apt-get upgrade 
            cd /opt/iobroker 
            iobroker update 
            iobroker upgrade self 
            iobroker start
            

            Nach dem Update ist soweit alles ok der Master scheint einwand frei zu laufen der slave aber nicht.
            Die Systeme :
            Screenshot_20210410_141122_com.sonelli.juicessh.jpg Screenshot_20210410_141244_com.sonelli.juicessh.jpg

            Der error
            iobroker.png

            Ich habe gängige Lösungsansätze schon versucht ohne Erfolg der slave bekommt keine stabile Verbindung.
            Gestern habe ich es mit dem Backup versucht und der vohergangenen node.js 12.20.1 Version damit hat alles wieder normal funktioniert.

            @wendy2702
            siehe oben die ersten bild sind aus der console mit dem Status der multihost system anzumerken ist das meine stats auf redist laufen das ist aber so gewollt ich habe den redis server konfiguriert und das bind via 0.0.0.0 in die config eingetragen das lief bislang so. Das war mein erster Gedanke das das Update hier etwas gelöscht hat dem war aber nicht so ich habe dann an dieser Stelle das binding noch mal nachvollzogen und keinen erfolg gehabt.

            1 Reply Last reply Reply Quote 0
            • Mr. Qi
              Mr. Qi last edited by Mr. Qi

              So ich habe jetzt folgendes gemacht um für euch den Prozess nachvollziehbar zu machen

              auf dem Master :

              Sudo nano /etc/redis/redis.conf
              
              Unter Network 
              bind 0.0.0.0 speichern und 
              
              sudo service redis-server restart
              
              iobroker setup custom
              
              Type of objects DB [file, couch, redis], default [file]: f
              Host of objects DB(file), default[0.0.0.0]: ENTER 
              Port of objects DB(file), default[9001]: ENTER
              Type of states DB [file, redis], default [file]: r
              Host of states DB (file), default[0.0.0.0]: ENTER
              Port of states DB (file), default[6379]: ENTER 
              Host name of this machine [hostname]: ENTER
              
              iobroker multihost enable
              Iobroker restart 
              

              Auf dem Slave dito

              iobroker setup custom
              
              Type of objects DB [file, couch, redis], default [file]: f
              Host of objects DB(file), default[ master ip ]: ENTER
              Port of objects DB(file), default[9001]: ENTER
              Type of states DB [file, redis], default [file]: r
              Host of states DB (file), default[ master ip ]: ENTER
              Port of states DB (file), default[6379]: ENTER 
              Host name of this machine [hostname]: ENTER
              
              iobroker multihost connect
              
              1 |       <MASTER-IP> |  host |       192.168.xx.xx | "authentication required"
              Please select host [1]: 1
              Enter secret phrase for connection: *****
              
              Config ok. Please restart ioBroker: "iobroker restart"
              
              Iobroker restart 
              

              Das habe ich jetzt aktuell so ausgeführt und ohne Erfolg.
              Die Fehler bleiben.

              Latzi 1 Reply Last reply Reply Quote 0
              • Latzi
                Latzi @Mr. Qi last edited by Latzi

                @mr-qi
                beim Slave muss unter "Host of states" die iP des Masters rein

                Mr. Qi 1 Reply Last reply Reply Quote -1
                • Mr. Qi
                  Mr. Qi @Latzi last edited by Mr. Qi

                  @latzi

                  Sorry für copy und past aber das ist klar 👍
                  ich hab es oben korrigiert.

                  Erklärt sich aber von selber und ist nicht die lösung des Problems. Vor dem Update hat noch alles funktioniert. Ergo ist da alles richtig konfiguriert.

                  Unteranderem hilft es die vorhergegangen post zu lesen @latzi um hilfreiche Lösungen zu bieten und nicht einfach was in den Raum zu schmeißen. Danke

                  wendy2702 1 Reply Last reply Reply Quote 0
                  • Mr. Qi
                    Mr. Qi last edited by

                    Update :
                    jetzt habe ich mich mal mit der fix und dem npm cach befasst:

                    Iobroker stop
                    
                    Iobroker fix 
                    
                    npm cache clean - - force
                    
                    (hier ist aufgefallen das ich bei npm noch nicht uptodate war eigendlich war ich der meinung vollständig uptodate zusein. Ich war noch auf npm 6.14.12) 
                    
                    npm install -g npm (7.9. 0)
                    
                    Und das ganze noch mal von vorn. 
                    Zum Abschluss :
                    
                    Iobroker update 
                    Iobroker upgrade
                    Iobroker rebuild self 
                    
                    

                    Ich hab es singer weiß auf beiden system ausgeführt ohne erfolg der fehler bleibt.

                    Thomas Braun wendy2702 2 Replies Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Mr. Qi last edited by

                      @mr-qi

                      Nein, bitte NICHT manuell global auf npm@7 updaten. Das funktioniert mit vielen Adaptern noch nicht richtig.

                      Mr. Qi 1 Reply Last reply Reply Quote 0
                      • Mr. Qi
                        Mr. Qi @Thomas Braun last edited by Mr. Qi

                        @thomas-braun
                        OH OK der Text bei npm cach war so eindeutig das ich dachte es wäre rel. Dan wieder zurück auf npm 6.14.12?

                        Screenshot_20210411_165036_com.sonelli.juicessh.jpg

                        UPS ja im link steht es ja releases/tag oder ander dayli XD das könnte man wirklich offensichtlicher machen.
                        an so einem info text wird dan wieder gespart.

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Mr. Qi last edited by Thomas Braun

                          @mr-qi

                          Ein Punkt im username ist eine sichere Quelle für Fehler.

                          Irgendwie kann ich deinen Postings nur schwer folgen. Bitte klarer formulieren.

                          1 Reply Last reply Reply Quote 1
                          • wendy2702
                            wendy2702 @Mr. Qi last edited by

                            @mr-qi sagte in Probleme mit multihost slave nach node.js update:

                            Unteranderem hilft es die vorhergegangen post zu lesen @latzi um hilfreiche Lösungen zu bieten und nicht einfach was in den Raum zu schmeißen.

                            Sorry, du vergreifst dich aus meiner Sicht gerade etwas im Ton.

                            Du stellst eine Frage und man versucht auf freiwilliger Basis zu helfen. Das mit dem Copy & Paste ist schließlich dein Fehler gewesen und ich hätte dir dasselbe wie @Latzi geantwortet und bin mir sicher das du diese Antwort von einigen bekommen hättest.

                            Mr. Qi 1 Reply Last reply Reply Quote 0
                            • wendy2702
                              wendy2702 @Mr. Qi last edited by

                              @mr-qi sagte in Probleme mit multihost slave nach node.js update:

                              Iobroker update Iobroker upgrade Iobroker rebuild self

                              Was tippst du da eigentlich ein bzw was genau soll das Ziel sein ?

                              Wieso nach dem fixer wieder Update?

                              Ich habe jetzt den Überblick verloren auf welchem Stand dein System ist und kann auch keine Antworten auf meine Fragen finden.

                              1 Reply Last reply Reply Quote 0
                              • Mr. Qi
                                Mr. Qi @wendy2702 last edited by

                                @wendy2702
                                @Thomas-Braun
                                Ja. Ja schon klar geb ich ja zu ich hab es nicht böse gemeint aber langsam kommt hier ein Knoten rein und das Ziel bleibt auf der Strecke.

                                Fackt ist

                                Ein funktionierender im vollen Umfang genutzter Rpi4 iobroker Master und ein Rpi3b Slave im multihost tun es nicht mehr.

                                Letzte Woche war der 2 Jahrestag des Broker und das soweit fehlerfrei. MULTIHOST confg eingeschlossen.

                                Im Laufe des Wochenende habe ich das Update von node.js 12.22.1 eingespielt anführsich keine große sache.
                                seid dem blinkt der Slave im Host menü grün und rot und ich habe im log verbindungsfehler:

                                Hier das log vom Master Rpi4

                                2021-04-09 20:14:23.749 - warn: javascript.0 (1070) getState "tado.0.526573.Rooms.5.Actual_Temperature" not found (3) states[id]=null
                                2021-04-09 20:14:23.780 - warn: javascript.0 (1070) at Object. (script.js.meineSkripte.VIS.Temperatur.TempKorri:8:37)
                                2021-04-09 20:14:23.781 - warn: javascript.0 (1070) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1075:38)
                                2021-04-09 20:14:23.781 - warn: javascript.0 (1070) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:502:29)
                                2021-04-09 20:14:23.782 - warn: javascript.0 (1070) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5555:41)
                                2021-04-09 20:14:23.782 - warn: javascript.0 (1070) at processImmediate (internal/timers.js:461:21)
                                2021-04-09 20:14:24.063 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
                                2021-04-09 20:14:25.154 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
                                2021-04-09 20:14:25.211 - info: tado.0 (1071) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
                                2021-04-09 20:14:30.715 - warn: host.IobrokerMaster "system.host.IobrokerSlave" is offline
                                2021-04-09 20:14:44.076 - info: alexa2.0 (1171) Subscribing to states...
                                2021-04-09 20:14:44.081 - info: alexa2.0 (1171) Deleting the following states: ["Echo-Devices.G0W19D04019407VG.Alarm","Echo-Devices.G0W19D04019407VG.Timer","Echo-Devices.G0W19D04019407VG.Alarm.New","Echo-Devices.G0W19D04019407VG.Timer.triggered"]
                                2021-04-09 20:15:50.053 - info: web.0 (1170) <==Disconnect system.user.admin from ::ffff:192.168.178.190 vis.0
                                2021-04-09 20:15:50.067 - info: web.0 (1170) <==Disconnect system.user.admin from ::ffff:192.168.178.190 vis.0
                                2021-04-09 20:17:51.443 - info: tado.0 (1071) Temperature changed for room : 8 in home : 526573 to API with : 23
                                2021-04-09 20:17:55.527 - info: tado.0 (1071) Overlay cleared for room : 8 in home : 526573
                                2021-04-09 20:18:02.670 - info: tado.0 (1071) Temperature changed for room : 1 in home : 526573 to API with : 23
                                2021-04-09 20:21:09.792 - error: host.IobrokerMaster-Server Cannot save backup file /opt/iobroker/iobroker-data/objects.json.bak: ENOENT: no such file or directory, rename '/opt/iobroker/iobroker-data/objects.json' -> '/opt/iobroker/iobroker-data/objects.json.bak'
                                2021-04-09 20:24:37.063 - info: host.IobrokerMaster Multihost discovery server stopped after 15 minutes, because only temporarily activated
                                2021-04-09 20:30:00.083 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 1888
                                2021-04-09 20:30:02.133 - info: ical.0 (1888) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 20:30:02.515 - info: ical.0 (1888) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
                                2021-04-09 20:30:07.604 - info: ical.0 (1888) Terminated (NO_ERROR): Without reason
                                2021-04-09 20:30:08.129 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2021-04-09 20:44:39.006 - info: tado.0 (1071) Temperature changed for room : 5 in home : 526573 to API with : 23
                                2021-04-09 21:00:00.032 - info: tado.0 (1071) Scheduled restart.
                                2021-04-09 21:00:00.036 - info: tado.0 (1071) cleaned everything up...
                                2021-04-09 21:00:00.042 - info: tado.0 (1071) terminating
                                2021-04-09 21:00:00.048 - info: tado.0 (1071) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 21:00:00.101 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2041
                                2021-04-09 21:00:00.684 - info: host.IobrokerMaster instance system.adapter.tado.0 scheduled normal terminated and will be restarted on schedule.
                                2021-04-09 21:00:00.685 - info: host.IobrokerMaster Restart adapter system.adapter.tado.0 because enabled
                                2021-04-09 21:00:01.713 - info: host.IobrokerMaster instance system.adapter.tado.0 started with pid 2052
                                2021-04-09 21:00:02.206 - info: ical.0 (2041) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 21:00:02.574 - info: ical.0 (2041) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
                                2021-04-09 21:00:03.635 - info: tado.0 (2052) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.tado, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 21:00:04.312 - info: tado.0 (2052) Connected to Tado cloud, initialyzing ...
                                2021-04-09 21:00:07.676 - info: ical.0 (2041) Terminated (NO_ERROR): Without reason
                                2021-04-09 21:00:08.203 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2021-04-09 21:00:10.671 - info: tado.0 (2052) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
                                2021-04-09 21:06:53.760 - info: web.0 (1170) <==Disconnect system.user.admin from ::ffff:192.168.178.23 vis.0
                                2021-04-09 21:20:00.034 - info: tado.0 (2052) Scheduled restart.
                                2021-04-09 21:20:00.041 - info: tado.0 (2052) cleaned everything up...
                                2021-04-09 21:20:00.045 - info: tado.0 (2052) terminating
                                2021-04-09 21:20:00.049 - info: tado.0 (2052) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 21:20:00.648 - info: host.IobrokerMaster instance system.adapter.tado.0 scheduled normal terminated and will be restarted on schedule.
                                2021-04-09 21:20:00.653 - info: host.IobrokerMaster Restart adapter system.adapter.tado.0 because enabled
                                2021-04-09 21:20:01.717 - info: host.IobrokerMaster instance system.adapter.tado.0 started with pid 2154
                                2021-04-09 21:20:03.592 - info: tado.0 (2154) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.tado, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 21:20:04.236 - info: tado.0 (2154) Connected to Tado cloud, initialyzing ...
                                2021-04-09 21:20:10.219 - info: tado.0 (2154) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
                                2021-04-09 21:30:00.044 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2211
                                2021-04-09 21:30:02.214 - info: ical.0 (2211) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 21:30:02.587 - info: ical.0 (2211) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
                                2021-04-09 21:30:07.683 - info: ical.0 (2211) Terminated (NO_ERROR): Without reason
                                2021-04-09 21:30:08.234 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2021-04-09 21:40:00.037 - info: tado.0 (2154) Scheduled restart.
                                2021-04-09 21:40:00.045 - info: tado.0 (2154) cleaned everything up...
                                2021-04-09 21:40:00.051 - info: tado.0 (2154) terminating
                                2021-04-09 21:40:00.055 - info: tado.0 (2154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 21:40:00.926 - info: host.IobrokerMaster instance system.adapter.tado.0 scheduled normal terminated and will be restarted on schedule.
                                2021-04-09 21:40:00.930 - info: host.IobrokerMaster Restart adapter system.adapter.tado.0 because enabled
                                2021-04-09 21:40:01.989 - info: host.IobrokerMaster instance system.adapter.tado.0 started with pid 2357
                                2021-04-09 21:40:03.743 - info: tado.0 (2357) starting. Version 0.2.5 in /opt/iobroker/node_modules/iobroker.tado, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 21:40:04.328 - info: tado.0 (2357) Connected to Tado cloud, initialyzing ...
                                2021-04-09 21:40:10.237 - info: tado.0 (2357) Initialisation finished, connected to Tado Cloud service refreshing every : 15 seconds
                                2021-04-09 21:48:21.492 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.23
                                2021-04-09 21:48:43.697 - info: tado.0 (2357) Overlay cleared for room : 1 in home : 526573
                                2021-04-09 21:59:36.091 - info: tado.0 (2357) Overlay cleared for room : 5 in home : 526573
                                2021-04-09 22:00:00.046 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2474
                                2021-04-09 22:00:02.741 - info: ical.0 (2474) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 22:00:03.089 - info: ical.0 (2474) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
                                2021-04-09 22:00:08.181 - info: ical.0 (2474) Terminated (NO_ERROR): Without reason
                                2021-04-09 22:00:08.705 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2021-04-09 22:30:00.044 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2683
                                2021-04-09 22:30:02.058 - info: ical.0 (2683) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 22:30:02.279 - info: ical.0 (2683) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
                                2021-04-09 22:30:02.295 - error: trashschedule.0 (1109) no events found in iCal instance - check configuration and restart adapter
                                2021-04-09 22:30:07.301 - info: ical.0 (2683) Terminated (NO_ERROR): Without reason
                                2021-04-09 22:30:07.853 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2021-04-09 23:00:00.135 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 2813
                                2021-04-09 23:00:02.178 - info: ical.0 (2813) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 23:00:02.516 - info: ical.0 (2813) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
                                2021-04-09 23:00:07.605 - info: ical.0 (2813) Terminated (NO_ERROR): Without reason
                                2021-04-09 23:00:08.155 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2021-04-09 23:30:00.226 - info: host.IobrokerMaster instance system.adapter.ical.0 started with pid 3033
                                2021-04-09 23:30:02.241 - info: ical.0 (3033) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.1, js-controller: 3.2.16
                                2021-04-09 23:30:02.590 - info: ical.0 (3033) processing URL: Müll https://calendar.google.com/calendar/ical/s4ui58n39mbeq04597iktdkar8%40group.calendar.google.com/private-f698ad83a3b8024b21ec878526820fa0/basic.ics
                                2021-04-09 23:30:07.679 - info: ical.0 (3033) Terminated (NO_ERROR): Without reason
                                2021-04-09 23:30:08.231 - info: host.IobrokerMaster instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                                2021-04-09 23:46:19.669 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
                                2021-04-09 23:46:21.987 - info: web.0 (1170) ==>Connected system.user.admin from ::ffff:192.168.178.190
                                2021-04-09 23:46:22.585 - warn: host.IobrokerMaster "system.host.IobrokerSlave" is offline
                                2021-04-09 23:50:01.672 - error: tr-064.1 (1085) States database error: read ECONNRESET
                                2021-04-09 23:50:01.684 - error: lgtv.0 (992) States database error: read ECONNRESET
                                2021-04-09 23:50:01.686 - error: fritzdect.0 (1045) States database error: read ECONNRESET
                                2021-04-09 23:50:01.689 - error: alexa2.0 (1171) States database error: read ECONNRESET
                                2021-04-09 23:50:01.693 - error: trashschedule.0 (1109) States database error: read ECONNRESET
                                2021-04-09 23:50:01.699 - error: history.0 (1052) States database error: read ECONNRESET
                                2021-04-09 23:50:01.670 - error: info.0 (1053) States database error: read ECONNRESET
                                2021-04-09 23:50:01.694 - error: tr-064.2 (1086) States database error: read ECONNRESET
                                2021-04-09 23:50:01.678 - error: backitup.0 (978) States database error: read ECONNRESET
                                2021-04-09 23:50:01.714 - error: javascript.0 (1070) States database error: read ECONNRESET
                                2021-04-09 23:50:01.677 - error: web.0 (1170) States database error: read ECONNRESET
                                2021-04-09 23:50:01.723 - error: asuswrt.0 (971) States database error: read ECONNRESET
                                2021-04-09 23:50:01.705 - error: admin.0 (1014) States database error: read ECONNRESET
                                2021-04-09 23:50:01.732 - error: echarts.0 (985) States database error: read ECONNRESET
                                2021-04-09 23:50:01.704 - error: host.IobrokerMaster States database error: read ECONNRESET
                                2021-04-09 23:50:01.713 - error: upnp.0 (995) States database error: read ECONNRESET
                                2021-04-09 23:50:01.716 - error: tr-064.0 (1084) States database error: read ECONNRESET
                                2021-04-09 23:50:01.727 - error: vis-inventwo.0 (1120) States database error: read ECONNRESET
                                2021-04-09 23:50:06.696 - info: lgtv.0 (992) Objects database successfully reconnected
                                2021-04-09 23:50:06.697 - info: fritzdect.0 (1045) Objects database successfully reconnected
                                2021-04-09 23:50:06.714 - info: trashschedule.0 (1109) Objects database successfully reconnected
                                2021-04-09 23:50:06.733 - info: asuswrt.0 (971) Objects database successfully reconnected
                                2021-04-09 23:50:06.744 - info: tr-064.2 (1086) Objects database successfully reconnected
                                2021-04-09 23:50:06.751 - info: web.0 (1170) Objects database successfully reconnected
                                2021-04-09 23:50:06.744 - info: vis-inventwo.0 (1120) Objects database successfully reconnected
                                2021-04-09 23:50:06.751 - info: history.0 (1052) Objects database successfully reconnected
                                2021-04-09 23:50:06.751 - info: echarts.0 (985) Objects database successfully reconnected
                                2021-04-09 23:50:06.758 - info: alexa2.0 (1171) Objects database successfully reconnected
                                2021-04-09 23:50:06.773 - info: javascript.0 (1070) Objects database successfully reconnected
                                2021-04-09 23:50:06.775 - info: info.0 (1053) Objects database successfully reconnected
                                2021-04-09 23:50:06.727 - info: backitup.0 (978) Objects database successfully reconnected
                                2021-04-09 23:50:06.781 - info: tr-064.1 (1085) Objects database successfully reconnected
                                2021-04-09 23:50:06.787 - info: upnp.0 (995) Objects database successfully reconnected
                                2021-04-09 23:50:06.794 - info: admin.0 (1014) Objects database successfully reconnected
                                2021-04-09 23:50:06.802 - info: host.IobrokerMaster Objects database successfully reconnected
                                2021-04-09 23:50:06.790 - info: tr-064.0 (1084) Objects database successfully reconnected
                                2021-04-09 23:54:45.811 - info: backitup.0 (978) cleaned everything up...
                                2021-04-09 23:54:45.810 - info: fritzdect.0 (1045) cleaned everything up...
                                2021-04-09 23:54:45.819 - info: vis-inventwo.0 (1120) cleaned everything up...
                                2021-04-09 23:54:45.825 - info: vis-inventwo.0 (1120) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.815 - info: fritzdect.0 (1045) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.826 - info: tr-064.1 (1085) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.830 - info: info.0 (1053) cleaned everything up...
                                2021-04-09 23:54:45.832 - info: upnp.0 (995) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.836 - info: trashschedule.0 (1109) cleaned everything up...
                                2021-04-09 23:54:45.844 - info: alexa2.0 (1171) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.845 - info: lgtv.0 (992) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.827 - info: asuswrt.0 (971) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.835 - info: tr-064.2 (1086) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.849 - info: admin.0 (1014) terminating http server on port 8081
                                2021-04-09 23:54:45.850 - info: javascript.0 (1070) Stop script script.js.meineSkripte.VIS.Heizung.Heizung_Auto_Manuel
                                2021-04-09 23:54:45.851 - info: lgtv.1 (993) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.850 - info: info.0 (1053) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.856 - info: trashschedule.0 (1109) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.840 - info: web.0 (1170) terminated http server on port 8082
                                2021-04-09 23:54:45.857 - info: admin.0 (1014) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2021-04-09 23:54:45.856 - info: backitup.0 (978) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                

                                Hier das log vom Slave

                                master.admin@IobrokerSlave:~ $ iobroker logs
                                
                                2021-04-10 22:20:08.939  - info: host.IobrokerSlave iobroker.js-controller version 3.2.16 js-controller starting
                                2021-04-10 22:20:08.947  - info: host.IobrokerSlave Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                                2021-04-10 22:20:08.948  - info: host.IobrokerSlave hostname: IobrokerSlave, node: v12.22.1
                                2021-04-10 22:20:08.949  - info: host.IobrokerSlave ip addresses: 192.168.178.29 2001:4dd4:1f53:0:b759:2505:bb8b:2763 fe80::ebd8:7d12:20c5:ad6e 192.168.178.36 2001:4dd4:1f53:0:2403:815c:196b:b0c fe80::3249:f072:1cc:e47
                                2021-04-10 22:20:09.145  - info: host.IobrokerSlave connected to Objects and States
                                2021-04-10 22:20:09.177  - info: host.IobrokerSlave added notifications configuration of host
                                2021-04-10 22:20:09.746  - error: host.IobrokerSlave uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
                                2021-04-10 22:20:09.747  - error: host.IobrokerSlave Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
                                    at Decipheriv.final (internal/crypto/cipher.js:172:29)
                                    at Object.decrypt (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:1867:79)
                                    at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:202:46)
                                    at processImmediate (internal/timers.js:463:21)
                                2021-04-10 22:20:09.760  - info: host.IobrokerSlave iobroker _restart
                                2021-04-10 22:20:09.806  - warn: host.IobrokerSlave Cannot get view: Connection is closed.
                                2021-04-10 22:20:09.807  - warn: host.IobrokerSlave Cannot get view: Connection is closed.
                                2021-04-10 22:20:09.819  - info: host.IobrokerSlave no instances found
                                2021-04-10 22:20:09.824  - error: host.IobrokerSlave Cannot write host object:Error: DB closed
                                2021-04-10 22:20:09.827  - info: host.IobrokerSlave terminated
                                2021-04-10 22:20:11.708  - info: host.IobrokerSlave iobroker.js-controller version 3.2.16 js-controller starting
                                2021-04-10 22:20:11.716  - info: host.IobrokerSlave Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
                                2021-04-10 22:20:11.717  - info: host.IobrokerSlave hostname: IobrokerSlave, node: v12.22.1
                                2021-04-10 22:20:11.718  - info: host.IobrokerSlave ip addresses: 192.168.178.29 2001:4dd4:1f53:0:b759:2505:bb8b:2763 fe80::ebd8:7d12:20c5:ad6e 192.168.178.36 2001:4dd4:1f53:0:2403:815c:196b:b0c fe80::3249:f072:1cc:e47
                                2021-04-10 22:20:11.909  - info: host.IobrokerSlave connected to Objects and States
                                2021-04-10 22:20:11.942  - info: host.IobrokerSlave added notifications configuration of host
                                2021-04-10 22:20:12.565  - error: host.IobrokerSlave uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
                                2021-04-10 22:20:12.567  - error: host.IobrokerSlave Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
                                    at Decipheriv.final (internal/crypto/cipher.js:172:29)
                                    at Object.decrypt (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:1867:79)
                                    at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/main.js:202:46)
                                    at processImmediate (internal/timers.js:463:21)
                                

                                auf die ausage von @wendy2702 habe ich den multihost noch mal reconfiguriert. Ohne Erfolg

                                Anschließend hab ich noch in iobroker fix durchgeführt und den Fehler mit dem npm gemacht Anfänger Fehler zwei mal denken einmal tippen.

                                Ich weiß das das mit dem npm nicht so einfach war wieder zurück zu gehen ich finde aber gerade nicht
                                Die Anleitung nicht dazu komisch. Weir kann mir sagen wie ich sicher wieder auf das gängige npm zurück komme

                                Danke dafür

                                wendy2702 1 Reply Last reply Reply Quote 0
                                • wendy2702
                                  wendy2702 @Mr. Qi last edited by

                                  @mr-qi sagte in Probleme mit multihost slave nach node.js update:

                                  Die Anleitung nicht dazu komisch. Weir kann mir sagen wie ich sicher wieder auf das gängige npm zurück komme

                                  Schau mal in die Signatur von @Thomas-Braun

                                  Nochmal, mit den Befehlen die du im ersten Post geschrieben hast machst du auch ein Update vom JS-Controller. Hierbei ist bei Master-Slave Systemen die Reihenfolge wichtig.

                                  Wenn du nur Node updaten willst reicht das

                                  apt update 
                                  apt upgrade 
                                  

                                  Wenn du schon eine Version 12.x hast.

                                  Sonnst vorher noch die Paketquellen anpassen.

                                  Mr. Qi 1 Reply Last reply Reply Quote 0
                                  • Mr. Qi
                                    Mr. Qi @wendy2702 last edited by

                                    @wendy2702

                                    OK also habe ich bei der update Reihenfolge was falsch gemacht ja es ging nur um node.js eigendlich.

                                    Hab aber in dem ahtemzug soweit alles auf stand gebracht und mich irgendwo verdattelt also ist die such nach dem fehler eine nadel im Heuhaufen.

                                    Was meint ihr neu aufspielen und backup laden?
                                    Vollständiges Backup vorhanden!

                                    wendy2702 1 Reply Last reply Reply Quote 0
                                    • wendy2702
                                      wendy2702 @Mr. Qi last edited by

                                      @mr-qi Weißt du noch welche JS-Controller Version vorher lief?

                                      Wenn du Backup hast, auch vom Slave mach mal auf dem Slave

                                      
                                      sudo -H -u iobroker npm install iobroker.js-controller
                                      
                                      
                                      Mr. Qi 2 Replies Last reply Reply Quote 0
                                      • Mr. Qi
                                        Mr. Qi @wendy2702 last edited by

                                        @wendy2702
                                        Moment jetzt sind wir beim js-controller der Fehler trat aber beim node.js update auf. alles andere war auf dem aktuellsten Stand vorher schon da lief aber alles.

                                        Ja ich habe full backup vom Master und Slave.
                                        Hier die Ausgabe von Slave mit deiner Eingabe:

                                        Linux IobrokerSlave 5.10.17-v7+ #1403 SMP Mon Feb 22 11:29:51 GMT 2021 armv7l
                                        
                                        The programs included with the Debian GNU/Linux system are free software;
                                        the exact distribution terms for each program are described in the
                                        individual files in /usr/share/doc/*/copyright.
                                        
                                        Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
                                        permitted by applicable law.
                                        Last login: Sun Apr 11 17:24:23 2021 from 192.168.178.31
                                        master.admin@IobrokerSlave:~ $ sudo -H -u iobroker npm install iobroker.js-controller
                                        [sudo] password for master.admin:
                                        npm ERR! code EACCES
                                        npm ERR! syscall mkdir
                                        npm ERR! path /home/master.admin/node_modules
                                        npm ERR! errno -13
                                        npm ERR! Error: EACCES: permission denied, mkdir '/home/master.admin/node_modules'
                                        npm ERR!  [Error: EACCES: permission denied, mkdir '/home/master.admin/node_modules'] {
                                        npm ERR!   errno: -13,
                                        npm ERR!   code: 'EACCES',
                                        npm ERR!   syscall: 'mkdir',
                                        npm ERR!   path: '/home/master.admin/node_modules'
                                        npm ERR! }
                                        npm ERR!
                                        npm ERR! The operation was rejected by your operating system.
                                        npm ERR! It is likely you do not have the permissions to access this file as the current user
                                        npm ERR!
                                        npm ERR! If you believe this might be a permissions issue, please double-check the
                                        npm ERR! permissions of the file and its containing directories, or try running
                                        npm ERR! the command again as root/Administrator.
                                        
                                        npm ERR! A complete log of this run can be found in:
                                        npm ERR!     /home/iobroker/.npm/_logs/2021-04-11T16_27_21_321Z-debug.log
                                        master.admin@IobrokerSlave:~ $
                                        
                                        wendy2702 1 Reply Last reply Reply Quote 0
                                        • wendy2702
                                          wendy2702 @Mr. Qi last edited by

                                          @mr-qi Sorry,

                                          Du muss vorher natürlich ins iobroker Verzeichnis wechseln:

                                          cd/opt/iobroker
                                          

                                          Du hast aber mit den Befehlen auch den Controller upgedated sollte der nicht auf dem aktuellen Stand gewesen sein.

                                          Deshalb hier meine Frage:

                                          @wendy2702 sagte in Probleme mit multihost slave nach node.js update:

                                          @mr-qi Weißt du noch welche JS-Controller Version vorher lief?

                                          Mr. Qi 1 Reply Last reply Reply Quote 0
                                          • Mr. Qi
                                            Mr. Qi @wendy2702 last edited by Mr. Qi

                                            @wendy2702

                                            Noch mal vorweg ich bin kein Pro ich kann etwas mehr als ein Anfänger aber nicht genug zum supporten XD

                                            Also ich hab es im Verzeichnis iobroker ausgeführt und er hat zwei packages geadded

                                            Update: keine Verbesserung bis jetzt der Fehler bleibt.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            756
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            crypto-js multihost verbindung multihostbetrieb node.js node node.js update
                                            5
                                            36
                                            2726
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo