js-controller Lucy (Version 7.0) jetzt im Stable Repository
-
Habe den aktuellen und offiziellen ioBroker Docker und mir wird ein js Update gemeldet. Rödelt kurz und bricht dann mit folgender Meldung ab:
CPU: 15.13 % RAM: 9 % Betriebszeit: 0h Verfügbar: 7.0.6 Installiert: 7.0.3 Ereignisse: ⇥38 / ↦13 Plattform: docker (official image - v10.0.0) Betriebssystem: linux Architektur: x64 CPUs: 4 Geschwindigkeit: 4099 MHz Modell: Intel(R) Core(TM) i3-9100 CPU @ 3.60GHz RAM: 62.5 GB System-Betriebszeit: 119 T. 22:14:59 Node.js: v20.18.1 time: 1735467614948 timeOffset: -60 NPM: 10.8.2 Adapter-Anzahl: 550 Datenträgergröße: 20.0 GB Freier Festplattenspeicher: 13.7 GB Aktive Instanzen: 32 Pfad: /opt/iobroker/ Betriebszeit: 00:34:43 -
Bekannter Phänomen. Gab gerade gestern noch einen Thread dazu.
-
@warp735
Bekannter Phänomen.Um etwas genauer zu sein: die js-controller Versionen ca. 7.0.2 bis 7.0.5 haben bei Systemen, die nicht auf systemd basieren (also auch Docker) ein Problem beim Upgrade über die UI.
Heißt für dich: jetzt einmalig über die Konsole aktualisieren, danach gehts wieder über die ioBroker Web-Oberfläche.
-
@marc-berg said in js-controller Lucy (Version 7.0) jetzt im Stable Repository:
Heißt für dich: jetzt einmalig über die Konsole aktualisieren, danach gehts wieder über die ioBroker Web-Oberfläche.
Heißt das jetzt auch für mich , aktuell mit js-controller 6.0.11 und aktuellem buanet Image 10.0.0 das ich dann auf der Console folgendes machen muß?
pkill -u iobroker
iobroker update
iobroker upgrade selfoder geht das anders?
-
-
Danke , muß ich den Container vorher stoppen?
-
-
Oki, Danke ich probiere, aber vorher erst nochmal sicherheitshalber backup machen.
-
@warp735 sagte in js-controller Lucy (Version 7.0) jetzt im Stable Repository:
su iobroker
maintenance on
maintenance upgradeund dann Docker wieder starten
Es gibt übrigens auch die Kurzform, die alles in einem Rutsch macht
iob m upgrade -y- User iobroker verwenden
- ioBroker stoppen (Maintenance Mode on)
- js-controller updaten
- neu starten (Maintenance Mode off)
-
js-controller update kommt mit syntax Error
SyntaxError: Unexpected token '<', "<!doctype "... is not valid JSON
Wollte gerade das update machen, kommt aber mit syntax Error.
iob diag.Script v.2024-10-19 [34;107m*** BASE SYSTEM ***[0m Hardware Vendor : Synology Kernel : x86_64 Userland : 64 bit Docker : v10.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 00:10:43 up 31 days, 2:03, 0 user, load average: 2.09, 2.27, 2.31 CPU threads: 4 [34;107m*** LIFE CYCLE STATUS ***[0m Unknown release codenamed ''. Please check yourself if the Operating System is actively maintained. [34;107m*** TIME AND TIMEZONES ***[0m Sun Dec 29 23:10:43 UTC 2024 Mon Dec 30 00:10:43 CET 2024 CET +0100 Etc/UTC [34;107m*** Users and Groups ***[0m User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker sudo: unable to resolve host iobroker: Name or service not known HOME=/opt/iobroker sudo: unable to resolve host iobroker: Name or service not known GROUPS=iobroker tty dialout audio video plugdev [34;107m*** DISPLAY-SERVER SETUP ***[0m Display-Server: false Desktop: Terminal: [34;107m*** MEMORY ***[0m total used free shared buff/cache available Mem: 8.2G 2.2G 227M 41M 6.1G 5.9G Swap: 7.1G 963M 6.1G Total: 15G 3.2G 6.3G Active iob-Instances: 15 7792 M total memory 2138 M used memory 2125 M active memory 4401 M inactive memory 216 M free memory 115 M buffer memory 5657 M swap cache 6723 M total swap 918 M used swap 5805 M free swap [34;107m*** top - Table Of Processes ***[0m top - 00:10:43 up 31 days, 2:03, 0 user, load average: 2.09, 2.27, 2.31 Tasks: 22 total, 1 running, 21 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 50.0 sy, 0.0 ni, 50.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7792.1 total, 215.6 free, 2139.9 used, 5772.7 buff/cache MiB Swap: 6723.9 total, 5805.5 free, 918.4 used. 5652.2 avail Mem [34;107m*** DMESG CRITICAL ERRORS ***[0m sudo: unable to resolve host iobroker: Name or service not known 1 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for details [34;107m*** FILESYSTEM ***[0m Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/cachedev_0 btrfs 7.0T 4.0T 3.0T 58% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 btrfs 7.0T 4.0T 3.0T 58% /opt/iobroker /dev/mapper/cachedev_0 btrfs 7.0T 4.0T 3.0T 58% /etc/hosts tmpfs tmpfs 3.9G 0 3.9G 0% /proc/acpi tmpfs tmpfs 3.9G 0 3.9G 0% /proc/scsi tmpfs tmpfs 3.9G 0 3.9G 0% /sys/firmware [32mMessages concerning ext4 filesystem in dmesg:[0m sudo: unable to resolve host iobroker: Name or service not known [Thu Nov 28 22:07:53 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Thu Nov 28 22:07:53 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Thu Nov 28 22:07:53 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Thu Nov 28 22:07:53 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Thu Nov 28 22:07:58 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Thu Nov 28 22:07:58 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Thu Nov 28 22:07:58 2024] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Thu Nov 28 22:07:58 2024] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Thu Nov 28 22:08:11 2024] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [Thu Nov 28 22:08:20 2024] EXT4-fs (usb1p1): mounted filesystem with ordered data mode. Opts: nodelalloc,synoacl [32mShow mounted filesystems:[0m TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/cachedev_0[/@syno/@docker/btrfs/subvolumes/486fac7a383dfe7324577f90ec5aef2606493c34a5045a32af59be68df69a930] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=1665,subvol=/@syno/@docker/btrfs/subvolumes/486fac7a383dfe7324577f90ec5aef2606493c34a5045a32af59be68df69a930 |-/opt/iobroker /dev/mapper/cachedev_0[/@syno/docker/iobroker] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=693,subvol=/@syno/docker |-/etc/resolv.conf /dev/mapper/cachedev_0[/@syno/@docker/containers/cd536b38584fca2d7de1f9a5f72068a8b68896b4222931cdcc1d7211e77f66e0/resolv.conf] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno |-/etc/hostname /dev/mapper/cachedev_0[/@syno/@docker/containers/cd536b38584fca2d7de1f9a5f72068a8b68896b4222931cdcc1d7211e77f66e0/hostname] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno `-/etc/hosts /dev/mapper/cachedev_0[/@syno/@docker/containers/cd536b38584fca2d7de1f9a5f72068a8b68896b4222931cdcc1d7211e77f66e0/hosts] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno [32mFiles in neuralgic directories:[0m [32m/var:[0m sudo: unable to resolve host iobroker: Name or service not known 16M /var/ 14M /var/lib 13M /var/lib/dpkg/info 13M /var/lib/dpkg 1.9M /var/cache [32m/opt/iobroker/backups:[0m 520M /opt/iobroker/backups/ [32m/opt/iobroker/iobroker-data:[0m 1.8G /opt/iobroker/iobroker-data/ 1.7G /opt/iobroker/iobroker-data/files 891M /opt/iobroker/iobroker-data/files/0_userdata.0 886M /opt/iobroker/iobroker-data/files/0_userdata.0/history 616M /opt/iobroker/iobroker-data/files/javascript.admin [32mThe five largest files in iobroker-data are:[0m 27M /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 12M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.bd24114f.js 11M /opt/iobroker/iobroker-data/objects.jsonl [32mUSB-Devices by-id:[0m USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' [34;107m*** NodeJS-Installation ***[0m /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 20.18.1-1nodesource1 Candidate: 20.18.1-1nodesource1 Version table: *** 20.18.1-1nodesource1 100 100 /var/lib/dpkg/status [32mTemp directories causing deletion problem:[0m 0 No problems detected [32mErrors in npm tree:[0m 0 No problems detected [34;107m*** ioBroker-Installation ***[0m [32mioBroker Status[0m iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 7.0.3, hostname: iobroker , alive, uptime: 376) [32mCore adapters versions[0m js-controller: 7.0.3 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 0 [32mAdapter State[0m + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 10.88.0.5, run as: admin + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.broadlink2.0 : broadlink2 : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled system.adapter.flot.0 : flot : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled + system.adapter.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 0 system.adapter.icons-material-svg.0 : icons-material-svg : iobroker - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.modbus.0 : modbus : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.tankerkoenig.0 : tankerkoenig : iobroker - enabled system.adapter.vis-history.0 : vis-history : iobroker - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : iobroker - enabled system.adapter.vis-material-advanced.0 : vis-material-advanced : iobroker - enabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: ubecker + instance is alive [32mEnabled adapters with bindings[0m + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 10.88.0.5, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: ubecker [32mioBroker-Repositories[0m ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none [32mInstalled ioBroker-Instances[0m Used repository: stable Adapter "admin" : 7.1.5 , installed 7.1.5 Adapter "backitup" : 3.0.25 , installed 3.0.25 Adapter "broadlink2" : 2.3.0 , installed 2.3.0 Adapter "email" : 1.3.1 , installed 1.3.1 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "icons-material-svg": 0.1.0, installed 0.1.0 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.3 [Updatable] Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "tankerkoenig" : 3.4.0 , installed 3.4.0 Adapter "vis" : 1.5.6 , installed 1.4.16 [Updatable] Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.0.12 [Updatable] Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.6.2 [32mObjects and States[0m Please stand by - This may take a while Objects: 4842 States: 3702 [34;107m*** OS-Repositories and Updates ***[0m sudo: unable to resolve host iobroker: Name or service not known sudo: unable to resolve host iobroker: Name or service not known Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 0 [34;107m*** Listening Ports ***[0m sudo: unable to resolve host iobroker: Name or service not known Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 10.88.0.5:2001 0.0.0.0:* LISTEN 1000 103282343 - tcp 0 0 10.88.0.5:8081 0.0.0.0:* LISTEN 1000 103281142 - tcp 0 0 127.0.0.1:915 0.0.0.0:* LISTEN 0 94907 - tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 0 40344 - tcp 0 0 0.0.0.0:662 0.0.0.0:* LISTEN 0 35057 - tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 27264 - tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 55 68009 - tcp 0 0 127.0.0.1:33304 0.0.0.0:* LISTEN 0 32148 - tcp 0 0 10.88.0.5:2010 0.0.0.0:* LISTEN 1000 103284990 - tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1000 103284062 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 40797 - tcp 0 0 0.0.0.0:892 0.0.0.0:* LISTEN 0 34679 - tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 44201 - tcp 0 0 127.0.0.1:512 0.0.0.0:* LISTEN 0 102355 - tcp 0 0 127.0.0.1:161 0.0.0.0:* LISTEN 0 41281 - tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 0 40549 - tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN 0 1315912 - tcp 0 0 0.0.0.0:6690 0.0.0.0:* LISTEN 0 112391 - tcp 0 0 0.0.0.0:5510 0.0.0.0:* LISTEN 192868 91994 - tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1000 103280162 - tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 0 40791 - tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1000 103278525 - tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN 0 40793 - tcp 0 0 0.0.0.0:873 0.0.0.0:* LISTEN 0 37813 - tcp 0 0 0.0.0.0:42 0.0.0.0:* LISTEN 0 27268 - tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 44202 - tcp 0 0 10.88.0.5:9292 0.0.0.0:* LISTEN 1000 103284249 - tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN 0 45096 - tcp 0 0 0.0.0.0:4045 0.0.0.0:* LISTEN 0 40570 - tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 23434 - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 40795 - tcp6 0 0 :::8082 :::* LISTEN 1000 103286086 - tcp6 0 0 :::21 :::* LISTEN 0 40345 - tcp6 0 0 :::662 :::* LISTEN 0 35061 - tcp6 0 0 :::22 :::* LISTEN 0 27266 - tcp6 0 0 :::443 :::* LISTEN 0 40798 - tcp6 0 0 :::892 :::* LISTEN 0 34685 - tcp6 0 0 :::3261 :::* LISTEN 0 45980 - tcp6 0 0 :::445 :::* LISTEN 0 44199 - tcp6 0 0 :::5566 :::* LISTEN 0 72181 - tcp6 0 0 :::3263 :::* LISTEN 0 45979 - tcp6 0 0 :::3264 :::* LISTEN 0 45981 - tcp6 0 0 :::3265 :::* LISTEN 0 51239 - tcp6 0 0 :::2049 :::* LISTEN 0 40560 - tcp6 0 0 :::6690 :::* LISTEN 0 112392 - tcp6 0 0 :::5510 :::* LISTEN 192868 91995 - tcp6 0 0 :::5000 :::* LISTEN 0 40792 - tcp6 0 0 :::5001 :::* LISTEN 0 40794 - tcp6 0 0 :::873 :::* LISTEN 0 37814 - tcp6 0 0 :::42 :::* LISTEN 0 27270 - tcp6 0 0 :::139 :::* LISTEN 0 44200 - tcp6 0 0 :::5357 :::* LISTEN 0 45097 - tcp6 0 0 :::4045 :::* LISTEN 0 40572 - tcp6 0 0 :::111 :::* LISTEN 0 23437 - tcp6 0 0 :::80 :::* LISTEN 0 40796 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 99 41429 - udp 0 0 0.0.0.0:4045 0.0.0.0:* 0 40569 - udp 0 0 10.88.0.5:69 0.0.0.0:* 0 41118 - udp 0 0 127.0.0.1:69 0.0.0.0:* 0 41117 - udp 0 0 0.0.0.0:111 0.0.0.0:* 0 23425 - udp 0 0 0.0.0.0:123 0.0.0.0:* 0 34806 - udp 0 0 10.88.0.255:137 0.0.0.0:* 0 2899749 - udp 0 0 10.88.0.5:137 0.0.0.0:* 0 2899748 - udp 0 0 0.0.0.0:137 0.0.0.0:* 0 2899717 - udp 0 0 10.88.0.255:138 0.0.0.0:* 0 2899751 - udp 0 0 10.88.0.5:138 0.0.0.0:* 0 2899750 - udp 0 0 0.0.0.0:138 0.0.0.0:* 0 2899718 - udp 0 0 127.0.0.1:161 0.0.0.0:* 0 41280 - udp 0 0 127.0.0.1:323 0.0.0.0:* 0 34804 - udp 0 0 0.0.0.0:514 0.0.0.0:* 0 1315911 - udp 0 0 0.0.0.0:662 0.0.0.0:* 0 35055 - udp 0 0 0.0.0.0:892 0.0.0.0:* 0 34676 - udp 0 0 127.0.0.1:908 0.0.0.0:* 0 33535 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 0 108446 - udp 0 0 0.0.0.0:38201 0.0.0.0:* 1000 103282519 - udp 0 0 0.0.0.0:9997 0.0.0.0:* 0 27215 - udp 0 0 0.0.0.0:9998 0.0.0.0:* 0 27214 - udp 0 0 0.0.0.0:9999 0.0.0.0:* 0 27213 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 44231 - udp 0 0 0.0.0.0:2049 0.0.0.0:* 0 40559 - udp 0 0 0.0.0.0:51368 0.0.0.0:* 0 23433 - udp 0 0 0.0.0.0:15001 0.0.0.0:* 1000 103284790 - udp 0 0 0.0.0.0:44057 0.0.0.0:* 0 108448 - udp 0 0 0.0.0.0:40217 0.0.0.0:* 1000 103284074 - udp6 0 0 :::3702 :::* 99 41431 - udp6 0 0 :::4045 :::* 0 40571 - udp6 0 0 :::111 :::* 0 23435 - udp6 0 0 :::123 :::* 0 34807 - udp6 0 0 ::1:323 :::* 0 34805 - udp6 0 0 fe80::211:32ff:fee9:546 :::* 0 226637 - udp6 0 0 :::662 :::* 0 35059 - udp6 0 0 :::892 :::* 0 34682 - udp6 0 0 :::62494 :::* 0 23436 - udp6 0 0 :::5353 :::* 0 108447 - udp6 0 0 :::2049 :::* 0 40561 - udp6 0 0 :::40356 :::* 0 108449 - [34;107m*** Log File - Last 25 Lines ***[0m 2024-12-30 00:05:08.727 - [32minfo[39m: hm-rpc.1 (356) xmlrpc client is trying to connect to 10.88.0.6:2010/ with ["http://10.88.0.5:2010","iobroker:hm-rpc.1:d1d61b99541491796936c2d69a20dcf4"] 2024-12-30 00:05:08.806 - [32minfo[39m: hm-rpc.1 (356) Connected 2024-12-30 00:05:09.297 - [32minfo[39m: hm-rpc.1 (356) xmlrpc <- listDevices ["iobroker:hm-rpc.1:d1d61b99541491796936c2d69a20dcf4"] 2024-12-30 00:05:09.320 - [32minfo[39m: hm-rpc.1 (356) xmlrpc -> 0 devices 2024-12-30 00:05:10.268 - [32minfo[39m: hm-rpc.1 (356) xmlrpc <- newDevices 79 2024-12-30 00:05:10.287 - [32minfo[39m: hm-rpc.1 (356) new HMIP devices/channels after filter: 0 2024-12-30 00:05:11.598 - [32minfo[39m: host.iobroker instance system.adapter.hm-rpc.2 in version "2.0.2" started with pid 371 2024-12-30 00:05:12.580 - [32minfo[39m: hm-rpc.2 (371) starting. Version 2.0.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v20.18.1, js-controller: 7.0.3 2024-12-30 00:05:12.688 - [32minfo[39m: hm-rpc.2 (371) xmlrpc server is trying to listen on 10.88.0.5:9292 2024-12-30 00:05:12.689 - [32minfo[39m: hm-rpc.2 (371) xmlrpc client is trying to connect to 10.88.0.6:9292/groups/ with ["http://10.88.0.5:9292","iobroker:hm-rpc.2:6355fcda139f55df0f77add91cd3a08f"] 2024-12-30 00:05:13.048 - [32minfo[39m: hm-rpc.2 (371) xmlrpc <- listDevices ["iobroker:hm-rpc.2:6355fcda139f55df0f77add91cd3a08f"] 2024-12-30 00:05:13.063 - [32minfo[39m: hm-rpc.2 (371) xmlrpc -> 12 devices 2024-12-30 00:05:13.469 - [32minfo[39m: hm-rpc.2 (371) xmlrpc <- newDevices 12 2024-12-30 00:05:13.481 - [32minfo[39m: hm-rpc.2 (371) new virtual-devices devices/channels after filter: 0 2024-12-30 00:05:13.521 - [32minfo[39m: hm-rpc.2 (371) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:6355fcda139f55df0f77add91cd3a08f","INT0000004"] 2024-12-30 00:05:13.563 - [32minfo[39m: hm-rpc.2 (371) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:6355fcda139f55df0f77add91cd3a08f","INT0000005"] 2024-12-30 00:05:13.588 - [32minfo[39m: hm-rpc.2 (371) xmlrpc <- setReadyConfig ["iobroker:hm-rpc.2:6355fcda139f55df0f77add91cd3a08f","INT0000006"] 2024-12-30 00:05:15.592 - [32minfo[39m: host.iobroker instance system.adapter.web.0 in version "6.2.5" started with pid 398 2024-12-30 00:05:22.015 - [32minfo[39m: host.iobroker instance system.adapter.vis.0 terminated while should be started once 2024-12-30 00:05:22.796 - [32minfo[39m: hm-rpc.2 (371) Connected 2024-12-30 00:05:24.050 - [32minfo[39m: host.iobroker instance system.adapter.tankerkoenig.0 in version "3.4.0" started with pid 428 2024-12-30 00:05:25.044 - [32minfo[39m: tankerkoenig.0 (428) starting. Version 3.4.0 in /opt/iobroker/node_modules/iobroker.tankerkoenig, node: v20.18.1, js-controller: 7.0.3 2024-12-30 00:05:25.063 - [32minfo[39m: tankerkoenig.0 (428) Adapter is already in daemon mode 2024-12-30 00:05:25.064 - [32minfo[39m: tankerkoenig.0 (428) Sync time set to 15 minutes or 900000 ms 2024-12-30 00:05:27.462 - [32minfo[39m: tankerkoenig.0 (428) Start first requestwas kann ich machen? System funktioniert einwandfrei mit 7.03
im log steht nichts ausserhost.iobroker
2024-12-30 00:28:07.469 info Controller will upgrade itself to version 7.0.6
noch mal edit:
root@iobroker:/opt/iobroker# cat /opt/.docker_config/.build
20241226.234319 Docker Version -
@ubecker sagte in js-controller update 7.03 auf 7.06 Fehler:
was kann ich machen?
Suchfunktion...
Du bist nicht der erste und einzige mit dem Ding. -
@thomas-braun said in js-controller update 7.03 auf 7.06 Fehler:
@ubecker sagte in js-controller update 7.03 auf 7.06 Fehler:
was kann ich machen?
Suchfunktion...
Du bist nicht der erste und einzige mit dem Ding.oh hab ich was übersehen? dann suche ich mal
-
@thomas-braun hab was gefunden https://forum.iobroker.net/post/1219662
aber ohne Lösung. Da ja alles funktioniert lasse ich es erst mal bei 7.03 -
Aus dem Admin über die GUI gibt es aktuell noch eine Fehlermeldung .
Mach es über die Konsole .pkill -u iobroker
iobroker upgrade selfDann Iobroker wieder starten.
Das ist momentan der Weg für die Container/Dockerfreunde.
-
@ubecker sagte in js-controller Lucy (Version 7.0) jetzt im Stable Repository:
@thomas-braun said in js-controller update 7.03 auf 7.06 Fehler:
oh hab ich was übersehen? dann suche ich malich hab das mal zusammengeführt
-
Hallo, ich wollte gerade den Host updaten.
Es klappt aber leider nicht mit folgender Fehlermeldung
-
@haselchen said in js-controller Lucy (Version 7.0) jetzt im Stable Repository:
Aus dem Admin über die GUI gibt es aktuell noch eine Fehlermeldung .
Mach es über die Konsole .pkill -u iobroker
iobroker upgrade selfDann Iobroker wieder starten.
Das ist momentan der Weg für die Container/Dockerfreunde.
ok, danke.
Ist das sinnvoll oder besser auf 7.03 lassen bis zum nächsten Docker update? -
Sinnvoll als „normaler“ User ist stable Versionen zu benutzen.
Beta Versionen sind eher für die erfahrenen User zum Testen gedacht.
-
@haselchen habe jetzt das update über die console gemacht. Soweit ok.
Jetzt meldet diag1 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for details Unknown release codenamed ''. Please check yourself if the Operating System is actively maintained. # dmesg --level=emerg,alert,crit -T [32m[Mo Dez 30 00:18:31 2024] [0m[7m[31mBoth CLEAN and DIRTY blocks exist in cache[0m # exitVerwaltet nicht mein NAS den Speicher? Dort wird kein Fehler gemeldet.
-
Hallo,
das Update des js Controllers von 7.0.3 auf 7.0.6 funktioniert nicht über die Oberfläche.
Es kommt folgende Fehlermeldung:
SyntaxError: Unexpected token '<', "<!doctype "... is not valid JSONFolgendes steht im log:
host.IOBroker-Holger
2025-01-10 17:24:08.633 info Controller will upgrade itself to version 7.0.6
Wann würde er gerne selbst updaten?
