Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 4.0 jetzt im BETA/LATEST!

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 4.0 jetzt im BETA/LATEST!

    This topic has been deleted. Only users with topic management privileges can see it.
    • gelberlemmy
      gelberlemmy @apollon77 last edited by

      @apollon77 ich habe einmal die Errors heraus gezogen. Erst einmal nach einem Neustart von IOBroker :

      
      admin.0
      2022-02-22 20:31:13.713	error	error
      
      shelly.0
      2022-02-22 20:30:43.805	error	DB closed
      
      shelly.0
      2022-02-22 20:30:43.805	error	Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:475:12) at TCP.<anonymous> (net.js:686:12)
      
      shelly.0
      2022-02-22 20:30:43.799	error	unhandled promise rejection: DB closed
      
      shelly.0
      2022-02-22 20:30:43.799	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      
      
      
      Zeile 562: 2022-02-22 03:16:28.032 - error: homeconnect.0 (1264) EventSource error: {"type":"error"}
      	Zeile 562: 2022-02-22 03:16:28.032 - error: homeconnect.0 (1264) EventSource error: {"type":"error"}
      	Zeile 564: 2022-02-22 03:16:28.085 - error: homeconnect.0 (1264) EventSource error: {"type":"error"}
      	Zeile 564: 2022-02-22 03:16:28.085 - error: homeconnect.0 (1264) EventSource error: {"type":"error"}
      	Zeile 566: 2022-02-22 03:16:29.218 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"}
      	Zeile 566: 2022-02-22 03:16:29.218 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"}
      	Zeile 567: 2022-02-22 03:16:29.219 - error: homeconnect.0 (1264) 401 Unauthorized
      	Zeile 568: 2022-02-22 03:16:29.219 - error: homeconnect.0 (1264) Error (SIEMENS-HB678GBS6-68A40E16D548)
      	Zeile 570: 2022-02-22 03:16:29.222 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"}
      	Zeile 570: 2022-02-22 03:16:29.222 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"}
      	Zeile 571: 2022-02-22 03:16:29.223 - error: homeconnect.0 (1264) 401 Unauthorized
      	Zeile 572: 2022-02-22 03:16:29.227 - error: homeconnect.0 (1264) Error (SIEMENS-SN658X06TE-68A40E1BED72)
      	Zeile 1885: 2022-02-22 09:55:02.967 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1887: 2022-02-22 09:55:08.088 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1888: 2022-02-22 09:55:13.194 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1889: 2022-02-22 09:55:18.315 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1890: 2022-02-22 09:55:23.445 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1891: 2022-02-22 09:55:28.532 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1892: 2022-02-22 09:55:33.622 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1894: 2022-02-22 09:55:38.734 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1895: 2022-02-22 09:55:43.839 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1896: 2022-02-22 09:55:48.937 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1897: 2022-02-22 09:55:54.029 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 1898: 2022-02-22 09:55:59.118 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026
      	Zeile 2085: 2022-02-22 11:00:22.028 - warn: ical.0 (3185) get state error: Connection is closed.
      	Zeile 3263: 2022-02-22 16:53:03.553 - error: admin.0 (302) failed connection to socket.io from ::ffff:192.168.171.68:
      	Zeile 3264: 2022-02-22 16:53:03.558 - error: admin.0 (302) error
      	Zeile 3440: 2022-02-22 17:00:29.873 - error: cloud.0 (1170) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud
      	Zeile 3465: 2022-02-22 17:02:11.084 - error: cloud.0 (1170) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud
      	Zeile 3482: 2022-02-22 17:02:12.295 - error: cloud.0 (1170) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud
      	Zeile 4020: 2022-02-22 19:39:51.929 - error: admin.0 (3951) failed connection to socket.io from ::ffff:192.168.171.75:
      	Zeile 4021: 2022-02-22 19:39:51.934 - error: admin.0 (3951) error
      	Zeile 4200: 2022-02-22 20:00:36.184 - warn: ical.0 (4296) get state error: Connection is closed.
      	Zeile 4201: 2022-02-22 20:00:36.193 - warn: ical.0 (4296) get state error: DB closed
      	Zeile 4296: 2022-02-22 20:02:55.007 - error: mihome-vacuum.0 (535) Socket Close
      	Zeile 4475: 2022-02-22 20:02:56.762 - warn: shelly.0 (604) get state error: Connection is closed.
      	Zeile 4476: 2022-02-22 20:02:56.889 - warn: shelly.0 (604) get state error: Connection is closed.
      	Zeile 4477: 2022-02-22 20:02:56.890 - warn: shelly.0 (604) get state error: Connection is closed.
      	Zeile 4481: 2022-02-22 20:02:56.998 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#68C63AF991B6#1.Relay1.ChannelName for 192.168.171.7 (shellyswitch25 / shellyswitch25-68C63AF991B6 / SHSW-25#68C63AF991B6#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}"
      	Zeile 4481: 2022-02-22 20:02:56.998 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#68C63AF991B6#1.Relay1.ChannelName for 192.168.171.7 (shellyswitch25 / shellyswitch25-68C63AF991B6 / SHSW-25#68C63AF991B6#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}"
      	Zeile 4483: 2022-02-22 20:02:57.000 - warn: shelly.0 (604) get state error: Connection is closed.
      	Zeile 4485: 2022-02-22 20:02:57.001 - warn: shelly.0 (604) get state error: Connection is closed.
      	Zeile 4486: 2022-02-22 20:02:57.004 - error: shelly.0 (604) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4487: 2022-02-22 20:02:57.004 - error: shelly.0 (604) unhandled promise rejection: DB closed
      	Zeile 4488: 2022-02-22 20:02:57.015 - error: shelly.0 (604) Error: DB closed
      	Zeile 4488: 2022-02-22 20:02:57.015 - error: shelly.0 (604) Error: DB closed
      	Zeile 4493: 2022-02-22 20:02:57.015 - error: shelly.0 (604) DB closed
      	Zeile 4494: 2022-02-22 20:02:57.028 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.name for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"device":{"type":"SHSW-25","mac":"483FDA8DB8F7","hostname":"shellyswitch25-483FDA8DB8F7","num_outputs":2, "num_meters":2, "num_rollers":1},"wifi_ap":{"enabled":false,"ssid":"shellyswitch25-483FDA8DB8F7","key":""},"wifi_sta":{"enabled":true,"ssid":"Home_Lan","ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"ap_roaming":{"enabled":false,"threshold":-70},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellyswitch25-483FDA8DB8F7","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"max_qos":0,"retain":false,"update_period":30},"coiot": {"enabled":true,"update_period":15,"peer":""},"sntp":{"server":"time.google.com","enabled":true},"login":{"enabled":true,"unprotected":false,"username":"gelberlemmy"},"pin_code":"","name":null,"fw":"20220209-093016/v1.11.8-g8c7bb8d","factory_reset_from_switch":true,"discoverable":true,"build_info":{"build_id":"20220209-093016/v1.11.8-g8c7bb8d","build_timestamp":"2022-02-09T09:30:16Z","build_version":"1.0"},"cloud":{"enabled":false,"connected":false},"timezone":"Europe/Berlin","lat":52.464722,"lng":13.395710,"tzautodetect":true,"tz_utc_offset":3600,"tz_dst":false,"tz_dst_auto":true,"time":"21:02","unixtime":1645560176,"led_status_disable":false,"debug_enable":false,"allow_cross_origin":false,"actions":{"active":false,"names":["btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","roller_open_url","roller_close_url","roller_stop_url"]},"hwinfo":{"hw_revision":"prod-191217", "batch_id":1},"mode":"roller","max_power":1840,"l ...
      	Zeile 4494: 2022-02-22 20:02:57.028 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.name for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"device":{"type":"SHSW-25","mac":"483FDA8DB8F7","hostname":"shellyswitch25-483FDA8DB8F7","num_outputs":2, "num_meters":2, "num_rollers":1},"wifi_ap":{"enabled":false,"ssid":"shellyswitch25-483FDA8DB8F7","key":""},"wifi_sta":{"enabled":true,"ssid":"Home_Lan","ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"ap_roaming":{"enabled":false,"threshold":-70},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellyswitch25-483FDA8DB8F7","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"max_qos":0,"retain":false,"update_period":30},"coiot": {"enabled":true,"update_period":15,"peer":""},"sntp":{"server":"time.google.com","enabled":true},"login":{"enabled":true,"unprotected":false,"username":"gelberlemmy"},"pin_code":"","name":null,"fw":"20220209-093016/v1.11.8-g8c7bb8d","factory_reset_from_switch":true,"discoverable":true,"build_info":{"build_id":"20220209-093016/v1.11.8-g8c7bb8d","build_timestamp":"2022-02-09T09:30:16Z","build_version":"1.0"},"cloud":{"enabled":false,"connected":false},"timezone":"Europe/Berlin","lat":52.464722,"lng":13.395710,"tzautodetect":true,"tz_utc_offset":3600,"tz_dst":false,"tz_dst_auto":true,"time":"21:02","unixtime":1645560176,"led_status_disable":false,"debug_enable":false,"allow_cross_origin":false,"actions":{"active":false,"names":["btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","roller_open_url","roller_close_url","roller_stop_url"]},"hwinfo":{"hw_revision":"prod-191217", "batch_id":1},"mode":"roller","max_power":1840,"l ...
      	Zeile 4496: 2022-02-22 20:02:57.130 - warn: shelly.0 (604) get state error: Connection is closed.
      	Zeile 4498: 2022-02-22 20:02:57.130 - warn: shelly.0 (604) get state error: Connection is closed.
      	Zeile 4499: 2022-02-22 20:02:57.220 - warn: zwave2.0 (1798) get state error: Connection is closed.
      	Zeile 4500: 2022-02-22 20:02:57.236 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.Relay1.ChannelName for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}"
      	Zeile 4500: 2022-02-22 20:02:57.236 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.Relay1.ChannelName for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}"
      	Zeile 4502: 2022-02-22 20:02:57.256 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4504: 2022-02-22 20:02:57.269 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4506: 2022-02-22 20:02:57.270 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4508: 2022-02-22 20:02:57.270 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4510: 2022-02-22 20:02:57.271 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4512: 2022-02-22 20:02:57.272 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4514: 2022-02-22 20:02:57.272 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4516: 2022-02-22 20:02:57.273 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4518: 2022-02-22 20:02:57.274 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4520: 2022-02-22 20:02:57.290 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4522: 2022-02-22 20:02:57.291 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4524: 2022-02-22 20:02:57.292 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4526: 2022-02-22 20:02:57.292 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4528: 2022-02-22 20:02:57.293 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4530: 2022-02-22 20:02:57.294 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4532: 2022-02-22 20:02:57.294 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4534: 2022-02-22 20:02:57.295 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4536: 2022-02-22 20:02:57.296 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4538: 2022-02-22 20:02:57.296 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4540: 2022-02-22 20:02:57.297 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4542: 2022-02-22 20:02:57.297 - warn: device-reminder.0 (1188) get state error: Connection is closed.
      	Zeile 4543: 2022-02-22 20:02:57.311 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4544: 2022-02-22 20:02:57.311 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4545: 2022-02-22 20:02:57.314 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4545: 2022-02-22 20:02:57.314 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4553: 2022-02-22 20:02:57.315 - error: device-reminder.0 (1188) DB closed
      	Zeile 4554: 2022-02-22 20:02:57.316 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4555: 2022-02-22 20:02:57.317 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4556: 2022-02-22 20:02:57.338 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4556: 2022-02-22 20:02:57.338 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4564: 2022-02-22 20:02:57.339 - error: device-reminder.0 (1188) DB closed
      	Zeile 4565: 2022-02-22 20:02:57.340 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4566: 2022-02-22 20:02:57.340 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4567: 2022-02-22 20:02:57.341 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4567: 2022-02-22 20:02:57.341 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4575: 2022-02-22 20:02:57.341 - error: device-reminder.0 (1188) DB closed
      	Zeile 4576: 2022-02-22 20:02:57.342 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4577: 2022-02-22 20:02:57.342 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4578: 2022-02-22 20:02:57.470 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4578: 2022-02-22 20:02:57.470 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4586: 2022-02-22 20:02:57.471 - error: device-reminder.0 (1188) DB closed
      	Zeile 4587: 2022-02-22 20:02:57.471 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4588: 2022-02-22 20:02:57.472 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4589: 2022-02-22 20:02:57.472 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4589: 2022-02-22 20:02:57.472 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4597: 2022-02-22 20:02:57.473 - error: device-reminder.0 (1188) DB closed
      	Zeile 4598: 2022-02-22 20:02:57.473 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4599: 2022-02-22 20:02:57.478 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4600: 2022-02-22 20:02:57.480 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4600: 2022-02-22 20:02:57.480 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4608: 2022-02-22 20:02:57.480 - error: device-reminder.0 (1188) DB closed
      	Zeile 4609: 2022-02-22 20:02:57.482 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4610: 2022-02-22 20:02:57.482 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4611: 2022-02-22 20:02:57.483 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4611: 2022-02-22 20:02:57.483 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4619: 2022-02-22 20:02:57.483 - error: device-reminder.0 (1188) DB closed
      	Zeile 4620: 2022-02-22 20:02:57.484 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4621: 2022-02-22 20:02:57.484 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4622: 2022-02-22 20:02:57.485 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4622: 2022-02-22 20:02:57.485 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4630: 2022-02-22 20:02:57.485 - error: device-reminder.0 (1188) DB closed
      	Zeile 4631: 2022-02-22 20:02:57.488 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4632: 2022-02-22 20:02:57.488 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4633: 2022-02-22 20:02:57.495 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4633: 2022-02-22 20:02:57.495 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4641: 2022-02-22 20:02:57.495 - error: device-reminder.0 (1188) DB closed
      	Zeile 4642: 2022-02-22 20:02:57.496 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4643: 2022-02-22 20:02:57.496 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4644: 2022-02-22 20:02:57.497 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4644: 2022-02-22 20:02:57.497 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4652: 2022-02-22 20:02:57.497 - error: device-reminder.0 (1188) DB closed
      	Zeile 4653: 2022-02-22 20:02:57.498 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4654: 2022-02-22 20:02:57.498 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4655: 2022-02-22 20:02:57.500 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4655: 2022-02-22 20:02:57.500 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4663: 2022-02-22 20:02:57.500 - error: device-reminder.0 (1188) DB closed
      	Zeile 4664: 2022-02-22 20:02:57.501 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4665: 2022-02-22 20:02:57.501 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4666: 2022-02-22 20:02:57.502 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4666: 2022-02-22 20:02:57.502 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4674: 2022-02-22 20:02:57.502 - error: device-reminder.0 (1188) DB closed
      	Zeile 4675: 2022-02-22 20:02:57.503 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4676: 2022-02-22 20:02:57.503 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4677: 2022-02-22 20:02:57.504 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4677: 2022-02-22 20:02:57.504 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4685: 2022-02-22 20:02:57.504 - error: device-reminder.0 (1188) DB closed
      	Zeile 4686: 2022-02-22 20:02:57.505 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4687: 2022-02-22 20:02:57.505 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4688: 2022-02-22 20:02:57.506 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4688: 2022-02-22 20:02:57.506 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4696: 2022-02-22 20:02:57.507 - error: device-reminder.0 (1188) DB closed
      	Zeile 4697: 2022-02-22 20:02:57.507 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4698: 2022-02-22 20:02:57.508 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4699: 2022-02-22 20:02:57.509 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4699: 2022-02-22 20:02:57.509 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4707: 2022-02-22 20:02:57.509 - error: device-reminder.0 (1188) DB closed
      	Zeile 4708: 2022-02-22 20:02:57.510 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4709: 2022-02-22 20:02:57.510 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4710: 2022-02-22 20:02:57.511 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4710: 2022-02-22 20:02:57.511 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4718: 2022-02-22 20:02:57.511 - error: device-reminder.0 (1188) DB closed
      	Zeile 4719: 2022-02-22 20:02:57.512 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4720: 2022-02-22 20:02:57.512 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4721: 2022-02-22 20:02:57.513 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4721: 2022-02-22 20:02:57.513 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4729: 2022-02-22 20:02:57.514 - error: device-reminder.0 (1188) DB closed
      	Zeile 4730: 2022-02-22 20:02:57.514 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4731: 2022-02-22 20:02:57.515 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4732: 2022-02-22 20:02:57.516 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4732: 2022-02-22 20:02:57.516 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4740: 2022-02-22 20:02:57.516 - error: device-reminder.0 (1188) DB closed
      	Zeile 4741: 2022-02-22 20:02:57.517 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4742: 2022-02-22 20:02:57.517 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4743: 2022-02-22 20:02:57.518 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4743: 2022-02-22 20:02:57.518 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4751: 2022-02-22 20:02:57.518 - error: device-reminder.0 (1188) DB closed
      	Zeile 4752: 2022-02-22 20:02:57.519 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4753: 2022-02-22 20:02:57.519 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4754: 2022-02-22 20:02:57.520 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4754: 2022-02-22 20:02:57.520 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4762: 2022-02-22 20:02:57.521 - error: device-reminder.0 (1188) DB closed
      	Zeile 4763: 2022-02-22 20:02:57.521 - error: device-reminder.0 (1188) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      	Zeile 4764: 2022-02-22 20:02:57.522 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed
      	Zeile 4765: 2022-02-22 20:02:57.523 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4765: 2022-02-22 20:02:57.523 - error: device-reminder.0 (1188) Error: DB closed
      	Zeile 4770: 2022-02-22 20:02:57.523 - error: device-reminder.0 (1188) DB closed
      	Zeile 4870: 2022-02-22 20:06:58.836 - error: admin.0 (5100) error
      	Zeile 5007: 2022-02-22 20:07:52.287 - error: javascript.0 (5145) In file included from ../src/binding.cc:1:
      	Zeile 5070: 2022-02-22 20:08:07.578 - error: javascript.0 (5145) In file included from ../src/binding.cc:6:
      	Zeile 5361: 2022-02-22 20:08:38.905 - error: cloud.0 (5901) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud
      	Zeile 5375: 2022-02-22 20:08:46.490 - error: discovergy.0 (5932) State type : printedFullSerialNumber unknown, send this information to the developer ==> printedFullSerialNumber : "1ESY1161230212"
      	Zeile 5610: 2022-02-22 20:09:09.158 - error: cloud.0 (5901) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud
      apollon77 2 Replies Last reply Reply Quote 0
      • apollon77
        apollon77 @gelberlemmy last edited by

        @gelberlemmy naja ich bin ehrlich ... nur Fehler ist ein bissl einseitig weil jeglicher Kontext fehlt. Am besten wäre das log direkt ab dem Controller Start vollständig anzusehen.

        1 Reply Last reply Reply Quote 0
        • gelberlemmy
          gelberlemmy last edited by

          @apollon77 okay, wie besprochen kommt das LOG per Mail. Danke

          1 Reply Last reply Reply Quote 0
          • E
            e-i-k-e @apollon77 last edited by

            @apollon77

            Danke. Mit 3.3.22 lief es, nach eine update auf 4.0.15 (inkl. iobroker fix) startet iobroker auf dem Slave nicht und ich erhalte folgendes im log.

            host.raspberrypi-display2
            2022-02-22 22:29:31.337	info	iobroker Starting node restart.js
            host.raspberrypi-display2
            2022-02-22 22:29:29.205	info	instance system.adapter.javascript.4 started with pid 26229
            host.raspberrypi-display2
            2022-02-22 22:29:29.139	info	iobroker _restart
            host.raspberrypi-display2
            2022-02-22 22:29:29.130	info	stopInstance system.adapter.rpi2.2 (force=false, process=false)
            host.raspberrypi-display2
            2022-02-22 22:29:29.129	info	stopInstance system.adapter.javascript.4 (force=false, process=false)
            host.raspberrypi-display2
            2022-02-22 22:29:29.123	error	TypeError: Cannot read property '_id' of null at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3422:42 at Array.map (<anonymous>) at ObjectsInRedisClient._applyViewFunc (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:3414:39) at processTicksAndRejections (internal/process/task_queues.js:95:5)
            host.raspberrypi-display2
            2022-02-22 22:29:29.121	error	uncaught exception: Cannot read property '_id' of null
            host.raspberrypi-display2
            2022-02-22 22:29:28.433	info	starting 2 instances
            host.raspberrypi-display2
            2022-02-22 22:29:28.326	info	86 instances found
            host.raspberrypi-display2
            2022-02-22 22:29:21.213	info	All instances are stopped.
            host.raspberrypi-display2
            2022-02-22 22:29:21.212	info	instance system.adapter.javascript.4 terminated with code null ()
            host.raspberrypi-display2
            2022-02-22 22:29:21.210	warn	instance system.adapter.javascript.4 terminated due to SIGTERM
            host.raspberrypi-display2
            2022-02-22 22:29:20.756	info	iobroker exit null
            host.raspberrypi-display2
            2022-02-22 22:29:20.738	info	received SIGTERM
            host.raspberrypi-display2
            2022-02-22 22:29:20.192	info	iobroker Starting node restart.js
            host.raspberrypi-display2
            2022-02-22 22:29:18.247	info	instance system.adapter.javascript.4 started with pid 26179
            host.raspberrypi-display2
            2022-02-22 22:29:18.043	info	iobroker _restart
            
            foxriver76 1 Reply Last reply Reply Quote 0
            • foxriver76
              foxriver76 Developer @e-i-k-e last edited by

              @e-i-k-e Objekte in redis? Multihost?

              E 1 Reply Last reply Reply Quote 0
              • E
                e-i-k-e @foxriver76 last edited by

                @foxriver76
                Ja redis/redis und ist auch ein Multihost System.
                Wobei nur dieser Slave die probleme macht, die anderen 5 laufen wie gewohnt.

                foxriver76 1 Reply Last reply Reply Quote 0
                • foxriver76
                  foxriver76 Developer @e-i-k-e last edited by

                  @e-i-k-e zeig mal redis-cli get meta.objects.features.useSets

                  E 1 Reply Last reply Reply Quote 0
                  • E
                    e-i-k-e @foxriver76 last edited by

                    @foxriver76
                    "1"

                    foxriver76 1 Reply Last reply Reply Quote 0
                    • foxriver76
                      foxriver76 Developer @e-i-k-e last edited by foxriver76

                      @e-i-k-e redis-cli set meta.objects.features.useSets '0'

                      Dann sollte es gehen, da der eine Host kleiner 4 war und die anderen 4 und Sets anscheinend aktiv sind diese out of sync gegangen. Der war evtl schon mal kurz 4 und dadurch sind die Sets aktiviert worden und dann wieder 3.

                      foxriver76 1 Reply Last reply Reply Quote 1
                      • foxriver76
                        foxriver76 Developer @foxriver76 last edited by

                        wenn sets in multihost genutzt werden sollen, alle hosts stoppen iob object activateSets dann starten und nie wieder einen der hosts kleiner 4 machen bzw vorher sets deaktivieren.

                        1 Reply Last reply Reply Quote 1
                        • apollon77
                          apollon77 @gelberlemmy last edited by

                          @gelberlemmy Also das gesendete Log Zeigt solche "DB closed" fehler als der Controller beendet wurde und damit wären es adapter issues. ABer auch da ist es 20:03 Uhr wo das passiert ... dein Log hier ist 20:30 ... das ist in dem Log aus der Mail aber nicht drin ...

                          gelberlemmy 2 Replies Last reply Reply Quote 0
                          • gelberlemmy
                            gelberlemmy @apollon77 last edited by

                            @apollon77 okay, ich dachte ich habe alles wichtige mitgesendet. Ich schicke Dir einmal das ganze Log. Danke für Deine Mühe

                            1 Reply Last reply Reply Quote 1
                            • gelberlemmy
                              gelberlemmy @apollon77 last edited by

                              @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                              @gelberlemmy Also das gesendete Log Zeigt solche "DB closed" fehler als der Controller beendet wurde und damit wären es adapter issues. ABer auch da ist es 20:03 Uhr wo das passiert ... dein Log hier ist 20:30 ... das ist in dem Log aus der Mail aber nicht drin ...

                              Moin Apollon, so habe Dir das ganze Log von gestern gesendet. Habe dies direkt über ssh herunter geladen.

                              Gruß André

                              apollon77 1 Reply Last reply Reply Quote 0
                              • E
                                e-i-k-e last edited by Negalein

                                Erhalte soeben nach einem Neustart von ioBroker folgendes.

                                Error in GUI!
                                Please open the browser console (F12), copy error text from there and create the issue on github
                                Without this information it is not possible to analyse the error.
                                It should looks like
                                error
                                If in the second line you will see at :3000/static/js/main.chunk.js:36903 and not the normal file name,
                                please try to reproduce an error with opened browser console. In this case the special "map" files will be loaded and the developers can see the real name of functions and files.
                                Loading chunk 14 failed. (error: https://192.168.3.100:8081/static/js/14.b28d85a4.chunk.js)
                                ChunkLoadError: Loading chunk 14 failed.function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}(error: https://192.168.3.100:8081/static/js/14.b28d85a4.chunk.js)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Function.u.e (https://192.168.3.100:8081/:1:3973)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at https://192.168.3.100:8081/static/js/main.22a9d49c.chunk.js:2:1113786function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at V (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5666268)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Zi (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5656452)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at jl (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5643113)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Sl (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5643041)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Cl (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5642904)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at zl (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5639870)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5589364function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at t.unstable_runWithPriority (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5672574)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Ga (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5589141)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Ka (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5589309)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Za (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5589244)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at pl (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5637247)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Object.enqueueSetState (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5593262)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at o.m.setState (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5664084)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at https://192.168.3.100:8081/static/js/main.22a9d49c.chunk.js:2:1126466function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at u (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5676516)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Generator._invoke (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5676304)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at Generator.throw (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:5676945)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at r (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:35792)function(e,t){return Object(ze.jsxs)("div",{children:[e,Object(ze.jsx)("br",{})]},t)}    at l (https://192.168.3.100:8081/static/js/6.501acaca.chunk.js:2:36031)
                                
                                :8081/static/js/14.b28d85a4.chunk.js:1          Failed to load resource: net::ERR_CONNECTION_REFUSED
                                :8081/img/no-image.png:1          Failed to load resource: net::ERR_CONNECTION_REFUSED
                                browserError.png:1          Failed to load resource: net::ERR_CONNECTION_REFUSED
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649045191&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649047813&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                168instrument.ts:125 notConnectedError
                                (anonymous) @ instrument.ts:125
                                :8081/#tab-intro:1 Uncaught (in promise) timeout
                                800instrument.ts:125 notConnectedError
                                (anonymous) @ instrument.ts:125
                                instrument.ts:125 [2022-02-23T20:44:11.805Z] Try to connect
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649051805&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                instrument.ts:125 [2022-02-23T20:44:12.831Z] Start reconnect 3
                                instrument.ts:125 [2022-02-23T20:44:12.831Z] ws connection error: CLOSE_ABNORMAL
                                (anonymous) @ instrument.ts:125
                                instrument.ts:125 [2022-02-23T20:44:12.831Z] Reconnect is already running 3
                                instrument.ts:125 [2022-02-23T20:44:16.807Z] Try to connect
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649056825&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                instrument.ts:125 [2022-02-23T20:44:17.850Z] Start reconnect 4
                                instrument.ts:125 [2022-02-23T20:44:17.851Z] ws connection error: CLOSE_ABNORMAL
                                (anonymous) @ instrument.ts:125
                                instrument.ts:125 [2022-02-23T20:44:17.851Z] Reconnect is already running 4
                                instrument.ts:125 [2022-02-23T20:44:22.817Z] Try to connect
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649062840&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                instrument.ts:125 [2022-02-23T20:44:23.875Z] Start reconnect 5
                                instrument.ts:125 [2022-02-23T20:44:23.875Z] ws connection error: CLOSE_ABNORMAL
                                (anonymous) @ instrument.ts:125
                                instrument.ts:125 [2022-02-23T20:44:23.875Z] Reconnect is already running 5
                                instrument.ts:125 [2022-02-23T20:44:29.803Z] Try to connect
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649069820&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                instrument.ts:125 [2022-02-23T20:44:30.850Z] Start reconnect 5
                                instrument.ts:125 [2022-02-23T20:44:30.850Z] ws connection error: CLOSE_ABNORMAL
                                (anonymous) @ instrument.ts:125
                                instrument.ts:125 [2022-02-23T20:44:30.850Z] Reconnect is already running 5
                                instrument.ts:125 [2022-02-23T20:44:36.803Z] Try to connect
                                instrument.ts:125 [2022-02-23T20:44:40.804Z] No READY flag received in 3 seconds. Re-init
                                (anonymous) @ instrument.ts:125
                                socket.io.js:344 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649076827&name=admin' failed: WebSocket is closed before the connection is established.
                                SocketClient.close @ socket.io.js:344
                                instrument.ts:125 [2022-02-23T20:44:40.821Z] Start reconnect 5
                                instrument.ts:125 [2022-02-23T20:44:40.821Z] ws connection error: CLOSE_ABNORMAL
                                (anonymous) @ instrument.ts:125
                                2instrument.ts:125 [2022-02-23T20:44:40.821Z] Reconnect is already running 5
                                instrument.ts:125 [2022-02-23T20:44:46.804Z] Try to connect
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649086826&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                instrument.ts:125 [2022-02-23T20:44:47.882Z] Start reconnect 5
                                instrument.ts:125 [2022-02-23T20:44:47.882Z] ws connection error: CLOSE_ABNORMAL
                                (anonymous) @ instrument.ts:125
                                instrument.ts:125 [2022-02-23T20:44:47.882Z] Reconnect is already running 5
                                instrument.ts:125 [2022-02-23T20:44:53.805Z] Try to connect
                                socket.io.js:94 WebSocket connection to 'wss://192.168.3.100:8081/?sid=1645649093828&name=admin' failed: 
                                SocketClient.connect @ socket.io.js:94
                                instrument.ts:125 [2022-02-23T20:44:54.863Z] Start reconnect 5
                                instrument.ts:125 [2022-02-23T20:44:54.863Z] ws connection error: CLOSE_ABNORMAL
                                (anonymous) @ instrument.ts:125
                                instrument.ts:125 [2022-02-23T20:44:54.863Z] Reconnect is already running 5
                                instrument.ts:125 [2022-02-23T20:45:00.805Z] Try to connect
                                sentry.iobroker.net/api/58/envelope/?sentry_key=43643152dab3481db69950ba866ee9d6&sentry_version=7:1          Failed to load resource: the server responded with a status of 400 ()
                                
                                wendy2702 apollon77 2 Replies Last reply Reply Quote 0
                                • wendy2702
                                  wendy2702 @e-i-k-e last edited by

                                  @e-i-k-e Habe ich auch hin und wieder. Ist bei mir nach reload der Seite dann immer erledigt

                                  E 1 Reply Last reply Reply Quote 0
                                  • E
                                    e-i-k-e @wendy2702 last edited by

                                    @wendy2702
                                    Ist bei mir auch so.

                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 @e-i-k-e last edited by

                                      @e-i-k-e Hat mit controller nix zu tun ... da sist wohl eher admin bzw das Javascriipt von Admin vs ein Admin restart

                                      1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @gelberlemmy last edited by

                                        @gelberlemmy Ja log ist eindeutig. Auch um 20:30:42 wurde der Controller beendet. Frage ist nur warum ... wenn du es nicht warst dann schau mal ob in /var/log/syslog was dazu steht um diese Zeit, vllt ja RAM knapp?

                                        Und im Rahmen dieses "alles beenden" hat das SHelly wieder zu lange gebraucht. Also hier bei den Adaptern die solche DB closed werfen schauen ob es neuere Versionen gibt und die ggf probieren - sonst Issues anlegen

                                        lobomau gelberlemmy Diginix 3 Replies Last reply Reply Quote 1
                                        • lobomau
                                          lobomau @apollon77 last edited by

                                          @apollon77 ich habe gestern mein System geupdatet von 3.3.22 auf 4.0.15. Ich habe keine Probleme, scheint sogar etwas resourcenschonender zu sein.
                                          Ein Problem habe ich: ein slave ist ein Pi1 und hier bekomme nich so einfach node 12 installiert. Noch scheint es ja zu funktionieren. Aber wie lange noch oder kann das jetzt schon zu Problemen führen?

                                          Hier sieht man wie beim slave Pi3 die CPU-Temperatur zurückgegangen ist durch das Update des js-controllers von 58°C auf 55°C (jeweils tiefste Temperatur)

                                          d143d6c0-80e0-4f0a-901f-761bee5d2e48-image.png
                                          Hosts:
                                          e7cc9bd2-0e58-4c66-a191-241f23e99c9e-image.png

                                          Thomas Braun lobomau 2 Replies Last reply Reply Quote 1
                                          • arteck
                                            arteck Developer Most Active last edited by arteck

                                            @lobomau sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                            Ein Problem habe ich: ein slave ist ein Pi1 und hier bekomme nich so einfach node 12 installiert.

                                            was hast du da laufen ? 3 aktive instanzen ??

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

                                            Support us

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

                                            966
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            70
                                            747
                                            165693
                                            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