Admin Adapter startet nach restore nicht mehr
-
Hallo zusammen,
ich habe vorhin ein Backup meiner IoB Instanz über den BackItUp Adapter gemacht und jetzt versucht den bei der neuen Instanz zu restoren (ist in beiden fällen ein Docker Container - nur neuer Host). Der restore an sich wird auch erfolgreich durchgeführt, als letzte Nachricht steht da, dass neu gestartet wird. Wenn ich jetzt in den Log des COntainers schaue kommt folgende Fehlermeldung:================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]Über den Befehl
iob logskonnte ich sehen, dass noch die npm Module installiert werden. Dies habe ich abgewartet. Hierbei tritt der Fehler auf, dass er den vis Adapter nicht installieren kann, aber das ist vermutlich noch ein anderes Problem:2023-08-09 13:30:55.758 - error: vis.0 (1387) 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-08-09 13:30:55.759 - error: vis.0 (1387) unhandled promise rejection: Not exists 2023-08-09 13:30:55.760 - error: vis.0 (1387) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at process.processImmediate (node:internal/timers:478:21) 2023-08-09 13:30:55.761 - error: vis.0 (1387) Not exists 2023-08-09 13:30:56.267 - info: vis.0 (1387) terminating 2023-08-09 13:30:56.270 - warn: vis.0 (1387) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-08-09 13:30:57.140 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-08-09 13:31:58.057 - info: host.iobroker iobroker npm-install: exit 25 2023-08-09 13:31:59.058 - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log!Danach passiert nichts mehr (habe noch ca. ne Stunde gewartet) und hab dann den Container nochmal neu gestartet.
Der admin Adapter ist jedoch nicht gestartet und lässt sich auch nicht starten. Mitiob start adminwirft er zwar keine Fehlermeldung, aber er startet den Adapter auch nicht.
Wenn ich versuche ihn mit folgenden Command zu startennode node_modules/iobroker.admin/main.js --logserhalte ich nur einen Fehler:2023-08-09 14:39:30.382 - error: admin.0 (2200) admin.0 invalid process id scenario 170 vs. own ID 2200. Stopping 2023-08-09 14:39:30.389 - info: admin.0 (2200) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reasonKann mir hier jemand helfen oder hat noch ne Idee was ich falsch gemacht haben könnte?
Viele Grüße
Henrik -
@ghostrider sagte in Admin Adapter startet nach restore nicht mehr:
Hierbei tritt der Fehler auf, dass er den vis Adapter nicht installieren kann, aber das ist vermutlich noch ein anderes Problem:
richtig ... steht hier alles zu im Forum . ( alte Vis Version installieren dann ein upgrade ... )
und hab dann den Container nochmal neu gestartet.
zeige mal das ioBroker Log davon !
-
@glasfaser
Hier der Log des Docker Containers, seit 1. Start bis zum Ende (1 Neustart)-------------------------------------------------------------------------------- ------------------------- 2023-08-09 14:20:52 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: x86_64 ----- ----- hostname: iobroker ----- ----- ----- ----- Version Information ----- ----- image: v8.0.1 ----- ----- build: 2023-07-19T23:45:22+00:00 ----- ----- node: v18.17.0 ----- ----- npm: 9.6.7 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- ----- USBDEVICES: /dev/ttyUSB0 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- Updating Linux packages on first run... Done. Registering maintenance script as command... Done. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- IoBroker backup file detected in /opt/iobroker. Since Docker Image v8, automatic initial restore is no longer supported! IoBroker will start with a fresh installation, while your backup file will be copied into the backup directory. You will be able to restore your backup file manually by using the backitup adapter or the containers maintenance script. For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). Copying backup file and restoring initial ioBroker installation... Done. -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo with gosu... Done. Initializing a fresh installation of ioBroker... Done. Hostname in ioBroker does not match the hostname of this container. Updating hostname to "iobroker"... The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "iobroker". The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "iobroker". The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "iobroker". Done. -------------------------------------------------------------------------------- ----- Step 4 of 5: Applying special settings ----- -------------------------------------------------------------------------------- Some adapters have special requirements/ settings which can be activated by the use of environment variables. For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). USBDEVICES is set. Setting permissions for "/dev/ttyUSB0"... Done. -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### host.iobroker check instance "system.adapter.admin.0" for host "iobroker" host.iobroker check instance "system.adapter.discovery.0" for host "iobroker" host.iobroker check instance "system.adapter.backitup.0" for host "iobroker" ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging] Send diag info: {"uuid":"XXX","language":"de","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.17.0","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.23","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"Common KVM processor","cpus":4,"mem":8323035136,"ostype":"Linux","city":""} ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] Terminated Recived termination signal (SIGTERM). Shutting down ioBroker... -------------------------------------------------------------------------------- ------------------------- 2023-08-09 14:25:47 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: x86_64 ----- ----- hostname: iobroker ----- ----- ----- ----- Version Information ----- ----- image: v8.0.1 ----- ----- build: 2023-07-19T23:45:22+00:00 ----- ----- node: v18.17.0 ----- ----- npm: 9.6.7 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- ----- USBDEVICES: /dev/ttyUSB0 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- This is not the first run of this container. Skipping first run preparation. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo with gosu... Done. Checking Database connection... Done. Hostname in ioBroker matches the hostname of this container. No action required. -------------------------------------------------------------------------------- ----- Step 4 of 5: Applying special settings ----- -------------------------------------------------------------------------------- Some adapters have special requirements/ settings which can be activated by the use of environment variables. For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). USBDEVICES is set. Setting permissions for "/dev/ttyUSB0"... Done. -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### ================================== > LOG REDIRECT system.adapter.admin.0 => true [starting] host.iobroker check instance "system.adapter.admin.0" for host "iobroker" host.iobroker check instance "system.adapter.influxdb.0" for host "iobroker" host.iobroker check instance "system.adapter.javascript.0" for host "iobroker" host.iobroker check instance "system.adapter.telegram.0" for host "iobroker" host.iobroker check instance "system.adapter.mqtt.0" for host "iobroker" host.iobroker check instance "system.adapter.ping.0" for host "iobroker" host.iobroker check instance "system.adapter.samsung.0" for host "iobroker" host.iobroker check instance "system.adapter.sonoff.0" for host "iobroker" host.iobroker check instance "system.adapter.spotify-premium.0" for host "iobroker" host.iobroker check instance "system.adapter.unifi.0" for host "iobroker" host.iobroker check instance "system.adapter.zigbee.0" for host "iobroker" host.iobroker check instance "system.adapter.discovery.0" for host "iobroker" host.iobroker check instance "system.adapter.backitup.0" for host "iobroker" host.iobroker check instance "system.adapter.anelhut.0" for host "iobroker" host.iobroker check instance "system.adapter.birthdays.0" for host "iobroker" host.iobroker check instance "system.adapter.birthdays.1" for host "iobroker" host.iobroker check instance "system.adapter.device-reminder.0" for host "iobroker" host.iobroker check instance "system.adapter.discord.0" for host "iobroker" host.iobroker check instance "system.adapter.linux-control.0" for host "iobroker" host.iobroker check instance "system.adapter.net-tools.0" for host "iobroker" host.iobroker check instance "system.adapter.parser.0" for host "iobroker" host.iobroker check instance "system.adapter.pi-hole.0" for host "iobroker" host.iobroker check instance "system.adapter.proxmox.0" for host "iobroker" host.iobroker check instance "system.adapter.simple-api.0" for host "iobroker" host.iobroker check instance "system.adapter.vis.0" for host "iobroker" host.iobroker check instance "system.adapter.web.0" for host "iobroker" Send diag info: {"uuid":"XXX","language":"","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.17.0","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.6.23","platform":"Javascript/Node.js"},"anelhut":{"version":"1.0.13","platform":"Javascript/Node.js"},"birthdays":{"version":"2.2.0","platform":"Javascript/Node.js"},"device-reminder":{"version":"1.2.9","platform":"Javascript/Node.js"},"discord":{"version":"1.1.6","platform":"Javascript/Node.js"},"influxdb":{"version":"3.2.0","platform":"Javascript/Node.js"},"javascript":{"version":"7.0.3","platform":"Javascript/Node.js"},"linux-control":{"version":"1.1.3","platform":"Javascript/Node.js"},"mqtt":{"version":"4.1.1","platform":"Javascript/Node.js"},"net-tools":{"version":"0.2.0","platform":"Javascript/Node.js"},"parser":{"version":"1.3.2","platform":"Javascript/Node.js"},"pi-hole":{"version":"1.3.6","platform":"Javascript/Node.js"},"ping":{"version":"1.5.3","platform":"Javascript/Node.js"},"proxmox":{"version":"1.3.5","platform":"Javascript/Node.js"},"samsung":{"version":"0.5.11","platform":"Javascript/Node.js"},"simple-api":{"version":"2.7.2","platform":"Javascript/Node.js"},"socketio":{"version":"4.2.0","platform":"Javascript/Node.js"},"sonoff":{"version":"2.5.3","platform":"Javascript/Node.js"},"spotify-premium":{"version":"1.2.2","platform":"Javascript/Node.js"},"telegram":{"version":"1.16.0","platform":"Javascript/Node.js"},"unifi":{"version":"0.6.6","platform":"Javascript/Node.js"},"vis":{"version":"1.4.16","platform":"Javascript/Node.js"},"web":{"version":"4.3.0","platform":"Javascript/Node.js"},"zigbee":{"version":"1.8.21","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":26,"compactMode":false,"noCompactInstances":0,"model":"Common KVM processor","cpus":4,"mem":8323035136,"ostype":"Linux","city":"","vis":0} ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]Oder meintest du diesen Log von IoBroker selbst?
2023-08-09 14:31:15.151 - info: host.iobroker iobroker npm-install: host.iobroker object system.adapter.web created/updated 2023-08-09 14:31:16.185 - info: host.iobroker iobroker npm-install: exit 0 2023-08-09 14:31:17.186 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 2 attempt 2023-08-09 14:31:17.188 - info: host.iobroker iobroker install vis@1.4.16 using installedFrom 2023-08-09 14:31:20.716 - info: host.iobroker iobroker npm-install: NPM version: 9.6.7Installing iobroker.vis@1.4.16... (System call) 2023-08-09 14:31:28.062 - info: vis.0 (1509) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24 2023-08-09 14:31:28.379 - info: vis.0 (1509) vis license is OK. 2023-08-09 14:31:28.426 - error: vis.0 (1509) 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-08-09 14:31:28.428 - error: vis.0 (1509) unhandled promise rejection: Not exists 2023-08-09 14:31:28.435 - error: vis.0 (1509) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at process.processImmediate (node:internal/timers:478:21) 2023-08-09 14:31:28.437 - error: vis.0 (1509) Not exists 2023-08-09 14:31:28.945 - info: vis.0 (1509) terminating 2023-08-09 14:31:28.945 - warn: vis.0 (1509) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-08-09 14:31:29.574 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-08-09 14:31:30.616 - info: host.iobroker iobroker npm-install: exit 25 2023-08-09 14:31:31.617 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 3 attempt 2023-08-09 14:31:31.617 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-08-09 14:31:33.772 - info: host.iobroker iobroker npm-install: NPM version: 9.6.7 2023-08-09 14:31:33.773 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-08-09 14:31:41.407 - info: vis.0 (1567) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24 2023-08-09 14:31:41.546 - info: vis.0 (1567) vis license is OK. 2023-08-09 14:31:41.574 - error: vis.0 (1567) 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-08-09 14:31:41.575 - error: vis.0 (1567) unhandled promise rejection: Not exists 2023-08-09 14:31:41.576 - error: vis.0 (1567) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at process.processImmediate (node:internal/timers:478:21) 2023-08-09 14:31:41.577 - error: vis.0 (1567) Not exists 2023-08-09 14:31:42.082 - info: vis.0 (1567) terminating 2023-08-09 14:31:42.085 - warn: vis.0 (1567) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-08-09 14:31:42.778 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-08-09 14:31:43.818 - info: host.iobroker iobroker npm-install: exit 25 2023-08-09 14:31:44.820 - warn: host.iobroker startInstance cannot find adapter "vis@1.4.16". Try to install it... 4 attempt 2023-08-09 14:31:44.821 - info: host.iobroker iobroker install vis@1.4.16 using installedVersion 2023-08-09 14:31:47.179 - info: host.iobroker iobroker npm-install: NPM version: 9.6.7 2023-08-09 14:31:47.182 - info: host.iobroker iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2023-08-09 14:31:55.581 - info: vis.0 (1627) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24 2023-08-09 14:31:55.914 - info: vis.0 (1627) vis license is OK. 2023-08-09 14:31:55.943 - error: vis.0 (1627) 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-08-09 14:31:55.944 - error: vis.0 (1627) unhandled promise rejection: Not exists 2023-08-09 14:31:55.946 - error: vis.0 (1627) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at process.processImmediate (node:internal/timers:478:21) 2023-08-09 14:31:55.946 - error: vis.0 (1627) Not exists 2023-08-09 14:31:56.449 - info: vis.0 (1627) terminating 2023-08-09 14:31:56.450 - warn: vis.0 (1627) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-08-09 14:31:57.040 - error: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis@1.4.16: 6 2023-08-09 14:31:58.057 - info: host.iobroker iobroker npm-install: exit 25 2023-08-09 14:31:59.058 - error: host.iobroker Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log! 2023-08-09 14:39:30.382 - error: admin.0 (2200) admin.0 invalid process id scenario 170 vs. own ID 2200. Stopping 2023-08-09 14:39:30.389 - info: admin.0 (2200) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-08-09 14:43:35.437 - info: vis.0 (2422) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.0, js-controller: 4.0.24 2023-08-09 14:43:35.796 - info: vis.0 (2422) vis license is OK. 2023-08-09 14:43:35.829 - error: vis.0 (2422) 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-08-09 14:43:35.829 - error: vis.0 (2422) unhandled promise rejection: Not exists 2023-08-09 14:43:35.831 - error: vis.0 (2422) Error: Not exists at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2983:17) at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1043:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:1092:29) at process.processImmediate (node:internal/timers:478:21) 2023-08-09 14:43:35.831 - error: vis.0 (2422) Not exists 2023-08-09 14:43:36.334 - info: vis.0 (2422) terminating 2023-08-09 14:43:36.335 - warn: vis.0 (2422) Terminated (UNCAUGHT_EXCEPTION): Without reasonDas ist ein Teil den ich noch über
iob logserhalte. Brauchst du mehr, dann könnte ich noch den kompletten Log als Datei anhängen. -
ok, hat sich erledigt, das ganze war meine Schuld. Ich hatte auf der alten Instanz SSL mit einem extra Docker Volume für die Zertifikate eingerichtet. Das Volume habe ich zwar auch beim neuen Container gemappt, allerdings vergessen die Zertifikatsdateien hinzuzufügen. Danach und einem Neustart des Containers ist der Adapter auch problemlos gestartet.
