System & Admin Upgrade "exited with code 25" Start-Schleife?
-
@wendy2702 Eben die Zeilen 1-500, hier der Rest. Das merkwürdige Runterfahren ist hier eher am Anfang
2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.673 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.674 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.675 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:48.675 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.063 - info: sonoff.0 (130093) terminating with timeout 2025-05-27 19:03:49.064 - info: sonoff.0 (130093) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.064 - info: mielecloudservice.0 (130191) terminating with timeout 2025-05-27 19:03:49.065 - info: mielecloudservice.0 (130191) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.065 - info: lg-thinq.0 (130313) terminating with timeout 2025-05-27 19:03:49.066 - info: evcc.0 (130298) terminating with timeout 2025-05-27 19:03:49.066 - info: lg-thinq.0 (130313) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.067 - info: device-watcher.0 (130343) terminating with timeout 2025-05-27 19:03:49.069 - info: nut.0 (130221) terminating with timeout 2025-05-27 19:03:49.068 - info: device-watcher.0 (130343) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.069 - info: web.0 (130369) terminating with timeout 2025-05-27 19:03:49.071 - info: wiegand-tcpip.0 (130206) terminating with timeout 2025-05-27 19:03:49.071 - info: nut.0 (130221) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.072 - info: wiegand-tcpip.0 (130206) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.073 - info: modbus.0 (130253) terminating with timeout 2025-05-27 19:03:49.075 - info: homeconnect.0 (130169) terminating with timeout 2025-05-27 19:03:49.076 - info: homeconnect.0 (130169) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.077 - info: opendtu.0 (130328) terminating with timeout 2025-05-27 19:03:49.078 - info: opendtu.0 (130328) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.076 - info: modbus.1 (130268) terminating with timeout 2025-05-27 19:03:49.077 - info: modbus.1 (130268) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.079 - info: ping.0 (130135) terminating with timeout 2025-05-27 19:03:49.080 - info: backitup.0 (130078) terminating with timeout 2025-05-27 19:03:49.081 - info: backitup.0 (130078) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.070 - info: web.0 (130369) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.082 - info: discovery.0 (130358) terminating with timeout 2025-05-27 19:03:49.067 - info: evcc.0 (130298) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.074 - info: modbus.0 (130253) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.081 - info: ping.0 (130135) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.084 - info: tr-064.0 (129955) terminating with timeout 2025-05-27 19:03:49.084 - info: discovery.0 (130358) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.085 - info: tr-064.0 (129955) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.088 - info: telegram.0 (129928) terminating with timeout 2025-05-27 19:03:49.089 - info: telegram.0 (129928) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.089 - info: email.0 (129879) terminating with timeout 2025-05-27 19:03:49.091 - info: email.0 (129879) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.092 - info: hm-rega.0 (130033) terminating with timeout 2025-05-27 19:03:49.093 - info: hm-rega.0 (130033) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.095 - info: admin.0 (129805) terminating with timeout 2025-05-27 19:03:49.096 - info: admin.0 (129805) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.566 - info: hm-rpc.2 (130119) terminating with timeout 2025-05-27 19:03:49.567 - info: hm-rpc.2 (130119) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.583 - info: hm-rpc.1 (130018) terminating with timeout 2025-05-27 19:03:49.584 - info: hm-rpc.1 (130018) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.592 - info: hm-rpc.0 (130003) terminating with timeout 2025-05-27 19:03:49.593 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.593 - info: hm-rpc.0 (130003) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.609 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:49.610 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.593 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:50.608 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.594 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.595 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.596 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.597 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.600 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.601 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.602 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.603 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.604 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.605 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.606 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:51.607 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.508 - error: web.0 (130369) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.529 - error: wiegand-tcpip.0 (130206) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.534 - error: tuya.0 (130283) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.541 - error: mielecloudservice.0 (130191) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.546 - error: modbus.0 (130253) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.549 - error: backitup.0 (130078) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.551 - warn: discovery.0 (130358) get state error: Connection is closed. 2025-05-27 19:03:52.552 - warn: unifi.0 (130063) get state error: DB closed 2025-05-27 19:03:52.536 - error: tuya.0 (130283) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.558 - warn: hm-rega.0 (130033) get state error: Connection is closed. 2025-05-27 19:03:52.561 - error: hm-rpc.1 (130018) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.561 - info: hm-rega.0 (130033) terminating 2025-05-27 19:03:52.562 - error: telegram.0 (129928) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.549 - error: nut.0 (130221) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.566 - error: evcc.0 (130298) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.569 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.570 - error: admin.0 (129805) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.575 - error: opendtu.0 (130328) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.575 - error: hm-rpc.2 (130119) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.579 - warn: ping.0 (130135) get state error: Connection is closed. 2025-05-27 19:03:52.577 - warn: admin.0 (129805) get state error: Connection is closed. 2025-05-27 19:03:52.577 - warn: admin.0 (129805) get state error: DB closed 2025-05-27 19:03:52.578 - info: admin.0 (129805) terminating 2025-05-27 19:03:52.578 - info: admin.0 (129805) terminating 2025-05-27 19:03:52.581 - error: homeconnect.0 (130169) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.583 - error: lg-thinq.0 (130313) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.587 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.591 - warn: sonoff.0 (130093) get state error: Connection is closed. 2025-05-27 19:03:52.593 - error: modbus.1 (130268) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.591 - error: tr-064.0 (129955) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.596 - warn: backitup.0 (130078) get state error: Connection is closed. 2025-05-27 19:03:52.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.553 - error: device-watcher.0 (130343) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.606 - warn: hm-rpc.1 (130018) get state error: DB closed 2025-05-27 19:03:52.595 - error: hm-rpc.0 (130003) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.589 - error: history.0 (129834) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.598 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.599 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.617 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.618 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.592 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.alive, error - DB closed 2025-05-27 19:03:52.592 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.modeReadColors, error - DB closed 2025-05-27 19:03:52.593 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.alive, error - DB closed 2025-05-27 19:03:52.593 - warn: sonoff.0 (130093) redis get sonoff.0.gosuna-usb-1.modeReadColors, error - DB closed 2025-05-27 19:03:52.593 - info: sonoff.0 (130093) terminating 2025-05-27 19:03:52.609 - error: email.0 (129879) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:52.564 - warn: nut.0 (130221) get state error: Connection is closed. 2025-05-27 19:03:52.565 - warn: nut.0 (130221) get state error: DB closed 2025-05-27 19:03:52.611 - info: nut.0 (130221) terminating 2025-05-27 19:03:52.612 - info: nut.0 (130221) terminating 2025-05-27 19:03:52.573 - warn: mielecloudservice.0 (130191) get state error: Connection is closed. 2025-05-27 19:03:52.574 - info: mielecloudservice.0 (130191) terminating 2025-05-27 19:03:52.577 - warn: hm-rpc.2 (130119) get state error: DB closed 2025-05-27 19:03:52.578 - warn: hm-rpc.2 (130119) get state error: DB closed 2025-05-27 19:03:52.625 - info: hm-rpc.2 (130119) terminating 2025-05-27 19:03:52.625 - info: hm-rpc.2 (130119) terminating 2025-05-27 19:03:52.578 - warn: opendtu.0 (130328) get state error: Connection is closed. 2025-05-27 19:03:52.578 - warn: opendtu.0 (130328) get state error: DB closed 2025-05-27 19:03:52.632 - info: opendtu.0 (130328) terminating 2025-05-27 19:03:52.633 - info: opendtu.0 (130328) terminating 2025-05-27 19:03:52.606 - warn: hm-rpc.1 (130018) get state error: DB closed 2025-05-27 19:03:52.637 - info: hm-rpc.1 (130018) terminating 2025-05-27 19:03:52.638 - info: hm-rpc.1 (130018) terminating 2025-05-27 19:03:52.583 - warn: homeconnect.0 (130169) get state error: Connection is closed. 2025-05-27 19:03:52.584 - warn: homeconnect.0 (130169) get state error: DB closed 2025-05-27 19:03:52.585 - info: homeconnect.0 (130169) terminating 2025-05-27 19:03:52.586 - info: homeconnect.0 (130169) terminating 2025-05-27 19:03:52.639 - warn: modbus.1 (130268) get state error: Connection is closed. 2025-05-27 19:03:52.643 - info: modbus.1 (130268) terminating 2025-05-27 19:03:52.620 - error: sql.0 (129913) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:52.621 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.621 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.622 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.662 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.663 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:52.663 - warn: sql.0 (129913) No Connection to database 2025-05-27 19:03:53.563 - info: tuya.0 (130283) terminating with timeout 2025-05-27 19:03:53.564 - info: tuya.0 (130283) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:56.031 - info: homeconnect.0 (130169) Keep Alive failed Reconnect EventStream 2025-05-27 19:03:56.106 - error: homeconnect.0 (130169) 429 Too Many Requests 2025-05-27 19:03:56.106 - error: homeconnect.0 (130169) Start Event Stream Error: {"type":"error","status":429,"message":"Too Many Requests"} 2025-05-27 19:03:56.107 - info: homeconnect.0 (130169) Too many requests. Please wait 24h. 2025-05-27 19:03:57.552 - error: tuya.0 (130283) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.554 - warn: tuya.0 (130283) get state error: Connection is closed. 2025-05-27 19:03:57.555 - warn: tuya.0 (130283) get state error: DB closed 2025-05-27 19:03:57.556 - info: tuya.0 (130283) terminating 2025-05-27 19:03:57.557 - info: tuya.0 (130283) terminating 2025-05-27 19:03:57.567 - error: nut.0 (130221) Cannot check object existence of "nut.0.battery.charge": DB closed 2025-05-27 19:03:57.571 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.581 - error: opendtu.0 (130328) Cannot find view "system" for search "folder" : Connection is closed. 2025-05-27 19:03:57.592 - error: history.0 (129834) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:57.594 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:03:57.601 - error: modbus.1 (130268) Cannot find view "system" for search "state" : DB closed 2025-05-27 19:03:57.667 - error: sql.0 (129913) States database error: connect ECONNREFUSED 0.0.0.0:9000 2025-05-27 19:03:58.588 - info: history.0 (129834) terminating with timeout 2025-05-27 19:03:58.588 - info: history.0 (129834) Terminated (NO_ERROR): Without reason 2025-05-27 19:03:58.594 - info: sql.0 (129913) terminating with timeout 2025-05-27 19:03:58.594 - info: sql.0 (129913) Terminated (NO_ERROR): Without reason 2025-05-27 19:04:02.574 - error: sql.0 (129913) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:04:02.596 - error: history.0 (129834) Objects database error: connect ECONNREFUSED 0.0.0.0:9001 2025-05-27 19:04:02.597 - warn: history.0 (129834) get state error: Connection is closed. 2025-05-27 19:04:02.671 - warn: sql.0 (129913) get state error: Connection is closed. 2025-05-27 19:04:02.673 - warn: sql.0 (129913) get state error: DB closed 2025-05-27 19:04:02.673 - info: sql.0 (129913) terminating 2025-05-27 19:04:02.673 - info: sql.0 (129913) terminating 2025-05-27 19:04:31.403 - info: host.RoofServer iobroker.js-controller version 7.0.7 js-controller starting 2025-05-27 19:04:31.406 - info: host.RoofServer Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker 2025-05-27 19:04:31.407 - info: host.RoofServer hostname: RoofServer, node: v20.19.2 2025-05-27 19:04:31.407 - info: host.RoofServer ip addresses: 192.168.66.75 fe80::ee2c:259e:69f8:4bec fe80::bee1:cabf:72ba:3764 172.16.100.9 2025-05-27 19:04:33.422 - info: host.RoofServer connected to Objects and States 2025-05-27 19:04:33.439 - info: host.RoofServer added notifications configuration of host 2025-05-27 19:04:34.220 - info: host.RoofServer 62 instances found 2025-05-27 19:04:34.253 - info: host.RoofServer starting 54 instances 2025-05-27 19:04:34.839 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeCurrent" 2025-05-27 19:04:35.009 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeNewest" 2025-05-27 19:04:35.014 - info: host.RoofServer Delete state "system.host.RoofServer.versions.nodeNewestNext" 2025-05-27 19:04:35.065 - info: host.RoofServer instance system.adapter.admin.0 in version "7.6.3" started with pid 130519 2025-05-27 19:04:35.068 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmCurrent" 2025-05-27 19:04:35.112 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmNewest" 2025-05-27 19:04:35.157 - info: host.RoofServer Delete state "system.host.RoofServer.versions.npmNewestNext" 2025-05-27 19:04:35.200 - info: host.RoofServer Some obsolete host states deleted. 2025-05-27 19:04:36.911 - error: admin.0 (130519) admin.0 already running 2025-05-27 19:04:36.913 - warn: admin.0 (130519) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:37.661 - error: host.RoofServer instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:37.662 - info: host.RoofServer Restart adapter system.adapter.admin.0 because enabled 2025-05-27 19:04:38.967 - info: host.RoofServer instance system.adapter.history.0 in version "3.0.1" started with pid 130530 2025-05-27 19:04:40.486 - error: history.0 (130530) history.0 already running 2025-05-27 19:04:40.488 - warn: history.0 (130530) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:41.203 - error: host.RoofServer instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:41.204 - info: host.RoofServer Restart adapter system.adapter.history.0 because enabled 2025-05-27 19:04:42.894 - info: host.RoofServer instance system.adapter.javascript.0 in version "8.8.3" started with pid 130541 2025-05-27 19:04:44.936 - error: javascript.0 (130541) javascript.0 already running 2025-05-27 19:04:44.938 - warn: javascript.0 (130541) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:45.667 - error: host.RoofServer instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:45.667 - info: host.RoofServer Restart adapter system.adapter.javascript.0 because enabled 2025-05-27 19:04:46.968 - info: host.RoofServer instance system.adapter.email.0 in version "2.0.3" started with pid 130584 2025-05-27 19:04:48.495 - error: email.0 (130584) email.0 already running 2025-05-27 19:04:48.497 - warn: email.0 (130584) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:49.205 - error: host.RoofServer instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:49.205 - info: host.RoofServer Restart adapter system.adapter.email.0 because enabled 2025-05-27 19:04:50.876 - info: host.RoofServer instance system.adapter.sql.0 in version "3.0.1" started with pid 130595 2025-05-27 19:04:52.427 - error: sql.0 (130595) sql.0 already running 2025-05-27 19:04:52.429 - warn: sql.0 (130595) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:53.139 - error: host.RoofServer instance system.adapter.sql.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:53.139 - info: host.RoofServer Restart adapter system.adapter.sql.0 because enabled 2025-05-27 19:04:54.991 - info: host.RoofServer instance system.adapter.telegram.0 in version "4.1.0" started with pid 130606 2025-05-27 19:04:56.917 - error: telegram.0 (130606) telegram.0 already running 2025-05-27 19:04:56.919 - warn: telegram.0 (130606) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:04:57.637 - error: host.RoofServer instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:04:57.637 - info: host.RoofServer Restart adapter system.adapter.telegram.0 because enabled 2025-05-27 19:04:59.570 - info: host.RoofServer instance system.adapter.tr-064.0 in version "4.3.0" started with pid 130617 2025-05-27 19:04:59.582 - info: host.RoofServer instance system.adapter.telegram.0 in version "4.1.0" started with pid 130623 2025-05-27 19:05:02.151 - error: tr-064.0 (130617) tr-064.0 already running 2025-05-27 19:05:02.152 - warn: tr-064.0 (130617) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:02.878 - info: host.RoofServer instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 130641 2025-05-27 19:05:03.054 - error: host.RoofServer instance system.adapter.tr-064.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:03.054 - info: host.RoofServer Restart adapter system.adapter.tr-064.0 because enabled 2025-05-27 19:05:03.181 - info: telegram.0 (130623) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:03.771 - error: telegram.0 (130623) Failed sending [chatId - 1173210274]: Error: ETELEGRAM: 403 Forbidden: bot was blocked by the user 2025-05-27 19:05:04.551 - error: hm-rpc.0 (130641) hm-rpc.0 already running 2025-05-27 19:05:04.553 - warn: hm-rpc.0 (130641) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:05.258 - error: host.RoofServer instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:05.258 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.0 because enabled 2025-05-27 19:05:07.007 - info: host.RoofServer instance system.adapter.hm-rpc.1 in version "2.0.2" started with pid 130656 2025-05-27 19:05:08.693 - info: host.RoofServer instance system.adapter.admin.0 in version "7.6.3" started with pid 130667 2025-05-27 19:05:09.067 - error: hm-rpc.1 (130656) hm-rpc.1 already running 2025-05-27 19:05:09.069 - warn: hm-rpc.1 (130656) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:09.778 - error: host.RoofServer instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:09.779 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.1 because enabled 2025-05-27 19:05:10.967 - info: host.RoofServer instance system.adapter.hm-rega.0 in version "5.1.0" started with pid 130678 2025-05-27 19:05:12.195 - info: host.RoofServer instance system.adapter.history.0 in version "3.0.1" started with pid 130689 2025-05-27 19:05:12.860 - error: hm-rega.0 (130678) hm-rega.0 already running 2025-05-27 19:05:12.863 - warn: hm-rega.0 (130678) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:12.871 - info: admin.0 (130667) starting. Version 7.6.3 in /opt/iobroker/node_modules/iobroker.admin, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:12.903 - info: admin.0 (130667) requesting all objects 2025-05-27 19:05:16.332 - error: host.RoofServer instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:16.333 - info: host.RoofServer Restart adapter system.adapter.hm-rega.0 because enabled 2025-05-27 19:05:16.536 - info: admin.0 (130667) received all objects 2025-05-27 19:05:17.243 - info: admin.0 (130667) socket.io server listening on port 8081 2025-05-27 19:05:17.244 - info: admin.0 (130667) http server listening on port 8081 2025-05-27 19:05:17.245 - info: admin.0 (130667) Use link "http://127.0.0.1:8081" to configure. 2025-05-27 19:05:18.279 - info: host.RoofServer instance scheduled system.adapter.ical.0 2,32 * * * * 2025-05-27 19:05:18.287 - info: host.RoofServer instance system.adapter.ical.0 in version "1.16.1" started with pid 130720 2025-05-27 19:05:19.921 - info: host.RoofServer instance system.adapter.javascript.0 in version "8.8.3" started with pid 130737 2025-05-27 19:05:21.039 - info: host.RoofServer instance system.adapter.unifi.0 in version "0.7.0" started with pid 130744 2025-05-27 19:05:21.268 - info: host.RoofServer instance system.adapter.email.0 in version "2.0.3" started with pid 130755 2025-05-27 19:05:21.904 - info: admin.0 (130667) ==> Connected system.user.admin from ::ffff:192.168.66.108 2025-05-27 19:05:28.629 - error: unifi.0 (130744) unifi.0 already running 2025-05-27 19:05:28.632 - warn: unifi.0 (130744) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:28.700 - info: host.RoofServer instance system.adapter.backitup.0 in version "3.0.31" started with pid 130784 2025-05-27 19:05:28.889 - info: host.RoofServer instance system.adapter.sql.0 in version "3.0.1" started with pid 130791 2025-05-27 19:05:29.032 - info: host.RoofServer instance system.adapter.sonoff.0 in version "3.1.2" started with pid 130798 2025-05-27 19:05:29.048 - info: history.0 (130689) starting. Version 3.0.1 in /opt/iobroker/node_modules/iobroker.history, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:29.861 - error: host.RoofServer instance system.adapter.unifi.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:29.862 - info: host.RoofServer Restart adapter system.adapter.unifi.0 because enabled 2025-05-27 19:05:30.067 - info: ical.0 (130720) starting. Version 1.16.1 in /opt/iobroker/node_modules/iobroker.ical, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:30.298 - info: email.0 (130755) starting. Version 2.0.3 in /opt/iobroker/node_modules/iobroker.email, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:31.496 - info: ical.0 (130720) processing URL: MH https://calendar.google.com/calendar/ical/c530e1fa7a07a45ab04e116a7f389806477602687d99c31f461cc294fa6864d2%40group.calendar.google.com/private-063afafa12704b6d953907c2d98a219d/basic.ics 2025-05-27 19:05:32.834 - info: host.RoofServer instance system.adapter.hm-rpc.2 in version "2.0.2" started with pid 130829 2025-05-27 19:05:33.290 - error: backitup.0 (130784) backitup.0 already running 2025-05-27 19:05:33.292 - warn: backitup.0 (130784) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:33.696 - error: sonoff.0 (130798) sonoff.0 already running 2025-05-27 19:05:33.699 - warn: sonoff.0 (130798) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:34.351 - error: host.RoofServer instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:34.351 - info: host.RoofServer Restart adapter system.adapter.backitup.0 because enabled 2025-05-27 19:05:34.934 - info: host.RoofServer instance system.adapter.tr-064.0 in version "4.3.0" started with pid 130840 2025-05-27 19:05:35.375 - error: host.RoofServer instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:35.376 - info: host.RoofServer Restart adapter system.adapter.sonoff.0 because enabled 2025-05-27 19:05:35.563 - info: javascript.0 (130737) starting. Version 8.8.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.19.2, js-controller: 7.0.7 2025-05-27 19:05:37.971 - error: hm-rpc.2 (130829) hm-rpc.2 already running 2025-05-27 19:05:37.974 - warn: hm-rpc.2 (130829) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-05-27 19:05:38.202 - info: host.RoofServer instance system.adapter.ping.0 in version "1.6.2" started with pid 130866 2025-05-27 19:05:39.339 - info: host.RoofServer instance system.adapter.hm-rpc.0 in version "2.0.2" started with pid 130885 2025-05-27 19:05:39.795 - info: ical.0 (130720) Terminated (NO_ERROR): Without reason 2025-05-27 19:05:39.820 - error: host.RoofServer instance system.adapter.hm-rpc.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-05-27 19:05:39.820 - info: host.RoofServer Restart adapter system.adapter.hm-rpc.2 because enabled 2025-05-27 19:05:39.833 - info: host.RoofServer instance system.adapter.backitup.0 in version "3.0.31" started with pid 130894 -
@wendy2702 Ist dwd.0 das Problem?
(Im 1. Logfile-Teil, ca Zeile 320)
2025-05-27 19:03:47.364 - error: dwd.0 (130400) Cannot initialize database scripts: ENOENT: no such file or directory, scandir '/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/lua-v4' 2025-05-27 19:03:47.371 - error: host.RoofServer uncaught exception: Could not determine controller directory 2025-05-27 19:03:47.371 - error: host.RoofServer Error: Could not determine controller directory at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1833:11) at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1306:37) at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3219:30) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) -
Stoppen von dwd.0 hilft auch nicht
Nun finde ich sowas hier:
2025-05-27 19:21:38.759 - error: host.RoofServer startInstance statistics.0: cannot find start file! 2025-05-27 19:21:38.780 - error: web.0 (135592) Cannot initialize database scripts: ENOENT: no such file or directory, scandir '/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/lua-v4'...passt da im hintergrund was mit dem Nod(JS) nicht? Kann ich das Node_modules vielleicht neu bauen lassen oder so?
Gruss -
-
@adarof sieht eher so aus als ob was mit deiner database nicht passt für mich.
Wenn das nach dem Admin Update angefangen hat würde ich mal nach dem Error 25 im Forum suchen.
Oder kam das nach dem Ubuntu Upgrade?
-
@wendy2702
Würde tippen dass es nach dem UbuntuUpgrade kam, da das Admin Upgrade nun auch immernoch ansteht könnte es auch einfach nicht durchgeführt worden sein.
Kann ich die Datenbank checken irgendwie? -
Sehe gerade:
Wenn ich "schnell" nach dem "Absturz" ein "iob logs" mache, bekomme ich sowas hier:hmersch@RoofServer:/opt/iobroker$ iob logs node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] }....wenn ich dann 10 sek warte, tut es wieder.
Hat das vielleicht auch was damit zu tun?
-
@adarof Check ist mir erstmal nicht bekannt.
Was kam den bei der Ausführung von iob fix zurück?
Und ich würde trotzdem mal im Forum nach dem Error 25 suchen.
Edit: kann auch gut sein das der JS-Controller zerschossen ist. Installiere den doch mal neu
-
@wendy2702
Geht das so?iob stop cd /opt/iobroker sudo -H -u iobroker npm reinstall iobroker.js-controllerergibt:
hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller npm warn skipping integrity check for git dependency ssh://git@github.com/theknut/ioBroker.waterkotte-easycon.git npm warn skipping integrity check for git dependency ssh://git@github.com/eifel-tech/ioBroker.syrconnect.git npm warn skipping integrity check for git dependency ssh://git@github.com/nbuenger/ioBroker.govee.git npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated q@1.1.2: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm warn deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm warn deprecated multer@1.4.5-lts.2: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version. npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead npm warn deprecated sinon@15.2.0: 16.1.1 ⠦ removed 40 packages, and changed 1483 packages in 2m... aber nach "iob start" gleiches Verhalten
"iob fix" sagt nun das hier:
hmersch@RoofServer:/opt/iobroker$ iob fix library: loaded Library version=2024-10-22 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 205-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease OK:2 https://deb.nodesource.com/node_20.x nodistro InRelease Holen:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB] Holen:4 https://dl.cloudsmith.io/public/tvheadend/tvheadend/deb/ubuntu focal InRelease [4.418 B] OK:5 https://gcups-static.greencell.global/deb stable InRelease Holen:6 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB] Holen:7 https://dl.cloudsmith.io/public/tvheadend/tvheadend/deb/ubuntu focal/main amd64 Packages [36,7 kB] Holen:8 http://de.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [420 kB] Holen:9 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [114 kB] Holen:10 http://de.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 DEP-11 Metadata [212 B] Holen:11 http://de.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [359 kB] Holen:12 http://de.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B] Holen:13 http://de.archive.ubuntu.com/ubuntu jammy-backports/main amd64 DEP-11 Metadata [7.096 B] Holen:14 http://de.archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 DEP-11 Metadata [212 B] Holen:15 http://de.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [24,1 kB] Holen:16 http://de.archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 DEP-11 Metadata [212 B] OK:17 http://security.ubuntu.com/ubuntu jammy-security InRelease Es wurden 260 kB in 2 s geholt (126 kB/s). Paketlisten werden gelesen… Fertig N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot »https://deb.nodesource.com/node_20.x nodistro InRelease« die Architektur »i386« nicht unterstützt. ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Legitimierung ist zum Stoppen von »iobroker.service« notwendig. Multiple identities can be used for authentication: 1. user,,, (user) 2. hmersch 4. iobroker Choose identity to authenticate as (1-4): 2 Password: ==== AUTHENTICATION COMPLETE === Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Ich hatte schon nach Error-25 gesucht; meist scheint ein "iob fix" geholfen zu haben.
Meinst Du ich sollte "rm -rf node_modules" versuchen, wie hier beschrieben?
https://forum.iobroker.net/topic/56543/nach-nodejs-update-kein-adapter-mehr-updatebar/46closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
Keine Ahnung ob das hilft.
Kommt denn noch immer der Eintrag bezüglich JS Controller im log?
-
@wendy2702 Das ist doch mysteriös. Nun hatte ich bei "iob logs" (und auch iob status) permanent das hier:
node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] }Also hab ich nochmal
"sudo -H -u iobroker npm reinstall iobroker.js-controller" gemacht
Nun tut das wieder. laut Logs ausgabe war nun ein anderer Adapter unglücklich:2025-05-27 19:59:11.436 - error: unifi.0 (144596) [updateUnifiData site default] error: Cannot find module './admin/lib/objects_wlans.json' Require stack: - /opt/iobroker/node_modules/iobroker.unifi/main.js, stack: Error: Cannot find module './admin/lib/objects_wlans.json'Alsob da im Hintergrund noch was passiert, was da Dateien löscht / kompiliert / generiert.
Noch eine Idee?
-
Beim nächsten start doch wieder js-controller:
2025-05-27 20:22:15.697 - info: web.0 (150845) starting. Version 7.0.8 in /opt/iobroker/node_modules/iobroker.web, node: v20.19.2, js-controller: 7.0.7 2025-05-27 20:22:15.733 - error: web.0 (150845) 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(). 2025-05-27 20:22:15.741 - info: vis.0 (150856) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.19.2, js-controller: 7.0.7 2025-05-27 20:22:15.734 - error: web.0 (150845) unhandled promise rejection: Cannot find i18n directory 2025-05-27 20:22:15.738 - error: web.0 (150845) Error: Cannot find i18n directory at Module.init (file:///opt/iobroker/node_modules/@iobroker/i18n/build/esm/index.js:45:15) at WebAdapter.onReady (/opt/iobroker/node_modules/iobroker.web/dist/main.js:561:26) 2025-05-27 20:22:15.739 - error: web.0 (150845) Cannot find i18n directory 2025-05-27 20:22:15.760 - warn: web.0 (150845) setTimeout called, but adapter is shutting down 2025-05-27 20:22:15.860 - error: vis.0 (150856) 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(). 2025-05-27 20:22:15.860 - error: vis.0 (150856) unhandled promise rejection: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/lib/../www/js/config.js' 2025-05-27 20:22:15.862 - error: vis.0 (150856) Error: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/lib/../www/js/config.js' at Object.openSync (node:fs:574:18) at Object.readFileSync (node:fs:453:35) at syncWidgetSets (/opt/iobroker/node_modules/iobroker.vis/lib/install.js:192:24) at generatePages (/opt/iobroker/node_modules/iobroker.vis/main.js:157:21) at main (/opt/iobroker/node_modules/iobroker.vis/main.js:235:32)Es scheinen immer Verzeichnisse nicht auffindbar zu sein. Wenn ich dann aber z.B. nach "/opt/iobroker/node_modules/iobroker.vis/lib/../www/widgets/" ist es vorhanden
-
@adarof kannst du den installations Befehl mal so ausführen
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iob stop iob fix iob start iob updateAlso nicht mit „reinstall“
-
@wendy2702
iob stop war vorher, dann das hier:hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller npm warn skipping integrity check for git dependency ssh://git@github.com/theknut/ioBroker.waterkotte-easycon.git npm warn skipping integrity check for git dependency ssh://git@github.com/nbuenger/ioBroker.govee.git npm warn skipping integrity check for git dependency ssh://git@github.com/eifel-tech/ioBroker.syrconnect.git npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated q@1.1.2: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm warn deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm warn deprecated multer@1.4.5-lts.2: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version. npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead npm warn deprecated sinon@15.2.0: 16.1.1 added 1 package, and changed 1484 packages in 2m 180 packages are looking for funding run `npm fund` for details hmersch@RoofServer:/opt/iobroker$ iob fix library: loaded Library version=2024-10-22 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 205-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://security.ubuntu.com/ubuntu jammy-security InRelease OK:2 http://de.archive.ubuntu.com/ubuntu jammy InRelease OK:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease OK:4 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease OK:5 https://deb.nodesource.com/node_20.x nodistro InRelease OK:6 https://gcups-static.greencell.global/deb stable InRelease Holen:7 https://dl.cloudsmith.io/public/tvheadend/tvheadend/deb/ubuntu focal InRelease [4.418 B] Es wurden 4.418 B in 1 s geholt (5.136 B/s). Paketlisten werden gelesen… Fertig N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot »https://deb.nodesource.com/node_20.x nodistro InRelease« die Architektur »i386« nicht unterstützt. ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Legitimierung ist zum Stoppen von »iobroker.service« notwendig. Multiple identities can be used for authentication: 1. user,,, (user) 2. hmersch 4. iobroker Choose identity to authenticate as (1-4): 2 Password: ==== AUTHENTICATION COMPLETE === Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== hmersch@RoofServer:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller^C hmersch@RoofServer:/opt/iobroker$ iob start hmersch@RoofServer:/opt/iobroker$ iob update Used repository: stable Adapter "admin" : 7.6.17 , installed 7.6.3 [Updatable] Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "amazon-dash" : 1.2.0 , installed 1.2.0 Adapter "backitup" : 3.2.2 , installed 3.0.31 [Updatable] Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "device-watcher": 2.12.1 , installed 2.12.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "easee" : 1.0.10 , installed 1.0.10 Adapter "email" : 2.0.4 , installed 2.0.3 [Updatable] Adapter "evcc" : 0.1.1 , installed 0.2.2 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "ham" : 5.3.1 , installed 5.3.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "homeconnect" : 1.4.3 , installed 1.4.3 Adapter "ical" : 1.16.1 , installed 1.16.1 Adapter "icons-addictive-flavour-png": 0.1.0, installed 0.1.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.7 Adapter "klf200" : 1.3.5 , installed 1.3.5 Adapter "lg-thinq" : 1.1.0 , installed 1.1.0 Adapter "material" : 1.3.1 , installed 1.3.1 Adapter "mielecloudservice": 6.5.10, installed 6.5.10 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "nut" : 1.6.0 , installed 1.6.0 Adapter "opendtu" : 3.1.0 , installed 3.1.0 Adapter "parser" : 2.2.4 , installed 2.2.4 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "rickshaw" : 1.0.0 , installed 1.0.0 Adapter "sbfspot" : 4.4.2 , installed 4.4.2 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.1.2 , installed 3.1.2 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-colorpicker": 2.0.3 , installed 2.0.3 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "wiegand-tcpip": 0.4.6 , installed 0.4.7 Adapter "ws" : 2.6.2 , installed 2.6.2 hmersch@RoofServer:/opt/iobroker$closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
Ich sehe da auch immer viele "error instance system.adapter.sonoff.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)" von unterschiedlichsten Adaptern.
Als ob iobroker alle Adapter mehrfach startet - was dann ja zu den Zugriffsproblemen führen könnteJedenfalls hat das npm install & fix & start & update keine Änderung gebracht
-
Kann ich das Hochfahren irgendwie manuell machen - und könnte das helfen?
So grob stell ich mir das vor:
a) "iob start no-adapter"
b) "iob start admin.0"
c) ...via Webinterface von Admin danach der Reihe nach alle anderen Adapter starten. -
@adarof mal ne Frage, hast du den Rechner mal neu gestartet?
-
@wendy2702 Ja, einmal nach dem Ubuntu Update und auch gerade bevor ich Deine Idee mit dem "npm install & iob stop & iob fix & iob start & iob update" gemacht habe
-
iob stop all -
@thomas-braun Danke, stopped das mehr als einfach "iob stop" ?
Nun ist es wieder kaputt gegangen:
hmersch@RoofServer:/opt/iobroker$ iob stop all The adapter "admin.0" was stopped. The adapter "history.0" was stopped. The adapter "javascript.0" was stopped. The adapter "email.0" was stopped. The adapter "sql.0" was stopped. The adapter "telegram.0" was stopped. The adapter "tr-064.0" was stopped. The adapter "hm-rpc.0" was stopped. The adapter "hm-rpc.1" was stopped. The adapter "hm-rega.0" was stopped. The adapter "ical.0" was stopped. The adapter "unifi.0" was stopped. The adapter "backitup.0" was stopped. The adapter "sonoff.0" was stopped. The adapter "hm-rpc.2" was stopped. The adapter "ping.0" was stopped. The adapter "homeconnect.0" was stopped. The adapter "mielecloudservice.0" was stopped. The adapter "wiegand-tcpip.0" was stopped. The adapter "nut.0" was stopped. The adapter "alexa2.0" was stopped. The adapter "modbus.0" was stopped. The adapter "modbus.1" was stopped. The adapter "tuya.0" was stopped. The adapter "evcc.0" was stopped. The adapter "lg-thinq.0" was stopped. The adapter "opendtu.0" was stopped. The adapter "device-watcher.0" was stopped. The adapter "discovery.0" was stopped. The adapter "web.0" was stopped. The adapter "mobile.0" was stopped. The adapter "vis.0" was stopped. The adapter "dwd.0" was stopped. The adapter "icons-material-png.0" was stopped. The adapter "icons-mfd-svg.0" was stopped. The adapter "vis-timeandweather.0" was stopped. The adapter "vis-fancyswitch.0" was stopped. The adapter "vis-hqwidgets.0" was stopped. The adapter "vis-metro.0" was stopped. The adapter "vis-colorpicker.0" was stopped. The adapter "icons-mfd-png.0" was stopped. The adapter "vis-jqui-mfd.0" was stopped. The adapter "flot.0" was stopped. The adapter "vis-history.0" was stopped. The adapter "vis-bars.0" was stopped. The adapter "icons-addictive-flavour-png.0" was stopped. The adapter "text2command.0" was stopped. The adapter "daswetter.0" was stopped. The adapter "vis-canvas-gauges.0" was stopped. The adapter "material.0" was stopped. The adapter "nina.0" was stopped. The adapter "vis-rgraph.0" was stopped. The adapter "rickshaw.0" was stopped. The adapter "simple-api.0" was stopped. The adapter "govee.0" was stopped. The adapter "easee.1" was stopped. The adapter "parser.0" was stopped. The adapter "vw-connect.0" was stopped. The adapter "statistics.0" was stopped. hmersch@RoofServer:/opt/iobroker$ iob stop all^C hmersch@RoofServer:/opt/iobroker$ iob stop all Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.RoofServer"] Uncaught Rejection: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/opt/iobroker/node_modules/@iobroker/db-objects-jsonl/build/esm/index.js' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/dbConnection.js at finalizeResolution (node:internal/modules/esm/resolve:283:11) at moduleResolve (node:internal/modules/esm/resolve:952:10) at defaultResolve (node:internal/modules/esm/resolve:1188:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12) at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25) at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38) at ModuleLoader.import (node:internal/modules/esm/loader:539:34) at defaultImportModuleDynamicallyForModule (node:internal/modules/esm/utils:215:31) at importModuleDynamicallyCallback (node:internal/modules/esm/utils:254:12) hmersch@RoofServer:/opt/iobroker$ hmersch@RoofServer:/opt/iobroker$ hmersch@RoofServer:/opt/iobroker$ hmersch@RoofServer:/opt/iobroker$ iob stop all node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.19.2 hmersch@RoofServer:/opt/iobroker$ iob stop all node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.19.2 -
und ... ein paar sekunden später:
hmersch@RoofServer:/opt/iobroker$ iob status iobroker is running on this host. Objects type: jsonl States type: jsonlokay, davon kann ich dann "iob start admin.0" machen... oder auch nicht:
hmersch@RoofServer:/opt/iobroker$ iob start admin.0 node:internal/modules/cjs/loader:1215 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15) at Module._load (node:internal/modules/cjs/loader:1043:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] }nun ist es wieder kaputt und ich müsste mit "npm install .." loslegen?
Irgendwas ist da doch ganz ganz merkwürdig
Da läuft auch noch jede Menge bzw wird gestartet:
hmersch@RoofServer:/opt/iobroker$ ps aux |grep iobroker iobroker 16132 76.8 3.3 11995472 543668 ? Rsl 21:16 0:40 iobroker.js-controller iobroker 16218 13.5 0.6 11741200 100672 ? Sl 21:16 0:03 io.telegram.0 iobroker 16265 34.5 2.1 12091024 356848 ? Sl 21:16 0:05 io.admin.0 iobroker 16287 16.5 0.6 11565564 103964 ? Sl 21:16 0:01 io.history.0 iobroker 16331 41.2 0.6 11561820 102412 ? Sl 21:17 0:01 /usr/bin/node /opt/iobroker/node_modules/iobroker.ical/main.js --instance 0 --loglevel info iobroker 16342 113 0.9 11603300 156264 ? Rl 21:17 0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.javascript/main.js --instance 0 --loglevel info iobroker 16349 94.0 0.5 11559260 93536 ? Rl 21:17 0:01 /usr/bin/node /opt/iobroker/node_modules/iobroker.unifi/main.js --instance 0 --loglevel warn iobroker 16358 136 0.5 11538412 85436 ? Rl 21:17 0:01 /usr/bin/node /opt/iobroker/node_modules/iobroker.email/build/main.js --instance 0 --loglevel info hmersch 16380 0.0 0.0 9608 2428 pts/0 S+ 21:17 0:00 grep --color=auto iobrokerWer startet denn da noch was?
Gibt es unterschiedliche Wege, wie der iobroker Prozess gestartet wird und ich gehe beide wenn ich hier "iob start" macht?
Nach einem erneuten "iob stop all":
hmersch@RoofServer:/opt/iobroker$ ps aux |grep iobroker iobroker 16941 34.7 5.1 2045780 834000 ? Rl 21:19 0:43 npm install @iobroker-javascript.0/klf-200-api@npm:klf-200-api@latest hmersch 17589 0.0 0.0 9608 2348 pts/0 S+ 21:21 0:00 grep --color=auto iobroker...und dann wird neu gestartet. Das "iob stop all" scheint bei mir also nicht zu stoppen sondern zu restarten.
Kann sich das jemand erklären?
