Uralt System updaten oder Umzug
-
Danke.....
habs nirgends gefunden.
Bin gespannt, obs was wird. -
@mr-x sagte in Uralt System updaten oder Umzug:
Bin gespannt, obs was wird.
Hast du das uralte System denn zuvor soweit wie möglich an die aktuellen Versionen herangeführt?
-
Leider nein, da es mir, wie eingangs erwähnt, mit allen Anleitungen der Welt nicht gelungen ist.
Deswegen habe ich jetzt unter CT eine iobroker instanz laufen.
habe vom Grundsystem in Proxmox ein Backup erstellt.
Aber so wie es aussieht, reagiert ioBroker nach dem Einspielen des Backups nicht (wie von manchen erwartet).Somit bleibt mir wohl nichts anderes übrig, als hier erneut um Hilfe mit dem Upgrade meines Systems zu helfen.....
-
@mr-x sagte in Uralt System updaten oder Umzug:
da es mir, wie eingangs erwähnt, mit allen Anleitungen der Welt nicht gelungen ist.
heisst was?
Eine vollständige Aktualisierung aller Komponenten auf die neuesten Versionen wird natürlich nicht möglich sein.Die Frage war aber ob du alles soweit möglich aktualisiert hast.
@mr-x sagte in Uralt System updaten oder Umzug:
Aber so wie es aussieht, reagiert ioBroker nach dem Einspielen des Backups nicht
heisst was?
bitte Fakten in Form von logs o.ä. -
@mr-x sagte in Uralt System updaten oder Umzug:
Leider nein, da es mir, wie eingangs erwähnt, mit allen Anleitungen der Welt nicht gelungen ist.
Welche?
Und auf welchem Stand hockst du da auf dem Raspberry?iob stop iob fix iob diagUnd dann die Ausgabe von
iob diagin der Langfassung posten. Dann schauen wir mal, was da überhaupt Phase ist. -
@thomas-braun sagte in Uralt System updaten oder Umzug:
Und dann die Ausgabe von
iob diagin der Langfassung posten. Dann schauen wir mal, was da überhaupt Phase ist.Bin grad dabei,
passt das alles in den Post hier? oder anderweitig verlinken?
Die Antwort ist ja Ellenlang.... -
Sollte eigentlich alles hier rein passen.
-
@thomas-braun
Ich versuche es. Schon mal an ALLE BESTEN DANK.
Kann sein, dass ich erst morgen reagieren kann.
nodejs und npm scheinen OK zu sein. aber ich konnte nie den js.controller updaten.
Kann es daran liegen, dass ich die Adapter etc. nicht mehr updaten kann?Script v.2025-02-23 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.10.103-v7l+ Architecture: arm OS is similar to: debian Model : Raspberry Pi 4 Model B Rev 1.1 Docker : false Virtualization : none Kernel : armv7l Userland : 32 bit Systemuptime and Load: 21:50:51 up 11:31, 1 user, load average: 1.07, 1.47, 0.86 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'buster' is the current oldstable version. Please upgrade to the latest stable release '' in due time! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Thu 2025-05-08 21:50:51 CEST Universal time: Thu 2025-05-08 19:50:51 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker User that is running 'js-controller': js-controller is not running *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: tty *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 180M 2.9G 16M 793M 3.5G Swap: 99M 0B 99M Total: 3.9G 180M 3.0G Active iob-Instances: 1 3837 M total memory 180 M used memory 469 M active memory 333 M inactive memory 2862 M free memory 211 M buffer memory 582 M swap cache 99 M total swap 0 M used swap 99 M free swap *** top - Table Of Processes *** top - 21:50:51 up 11:31, 1 user, load average: 1.07, 1.47, 0.86 Tasks: 153 total, 1 running, 152 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.9 sy, 0.0 ni, 97.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3837.7 total, 2862.4 free, 181.0 used, 794.4 buff/cache MiB Swap: 100.0 total, 100.0 free, 0.0 used. 3483.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * iobroker.service loaded failed failed ioBroker Server LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 28G 6.2G 21G 23% / devtmpfs devtmpfs 1.8G 0 1.8G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 1.9G 17M 1.9G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/sda1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 384M 0 384M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu May 8 10:19:10 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:22:A7:57 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=e52a9d10-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [Thu May 8 10:19:12 2025] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [Thu May 8 10:19:12 2025] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Thu May 8 10:19:14 2025] EXT4-fs (sda2): re-mounted. Opts: (null) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 `-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.3G /var/ 625M /var/lib 536M /var/cache 531M /var/cache/apt 517M /var/lib/piVCCU3 Archived and active journals take up 16.0M in the file system. /opt/iobroker/backups: 156M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 302M /opt/iobroker/iobroker-data/ 141M /opt/iobroker/iobroker-data/files 120M /opt/iobroker/iobroker-data/backup-objects 41M /opt/iobroker/iobroker-data/files/javascript.admin 31M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 14M /opt/iobroker/iobroker-data/objects.jsonl 11M /opt/iobroker/iobroker-data/objects.json.migrated 11M /opt/iobroker/iobroker-data/objects.json.bak.migrated 8.0M /opt/iobroker/iobroker-data/files/jarvis/static/js/11.443f46f8.chunk.js.map 7.0M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/2.8fd7d552.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00 *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyACM0 HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyACM0 Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v16.18.1 /usr/bin/node v16.18.1 /usr/bin/npm 8.19.2 /usr/bin/npx 8.19.2 /usr/bin/corepack 0.14.1 nodejs: Installed: 16.18.1-deb-1nodesource1 Candidate: 16.20.2-deb-1nodesource1 Version table: 16.20.2-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages *** 16.18.1-deb-1nodesource1 100 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is not running on this host. Objects type: jsonl States type: jsonl Hosts: broker-slave broker-slave (version: 3.1.6, hostname: broker-slave , dead, uptime: 24) raspberrypi raspberrypi (version: 4.0.23, hostname: raspberrypi , dead, uptime: 39247) Core adapters versions js-controller: 4.0.23 admin: 4.2.2 javascript: 4.11.0 nodejs modules from github: 4 +-- iobroker.blockly-plus@0.0.1 invalid: "https://github.com/excal-foley/ioBroker.blockly-plus/tarball/8487239d69fc53c13853013110da15b42bc487e9" from the root project | `-- xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc +-- iobroker.jarvis@3.1.2 invalid: "https://github.com/Zefau/ioBroker.jarvis/tarball/master" from the root project | `-- socksv5@0.0.6 invalid: "https://github.com/christophgysin/socksv5/tarball/7b4eba5b30ecdb6d9e656dcfede1e6884dc7c6d9" from node_modules/iobroker.telegram Adapter State system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.blockly-plus.0 : blockly-plus : raspberrypi - enabled system.adapter.cloud.0 : cloud : raspberrypi - enabled system.adapter.devices.0 : devices : raspberrypi - enabled system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.flot.0 : flot : raspberrypi - disabled system.adapter.history.0 : history : raspberrypi - enabled system.adapter.hm-rega.0 : hm-rega : raspberrypi - enabled system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - enabled, port: 2010 system.adapter.iot.0 : iot : raspberrypi - enabled system.adapter.jarvis.0 : jarvis : raspberrypi - enabled system.adapter.javascript.0 : javascript : raspberrypi - enabled system.adapter.mqtt.0 : mqtt : raspberrypi - disabled, port: 1883, bind: 0.0.0.0 system.adapter.netatmo-crawler.0 : netatmo-crawler : raspberrypi - enabled system.adapter.nuki-extended.0 : nuki-extended : raspberrypi - disabled system.adapter.openweathermap.0 : openweathermap : raspberrypi - enabled system.adapter.scenes.0 : scenes : raspberrypi - enabled system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.socketio.0 : socketio : raspberrypi - enabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.statistics.0 : statistics : raspberrypi - enabled system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 system.adapter.tr-064.0 : tr-064 : raspberrypi - disabled system.adapter.tuya.0 : tuya : raspberrypi - disabled system.adapter.vis.0 : vis : raspberrypi - disabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - enabled system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0 system.adapter.zigbee.1 : zigbee : broker-slave - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - enabled, port: 2010 system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.socketio.0 : socketio : raspberrypi - enabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0 system.adapter.zigbee.1 : zigbee : broker-slave - enabled, port: /dev/ttyACM0 ioBroker-Repositories Stable (default): http://download.iobroker.net/sources-dist.json Beta (latest) : http://download.iobroker.net/sources-dist-latest.json Active repo(s): Stable (default) Installed ioBroker-Adapters Used repository: Stable (default) Adapter "admin" : 7.6.3 , installed 4.2.2 [Updatable] Adapter "alexa2" : 3.26.5 , installed 3.23.2 [Updatable] Adapter "amazon-dash" : 1.2.0 , installed 1.1.0 [Updatable] Adapter "backitup" : 3.0.31 , installed 2.5.9 [Updatable] Adapter "broadlink2" : 2.3.0 , installed 2.1.5 [Updatable] Adapter "cloud" : 5.0.1 , installed 4.3.0 [Updatable] Adapter "devices" : 1.1.5 , installed 0.3.16 [Updatable] Adapter "discovery" : 5.0.0 , installed 2.8.0 [Updatable] Adapter "flot" : 1.12.0 , installed 1.11.0 [Updatable] Adapter "habpanel" : 0.5.0 , installed 0.4.3 [Updatable] Adapter "ham" : 5.3.1 , installed 5.3.0 [Updatable] Adapter "history" : 3.0.1 , installed 1.11.1 [Updatable] Adapter "hm-rega" : 5.1.0 , installed 2.6.25 [Updatable] Adapter "hm-rpc" : 2.0.2 , installed 1.15.15 [Updatable] Adapter "iot" : 3.3.0 , installed 1.12.5 [Updatable] Adapter "jarvis" : 3.1.8 , installed 3.1.2 [Updatable] Adapter "javascript" : 8.8.3 , installed 4.11.0 [Updatable] Controller "js-controller": 7.0.6 , installed 4.0.23 [Updatable] Adapter "lovelace" : 4.1.15 , installed 1.5.0 [Updatable] Adapter "milight" : 0.4.0 , installed 0.3.6 [Updatable] Adapter "mqtt" : 6.1.2 , installed 2.7.4 [Updatable] Adapter "netatmo-crawler": 0.8.1 , installed 0.3.13 [Updatable] Adapter "nuki-extended": 2.7.0 , installed 2.6.5 [Updatable] Adapter "openweathermap": 1.1.2 , installed 0.1.0 [Updatable] Adapter "rpi2" : 2.4.0 , installed 1.3.2 [Updatable] Adapter "scenes" : 3.2.3 , installed 2.3.9 [Updatable] Adapter "shelly" : 9.2.0 , installed 4.1.2 [Updatable] Adapter "simple-api" : 2.8.0 , installed 2.7.2 [Updatable] Adapter "socketio" : 6.7.1 , installed 3.1.5 [Updatable] Adapter "sonoff" : 3.1.2 , installed 2.5.1 [Updatable] Adapter "statistics" : 2.4.0 , installed 1.1.1 [Updatable] Adapter "tankerkoenig" : 3.4.0 , installed 2.1.1 [Updatable] Adapter "telegram" : 4.1.0 , installed 1.15.2 [Updatable] Adapter "tr-064" : 4.3.0 , installed 4.2.17 [Updatable] Adapter "tuya" : 3.16.0 , installed 3.10.2 [Updatable] Adapter "vis" : 1.5.6 , installed 1.4.15 [Updatable] Adapter "weatherunderground": 3.7.0, installed 3.4.2 [Updatable] Adapter "web" : 7.0.8 , installed 3.4.16 [Updatable] Adapter "zigbee" : 2.0.5 , installed 1.8.7 [Updatable] Objects and States Please stand by - This may take a while Objects: 9414 States: 8048 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 https://deb.nodesource.com/node_16.x buster InRelease Hit:4 https://www.pivccu.de/piVCCU stable InRelease Reading package lists... Pending Updates: 174 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 16283 593/sshd tcp6 0 0 :::22 :::* LISTEN 0 16285 593/sshd udp 0 0 0.0.0.0:38918 0.0.0.0:* 108 16743 398/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 13992 447/dhclient udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 16741 398/avahi-daemon: r udp6 0 0 :::41490 :::* 108 16744 398/avahi-daemon: r udp6 0 0 :::5353 :::* 108 16742 398/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-05-08 21:45:44.450 - info: host.raspberrypi instance system.adapter.backit up.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2025-05-08 21:45:44.522 - info: host.raspberrypi instance system.adapter.statis tics.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2025-05-08 21:45:44.523 - info: host.raspberrypi instance system.adapter.alexa2 .0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2025-05-08 21:45:44.590 - info: host.raspberrypi instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2025-05-08 21:45:44.590 - info: host.raspberrypi All instances are stopped. 2025-05-08 21:45:44.822 - warn: host.raspberrypi Cannot get view: Connection is closed. 2025-05-08 21:45:44.822 - warn: host.raspberrypi Cannot get view: Connection is closed. 2025-05-08 21:45:44.823 - warn: host.raspberrypi Cannot get view: Connection is closed. 2025-05-08 21:45:44.823 - warn: host.raspberrypi Cannot get view: Connection is closed. 2025-05-08 21:45:44.823 - error: host.raspberrypi Cannot find view "system" for search "instance" : Connection is closed. 2025-05-08 21:45:44.826 - warn: host.raspberrypi instance system.adapter.javasc ript.0 terminated due to SIGTERM 2025-05-08 21:45:44.827 - info: host.raspberrypi instance system.adapter.javasc ript.0 terminated with code null () 2025-05-08 21:45:44.827 - info: host.raspberrypi All instances are stopped. 2025-05-08 21:45:44.827 - warn: host.raspberrypi instance system.adapter.tanker koenig.0 terminated due to SIGTERM 2025-05-08 21:45:44.828 - info: host.raspberrypi instance system.adapter.tanker koenig.0 terminated with code null () 2025-05-08 21:45:44.828 - info: host.raspberrypi All instances are stopped. 2025-05-08 21:45:44.828 - warn: host.raspberrypi instance system.adapter.telegr am.0 terminated due to SIGTERM 2025-05-08 21:45:44.829 - info: host.raspberrypi instance system.adapter.telegr am.0 terminated with code null () 2025-05-08 21:45:44.829 - info: host.raspberrypi All instances are stopped. 2025-05-08 21:45:44.829 - warn: host.raspberrypi instance system.adapter.zigbee .0 terminated due to SIGTERM 2025-05-08 21:45:44.829 - info: host.raspberrypi instance system.adapter.zigbee .0 terminated with code null () 2025-05-08 21:45:44.830 - info: host.raspberrypi All instances are stopped. 2025-05-08 21:45:44.830 - info: host.raspberrypi instance system.adapter.histor y.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2025-05-08 21:45:44.830 - info: host.raspberrypi All instances are stopped. 2025-05-08 21:45:44.902 - info: host.raspberrypi terminated -
@mr-x sagte in Uralt System updaten oder Umzug:
Kann es daran liegen, dass ich die Adapter etc. nicht mehr updaten kann?
Das ist alles total veraltet. Natürlich kann man irgendwann nicht mehr updaten, wenn die Versionen im Upstream dir weglaufen.
-
Nicht schimpfen.
ich gelobe zukünftig mehrmals im Jahr alles upzugraden.......
Falls hier noch was zu retten ist. -
iob stop sudo apt update sudo apt full-upgrade sudo reboot iob nodejs-update 18 iob update iob upgrade all -y iob upgrade self cd /opt/iobroker npm install iobroker.js-controller@5.0.0 iob start iob stop iob update iob upgrade all -y iob upgrade self cd /opt/iobroker npm install iobroker.js-controller@6.0.0 iob start iob stop iob update iob upgrade all -y iob upgrade self cd /opt/iobroker npm install iobroker.js-controller@latest iob start iob update iob upgrade all -yUnd dann noch mal die Ausgabe von
iob diag, damit man den Stand sieht.
Das ganze kann geraume Zeit dauern. -
Besten Dank, ihr seid die Besten.
Ich melde mich morgen mit dem Resultat. -
@mr-x sagte in Uralt System updaten oder Umzug:
ich gelobe zukünftig mehrmals im Jahr alles upzugraden.......
Nimm dir mehrmals im Monat vor. Und auch das Betriebssystem nicht vergessen. Das muss auch aktuell gehalten werden.
-
Guten morgen, bin wieder da und würde gerne einen kleinen zwischenstand liefern, da ich errors bekommen haben beim upgrade vom
js.controller.pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ npm install iobroker.js-crontroller@5.0.0 npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/iobroker.js-crontroller - Not found npm error 404 npm error 404 'iobroker.js-crontroller@5.0.0' is not in this registry. npm error 404 npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-05-09T07_08_45_905Z-debug-0.log -
@mr-x
Das Ding heißt "js-controller" und nicht "js-crontroller" !!! -
Peinlich.
Leider kriege ich es trotzdem nicht hin. Offenbar gibts die 5.0.0 nicht???pi@raspberrypi:/opt/iobroker $ npm install iobroker.js-controller@5.0.0 npm error code ETARGET npm error notarget No matching version found for iobroker.js-controller@5.0.0. npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-05-09T07_24_45_164Z-debug-0.log -
@mr-x sagte in Uralt System updaten oder Umzug:
Offenbar gibts die 5.0.0 nicht???
durchaus möglich.
du solltest die letzte 5.x nehmenEDIT nach Suche
@mcm1957 sagte in Problem beim Aktualisieren des Admin Adapters:
5.0.19 ist der letzte aktuelle 5er.
Ob 5.0.0 jemals online ging kann ich mich nicht erinnern -
pi@raspberrypi:/opt/iobroker $ npm install iobroker.js-controller@5.0.19 npm error code EBADENGINE npm error engine Unsupported engine npm error engine Not compatible with your version of node/npm: iobroker.jarvis@3.2.0-rc.17 npm error notsup Not compatible with your version of node/npm: iobroker.jarvis@3.2.0-rc.17 npm error notsup Required: {"node":">= 20","npm":">= 9.3.1","yarn":">= 1.21.1"} npm error notsup Actual: {"npm":"10.8.2","node":"v18.20.8"} npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-05-09T07_39_00_228Z-debug-0.log -
@mr-x noch kein node v20 drauf?
-
thomas-braun sagte in Uralt System updaten oder Umzug:
iob stop sudo apt update sudo apt full-upgrade sudo reboot iob nodejs-update 18 iob update iob upgrade all -y iob upgrade self cd /opt/iobroker npm install iobroker.js-controller@5.0.0 iob start iob stop iob update iob upgrade all -y iob upgrade self cd /opt/iobroker npm install iobroker.js-controller@6.0.0 iob start iob stop iob update iob upgrade all -y iob upgrade self cd /opt/iobroker npm install iobroker.js-controller@latest iob start iob update iob upgrade all -yUnd dann noch mal die Ausgabe von
iob diag, damit man den Stand sieht.
Das ganze kann geraume Zeit dauern.Ich habe mich jetzt an diese Anleitung gehalten und bin mit Node auf
pi@raspberrypi:/opt/iobroker $ node -v v18.20.8
