Keinerlei Adaperupdates seit Monaten
-
@alexzi sagte in Keinerlei Adaperupdates seit Monaten:
ioBroker-Repositories
List is emptyInstalled ioBroker-Instances
Error: Object "system.repositories" not foundDazu
iob stop iob setup firstder Rest zum ( alten ) System von dir , wurde schon oben genannt .
-
nach apt full upgrade und reboot sehen die uptime infos zumindest besser aus, ob das gut genug ist kann ich nicht beurteilen. Hatte auch noch den SD-Kopierer laufen, evtl. hat der die hohen Werte mit beeinflusst.
hier nochmal der Output von iob diag
wenn das OS viel zu alt ist, Empfehlung? Upgrade von Buster auf 'Name habe ich vergessen' ist ja nicht empfohlen, werde wohl um Neuanfang mit neuem OS nicht rum kommen
ja, X11 mag unnötig sein, aber ein paar Kleinigkeiten mache ich lieber über die GUI, bin nicht der CLI-Profi, wobei ohne ja eh nichts geht
Wie kann ich das umstellen, dass er Boot Target CLI hat?wenn ich nodejs mit iob nodejs-update aktualisieren will, zeigt er nichts neueres an.
ufffff, ich bin echt für jede Hilfe dankbar, egal was ich versuche, nur Probleme, Layer 8.
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: SYS-Server-Raspi4 Icon name: computer Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 5.10.103-v8+ Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : armhf Systemuptime and Load: 16:36:31 up 16 min, 3 users, load average: 0.33, 0.46, 0.63 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Wed 2023-12-27 16:36:31 CET Universal time: Wed 2023-12-27 15:36:31 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev lpadmin docker gpio i2c spi iobroker *** X-Server-Setup *** X-Server: true Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 1.4G 5.0G 59M 1.5G 6.3G Swap: 99M 0B 99M Total: 7.9G 1.4G 5.1G 7813 M total memory 1355 M used memory 467 M active memory 1851 M inactive memory 4972 M free memory 176 M buffer memory 1307 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 117G 70G 42G 63% / devtmpfs devtmpfs 3.7G 0 3.7G 0% /dev tmpfs tmpfs 3.9G 4.5M 3.9G 1% /dev/shm tmpfs tmpfs 3.9G 9.6M 3.9G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/mmcblk0p1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 782M 4.0K 782M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Dec 27 16:19:54 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60D smsc95xx.macaddr=DC:A6:32:FA:33:E0 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=64538962-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Wed Dec 27 16:19:55 2023] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Wed Dec 27 16:19:55 2023] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Wed Dec 27 16:19:56 2023] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Wed Dec 27 16:19:56 2023] EXT4-fs (mmcblk0p2): 4 orphan inodes deleted [Wed Dec 27 16:19:56 2023] EXT4-fs (mmcblk0p2): recovery complete [Wed Dec 27 16:19:56 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Wed Dec 27 16:19:56 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed Dec 27 16:19:58 2023] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 |-/run/user/1000/gvfs gvfsd-fuse fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.2G /var/ 717M /var/lib 417M /var/lib/docker 415M /var/lib/docker/overlay2 310M /var/lib/docker/overlay2/9a19718ad57ef0af959ba0272376648d9dab28c6da97bab8013bb20f26fad944/diff Archived and active journals take up 8.0M in the file system. /opt/iobroker/backups: 41G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 2.2G /opt/iobroker/iobroker-data/ 1.9G /opt/iobroker/iobroker-data/history 233M /opt/iobroker/iobroker-data/files 72M /opt/iobroker/iobroker-data/files/telegram.admin 52M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 8.9M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/2.7de3299d.chunk.js.map 7.5M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/2.2afdfa2c.chunk.js.map 7.4M /opt/iobroker/iobroker-data/states.jsonl 7.2M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x buster/main armhf Packages 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 npm8 problem: 0 No problems detected Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! invalid: @types/node@14.18.33 /opt/iobroker/node_modules/iobroker.javascript/node_modules/@types/node npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2023-12-27T15_36_45_002Z-debug-0.log *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: 6.1.4 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : SYS-Server-Raspi4 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : SYS-Server-Raspi4 - enabled + system.adapter.backitup.0 : backitup : SYS-Server-Raspi4 - enabled + system.adapter.bring.0 : bring : SYS-Server-Raspi4 - enabled system.adapter.daswetter.0 : daswetter : SYS-Server-Raspi4 - disabled + system.adapter.discovery.0 : discovery : SYS-Server-Raspi4 - enabled + system.adapter.harmony.0 : harmony : SYS-Server-Raspi4 - enabled + system.adapter.history.0 : history : SYS-Server-Raspi4 - enabled system.adapter.homeconnect.0 : homeconnect : SYS-Server-Raspi4 - disabled + system.adapter.info.0 : info : SYS-Server-Raspi4 - enabled + system.adapter.jarvis.0 : jarvis : SYS-Server-Raspi4 - enabled + system.adapter.javascript.0 : javascript : SYS-Server-Raspi4 - enabled system.adapter.meross.0 : meross : SYS-Server-Raspi4 - disabled + system.adapter.pi-hole.0 : pi-hole : SYS-Server-Raspi4 - enabled + system.adapter.scenes.0 : scenes : SYS-Server-Raspi4 - enabled + system.adapter.shelly.0 : shelly : SYS-Server-Raspi4 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.smartcontrol.0 : smartcontrol : SYS-Server-Raspi4 - enabled system.adapter.telegram.0 : telegram : SYS-Server-Raspi4 - disabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : SYS-Server-Raspi4 - enabled system.adapter.vis.0 : vis : SYS-Server-Raspi4 - enabled + system.adapter.web.0 : web : SYS-Server-Raspi4 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : SYS-Server-Raspi4 - enabled + system.adapter.yahka.0 : yahka : SYS-Server-Raspi4 - enabled + system.adapter.zigbee.0 : zigbee : SYS-Server-Raspi4 - enabled, port: /dev/ttyUSB0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : SYS-Server-Raspi4 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.shelly.0 : shelly : SYS-Server-Raspi4 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.web.0 : web : SYS-Server-Raspi4 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : SYS-Server-Raspi4 - enabled, port: /dev/ttyUSB0 ioBroker-Repositories List is empty Installed ioBroker-Instances Error: Object "system.repositories" not found Objects and States Please stand by - This may take a while Objects: 10043 States: 9057 *** 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://download.docker.com/linux/raspbian buster InRelease Hit:4 https://download.mono-project.com/repo/debian stable-raspbianbuster InRelease Hit:5 https://deb.nodesource.com/node_18.x buster InRelease Reading package lists... Pending Updates: 0 *** 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 127.0.0.1:3306 0.0.0.0:* LISTEN 116 21257 664/mysqld tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 26864 1260/smbd tcp 0 0 0.0.0.0:40395 0.0.0.0:* LISTEN 0 20705 599/rpc.mountd tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 0 20288 542/vncserver-x11-c tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 11699 1/init tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 33071 2219/io.jarvis.0 tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 20875 669/lighttpd tcp 0 0 127.0.0.1:35025 0.0.0.0:* LISTEN 1001 33416 2593/io.yahka.0 tcp 0 0 0.0.0.0:39441 0.0.0.0:* LISTEN 0 18404 599/rpc.mountd tcp 0 0 0.0.0.0:45491 0.0.0.0:* LISTEN 1001 31731 2593/io.yahka.0 tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 999 26817 582/pihole-FTL tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 21594 600/sshd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17014 423/cupsd tcp 0 0 0.0.0.0:43961 0.0.0.0:* LISTEN 1001 31729 2593/io.yahka.0 tcp 0 0 127.0.0.1:39035 0.0.0.0:* LISTEN 1001 33411 2593/io.yahka.0 tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 26863 1260/smbd tcp 0 0 0.0.0.0:52031 0.0.0.0:* LISTEN 0 17164 599/rpc.mountd tcp 0 0 0.0.0.0:44673 0.0.0.0:* LISTEN 0 17404 - tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 0 17397 - tcp 0 0 127.0.0.1:41605 0.0.0.0:* LISTEN 1001 34164 2593/io.yahka.0 tcp 0 0 0.0.0.0:39109 0.0.0.0:* LISTEN 1001 31727 2593/io.yahka.0 tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 999 26823 582/pihole-FTL tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 29006 541/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 28232 541/iobroker.js-con tcp6 0 0 :::37035 :::* LISTEN 0 17406 - tcp6 0 0 :::35819 :::* LISTEN 0 20695 599/rpc.mountd tcp6 0 0 :::139 :::* LISTEN 0 26862 1260/smbd tcp6 0 0 :::5900 :::* LISTEN 0 20287 542/vncserver-x11-c tcp6 0 0 :::111 :::* LISTEN 0 8983 1/init tcp6 0 0 :::51376 :::* LISTEN 998 27232 1650/homebridge tcp6 0 0 :::8080 :::* LISTEN 0 27008 1266/node /home/Shi tcp6 0 0 :::80 :::* LISTEN 0 20876 669/lighttpd tcp6 0 0 :::8081 :::* LISTEN 1001 26583 1557/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 30154 2204/io.web.0 tcp6 0 0 :::53 :::* LISTEN 999 26819 582/pihole-FTL tcp6 0 0 :::22 :::* LISTEN 0 21596 600/sshd tcp6 0 0 ::1:3350 :::* LISTEN 0 20685 581/xrdp-sesman tcp6 0 0 ::1:631 :::* LISTEN 0 17013 423/cupsd tcp6 0 0 :::57272 :::* LISTEN 998 30952 1650/homebridge tcp6 0 0 :::35613 :::* LISTEN 998 27237 1650/homebridge tcp6 0 0 :::3389 :::* LISTEN 115 23747 602/xrdp tcp6 0 0 :::445 :::* LISTEN 0 26054 1260/smbd tcp6 0 0 :::2049 :::* LISTEN 0 17401 - tcp6 0 0 :::58181 :::* LISTEN 998 31200 1650/homebridge tcp6 0 0 :::8581 :::* LISTEN 998 29229 1009/hb-service tcp6 0 0 :::61991 :::* LISTEN 1001 32370 2441/io.harmony.0 tcp6 0 0 ::1:4711 :::* LISTEN 999 26824 582/pihole-FTL tcp6 0 0 :::38759 :::* LISTEN 0 20711 599/rpc.mountd tcp6 0 0 :::54697 :::* LISTEN 0 17168 599/rpc.mountd udp 0 0 0.0.0.0:2049 0.0.0.0:* 0 17400 - udp 0 0 0.0.0.0:38990 0.0.0.0:* 0 17403 - udp 0 0 0.0.0.0:56151 0.0.0.0:* 108 18833 426/avahi-daemon: r udp 0 0 0.0.0.0:48823 0.0.0.0:* 0 20698 599/rpc.mountd udp 0 0 0.0.0.0:40652 0.0.0.0:* 0 18402 599/rpc.mountd udp 0 0 0.0.0.0:53 0.0.0.0:* 999 26816 582/pihole-FTL udp 0 0 0.0.0.0:68 0.0.0.0:* 0 23758 485/dhcpcd udp 0 0 0.0.0.0:111 0.0.0.0:* 0 11700 1/init udp 0 0 172.17.255.255:137 0.0.0.0:* 0 26763 543/nmbd udp 0 0 172.17.0.1:137 0.0.0.0:* 0 26762 543/nmbd udp 0 0 10.100.200.255:137 0.0.0.0:* 0 26759 543/nmbd udp 0 0 10.100.200.1:137 0.0.0.0:* 0 26758 543/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 0 22884 543/nmbd udp 0 0 172.17.255.255:138 0.0.0.0:* 0 26765 543/nmbd udp 0 0 172.17.0.1:138 0.0.0.0:* 0 26764 543/nmbd udp 0 0 10.100.200.255:138 0.0.0.0:* 0 26761 543/nmbd udp 0 0 10.100.200.1:138 0.0.0.0:* 0 26760 543/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 0 22885 543/nmbd udp 0 0 0.0.0.0:61991 0.0.0.0:* 1001 32371 2441/io.harmony.0 udp 0 0 0.0.0.0:631 0.0.0.0:* 0 20186 546/cups-browsed udp 0 0 0.0.0.0:42050 0.0.0.0:* 0 17170 599/rpc.mountd udp 0 0 10.100.200.1:5353 0.0.0.0:* 1001 34145 1877/io.tr-064.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 998 27238 1650/homebridge udp 0 0 0.0.0.0:5353 0.0.0.0:* 998 27233 1650/homebridge udp 0 0 0.0.0.0:5353 0.0.0.0:* 998 28407 1009/hb-service udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 18831 426/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 31317 2122/io.shelly.0 udp6 0 0 :::2049 :::* 0 17402 - udp6 0 0 :::60723 :::* 0 20708 599/rpc.mountd udp6 0 0 :::53 :::* 999 26818 582/pihole-FTL udp6 0 0 :::111 :::* 0 8986 1/init udp6 0 0 :::33280 :::* 0 17166 599/rpc.mountd udp6 0 0 :::546 :::* 0 21416 485/dhcpcd udp6 0 0 :::41984 :::* 0 20693 599/rpc.mountd udp6 0 0 :::33820 :::* 108 18834 426/avahi-daemon: r udp6 0 0 :::5353 :::* 108 18832 426/avahi-daemon: r udp6 0 0 :::58941 :::* 0 17405 - *** Log File - Last 25 Lines *** 2023-12-27 16:21:32.991 - info: yahka.0 (2593) publishing bridge ioBrokerPi4 on 10.100.200.1 using avahi 2023-12-27 16:21:33.081 - info: yahka.0 (2593) publishing camera Terrasse-Lounge-Kamera on 10.100.200.1 using avahi 2023-12-27 16:21:33.103 - info: yahka.0 (2593) publishing camera Hof-Haustuer-Kamera on 10.100.200.1 using avahi 2023-12-27 16:21:33.275 - warn: zigbee.0 (1866) DeviceAvailability:Failed to ping 0x60a423fffead7944 TS0121 2023-12-27 16:21:34.890 - warn: zigbee.0 (1866) DeviceAvailability:Failed to ping 0x60a423fffef8e119 TS0121 2023-12-27 16:21:35.974 - info: smartcontrol.0 (2739) starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.smartcontrol, node: v18.17.1, js-controller: 4.0.24 2023-12-27 16:21:36.888 - info: host.SYS-Server-Raspi4 instance system.adapter.bring.0 started with pid 3105 2023-12-27 16:21:37.212 - info: pi-hole.0 (3006) starting. Version 1.3.4 in /opt/iobroker/node_modules/iobroker.pi-hole, node: v18.17.1, js-controller: 4.0.24 2023-12-27 16:21:37.955 - info: smartcontrol.0 (2739) Adapter admin configuration successfully validated... 2023-12-27 16:21:38.943 - info: harmony.0 (2441) [DISCOVER] Discovered Wohnzimmer (10.100.200.74) and will try to connect 2023-12-27 16:21:39.455 - info: harmony.0 (2441) [CONNECT] Connecting to Wohnzimmer (10.100.200.74) 2023-12-27 16:21:40.783 - info: harmony.0 (2441) [CONNECT] Connected to Wohnzimmer (10.100.200.74) 2023-12-27 16:21:41.632 - info: harmony.0 (2441) [PROCESS] Synced hub config for Wohnzimmer (10.100.200.74) 2023-12-27 16:21:41.890 - info: bring.0 (3105) starting. Version 1.8.1 in /opt/iobroker/node_modules/iobroker.bring, node: v18.17.1, js-controller: 4.0.24 2023-12-27 16:21:42.067 - info: smartcontrol.0 (2739) Subscribing to all target devices and trigger states. 4 trigger schedules activated... 2023-12-27 16:21:43.034 - info: bring.0 (3105) [LOGIN] Successfully logged in as Ali 2023-12-27 16:21:44.064 - info: vis.0 (3152) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v18.17.1, js-controller: 4.0.24 2023-12-27 16:21:44.462 - info: vis.0 (3152) vis license is OK. 2023-12-27 16:21:44.625 - info: alexa2.0 (1817) Subscribing to states... 2023-12-27 16:21:44.635 - info: alexa2.0 (1817) Deleting the following states: ["Smart-Home-Devices.9f4e9ab6-8817-4fc0-837c-080303c57239","Smart-Home-Devices.3b42e75f-f188-487d-978b-4b716e9f3647","Smart-Home-Devices.deleteAll","Smart-Home-Devices.discoverDevices","Smart-Home-Devices.9f4e9ab6-8817-4fc0-837c-080303c57239.#enabled","Smart-Home-Devices.9f4e9ab6-8817-4fc0-837c-080303c57239.#delete","Smart-Home-Devices.3b42e75f-f188-487d-978b-4b716e9f3647.#enabled","Smart-Home-Devices.3b42e75f-f188-487d-978b-4b716e9f3647.#delete"] 2023-12-27 16:21:45.291 - info: vis.0 (3152) Terminated (NO_ERROR): Without reason 2023-12-27 16:21:45.621 - warn: zigbee.0 (1866) DeviceAvailability:Failed to ping 0x540f57fffe896f3f TS011F 2023-12-27 16:21:46.009 - info: host.SYS-Server-Raspi4 instance system.adapter.vis.0 terminated while should be started once 2023-12-27 16:21:46.394 - info: alexa2.0 (1817) Alexa-Push-Connection (macDms = true) established. Disable Polling 2023-12-27 16:21:52.495 - info: alexa2.0 (1817) Initialization Done ... -
$ iob setup first Successfully migrated 10930 objects to Redis Sets Existing earlier generated certificate is invalid (too old, validity longer then 345 days or keylength too short). Generating new Certificate! object system.certificates updated object system.repositories created object _design/system updated { "defaultPrivate": "-----BEGIN RSA PRIVATE KEY-----........-----END CERTIFICATE-----\r\n" } Update certificate defaultPrivate The object "system.certificates" was updated successfully. Update certificate defaultPublic The object "system.certificates" was updated successfully. pi@SYS-Server-Raspi4:~ $ iob update Used repository: Stable (default) Error: unknown repository is active - "Stable (default)". Known: stable, beta -
iob repo del beta iob repo del stable iob repo add stable http://download.iobroker.net/sources-dist.json iob repo add beta http://download.iobroker.net/sources-dist-latest.json iob repo list -
Danke, ich krieg nen Vogel...
pi@SYS-Server-Raspi4:~ $ iob repo del beta Repository "beta" deleted. stable : http://download.iobroker.net/sources-dist.json Active repo(s): Stable (default) pi@SYS-Server-Raspi4:~ $ iob repo del stable Repository "stable" deleted. Active repo(s): Stable (default) pi@SYS-Server-Raspi4:~ $ iob repo add stable http://download.iobroker.net/sources-dist.json Repository "stable" added as "http://download.iobroker.net/sources-dist.json" stable : http://download.iobroker.net/sources-dist.json Active repo(s): Stable (default) pi@SYS-Server-Raspi4:~ $ iob repo add beta http://download.iobroker.net/sources-dist-latest.json Repository "beta" added as "http://download.iobroker.net/sources-dist-latest.json" stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): Stable (default) pi@SYS-Server-Raspi4:~ $ iob repo list stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): Stable (default) pi@SYS-Server-Raspi4:~ $ iob stop pi@SYS-Server-Raspi4:~ $ iob update Used repository: Stable (default) Error: unknown repository is active - "Stable (default)". Known: stable, beta -
-
@alexzi iob repo unset "Stable (default)"
iob repo set stable -
@alexzi sagte in Keinerlei Adaperupdates seit Monaten:
Neuanfang mit neuem OS nicht rum kommen
Richtig, installier da Raspberry OS 12 'Bookworm' komplett neu in der 64Bit Lite Version.
-
@homoran
Halleluja, das wars, zumindest geht das Update wieder. DANKEBeim Rest muss ich mich reinbeißen.
Noch eine generelle Frage: ist es ratsam/empfehlenswert IOB in Docker laufen zu lassen? Wenn ich schon neu anfange, dann hoffentlich richtig (zumindest deutlich besser).
-
@alexzi
Für den "Otto-Normalanwender", der auf seinem PI ausschließlich ioBroker betreibt, bzw. betreiben will, ist (in meinen Augen) weder Docker noch eine Proxmox Umgebung sinnvoll. Du schaffst Dir höchstens mehr Probleme als Dir lieb ist.
