[GELÖST] Umzug vom Pin64 auf Proxmox schlägt fehl.
-
Schau dir die Kisten per
iob diagan.
Und grundsätzlich würde ich das Altsystem zuvor noch auf den allerletzten Stand (inkl. nodejs@20 und js-controller 6.0.9) bringen und damit dann in das neue System reinschlüpfen. -
Danke für die schnelle Antwort. Das ergab iob diag
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iobroker01 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.2.16-3-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Etc/UTC (UTC, +0000) User-ID: 0 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 21 Nodejs-Installation: /usr/bin/nodejs v18.20.4 /usr/bin/node v18.20.4 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.28.0 Recommended versions are nodejs 16.20.2 and npm 8.19.4 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 4.3G 375M 2.0G 118K 1.9G 3.9G Swap: 1.1G 0B 1.1G Total: 5.4G 375M 3.1G Active iob-Instances: 2 Upgrade policy: none ioBroker Core: js-controller 6.0.9 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker01 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : iobroker01 - disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 8926 States: 8169 Size of iob-Database: 19M /opt/iobroker/iobroker-data/objects.jsonl 4.4M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Dann werde ich mich mal mit der Ansatz vom Altsystem auf den allerletzten Stand (inkl. nodejs@20 und js-controller 6.0.9) bringen beschäftigen.
Viele Grüße
Kurt
-
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
von einem Pin64 (ähnlich Raspberry)
ich nehme mal an pine64, und hoffentlich mit armbian!?
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
Das Backup wurde mir auch als erfolgreich und abgeschlossen angezeigt.
ja, dann sind die Konfigurationsdateien wieder erfolgreich hergestellt.
Jetzt wird allesxfür das neue OS, das aktuelle node und die andere Hardware neu gebaut.
Das dauert.
in der Zeit das System nicht stören.@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
der admin Adapter als fehlerhaft gemeldet.
welcher Controller war auf dem Pine?
-
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
Timezone: Etc/UTC (UTC, +0000)
Auch im LXC ist die korrekte Zeitzone zu setzen.
admin ist in Version 7.x aktuell.
-
Ich habe jetzt geupdatet, aber jetzt habe ich auch gleich die Probleme, ich bekomme die Weboberfläche nicht mehr auf.
iob diag ergibt folgende Ausgabe
======================= SUMMARY ======================= v.2024-05-22 Static hostname: pineh64meins Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.89-sunxi64 Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 0 Display-Server: true Boot Target: graphical.target Pending OS-Updates: 1 Pending iob updates: 19 This system needs to be REBOOTED NOW! Nodejs-Installation: /usr/bin/nodejs v20.16.0 /usr/bin/node v20.16.0 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.2 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.0G 793M 645M 9.0M 1.6G 2.1G Swap: 1.5G 37M 1.5G Total: 4.5G 830M 2.1G Active iob-Instances: 9 Active repo(s): stable ioBroker Core: js-controller 4.0.23 admin 7.0.22 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : pineh64meins - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : pineh64meins - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 8924 States: 8210 Size of iob-Database: 9.7M /opt/iobroker/iobroker-data/objects.jsonl 2.7M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================beim Log File sehe ich nicht wirklich das Problem ...
d 2024-08-07 17:59:57.846 - info: host.pineh64meins iobroker.js-controller version 4.0.23 js-controller starting 2024-08-07 17:59:57.863 - info: host.pineh64meins Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2024-08-07 17:59:57.865 - info: host.pineh64meins hostname: pineh64meins, node: v20.16.0 2024-08-07 17:59:57.868 - info: host.pineh64meins ip addresses: 172.20.20.78 2001:9e8:e86d:c500:9542:2902:52af:acc0 fd00::32a6:e51:a40f:6520 fe80::7ed7:d731:864b:6 edd 10.8.0.1 fe80::ec98:7bba:6dca:a18e 2024-08-07 18:00:01.037 - info: host.pineh64meins connected to Objects and States 2024-08-07 18:00:01.182 - info: host.pineh64meins added notifications configuration of host 2024-08-07 18:00:01.188 - info: host.pineh64meins Node.js version has changed from 12.22.12 to 20.16.0 2024-08-07 18:00:01.884 - info: host.pineh64meins Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2024-08-07 18:00:02.627 - info: host.pineh64meins 21 instances found 2024-08-07 18:00:02.720 - info: host.pineh64meins starting 10 instances 2024-08-07 18:00:02.953 - info: host.pineh64meins instance system.adapter.javascript.0 started with pid 1562232 2024-08-07 18:00:06.880 - info: host.pineh64meins instance system.adapter.telegram.0 started with pid 1562241 2024-08-07 18:00:10.924 - info: host.pineh64meins instance system.adapter.tr-064.0 started with pid 1562252 2024-08-07 18:00:11.332 - info: javascript.0 (1562232) starting. Version 6.1.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.16.0, js-controller: 4. 0.23 2024-08-07 18:00:14.078 - info: javascript.0 (1562232) requesting all states 2024-08-07 18:00:14.085 - info: javascript.0 (1562232) requesting all objects 2024-08-07 18:00:15.168 - info: host.pineh64meins instance scheduled system.adapter.ical.0 0 */8 * * * 2024-08-07 18:00:15.182 - info: host.pineh64meins instance system.adapter.ical.0 started with pid 1562267 2024-08-07 18:00:18.536 - info: javascript.0 (1562232) received all objects 2024-08-07 18:00:18.836 - info: javascript.0 (1562232) received all states 2024-08-07 18:00:19.407 - info: host.pineh64meins instance system.adapter.tuya.0 started with pid 1562278 2024-08-07 18:00:19.836 - info: javascript.0 (1562232) Start javascript script.js.common.Skript_Abfall_Info 2024-08-07 18:00:20.290 - info: javascript.0 (1562232) script.js.common.Skript_Abfall_Info: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file s ...skipping 1 line 2024-08-07 18:00:20.406 - info: javascript.0 (1562232) Start javascript script.js.common.Skript_Stromzaehler 2024-08-07 18:00:20.436 - info: javascript.0 (1562232) script.js.common.Skript_Stromzaehler: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:20.440 - info: javascript.0 (1562232) Start javascript script.js.common.Skript_Bad_1_unten_Fensterkontakt 2024-08-07 18:00:20.461 - info: javascript.0 (1562232) script.js.common.Skript_Bad_1_unten_Fensterkontakt: registered 1 subscription, 0 schedules, 0 messages, 0 lo gs and 0 file subscriptions 2024-08-07 18:00:20.463 - info: javascript.0 (1562232) Start javascript script.js.common.Skript_Cube 2024-08-07 18:00:20.484 - info: javascript.0 (1562232) script.js.common.Skript_Cube: registered 5 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscri ptions 2024-08-07 18:00:20.487 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Zaehlerstand 2024-08-07 18:00:20.635 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Zaehlerstand: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:20.637 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solareinspeisung 2024-08-07 18:00:20.656 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solareinspeisung: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:20.658 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Energiebezug 2024-08-07 18:00:20.675 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Energiebezug: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:20.677 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solareinspeisung_Tag 2024-08-07 18:00:20.696 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solareinspeisung_Tag: registered 1 subscription, 0 schedules, 0 messages, 0 l ogs and 0 file subscriptions 2024-08-07 18:00:20.698 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solarertrag_Vortag 2024-08-07 18:00:20.741 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solarertrag_Vortag: registered 0 subscriptions, 1 schedule, 0 messages, 0 log s and 0 file subscriptions 2024-08-07 18:00:20.743 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solar_Steckdose_off 2024-08-07 18:00:20.762 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solar_Steckdose_off: registered 0 subscriptions, 1 schedule, 0 messages, 0 lo gs and 0 file subscriptions 2024-08-07 18:00:20.764 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solarertrag_Tag_1 2024-08-07 18:00:20.781 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solarertrag_Tag_1: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:20.783 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_WP_Einspeisung_ist 2024-08-07 18:00:20.799 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_WP_Einspeisung_ist: registered 1 subscription, 0 schedules, 0 messages, 0 log s and 0 file subscriptions 2024-08-07 18:00:20.811 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_WP_Einspeisung_Vortag 2024-08-07 18:00:20.874 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_WP_Einspeisung_Vortag: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:20.877 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_WP_Einspeisung_Tag 2024-08-07 18:00:20.897 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_WP_Einspeisung_Tag: registered 1 subscription, 0 schedules, 0 messages, 0 log s and 0 file subscriptions 2024-08-07 18:00:20.899 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solarertrag_Vortag_1 2024-08-07 18:00:20.953 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solarertrag_Vortag_1: registered 0 subscriptions, 1 schedule, 0 messages, 0 l ...skipping 1 line 2024-08-07 18:00:20.955 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solarertrag_Tag_2 2024-08-07 18:00:20.989 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solarertrag_Tag_2: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:20.991 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Heizung_WP 2024-08-07 18:00:21.013 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Heizung_WP: registered 3 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:21.015 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Bad2_Heizung_Einspeisung_ist 2024-08-07 18:00:21.032 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Bad2_Heizung_Einspeisung_ist: registered 1 subscription, 0 schedules, 0 messa ges, 0 logs and 0 file subscriptions 2024-08-07 18:00:21.037 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Bad2_Einspeisung_Tag 2024-08-07 18:00:21.054 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Bad2_Einspeisung_Tag: registered 1 subscription, 0 schedules, 0 messages, 0 l ogs and 0 file subscriptions 2024-08-07 18:00:21.057 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Bad2_Einspeisung_Vortag 2024-08-07 18:00:21.101 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Bad2_Einspeisung_Vortag: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions 2024-08-07 18:00:21.102 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solarertrag_Tag_real 2024-08-07 18:00:21.119 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solarertrag_Tag_real: registered 1 subscription, 0 schedules, 0 messages, 0 l ogs and 0 file subscriptions 2024-08-07 18:00:21.121 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solar_Summe_Eigenverbrauch_real 2024-08-07 18:00:21.138 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solar_Summe_Eigenverbrauch_real: registered 0 subscriptions, 1 schedule, 0 me ssages, 0 logs and 0 file subscriptions 2024-08-07 18:00:21.140 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Aztouch_Berechnung 2024-08-07 18:00:21.159 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Aztouch_Berechnung: registered 14 subscriptions, 0 schedules, 0 messages, 0 l ogs and 0 file subscriptions 2024-08-07 18:00:21.291 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solar_Steckdose_on 2024-08-07 18:00:21.322 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solar_Steckdose_on: registered 0 subscriptions, 1 schedule, 0 messages, 0 log s and 0 file subscriptions 2024-08-07 18:00:21.324 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solarertrag_ist 2024-08-07 18:00:21.357 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solarertrag_ist: registered 1 subscription, 0 schedules, 0 messages, 0 logs a nd 0 file subscriptions 2024-08-07 18:00:21.359 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Solarertrag_Tag 2024-08-07 18:00:21.412 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Solarertrag_Tag: registered 1 subscription, 0 schedules, 0 messages, 0 logs a nd 0 file subscriptions 2024-08-07 18:00:21.414 - info: javascript.0 (1562232) Start javascript script.js.common.Solar1.Skript_Berechnung_optimiert 2024-08-07 18:00:21.504 - info: javascript.0 (1562232) script.js.common.Solar1.Skript_Berechnung_optimiert: registered 1 subscription, 0 schedules, 0 messages, 0 l ogs and 0 file subscriptions 2024-08-07 18:00:21.659 - info: telegram.0 (1562241) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.16.0, js-controller: 4.0.2 3 2024-08-07 18:00:21.695 - info: tr-064.0 (1562252) starting. Version 4.2.17 in /opt/iobroker/node_modules/iobroker.tr-064, node: v20.16.0, js-controller: 4.0.23 2024-08-07 18:00:21.989 - error: tr-064.0 (1562252) Password error: Please re-enter the password in Admin. Stopping 2024-08-07 18:00:22.898 - info: host.pineh64meins instance system.adapter.sonoff.0 started with pid 1562297 ...skipping 1 line 2024-08-07 18:00:25.390 - info: ical.0 (1562267) processing URL: calendar1 https://calendar.google.com/...... 2024-08-07 18:00:26.931 - info: host.pineh64meins instance system.adapter.zigbee.0 started with pid 1562320 2024-08-07 18:00:27.412 - info: tuya.0 (1562278) starting. Version 3.12.1 in /opt/iobroker/node_modules/iobroker.tuya, node: v20.16.0, js-controller: 4.0.23 2024-08-07 18:00:29.589 - info: sonoff.0 (1562297) starting. Version 2.5.1 in /opt/iobroker/node_modules/iobroker.sonoff, node: v20.16.0, js-controller: 4.0.23 2024-08-07 18:00:29.903 - info: sonoff.0 (1562297) Starting MQTT authenticated server on port 1888 2024-08-07 18:00:30.651 - info: tuya.0 (1562278) bf02c1a29db1e7a25dm1qq: Connect locally to device 2024-08-07 18:00:30.656 - info: tuya.0 (1562278) bf02c1a29db1e7a25dm1qq Init with IP=172.20.20.119, Key=d4461386bb6df78d, Version=3.3 2024-08-07 18:00:30.674 - info: tuya.0 (1562278) bf515d7af7908e8e4724bg: Connect locally to device 2024-08-07 18:00:30.676 - info: tuya.0 (1562278) bf515d7af7908e8e4724bg Init with IP=172.20.20.66, Key=fe7d433533c0c615, Version=3.3 2024-08-07 18:00:30.691 - info: tuya.0 (1562278) bf7ab943c5f8465fe1kakg: Connect locally to device 2024-08-07 18:00:30.693 - info: tuya.0 (1562278) bf7ab943c5f8465fe1kakg Init with IP=172.20.20.90, Key=afcab1215365395a, Version=3.3 2024-08-07 18:00:30.714 - info: tuya.0 (1562278) bfb78c13d741ec6ed15jep: Connect locally to device 2024-08-07 18:00:30.720 - info: tuya.0 (1562278) Existing devices initialized 2024-08-07 18:00:30.737 - info: tuya.0 (1562278) Listen for local Tuya devices on port 6666 2024-08-07 18:00:30.740 - info: tuya.0 (1562278) Listen for encrypted local Tuya devices on port 6667 2024-08-07 18:00:30.887 - info: host.pineh64meins instance system.adapter.backitup.0 started with pid 1562342 2024-08-07 18:00:31.055 - info: ical.0 (1562267) Terminated (NO_ERROR): Without reason 2024-08-07 18:00:31.883 - info: host.pineh64meins instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) 2024-08-07 18:00:33.749 - warn: tuya.0 (1562278) bf515d7af7908e8e4724bg: Error on Reconnect (1): connect EHOSTUNREACH 172.20.20.66:6668 2024-08-07 18:00:33.760 - warn: tuya.0 (1562278) bf02c1a29db1e7a25dm1qq: Error on Reconnect (1): connect EHOSTUNREACH 172.20.20.119:6668 2024-08-07 18:00:34.946 - info: host.pineh64meins instance system.adapter.web.0 started with pid 1562353 2024-08-07 18:00:38.094 - info: backitup.0 (1562342) starting. Version 2.5.10 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.16.0, js-controller: 4.0.2 3 2024-08-07 18:00:38.397 - info: backitup.0 (1562342) [iobroker] backup was activated at 02:40 every 1 day(s) 2024-08-07 18:00:38.625 - info: zigbee.0 (1562320) starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.16.0, js-controller: 4.0.23 2024-08-07 18:00:38.893 - info: host.pineh64meins instance scheduled system.adapter.daswetter.0 */120 * * * * 2024-08-07 18:00:38.928 - info: host.pineh64meins instance system.adapter.daswetter.0 started with pid 1562372 2024-08-07 18:00:38.911 - info: zigbee.0 (1562320) Starting Zigbee npm ... 2024-08-07 18:00:40.613 - info: zigbee.0 (1562320) Installed Version: iobroker.zigbee@1.8.10 2024-08-07 18:00:41.885 - info: web.0 (1562353) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.web, node: v20.16.0, js-controller: 4.0.23 2024-08-07 18:00:42.430 - info: web.0 (1562353) socket.io server listening on port 8082 2024-08-07 18:00:42.452 - info: web.0 (1562353) http server listening on port 8082 2024-08-07 18:00:43.508 - info: zigbee.0 (1562320) Coordinator firmware version: {"type":"EZSP v8","meta":{"product":8,"majorrel":"6","minorrel":"10","maintrel":"3 ","revision":"6.10.3.0 build 297"}} 2024-08-07 18:00:43.515 - info: zigbee.0 (1562320) Unable to disable LED, unsupported function. 2024-08-07 18:00:43.559 - info: zigbee.0 (1562320) --> transmitPower : normal 2024-08-07 18:00:43.591 - info: zigbee.0 (1562320) Currently 14 devices are joined: 2024-08-07 18:00:43.704 - info: zigbee.0 (1562320) 0xa4c1381088ebb803 (addr 54056): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.719 - info: zigbee.0 (1562320) 0xa4c1387f5b9e86e9 (addr 5487): WSD500A - TuYa Temperature & humidity sensor (EndDevice) 2024-08-07 18:00:43.725 - info: zigbee.0 (1562320) 0xa4c138e7c5c834b1 (addr 17049): TS0203 - TuYa Door sensor (EndDevice) ...skipping 1 line 2024-08-07 18:00:43.736 - info: zigbee.0 (1562320) 0xa4c138c5b266a383 (addr 36846): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.743 - info: zigbee.0 (1562320) 0x00158d000760bf4e (addr 53362): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice) 2024-08-07 18:00:43.748 - info: zigbee.0 (1562320) 0xa4c138ce5ad986c6 (addr 61883): WSD500A - TuYa Temperature & humidity sensor (EndDevice) 2024-08-07 18:00:43.756 - info: zigbee.0 (1562320) 0xa4c1384066065878 (addr 64499): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.762 - info: zigbee.0 (1562320) 0xa4c1380d59c4e599 (addr 11686): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.769 - info: zigbee.0 (1562320) 0xa4c138027f2c263b (addr 7492): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.775 - info: zigbee.0 (1562320) 0xa4c138628cd4dab5 (addr 34703): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.783 - info: zigbee.0 (1562320) 0xa4c13840089d5bd7 (addr 908): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.818 - info: zigbee.0 (1562320) 0xa4c138c0998ae622 (addr 60942): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.825 - info: zigbee.0 (1562320) 0xa4c138a155ce9924 (addr 8852): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-08-07 18:00:43.828 - info: zigbee.0 (1562320) Zigbee started 2024-08-07 18:00:44.832 - info: daswetter.0 (1562372) starting. Version 3.1.4 in /opt/iobroker/node_modules/iobroker.daswetter, node: v20.16.0, js-controller: 4.0. 23 2024-08-07 18:00:56.838 - warn: tuya.0 (1562278) bf02c1a29db1e7a25dm1qq: Error on Reconnect (3): connect EHOSTUNREACH 172.20.20.119:6668 2024-08-07 18:00:56.845 - warn: tuya.0 (1562278) bf515d7af7908e8e4724bg: Error on Reconnect (3): connect EHOSTUNREACH 172.20.20.66:6668 2024-08-07 18:01:15.555 - warn: zigbee.0 (1562320) DeviceAvailability:Failed to ping 0xa4c138c5b266a383 TS011F 2024-08-07 18:01:15.764 - warn: zigbee.0 (1562320) DeviceAvailability:Failed to ping 0xa4c1380d59c4e599 TS011F 2024-08-07 18:01:15.811 - warn: zigbee.0 (1562320) DeviceAvailability:Failed to ping 0xa4c138027f2c263b TS011F 2024-08-07 18:01:16.216 - warn: zigbee.0 (1562320) DeviceAvailability:Failed to ping 0xa4c13840089d5bd7 TS011F 2024-08-07 18:01:16.413 - warn: zigbee.0 (1562320) DeviceAvailability:Failed to ping 0xa4c138c0998ae622 TS011F 2024-08-07 18:01:16.621 - warn: zigbee.0 (1562320) DeviceAvailability:Failed to ping 0xa4c138a155ce9924 TS011F 2024-08-07 18:01:19.922 - info: daswetter.0 (1562372) still wrong data structure from server received! repaired... 2024-08-07 18:01:29.166 - info: daswetter.0 (1562372) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment 2024-08-07 18:01:29.705 - info: daswetter.0 (1562372) cleaned everything up... 2024-08-07 18:01:29.860 - info: host.pineh64meins instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-08-07 18:01:39.911 - warn: tuya.0 (1562278) bf515d7af7908e8e4724bg: Error on Reconnect (5): connect EHOSTUNREACH 172.20.20.66:6668 2024-08-07 18:01:39.918 - warn: tuya.0 (1562278) bf02c1a29db1e7a25dm1qq: Error on Reconnect (5): connect EHOSTUNREACH 172.20.20.119:6668 2024-08-07 18:02:42.982 - warn: tuya.0 (1562278) bf02c1a29db1e7a25dm1qq: Error on Reconnect (7): connect EHOSTUNREACH 172.20.20.119:6668 2024-08-07 18:02:42.985 - warn: tuya.0 (1562278) bf515d7af7908e8e4724bg: Error on Reconnect (7): connect EHOSTUNREACH 172.20.20.66:6668 -
iob start admin -
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
iobroker.js-controller version 4.0.23 js-controller starting
woher stammt dieses log?
-
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
Pending OS-Updates: 1
Pending iob updates: 19
This system needs to be REBOOTED NOW!Zuvor
sudo systemctl set-default multi-user.target -
@thomas-braun
Danke das wars, aber warum muss ich nach dem Start (iobroker start) noch mal iob start admin ausführen? -
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
(iobroker start) noch mal iob start admin ausführen?
Weil das zwei paar Schuh' sind.
Kiste jetzt neugestartet? Die restlichen Updates eingespielt?
-
@homoran Vom iobroker, den js-controller muss ich noch auf eine höhere Version anheben.
-
@thomas-braun Danke, nein das habe ich noch nicht rebootet, muss ich noch. Mit restlichen Updates meinst Du js-controller?
-
Auch. Aber da hängen ja noch 18 weitere ioBroker-Updates in der Luft.
Neben einem für das OS. -
-
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
2024-08-07 18:00:25.390 - info: ical.0 (1562267) processing URL: calendar1 https://calendar.google.com/
@Homoran vllt besser die url rauszunehmen
-
@crunchip erledigt!
-
@thomas-braun @thomas-braun Danke jetzt bin ich wohl ertsmal mit den alten Server fast fertig,
Mal noch eine Frage, unter Instanzen gibt es alias manager.0 und devices.0 ohne Funktion. Ich habe mal iobroker add devices ausgeführt und bekomme aber folgende MeldungINFO: Directory "/opt/iobroker/node_modules/iobroker.devices/www" was not found! Nothing was uploaded or deleted. host.pineh64meins error: this adapter does not allow multiple instances Ist das korrekt, oder muss ich da noch was machen? Ich bin der Meinung, dass es vor dem Update nicht so war.t
-
@kurt_88 sagte in Umzug vom Pin64 auf Proxmox schlägt fehl.:
Pending OS-Updates: 1
Da hängt noch was.
sudo apt update sudo apt full-upgrade sudo rebootWo ist denn die Ausgabe von iob diag nun hin????
-
@thomas-braun said in Umzug vom Pin64 auf Proxmox schlägt fehl.:
apt full-upgrade
Sorry war noch eine alter Auszug, anbei der aktuelle
======================= SUMMARY ======================= v.2024-05-22 Static hostname: pineh64meins Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.6.36-current-sunxi64 Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 0 Display-Server: true Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.16.0 /usr/bin/node v20.16.0 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.2 Recommended versions are nodejs 20.16.0 and npm 10.8.1 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 2.9G 1.2G 977M 5.0M 795M 1.7G Swap: 1.5G 0B 1.5G Total: 4.4G 1.2G 2.4G Active iob-Instances: 16 Upgrade policy: none ioBroker Core: js-controller 6.0.9 admin 7.0.22 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : pineh64meins - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : pineh64meins - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 9007 States: 8238 Size of iob-Database: 12M /opt/iobroker/iobroker-data/objects.jsonl 13M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Danke jetzt bin ich wohl ertsmal mit den alten Server fast fertig,
Mal noch eine Frage, unter Instanzen gibt es alias manager.0 und devices.0 ohne Funktion. Ich habe mal iobroker add devices ausgeführt und bekomme aber folgende MeldungINFO: Directory "/opt/iobroker/node_modules/iobroker.devices/www" was not found! Nothing was uploaded or deleted. host.pineh64meins error: this adapter does not allow multiple instances -
Hampel da nicht als root herum...
Immer wieder die gleiche Leier...Display-Server: true Boot Target: multi-user.targetsollte eigentlich auch nicht gemeldet werden. Kann aber sein, das das falsch auf der Plattforn erkannt wird.
