NEWS
Troubleshooting NodeJS update
Installation
504
Beiträge
60
Kommentatoren
147.8k
Aufrufe
52
Watching
-
@thomas-braun guten morgen. Kann es sein, dass der Log vom Shutdown beim nächsten Start mit angezeigt wird ? So würden die ganzen Errors beim Shutdown kommen. Dann habe ich dies falsch interpretiert. Aber diese Errors hatte ich mit der Version 16 nicht.
23-07-02 08:22:19.793 - info: host.IOBroker-Proxmox stopInstance system.adapter.admin.1 send kill signal 2023-07-02 08:22:19.793 - info: host.IOBroker-Proxmox stopInstance system.adapter.email.0 send kill signal 2023-07-02 08:22:19.793 - info: host.IOBroker-Proxmox stopInstance system.adapter.javascript.0 send kill signal 2023-07-02 08:22:19.794 - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.0 send kill signal 2023-07-02 08:22:19.794 - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.1 send kill signal 2023-07-02 08:22:19.794 - info: host.IOBroker-Proxmox stopInstance system.adapter.alexa2.0 send kill signal 2023-07-02 08:22:19.794 - info: host.IOBroker-Proxmox stopInstance system.adapter.ham.0 send kill signal 2023-07-02 08:22:19.794 - info: host.IOBroker-Proxmox stopInstance system.adapter.hmip.0 send kill signal 2023-07-02 08:22:19.794 - info: host.IOBroker-Proxmox stopInstance system.adapter.mqtt.0 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.netatmo.0 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.0 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.sonoff.0 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.zigbee.0 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.nut.0 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.samsung.0 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.1 send kill signal 2023-07-02 08:22:19.795 - info: host.IOBroker-Proxmox stopInstance system.adapter.tr-064.0 send kill signal 2023-07-02 08:22:19.796 - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.0 send kill signal 2023-07-02 08:22:19.796 - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.1 send kill signal 2023-07-02 08:22:19.796 - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.2 send kill signal 2023-07-02 08:22:19.796 - info: host.IOBroker-Proxmox stopInstance system.adapter.amazon-dash.0 send kill signal 2023-07-02 08:22:19.796 - info: host.IOBroker-Proxmox stopInstance system.adapter.backitup.0 send kill signal 2023-07-02 08:22:19.796 - info: host.IOBroker-Proxmox stopInstance system.adapter.cloud.0 send kill signal 2023-07-02 08:22:19.796 - info: host.IOBroker-Proxmox stopInstance system.adapter.device-reminder.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.discovery.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.enocean.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.fb-checkpresence.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.homeconnect.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.hue-extended.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.info.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.iot.0 send kill signal 2023-07-02 08:22:19.797 - info: host.IOBroker-Proxmox stopInstance system.adapter.octoprint.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.pushsafer.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.sourceanalytix.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.text2command.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.trashschedule.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.web.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.zwave2.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.proxmox.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.worx.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.senec.0 send kill signal 2023-07-02 08:22:19.798 - info: host.IOBroker-Proxmox stopInstance system.adapter.accuweather.0 send kill signal 2023-07-02 08:22:19.799 - info: host.IOBroker-Proxmox stopInstance system.adapter.jarvis.0 send kill signal 2023-07-02 08:22:19.799 - info: host.IOBroker-Proxmox stopInstance system.adapter.energiefluss.0 send kill signal 2023-07-02 08:22:19.804 - info: jarvis.0 (1035) terminating with timeout 2023-07-02 08:22:19.805 - info: worx.0 (994) terminating with timeout 2023-07-02 08:22:19.811 - info: energiefluss.0 (1046) terminating with timeout 2023-07-02 08:22:19.813 - info: web.0 (957) terminating with timeout 2023-07-02 08:22:19.824 - info: telegram.0 (2000) terminating with timeout 2023-07-02 08:22:19.826 - info: cloud.0 (740) terminating with timeout 2023-07-02 08:22:19.830 - info: zigbee.0 (596) terminating with timeout 2023-07-02 08:22:19.833 - info: telegram.1 (2006) terminating with timeout 2023-07-02 08:22:19.836 - info: alexa2.0 (2385) terminating with timeout 2023-07-02 08:22:19.846 - info: backitup.0 (729) terminating with timeout 2023-07-02 08:22:19.863 - info: accuweather.0 (1020) terminating with timeout 2023-07-02 08:22:19.864 - info: admin.1 (351) terminating with timeout 2023-07-02 08:22:19.879 - info: info.0 (835) terminating with timeout 2023-07-02 08:22:19.884 - info: trashschedule.0 (946) terminating with timeout 2023-07-02 08:22:19.885 - info: hmip.0 (490) terminating with timeout 2023-07-02 08:22:19.895 - info: enocean.0 (781) terminating with timeout 2023-07-02 08:22:19.898 - info: senec.0 (1009) terminating with timeout 2023-07-02 08:22:19.899 - info: ham.0 (479) terminating with timeout 2023-07-02 08:22:19.927 - info: amazon-dash.0 (718) terminating with timeout 2023-07-02 08:22:20.042 - info: fb-checkpresence.0 (794) terminating 2023-07-02 08:22:20.038 - warn: senec.0 (1009) redis get senec.0._calc.LIVE_GRID_EXPORT.refMonth, error - Connection is closed. 2023-07-02 08:22:20.044 - warn: senec.0 (1009) redis get senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.refValueYear, error - DB closed 2023-07-02 08:22:20.049 - warn: shelly.0 (563) redis get shelly.0.SHUNI-1#349454790800#1.Relay0.Timer, error - Connection is closed. 2023-07-02 08:22:20.055 - warn: shelly.0 (563) get state error: Connection is closed. 2023-07-02 08:22:20.059 - warn: shelly.1 (641) get state error: Connection is closed. 2023-07-02 08:22:20.052 - error: senec.0 (1009) 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(). 2023-07-02 08:22:20.052 - error: senec.0 (1009) unhandled promise rejection: DB closed 2023-07-02 08:22:20.053 - error: senec.0 (1009) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP. (node:net:322:12) 2023-07-02 08:22:20.054 - error: senec.0 (1009) DB closed 2023-07-02 08:22:20.086 - warn: senec.0 (1009) redis get senec.0._calc.LIVE_GRID_IMPORT.year, error - Connection is closed. 2023-07-02 08:22:20.087 - warn: senec.0 (1009) redis get senec.0._calc.LIVE_BAT_CHARGE_MASTER.year, error - Connection is closed. 2023-07-02 08:22:20.105 - warn: senec.0 (1009) redis get senec.0._calc.Autarky.today, error - Connection is closed. 2023-07-02 08:22:20.207 - warn: senec.0 (1009) redis get senec.0.STATISTIC.LIVE_GRID_EXPORT, error - Connection is closed. 2023-07-02 08:22:20.342 - warn: senec.0 (1009) redis get senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year, error - Connection is closed. 2023-07-02 08:22:20.390 - info: fb-checkpresence.0 (794) terminating with timeout 2023-07-02 08:22:20.413 - error: senec.0 (1009) Cannot check object existence of "senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year": DB closed 2023-07-02 08:22:20.414 - warn: senec.0 (1009) Could not perform strict object check of state senec.0._calc.Autarky.today: DB closed 2023-07-02 08:22:20.415 - warn: senec.0 (1009) get state error: Connection is closed. 2023-07-02 08:22:20.415 - error: senec.0 (1009) 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(). 2023-07-02 08:22:20.415 - error: senec.0 (1009) unhandled promise rejection: DB closed 2023-07-02 08:22:20.415 - error: senec.0 (1009) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP. (node:net:322:12) 2023-07-02 08:22:20.416 - error: senec.0 (1009) DB closed 2023-07-02 08:22:20.416 - error: senec.0 (1009) 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(). 2023-07-02 08:22:20.416 - error: senec.0 (1009) unhandled promise rejection: DB closed 2023-07-02 08:22:20.417 - error: senec.0 (1009) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP. (node:net:322:12) 2023-07-02 08:22:20.417 - error: senec.0 (1009) DB closed 2023-07-02 08:22:20.417 - error: senec.0 (1009) 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(). 2023-07-02 08:22:20.417 - error: senec.0 (1009) unhandled promise rejection: Could not check object existence of senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year: Cannot check object existence of "senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year": DB closed 2023-07-02 08:22:20.420 - error: senec.0 (1009) Error: Could not check object existence of senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year: Cannot check object existence of "senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year": DB closed at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at Senec._setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:3416:49) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2023-07-02 08:22:20.420 - error: senec.0 (1009) Could not check object existence of senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year: Cannot check object existence of "senec.0._calc.LIVE_BAT_DISCHARGE_MASTER.year": DB closed 2023-07-02 08:22:20.428 - error: senec.0 (1009) 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(). 2023-07-02 08:22:20.428 - error: senec.0 (1009) unhandled promise rejection: DB closed 2023-07-02 08:22:20.429 - error: senec.0 (1009) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP. (node:net:322:12) 2023-07-02 08:22:20.429 - error: senec.0 (1009) DB closed 2023-07-02 08:22:20.450 - error: senec.0 (1009) 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(). 2023-07-02 08:22:20.450 - error: senec.0 (1009) unhandled promise rejection: DB closed 2023-07-02 08:22:20.451 - error: senec.0 (1009) Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/build/lib/states/statesInRedisClient.js:521:40) at Senec._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5472:34) at runNextTicks (node:internal/process/task_queues:60:5) at process.processImmediate (node:internal/timers:447:9) 2023-07-02 08:22:20.451 - error: senec.0 (1009) DB closed 2023-07-02 08:22:20.650 - warn: zwave2.0 (972) Could not perform strict object check of state zwave2.0.Node_001.ready: DB closed 2023-07-02 08:22:20.652 - warn: zwave2.0 (972) get state error: Connection is closed. 2023-07-02 08:22:20.653 - warn: zwave2.0 (972) get state error: Connection is closed. 2023-07-02 08:22:20.653 - info: zwave2.0 (972) terminating 2023-07-02 08:22:21.004 - info: host.IOBroker-Proxmox stopInstance system.adapter.admin.1 killing pid 351 2023-07-02 08:22:21.027 - warn: sonoff.0 (571) Could not perform strict object check of state sonoff.0.Trockner.Time: DB closed 2023-07-02 08:22:21.028 - warn: sonoff.0 (571) get state error: Connection is closed. 2023-07-02 08:22:21.030 - warn: sonoff.0 (571) Could not perform strict object check of state sonoff.0.Trockner.alive: DB closed 2023-07-02 08:22:21.031 - warn: sonoff.0 (571) get state error: Connection is closed. 2023-07-02 08:22:21.032 - warn: sonoff.0 (571) Could not perform strict object check of state sonoff.0.Trockner.Uptime: DB closed 2023-07-02 08:22:21.033 - warn: sonoff.0 (571) get state error: Connection is closed. 2023-07-02 08:22:21.052 - warn: sonoff.0 (571) Could not perform strict object check of state sonoff.0.Trockner.UptimeSec: DB closed 2023-07-02 08:22:21.052 - warn: sonoff.0 (571) get state error: Connection is closed. 2023-07-02 08:22:21.064 - warn: sonoff.0 (571) Could not perform strict object check of state sonoff.0.Trockner.Heap: DB closed 2023-07-02 08:22:21.065 - warn: sonoff.0 (571) get state error: Connection is closed. 2023-07-02 08:22:21.067 - warn: sonoff.0 (571) Could not perform strict object check of state sonoff.0.Trockner.SleepMode: DB closed 2023-07-02 08:22:21.068 - warn: sonoff.0 (571) get state error: Connection is closed. 2023-07-02 08:22:21.013 - info: host.IOBroker-Proxmox stopInstance system.adapter.javascript.0 killing pid 419 2023-07-02 08:22:21.034 - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.0 killing pid 2000 2023-07-02 08:22:21.048 - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.1 killing pid 2006 2023-07-02 08:22:21.065 - info: host.IOBroker-Proxmox stopInstance system.adapter.ham.0 killing pid 479 2023-07-02 08:22:21.066 - info: host.IOBroker-Proxmox stopInstance system.adapter.hmip.0 killing pid 490 2023-07-02 08:22:21.075 - info: host.IOBroker-Proxmox stopInstance system.adapter.mqtt.0 killing pid 520 2023-07-02 08:22:21.084 - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.0 killing pid 563 2023-07-02 08:22:21.086 - info: host.IOBroker-Proxmox stopInstance system.adapter.sonoff.0 killing pid 571 2023-07-02 08:22:21.087 - info: host.IOBroker-Proxmox stopInstance system.adapter.zigbee.0 killing pid 596 2023-07-02 08:22:21.106 - info: host.IOBroker-Proxmox stopInstance system.adapter.samsung.0 killing pid 614 2023-07-02 08:22:21.107 - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.1 killing pid 641 2023-07-02 08:22:21.107 - info: host.IOBroker-Proxmox stopInstance system.adapter.tr-064.0 killing pid 652 2023-07-02 08:22:21.108 - info: host.IOBroker-Proxmox stopInstance system.adapter.amazon-dash.0 killing pid 718 2023-07-02 08:22:21.108 - info: host.IOBroker-Proxmox stopInstance system.adapter.device-reminder.0 killing pid 751 2023-07-02 08:22:21.109 - info: host.IOBroker-Proxmox stopInstance system.adapter.hue-extended.0 killing pid 820 2023-07-02 08:22:21.109 - info: host.IOBroker-Proxmox stopInstance system.adapter.octoprint.0 killing pid 877 2023-07-02 08:22:21.109 - info: host.IOBroker-Proxmox stopInstance system.adapter.pushsafer.0 killing pid 896 2023-07-02 08:22:21.111 - info: host.IOBroker-Proxmox stopInstance system.adapter.sourceanalytix.0 killing pid 916 2023-07-02 08:22:21.112 - info: host.IOBroker-Proxmox stopInstance system.adapter.text2command.0 killing pid 927 2023-07-02 08:22:21.114 - info: host.IOBroker-Proxmox stopInstance system.adapter.trashschedule.0 killing pid 946 2023-07-02 08:22:21.114 - info: host.IOBroker-Proxmox stopInstance system.adapter.web.0 killing pid 957 2023-07-02 08:22:21.114 - info: host.IOBroker-Proxmox stopInstance system.adapter.zwave2.0 killing pid 972 2023-07-02 08:22:21.136 - info: host.IOBroker-Proxmox stopInstance system.adapter.proxmox.0 killing pid 979 2023-07-02 08:22:21.136 - info: host.IOBroker-Proxmox stopInstance system.adapter.jarvis.0 killing pid 1035 2023-07-02 08:22:20.096 - error: shelly.0 (563) 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(). 2023-07-02 08:22:20.097 - error: shelly.0 (563) unhandled promise rejection: DB closed 2023-07-02 08:22:21.359 - error: shelly.0 (563) Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) 2023-07-02 08:22:21.360 - error: shelly.0 (563) DB closed 2023-07-02 08:22:20.061 - error: shelly.1 (641) 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(). 2023-07-02 08:22:20.061 - error: shelly.1 (641) unhandled promise rejection: DB closed 2023-07-02 08:22:21.510 - error: shelly.1 (641) Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) 2023-07-02 08:22:21.511 - error: shelly.1 (641) DB closed 2023-07-02 08:22:21.698 - info: host.IOBroker-Proxmox instance system.adapter.admin.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:23.719 - info: host.IOBroker-Proxmox instance system.adapter.email.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.178 - info: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.218 - info: host.IOBroker-Proxmox instance system.adapter.alarm.1 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.383 - info: host.IOBroker-Proxmox instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.384 - info: host.IOBroker-Proxmox instance system.adapter.cloud.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.507 - info: host.IOBroker-Proxmox instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.563 - info: host.IOBroker-Proxmox instance system.adapter.enocean.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.637 - info: host.IOBroker-Proxmox instance system.adapter.info.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.637 - info: host.IOBroker-Proxmox instance system.adapter.accuweather.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.683 - info: host.IOBroker-Proxmox instance system.adapter.energiefluss.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.712 - info: host.IOBroker-Proxmox instance system.adapter.alarm.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.804 - info: host.IOBroker-Proxmox instance system.adapter.alarm.2 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.804 - info: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.834 - info: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.864 - info: host.IOBroker-Proxmox instance system.adapter.iot.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.956 - info: host.IOBroker-Proxmox instance system.adapter.worx.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.956 - info: host.IOBroker-Proxmox instance system.adapter.senec.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:26.986 - info: host.IOBroker-Proxmox instance system.adapter.alexa2.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.016 - info: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.187 - info: host.IOBroker-Proxmox instance system.adapter.admin.1 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.187 - info: host.IOBroker-Proxmox instance system.adapter.ham.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.304 - info: host.IOBroker-Proxmox instance system.adapter.hmip.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.491 - warn: host.IOBroker-Proxmox instance system.adapter.mqtt.0 terminated due to SIGTERM 2023-07-02 08:22:27.491 - info: host.IOBroker-Proxmox instance system.adapter.mqtt.0 terminated with code null () 2023-07-02 08:22:27.491 - info: host.IOBroker-Proxmox instance system.adapter.samsung.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.532 - info: host.IOBroker-Proxmox instance system.adapter.tr-064.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.574 - info: host.IOBroker-Proxmox instance system.adapter.amazon-dash.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.639 - info: host.IOBroker-Proxmox instance system.adapter.device-reminder.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.640 - info: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.683 - info: host.IOBroker-Proxmox instance system.adapter.octoprint.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.712 - warn: host.IOBroker-Proxmox instance system.adapter.pushsafer.0 terminated due to SIGTERM 2023-07-02 08:22:27.712 - info: host.IOBroker-Proxmox instance system.adapter.pushsafer.0 terminated with code null () 2023-07-02 08:22:27.797 - info: host.IOBroker-Proxmox instance system.adapter.sourceanalytix.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.797 - info: host.IOBroker-Proxmox instance system.adapter.trashschedule.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:27.826 - warn: host.IOBroker-Proxmox instance system.adapter.web.0 terminated due to SIGTERM 2023-07-02 08:22:27.826 - info: host.IOBroker-Proxmox instance system.adapter.web.0 terminated with code null () 2023-07-02 08:22:27.856 - warn: host.IOBroker-Proxmox instance system.adapter.telegram.0 terminated due to SIGTERM 2023-07-02 08:22:27.857 - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 terminated with code null () 2023-07-02 08:22:27.947 - warn: host.IOBroker-Proxmox instance system.adapter.telegram.1 terminated due to SIGTERM 2023-07-02 08:22:27.947 - info: host.IOBroker-Proxmox instance system.adapter.telegram.1 terminated with code null () 2023-07-02 08:22:27.948 - warn: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated due to SIGTERM 2023-07-02 08:22:27.948 - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated with code null () 2023-07-02 08:22:28.091 - error: host.IOBroker-Proxmox Caught by controller[0]: 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(). The promise rejected with the reason: 2023-07-02 08:22:28.091 - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed 2023-07-02 08:22:28.091 - error: host.IOBroker-Proxmox Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-07-02 08:22:28.092 - error: host.IOBroker-Proxmox Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-07-02 08:22:28.092 - error: host.IOBroker-Proxmox Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-07-02 08:22:28.092 - error: host.IOBroker-Proxmox Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) 2023-07-02 08:22:28.092 - warn: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated due to SIGTERM 2023-07-02 08:22:28.093 - info: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated with code null () 2023-07-02 08:22:28.211 - warn: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated due to SIGTERM 2023-07-02 08:22:28.211 - info: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated with code null () 2023-07-02 08:22:28.266 - warn: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated due to SIGTERM 2023-07-02 08:22:28.266 - info: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated with code null () 2023-07-02 08:22:28.266 - error: host.IOBroker-Proxmox Caught by controller[0]: 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(). The promise rejected with the reason: 2023-07-02 08:22:28.266 - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed 2023-07-02 08:22:28.266 - error: host.IOBroker-Proxmox Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2023-07-02 08:22:28.267 - error: host.IOBroker-Proxmox Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2023-07-02 08:22:28.267 - error: host.IOBroker-Proxmox Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) 2023-07-02 08:22:28.267 - error: host.IOBroker-Proxmox Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) 2023-07-02 08:22:28.267 - warn: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated due to SIGTERM 2023-07-02 08:22:28.267 - info: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated with code null () 2023-07-02 08:22:28.324 - warn: host.IOBroker-Proxmox instance system.adapter.text2command.0 terminated due to SIGTERM 2023-07-02 08:22:28.324 - info: host.IOBroker-Proxmox instance system.adapter.text2command.0 terminated with code null () 2023-07-02 08:22:28.378 - warn: host.IOBroker-Proxmox instance system.adapter.zwave2.0 terminated due to SIGTERM 2023-07-02 08:22:28.378 - info: host.IOBroker-Proxmox instance system.adapter.zwave2.0 terminated with code null () 2023-07-02 08:22:28.378 - info: host.IOBroker-Proxmox instance system.adapter.proxmox.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:28.416 - info: host.IOBroker-Proxmox instance system.adapter.jarvis.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:28.461 - info: host.IOBroker-Proxmox instance system.adapter.history.0 terminated with code 0 (NO_ERROR) 2023-07-02 08:22:28.461 - info: host.IOBroker-Proxmox All instances are stopped. 2023-07-02 08:22:28.548 - info: host.IOBroker-Proxmox terminated 2023-07-02 08:22:40.258 - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting 2023-07-02 08:22:40.264 - info: host.IOBroker-Proxmox Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2023-07-02 08:22:40.264 - info: host.IOBroker-Proxmox hostname: IOBroker-Proxmox, node: v18.16.1 2023-07-02 08:22:40.265 - info: host.IOBroker-Proxmox ip addresses: 192.168.171.35 fe80::a8d4:caff:fe76:9b25 2023-07-02 08:22:42.861 - info: host.IOBroker-Proxmox connected to Objects and States 2023-07-02 08:22:42.929 - info: host.IOBroker-Proxmox added notifications configuration of host 2023-07-02 08:22:44.098 - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeCurrent" 2023-07-02 08:22:44.099 - info: host.IOBroker-Proxmox 52 instances found 2023-07-02 08:22:44.201 - info: host.IOBroker-Proxmox starting 47 instances 2023-07-02 08:22:44.398 - info: host.IOBroker-Proxmox instance system.adapter.admin.0 started with pid 304 2023-07-02 08:22:44.411 - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeNewest" 2023-07-02 08:22:44.460 - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeNewestNext" 2023-07-02 08:22:44.466 - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmCurrent" 2023-07-02 08:22:44.472 - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmNewest" 2023-07-02 08:22:44.478 - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmNewestNext" 2023-07-02 08:22:44.484 - info: host.IOBroker-Proxmox Some obsolete host states deleted. 2023-07-02 08:22:47.062 - info: admin.0 (304) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:22:47.238 - info: admin.0 (304) requesting all states 2023-07-02 08:22:47.239 - info: admin.0 (304) requesting all objects 2023-07-02 08:22:49.031 - info: admin.0 (304) Request actual repository... 2023-07-02 08:22:50.673 - info: host.IOBroker-Proxmox instance system.adapter.admin.1 started with pid 331 2023-07-02 08:22:52.406 - info: admin.0 (304) received all objects 2023-07-02 08:22:52.747 - info: host.IOBroker-Proxmox instance system.adapter.email.0 started with pid 338 2023-07-02 08:22:53.503 - info: admin.0 (304) Secure socket.io server listening on port 8081 2023-07-02 08:22:53.516 - info: admin.0 (304) https server listening on port 8081 2023-07-02 08:22:53.516 - info: admin.0 (304) Use link "https://127.0.0.1:8081" to configure. 2023-07-02 08:22:53.959 - info: host.IOBroker-Proxmox Updating repository "Alternativ latest" under "http://iobroker.live/repo/sources-dist-latest.json" 2023-07-02 08:22:56.111 - info: admin.0 (304) Repository received successfully. 2023-07-02 08:22:57.236 - info: host.IOBroker-Proxmox instance system.adapter.history.0 started with pid 353 2023-07-02 08:22:58.740 - info: admin.1 (331) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:22:58.863 - info: admin.1 (331) requesting all states 2023-07-02 08:22:58.866 - info: admin.1 (331) requesting all objects 2023-07-02 08:22:59.468 - info: email.0 (338) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.email, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:23:03.023 - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 started with pid 384 2023-07-02 08:23:04.036 - info: admin.1 (331) received all objects 2023-07-02 08:23:04.638 - info: admin.1 (331) Request actual repository... 2023-07-02 08:23:04.712 - info: admin.1 (331) socket.io server listening on port 8088 2023-07-02 08:23:04.714 - info: admin.1 (331) http server listening on port 8088 2023-07-02 08:23:04.715 - info: admin.1 (331) Use link "http://127.0.0.1:8088" to configure. 2023-07-02 08:23:05.163 - info: host.IOBroker-Proxmox Updating repository "Alternativ latest" under "http://iobroker.live/repo/sources-dist-latest.json" 2023-07-02 08:23:05.328 - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 started with pid 391 2023-07-02 08:23:07.569 - info: history.0 (353) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.history, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:23:07.973 - info: history.0 (353) enabled logging of alias.0.Steckdosen.Steckdose Datenschrank.value_electric_w_consumed (Count=1), Alias=false 2023-07-02 08:23:07.975 - info: history.0 (353) enabled logging of alias.0.Steckdosen.Steckdose_Geschirrspüler.Power (Count=2), Alias=false 2023-07-02 08:23:07.976 - info: history.0 (353) enabled logging of alias.0.Steckdosen.Steckdose_Trockner.ENERGY_Power (Count=3), Alias=false 2023-07-02 08:23:07.976 - info: history.0 (353) enabled logging of shelly.0.SHPLG-S#9D8C29#1.Relay0.Power (Count=4), Alias=false 2023-07-02 08:23:07.977 - info: history.0 (353) enabled logging of sonoff.0.Trockner.ENERGY_Power (Count=5), Alias=false 2023-07-02 08:23:07.977 - info: history.0 (353) enabled logging of fb-checkpresence.0.Nadine (Count=6), Alias=false 2023-07-02 08:23:07.978 - info: history.0 (353) enabled logging of fb-checkpresence.0.Andre (Count=7), Alias=false 2023-07-02 08:23:08.102 - info: admin.1 (331) Repository received successfully. 2023-07-02 08:23:08.902 - info: host.IOBroker-Proxmox instance system.adapter.telegram.1 started with pid 406 2023-07-02 08:23:12.610 - info: host.IOBroker-Proxmox instance system.adapter.alexa2.0 started with pid 421 2023-07-02 08:23:13.911 - info: javascript.0 (384) starting. Version 7.0.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:23:14.001 - info: telegram.0 (391) starting. Version 1.16.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:23:16.752 - info: javascript.0 (384) requesting all states 2023-07-02 08:23:16.754 - info: javascript.0 (384) requesting all objects 2023-07-02 08:23:16.935 - info: host.IOBroker-Proxmox instance system.adapter.ham.0 started with pid 440 2023-07-02 08:23:21.513 - info: host.IOBroker-Proxmox instance system.adapter.hmip.0 started with pid 451 2023-07-02 08:23:22.514 - info: telegram.1 (406) starting. Version 1.16.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:23:24.032 - info: ham.0 (440) starting. Version 5.3.1 in /opt/iobroker/node_modules/iobroker.ham, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:23:24.158 - info: alexa2.0 (421) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v18.16.1, js-controller: 5.0.5 2023-07-02 08:23:24.217 - info: javascript.0 (384) received all objects 2023-07-02 08:23:24.130 - info: ham.0 (440) Install/Update the following Libraries: homebridge-govee@7.8.0 2023-07-02 08:23:24.161 - info: ham.0 (440) Install/Update homebridge-govee@7.8.0 2023-07-02 08:23:24.179 - info: ham.0 (440) All Libraries installed/updated 2023-07-02 08:23:24.181 - info: ham.0 (440) Adapter uses Wrapper mode 2023-07-02 08:23:26.489 - info: alexa2.0 (421) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. 2023-07-02 08:23:26.792 - info: javascript.0 (384) received all states 2023-07-02 08:23:26.835 - info: host.IOBroker-Proxmox instance scheduled system.adapter.ical.0 0,30 * * * * 2023-07-02 08:23:26.903 - info: host.IOBroker-Proxmox instance system.adapter.ical.0 started with pid 476 2023-07-02 08:23:27.793 - info: javascript.0 (384) script.js.global.icon_mapping: compiling TypeScript source... 2023-07-02 08:23:29.301 - info: javascript.0 (384) script.js.global.icon_mapping: source code did not change, using cached compilation result... 2023-07-02 08:23:30.634 - info: host.IOBroker-Proxmox instance system.adapter.mqtt.0 started with pid 498@gelberlemmy sagte in Troubleshooting NodeJS update:
Aber diese Errors hatte ich mit der Version 16 nicht.
nicht wegen nodejs, wohl eher wegen
@gelberlemmy sagte in Troubleshooting NodeJS update:
iobroker.js-controller version 5.0.5 js-controller
@gelberlemmy sagte in Troubleshooting NodeJS update:
Im Log schauen
du zeigst nie den Start deines amazon-dash.0, worum es doch ursprünglich geht
umgestiegen von Proxmox auf Unraid
-
@thomas-braun sagte in Troubleshooting NodeJS update:
Das sind Meldungen, weil die Datenbank da schon heruntergefahren wurde und die Adapter nicht wissen wohin damit.
Welche Datenbank wird von dir versendet?Wie meinst Du das mit dem versenden ?
@gelberlemmy sagte in Troubleshooting NodeJS update:
Wie meinst Du das mit dem versenden ?
verwendet
-
@gelberlemmy sagte in Troubleshooting NodeJS update:
Aber diese Errors hatte ich mit der Version 16 nicht.
nicht wegen nodejs, wohl eher wegen
@gelberlemmy sagte in Troubleshooting NodeJS update:
iobroker.js-controller version 5.0.5 js-controller
@gelberlemmy sagte in Troubleshooting NodeJS update:
Im Log schauen
du zeigst nie den Start deines amazon-dash.0, worum es doch ursprünglich geht
@crunchip sagte in Troubleshooting NodeJS update:
@gelberlemmy sagte in Troubleshooting NodeJS update:
Aber diese Errors hatte ich mit der Version 16 nicht.
nicht wegen nodejs, wohl eher wegen
@gelberlemmy sagte in Troubleshooting NodeJS update:
iobroker.js-controller version 5.0.5 js-controller
@gelberlemmy sagte in Troubleshooting NodeJS update:
Im Log schauen
du zeigst nie den Start deines amazon-dash.0, worum es doch ursprünglich geht
Der Dashbutton ist mir nur dabei einmalig aufgefallen. Der hat nur einmalig rumgezickt.....Es ging hauptsächlich um das Node.js Update von 16 auf 18. Da fing das alles an. Ahhh okay. Dann hat das wohl eher dann mit dem Controller zu tun.
-
@crunchip sagte in Troubleshooting NodeJS update:
@gelberlemmy sagte in Troubleshooting NodeJS update:
Aber diese Errors hatte ich mit der Version 16 nicht.
nicht wegen nodejs, wohl eher wegen
@gelberlemmy sagte in Troubleshooting NodeJS update:
iobroker.js-controller version 5.0.5 js-controller
@gelberlemmy sagte in Troubleshooting NodeJS update:
Im Log schauen
du zeigst nie den Start deines amazon-dash.0, worum es doch ursprünglich geht
Der Dashbutton ist mir nur dabei einmalig aufgefallen. Der hat nur einmalig rumgezickt.....Es ging hauptsächlich um das Node.js Update von 16 auf 18. Da fing das alles an. Ahhh okay. Dann hat das wohl eher dann mit dem Controller zu tun.
@gelberlemmy sagte in Troubleshooting NodeJS update:
Der Dashbutton ist mir nur dabei einmalig aufgefallen. Der hat nur einmalig rumgezickt
das wurde auch durchs nodejs upgrade ausgelöst,
der Rest deiner Meldungen hat allerdings weniger damit zu tunumgestiegen von Proxmox auf Unraid
-
Das sind Meldungen, weil die Datenbank da schon heruntergefahren wurde und die Adapter nicht wissen wohin damit.
Welche Datenbank wird von dir verwendet?Edit: Typo.
@thomas-braun sagte in Troubleshooting NodeJS update:
Das sind Meldungen, weil die Datenbank da schon heruntergefahren wurde und die Adapter nicht wissen wohin damit.
Welche Datenbank wird von dir verwendet?Edit: Typo.
Ich habe nie etwas vom Standart geändert. Wo kann ich dies ersehen ?
-
@crunchip sagte in Troubleshooting NodeJS update:
@gelberlemmy sagte in Troubleshooting NodeJS update:
Aber diese Errors hatte ich mit der Version 16 nicht.
nicht wegen nodejs, wohl eher wegen
@gelberlemmy sagte in Troubleshooting NodeJS update:
iobroker.js-controller version 5.0.5 js-controller
@gelberlemmy sagte in Troubleshooting NodeJS update:
Im Log schauen
du zeigst nie den Start deines amazon-dash.0, worum es doch ursprünglich geht
Der Dashbutton ist mir nur dabei einmalig aufgefallen. Der hat nur einmalig rumgezickt.....Es ging hauptsächlich um das Node.js Update von 16 auf 18. Da fing das alles an. Ahhh okay. Dann hat das wohl eher dann mit dem Controller zu tun.
@gelberlemmy sagte in Troubleshooting NodeJS update:
Der Dashbutton ist mir nur dabei einmalig aufgefallen. Der hat nur einmalig rumgezickt....
Der ist dann einmalig gegen nodejs18 neugebaut worden und gut ist.
-
@gelberlemmy sagte in Troubleshooting NodeJS update:
Der Dashbutton ist mir nur dabei einmalig aufgefallen. Der hat nur einmalig rumgezickt
das wurde auch durchs nodejs upgrade ausgelöst,
der Rest deiner Meldungen hat allerdings weniger damit zu tun@crunchip sagte in Troubleshooting NodeJS update:
@gelberlemmy sagte in Troubleshooting NodeJS update:
Der Dashbutton ist mir nur dabei einmalig aufgefallen. Der hat nur einmalig rumgezickt
das wurde auch durchs nodejs upgrade ausgelöst,
der Rest deiner Meldungen hat allerdings weniger damit zu tunOkay. Dies läuft jetzt ganz normal
-
@thomas-braun sagte in Troubleshooting NodeJS update:
Das sind Meldungen, weil die Datenbank da schon heruntergefahren wurde und die Adapter nicht wissen wohin damit.
Welche Datenbank wird von dir verwendet?Edit: Typo.
Ich habe nie etwas vom Standart geändert. Wo kann ich dies ersehen ?
@gelberlemmy sagte in Troubleshooting NodeJS update:
Ich habe nie etwas vom Standart geändert. Wo kann ich dies ersehen ?
U.a. in
iob diagOder
iob status -
@thomas-braun sagte in Troubleshooting NodeJS update:
Das sind Meldungen, weil die Datenbank da schon heruntergefahren wurde und die Adapter nicht wissen wohin damit.
Welche Datenbank wird von dir verwendet?Edit: Typo.
Ich habe nie etwas vom Standart geändert. Wo kann ich dies ersehen ?
-
@gelberlemmy sagte in Troubleshooting NodeJS update:
Ich habe nie etwas vom Standart geändert. Wo kann ich dies ersehen ?
U.a. in
iob diagOder
iob status@thomas-braun sagte in Troubleshooting NodeJS update:
iob diag
Ist dies ausreichend ?
======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Ubuntu 22.04.2 LTS Kernel: 5.15.108-1-pve Installation: lxc Timezone: Europe/Berlin (CEST, +0200) User-ID: 1001 X-Server: false Boot Target: graphical.target Pending OS-Updates: 1 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.16.1 /usr/bin/node v18.16.1 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 6.1G 3.6G 1.9G 0.0K 723M 2.6G Swap: 1.0G 0B 1.0G Total: 7.2G 3.6G 2.9G Active iob-Instances: 47 Active repo(s): Alternativ latest ioBroker Core: js-controller 5.0.5 admin 6.5.9 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : IOBroker-Proxmox - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : IOBroker-Proxmox - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : IOBroker-Proxmox - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 26026 States: 23558 Size of iob-Database: 32M /opt/iobroker/iobroker-data/objects.jsonl 20M /opt/iobroker/iobroker-data/objects.json.migrated 20M /opt/iobroker/iobroker-data/objects.json.bak.migrated 11M /opt/iobroker/iobroker-data/states.jsonl 4.0M /opt/iobroker/iobroker-data/states.json.migrated 4.0M /opt/iobroker/iobroker-data/states.json.bak.migrated 0 /opt/iobroker/iobroker-data/states.json.broken =================== END OF SUMMARY ==================== -
@thomas-braun sagte in Troubleshooting NodeJS update:
iob diag
Ist dies ausreichend ?
======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Ubuntu 22.04.2 LTS Kernel: 5.15.108-1-pve Installation: lxc Timezone: Europe/Berlin (CEST, +0200) User-ID: 1001 X-Server: false Boot Target: graphical.target Pending OS-Updates: 1 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v18.16.1 /usr/bin/node v18.16.1 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 6.1G 3.6G 1.9G 0.0K 723M 2.6G Swap: 1.0G 0B 1.0G Total: 7.2G 3.6G 2.9G Active iob-Instances: 47 Active repo(s): Alternativ latest ioBroker Core: js-controller 5.0.5 admin 6.5.9 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : IOBroker-Proxmox - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : IOBroker-Proxmox - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : IOBroker-Proxmox - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 26026 States: 23558 Size of iob-Database: 32M /opt/iobroker/iobroker-data/objects.jsonl 20M /opt/iobroker/iobroker-data/objects.json.migrated 20M /opt/iobroker/iobroker-data/objects.json.bak.migrated 11M /opt/iobroker/iobroker-data/states.jsonl 4.0M /opt/iobroker/iobroker-data/states.json.migrated 4.0M /opt/iobroker/iobroker-data/states.json.bak.migrated 0 /opt/iobroker/iobroker-data/states.json.broken =================== END OF SUMMARY ====================@gelberlemmy sagte in Troubleshooting NodeJS update:
Active repo(s): Alternativ latest
warum bist du nicht in stable unterwegs?
dann hättest du auch
@gelberlemmy sagte in Troubleshooting NodeJS update:
js-controller 5.0.5
nicht diese Beta-Test Version
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@gelberlemmy sagte in Troubleshooting NodeJS update:
Active repo(s): Alternativ latest
warum bist du nicht in stable unterwegs?
dann hättest du auch
@gelberlemmy sagte in Troubleshooting NodeJS update:
js-controller 5.0.5
nicht diese Beta-Test Version
@homoran sagte in Troubleshooting NodeJS update:
@gelberlemmy sagte in Troubleshooting NodeJS update:
Active repo(s): Alternativ latest
warum bist du nicht in stable unterwegs?
dann hättest du auch
@gelberlemmy sagte in Troubleshooting NodeJS update:
js-controller 5.0.5
nicht diese Beta-Test Version
Ja da hast Du recht. Werde umstellen.....
-
Nach dem Update auf node.js 18.x kann ich keinen Adapter mehr updaten. Dann bekomme ich folgende Meldung:
npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm,npm WARN old lockfile so supplemental metadata must be fetched from the registry.npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient...npm WARN old lockfile npm ERR! code EBADENGINE npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-05T08_17_34_310Z-debug-0.loghat jemand einen Tipp, wo ich hier ansetzten soll?
-
Nach dem Update auf node.js 18.x kann ich keinen Adapter mehr updaten. Dann bekomme ich folgende Meldung:
npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm,npm WARN old lockfile so supplemental metadata must be fetched from the registry.npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient...npm WARN old lockfile npm ERR! code EBADENGINE npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-05T08_17_34_310Z-debug-0.loghat jemand einen Tipp, wo ich hier ansetzten soll?
@bfelizardo Da muss mehr log sein? Nutzt du ggf daikin-cloud als Adapter? Dann bitte Github update des Adapters machen
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
Nach dem Update auf node.js 18.x kann ich keinen Adapter mehr updaten. Dann bekomme ich folgende Meldung:
npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm,npm WARN old lockfile so supplemental metadata must be fetched from the registry.npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient...npm WARN old lockfile npm ERR! code EBADENGINE npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-05T08_17_34_310Z-debug-0.loghat jemand einen Tipp, wo ich hier ansetzten soll?
@bfelizardo sagte in Troubleshooting NodeJS update:
EBADENGINE
wie hast du denn das
@bfelizardo sagte in Troubleshooting NodeJS update:
Update auf node.js 18.x
durchgeführt.
klingt nach einer falschen Version, die nicht zu deiner Hardware passt.kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@bfelizardo Da muss mehr log sein? Nutzt du ggf daikin-cloud als Adapter? Dann bitte Github update des Adapters machen
@apollon77 Danke für die Antwort! Ne, ich nutzte kein Daikin Adapter.
Ich habe versucht den javascript Adapter von v6.1.4 auf v7.0.3 upzudaten. Hier die vollständige Logausgabe, wenn ich versuche den Apdapbter im iobroker unter Adapter upzudaten. Gleiche Fehler bekomme ich auch beim update vom HomeMatic RPC Adpater. Denke das passiert egal welchen Adpater ich updaten will.
$ iobroker upgrade javascript@7.0.3 --debug Update javascript from @6.1.4 to @7.0.3 NPM version: 9.7.2 Installing iobroker.javascript@7.0.3... (System call) npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm,npm WARN old lockfile so supplemental metadata must be fetched from the registry.npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient...npm WARN old lockfile npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! notsup Required: {"node":"^12.16.1 || ^10.15.2 || ^8.15.1","npm":"^6.4.1"}npm ERR! notsup Actual: {"npm":"9.7.2","node":"v18.16.1"}npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-05T08_46_11_943Z-debug-0.log upload [261] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/adminWords.js adminWords.js application/javascript upload [250] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/click.ogg google-blockly/media/click.ogg audio/ogg upload [200] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/own/msg/uk.js google-blockly/own/msg/uk.js application/javascript upload [150] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Amplifier.6f5d18048328386033f8.svg static/media/Amplifier.6f5d18048328386033f8.svg image/svg+xml upload [100] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Heater.b53bccc334bbb9238a36.svg static/media/Heater.b53bccc334bbb9238a36.svg image/svg+xml upload [90] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Light.21f1a5dfcc93f8ba1214.svg static/media/Light.21f1a5dfcc93f8ba1214.svg image/svg+xml upload [80] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Office.7e6a38218390b655e270.svg static/media/Office.7e6a38218390b655e270.svg image/svg+xml upload [70] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Receiver.26b5ae166395a6dcb83f.svg static/media/Receiver.26b5ae166395a6dcb83f.svg image/svg+xml upload [60] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Speaker.db548379676317470c4f.svg static/media/Speaker.db548379676317470c4f.svg image/svg+xml upload [50] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Toilet.83604dd2daafb67067dd.svg static/media/Toilet.83604dd2daafb67067dd.svg image/svg+xml upload [40] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Water.f50411984c5c24fa574d.svg static/media/Water.f50411984c5c24fa574d.svg image/svg+xml upload [30] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/names.e7efb5283d98000c74ac.txt static/media/names.e7efb5283d98000c74ac.txt text/plain upload [20] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.js vs/editor/editor.main.js application/javascript upload [19] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.de.js vs/editor/editor.main.nls.de.js application/javascript upload [18] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.es.js vs/editor/editor.main.nls.es.js application/javascript upload [17] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.fr.js vs/editor/editor.main.nls.fr.js application/javascript upload [16] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.it.js vs/editor/editor.main.nls.it.js application/javascript upload [15] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.ja.js vs/editor/editor.main.nls.ja.js application/javascript upload [14] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.js vs/editor/editor.main.nls.js application/javascript upload [13] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.ko.js vs/editor/editor.main.nls.ko.js application/javascript upload [12] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.ru.js vs/editor/editor.main.nls.ru.js application/javascript upload [11] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.zh-cn.js vs/editor/editor.main.nls.zh-cn.js application/javascript upload [10] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.zh-tw.js vs/editor/editor.main.nls.zh-tw.js application/javascript upload [9] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/css/cssMode.js vs/language/css/cssMode.js application/javascript upload [8] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/css/cssWorker.js vs/language/css/cssWorker.js application/javascript upload [7] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/html/htmlMode.js vs/language/html/htmlMode.js application/javascript upload [6] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/html/htmlWorker.js vs/language/html/htmlWorker.js application/javascript upload [5] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/json/jsonMode.js vs/language/json/jsonMode.js application/javascript upload [4] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/json/jsonWorker.js vs/language/json/jsonWorker.js application/javascript upload [3] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/typescript/tsMode.js vs/language/typescript/tsMode.js application/javascript upload [2] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/typescript/tsWorker.js vs/language/typescript/tsWorker.js application/javascript upload [0] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/monaco.d.ts vs/monaco.d.ts video/mp2t Process exited with code 0 -
@apollon77 Danke für die Antwort! Ne, ich nutzte kein Daikin Adapter.
Ich habe versucht den javascript Adapter von v6.1.4 auf v7.0.3 upzudaten. Hier die vollständige Logausgabe, wenn ich versuche den Apdapbter im iobroker unter Adapter upzudaten. Gleiche Fehler bekomme ich auch beim update vom HomeMatic RPC Adpater. Denke das passiert egal welchen Adpater ich updaten will.
$ iobroker upgrade javascript@7.0.3 --debug Update javascript from @6.1.4 to @7.0.3 NPM version: 9.7.2 Installing iobroker.javascript@7.0.3... (System call) npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm,npm WARN old lockfile so supplemental metadata must be fetched from the registry.npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient...npm WARN old lockfile npm ERR! code EBADENGINE npm ERR! engine Unsupported engine npm ERR! notsup Required: {"node":"^12.16.1 || ^10.15.2 || ^8.15.1","npm":"^6.4.1"}npm ERR! notsup Actual: {"npm":"9.7.2","node":"v18.16.1"}npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-05T08_46_11_943Z-debug-0.log upload [261] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/adminWords.js adminWords.js application/javascript upload [250] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/media/click.ogg google-blockly/media/click.ogg audio/ogg upload [200] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/google-blockly/own/msg/uk.js google-blockly/own/msg/uk.js application/javascript upload [150] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Amplifier.6f5d18048328386033f8.svg static/media/Amplifier.6f5d18048328386033f8.svg image/svg+xml upload [100] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Heater.b53bccc334bbb9238a36.svg static/media/Heater.b53bccc334bbb9238a36.svg image/svg+xml upload [90] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Light.21f1a5dfcc93f8ba1214.svg static/media/Light.21f1a5dfcc93f8ba1214.svg image/svg+xml upload [80] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Office.7e6a38218390b655e270.svg static/media/Office.7e6a38218390b655e270.svg image/svg+xml upload [70] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Receiver.26b5ae166395a6dcb83f.svg static/media/Receiver.26b5ae166395a6dcb83f.svg image/svg+xml upload [60] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Speaker.db548379676317470c4f.svg static/media/Speaker.db548379676317470c4f.svg image/svg+xml upload [50] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Toilet.83604dd2daafb67067dd.svg static/media/Toilet.83604dd2daafb67067dd.svg image/svg+xml upload [40] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/Water.f50411984c5c24fa574d.svg static/media/Water.f50411984c5c24fa574d.svg image/svg+xml upload [30] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/static/media/names.e7efb5283d98000c74ac.txt static/media/names.e7efb5283d98000c74ac.txt text/plain upload [20] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.js vs/editor/editor.main.js application/javascript upload [19] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.de.js vs/editor/editor.main.nls.de.js application/javascript upload [18] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.es.js vs/editor/editor.main.nls.es.js application/javascript upload [17] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.fr.js vs/editor/editor.main.nls.fr.js application/javascript upload [16] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.it.js vs/editor/editor.main.nls.it.js application/javascript upload [15] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.ja.js vs/editor/editor.main.nls.ja.js application/javascript upload [14] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.js vs/editor/editor.main.nls.js application/javascript upload [13] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.ko.js vs/editor/editor.main.nls.ko.js application/javascript upload [12] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.ru.js vs/editor/editor.main.nls.ru.js application/javascript upload [11] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.zh-cn.js vs/editor/editor.main.nls.zh-cn.js application/javascript upload [10] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/editor/editor.main.nls.zh-tw.js vs/editor/editor.main.nls.zh-tw.js application/javascript upload [9] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/css/cssMode.js vs/language/css/cssMode.js application/javascript upload [8] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/css/cssWorker.js vs/language/css/cssWorker.js application/javascript upload [7] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/html/htmlMode.js vs/language/html/htmlMode.js application/javascript upload [6] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/html/htmlWorker.js vs/language/html/htmlWorker.js application/javascript upload [5] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/json/jsonMode.js vs/language/json/jsonMode.js application/javascript upload [4] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/json/jsonWorker.js vs/language/json/jsonWorker.js application/javascript upload [3] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/typescript/tsMode.js vs/language/typescript/tsMode.js application/javascript upload [2] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/language/typescript/tsWorker.js vs/language/typescript/tsWorker.js application/javascript upload [0] javascript.admin /opt/iobroker/node_modules/iobroker.javascript/admin/vs/monaco.d.ts vs/monaco.d.ts video/mp2t Process exited with code 0@apollon77 scheint als müsste ich wieder downgraden auf node.js 12.x
-
@bfelizardo sagte in Troubleshooting NodeJS update:
EBADENGINE
wie hast du denn das
@bfelizardo sagte in Troubleshooting NodeJS update:
Update auf node.js 18.x
durchgeführt.
klingt nach einer falschen Version, die nicht zu deiner Hardware passt.@homoran danke! Habe die Anleitung verwendet von Dutchman: https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18
-
@homoran danke! Habe die Anleitung verwendet von Dutchman: https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18
-
@thomas-braun welchen Teil soll ich da genau posten. Steckt ja recht viel Info drin oder darf ich dir das per pm schicken?
Support us
713
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge