Passwort Iobroker über Mac-Terminal anders?
-
@thomas-braun said in Passwort Iobroker über Mac-Terminal anders?:
iob diag
Here it comes....
========== Start marking the full check here =========== ```bash Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.61-v8+ Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 14:55:01 up 1 day, 22:27, 3 users, load average: 0.58, 0.62, 0.34 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian Release codenamed 'bullseye' reached its END OF LIFE and needs to be updated to the latest stable release '' NOW! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Fri 2024-10-25 14:55:01 CEST Universal time: Fri 2024-10-25 12:55:01 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': iobroker HOME=/home/iobroker GROUPS=iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth lpadmin gpio i2c spi User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth lpadmin gpio i2c spi A default user should be created! This user will be enabled to temporarily switch to root via 'sudo'! A root login is not required in most Linux Distributions. Run 'iobroker fix' or use the system tools to create a user. *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: tty System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix' *** MEMORY *** total used free shared buff/cache available Mem: 1.8G 1.4G 236M 34M 216M 349M Swap: 99M 99M 0.0K Total: 1.9G 1.5G 236M Active iob-Instances: 20 1849 M total memory 1396 M used memory 168 M active memory 1283 M inactive memory 236 M free memory 27 M buffer memory 189 M swap cache 99 M total swap 99 M used swap 0 M free swap *** top - Table Of Processes *** top - 14:55:02 up 1 day, 22:27, 3 users, load average: 0.58, 0.62, 0.34 Tasks: 209 total, 1 running, 208 sleeping, 0 stopped, 0 zombie %Cpu(s): 13.9 us, 6.9 sy, 0.0 ni, 79.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 1849.2 total, 235.6 free, 1395.8 used, 217.8 buff/cache MiB Swap: 100.0 total, 0.0 free, 100.0 used. 348.6 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** [sudo] password for iobroker: No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 15G 7.1G 6.5G 53% / devtmpfs devtmpfs 763M 0 763M 0% /dev tmpfs tmpfs 925M 0 925M 0% /dev/shm tmpfs tmpfs 370M 1.2M 369M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 34M 222M 13% /boot tmpfs tmpfs 185M 20K 185M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Oct 23 16:27:32 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:26:FE:1A vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=bbc14122-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Wed Oct 23 16:27:33 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Wed Oct 23 16:27:33 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Wed Oct 23 16:27:33 2024] EXT4-fs (mmcblk0p2): recovery complete [Wed Oct 23 16:27:33 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [Wed Oct 23 16:27:33 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed Oct 23 16:27:35 2024] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null). Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/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.9G /var/ 1.5G /var/log/journal/60dd197ce1dd470bacf92c92630f1c5a 1.5G /var/log/journal 1.5G /var/log 184M /var/lib Archived and active journals take up 1.4G in the file system. /opt/iobroker/backups: 279M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 378M /opt/iobroker/iobroker-data/ 298M /opt/iobroker/iobroker-data/files 99M /opt/iobroker/iobroker-data/files/vis-2-beta 52M /opt/iobroker/iobroker-data/files/javascript.admin 47M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 27M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 9.7M /opt/iobroker/iobroker-data/files/vis-2-beta/material-icons/knx-uf.json 8.5M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js 8.0M /opt/iobroker/iobroker-data/states.jsonl USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** NodeJS-Installation *** nodejs: N/A /usr/bin/node v16.17.0 /usr/bin/npm 8.15.0 /usr/bin/npx 8.15.0 /usr/bin/corepack 0.12.1 *** nodejs is NOT correctly installed *** nodejs: Installed: 16.17.0-deb-1nodesource1 Candidate: 16.20.2-deb-1nodesource1 Version table: 16.20.2-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main arm64 Packages *** 16.17.0-deb-1nodesource1 100 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u5 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 4.0.23, hostname: iobroker , alive, uptime: 165159) Core adapters versions js-controller: 4.0.23 admin: 6.13.16 javascript: 7.1.4 nodejs modules from github: 2 | +-- samsungtv@0.0.0 (git+https://git@github.com/luca-saggese/samsungtv.git#7fc20107455414e2afb94022682e0787e8635550) +-- iobroker.vis-materialdesign@0.5.94 (git+ssh://git@github.com/Scrounger/ioBroker.vis-materialdesign.git#8b7529d493f223dfc4f1d1f632553fcb35bbcc92) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.denon.0 : denon : iobroker - enabled + system.adapter.discovery.0 : discovery : iobroker - enabled + system.adapter.fritzdect.0 : fritzdect : iobroker - enabled system.adapter.habpanel.0 : habpanel : 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.hm-rpc.3 : hm-rpc : iobroker - disabled, port: 0 system.adapter.hue-extended.0 : hue-extended : iobroker - disabled + system.adapter.hue.0 : hue : iobroker - enabled, port: 443 system.adapter.ical.0 : ical : iobroker - disabled + system.adapter.jarvis.0 : jarvis : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.openweathermap.0 : openweathermap : iobroker - enabled + system.adapter.ping.0 : ping : iobroker - enabled + system.adapter.pushover.0 : pushover : iobroker - enabled + system.adapter.samsung.0 : samsung : iobroker - enabled + system.adapter.terminal.0 : terminal : iobroker - enabled, port: 8088, bind: 0.0.0.0, run as: admin system.adapter.vis-2-beta.0 : vis-2-beta : iobroker - disabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : iobroker - enabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : iobroker - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: iobroker - enabled system.adapter.vis-inventwo.0 : vis-inventwo : iobroker - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : iobroker - enabled system.adapter.vis.0 : vis : iobroker - disabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.yahka.0 : yahka : iobroker - enabled + system.adapter.zigbee.0 : zigbee : iobroker - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, 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.hue.0 : hue : iobroker - enabled, port: 443 + system.adapter.terminal.0 : terminal : iobroker - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 7.1.5 , installed 6.13.16 [Updatable] Adapter "backitup" : 3.0.25 , installed 2.11.0 [Updatable] Adapter "denon" : 1.15.12 , installed 1.15.5 [Updatable] Adapter "discovery" : 5.0.0 , installed 4.4.0 [Updatable] Adapter "fritzdect" : 2.5.11 , installed 2.5.9 [Updatable] Adapter "habpanel" : 0.5.0 , installed 0.5.0 Adapter "hm-rega" : 5.1.0 , installed 4.0.0 [Updatable] Adapter "hm-rpc" : 2.0.2 , installed 1.17.0 [Updatable] Adapter "hue" : 3.12.0 , installed 3.10.1 [Updatable] Adapter "ical" : 1.15.0 , installed 1.13.3 [Updatable] Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 8.8.3 , installed 7.1.4 [Updatable] Controller "js-controller": 6.0.11 , installed 4.0.23 [Updatable] Adapter "openweathermap": 1.1.2 , installed 1.0.4 [Updatable] Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "pushover" : 4.1.0 , installed 3.0.6 [Updatable] Adapter "samsung" : 0.6.1 , installed 0.5.11 [Updatable] Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.5.5 [Updatable] Adapter "terminal" : 1.0.0 , installed 1.0.0 Adapter "vis" : 1.5.6 , installed 1.5.4 [Updatable] Adapter "vis-2-widgets-energy": 1.0.2, installed 0.3.11 [Updatable] Adapter "vis-2-widgets-gauges": 1.1.0, installed 1.0.3 [Updatable] Adapter "vis-2-widgets-material": 1.4.10, installed 1.3.25 [Updatable] Adapter "vis-inventwo" : 3.3.4 , installed 3.3.3 [Updatable] Adapter "vis-materialdesign": 0.5.9, installed 0.5.94 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.6.1 [Updatable] Adapter "yahka" : 1.0.3 , installed 1.0.3 Adapter "zigbee" : 1.10.3 , installed 1.8.24 [Updatable] Objects and States Please stand by - This may take a while Objects: 6827 States: 5615 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 http://security.debian.org/debian-security bullseye-security InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease Reading package lists... Pending Updates: 325 *** 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 192.168.178.22:9292 0.0.0.0:* LISTEN 1000 45177 6369/io.hm-rpc.1 tcp 0 0 192.168.178.22:2010 0.0.0.0:* LISTEN 1000 45202 6386/io.hm-rpc.2 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 43296 6175/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 42823 6175/iobroker.js-co tcp 0 0 192.168.178.22:2001 0.0.0.0:* LISTEN 1000 41943 6322/io.hm-rpc.0 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 866244 82966/cupsd tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1000 46259 6524/io.jarvis.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 11603 571/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1000 40887 6193/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1000 46229 6479/io.web.0 tcp6 0 0 :::8088 :::* LISTEN 1000 45400 6535/io.terminal.0 tcp6 0 0 ::1:631 :::* LISTEN 0 866243 82966/cupsd tcp6 0 0 :::34957 :::* LISTEN 1000 43687 6494/io.yahka.0 tcp6 0 0 :::22 :::* LISTEN 0 11605 571/sshd: /usr/sbin udp 0 0 0.0.0.0:631 0.0.0.0:* 0 868513 82968/cups-browsed udp 0 0 0.0.0.0:52180 0.0.0.0:* 108 14204 340/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 13063 468/dhcpcd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14202 340/avahi-daemon: r udp6 0 0 :::44790 :::* 108 14205 340/avahi-daemon: r udp6 0 0 :::5353 :::* 108 14203 340/avahi-daemon: r udp6 0 0 :::546 :::* 0 13290 468/dhcpcd *** Log File - Last 25 Lines *** 2024-10-25 14:55:48.028 - error: hue.0 (6272) Could not poll all: unauthorized user 2024-10-25 14:55:48.559 - info: hue.0 (6272) Push connection error: Forbidden 2024-10-25 14:55:48.710 - error: hue.0 (6272) unauthorized user 2024-10-25 14:55:48.711 - warn: hue.0 (6272) Could not get configuration from HUE bridge (192.168.178.111:443) 2024-10-25 14:55:53.984 - info: hue.0 (6272) Push connection error: Forbidden 2024-10-25 14:55:54.197 - error: hue.0 (6272) unauthorized user 2024-10-25 14:55:54.198 - warn: hue.0 (6272) Could not get configuration from HUE bridge (192.168.178.111:443) 2024-10-25 14:55:58.048 - error: hue.0 (6272) Could not poll all: unauthorized user 2024-10-25 14:55:59.487 - info: hue.0 (6272) Push connection error: Forbidden 2024-10-25 14:55:59.647 - error: hue.0 (6272) unauthorized user 2024-10-25 14:55:59.647 - warn: hue.0 (6272) Could not get configuration from HUE bridge (192.168.178.111:443) 2024-10-25 14:56:04.949 - info: hue.0 (6272) Push connection error: Forbidden 2024-10-25 14:56:05.098 - error: hue.0 (6272) unauthorized user 2024-10-25 14:56:05.098 - warn: hue.0 (6272) Could not get configuration from HUE bridge (192.168.178.111:443) 2024-10-25 14:56:08.066 - error: hue.0 (6272) Could not poll all: unauthorized user 2024-10-25 14:56:10.395 - info: hue.0 (6272) Push connection error: Forbidden 2024-10-25 14:56:10.552 - error: hue.0 (6272) unauthorized user 2024-10-25 14:56:10.553 - warn: hue.0 (6272) Could not get configuration from HUE bridge (192.168.178.111:443) 2024-10-25 14:56:15.848 - info: hue.0 (6272) Push connection error: Forbidden 2024-10-25 14:56:15.996 - error: hue.0 (6272) unauthorized user 2024-10-25 14:56:15.996 - warn: hue.0 (6272) Could not get configuration from HUE bridge (192.168.178.111:443) 2024-10-25 14:56:18.081 - error: hue.0 (6272) Could not poll all: unauthorized user 2024-10-25 14:56:21.282 - info: hue.0 (6272) Push connection error: Forbidden 2024-10-25 14:56:21.441 - error: hue.0 (6272) unauthorized user 2024-10-25 14:56:21.448 - warn: hue.0 (6272) Could not get configuration from HUE bridge (192.168.178.111:443)============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
Hier noch die anschließende Summary:Copy text starting here:
======================= SUMMARY ======================= v.2024-10-19 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.15.61-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 325 Pending iob updates: 22 Nodejs-Installation: nodejs: N/A /usr/bin/node v16.17.0 /usr/bin/npm 8.15.0 /usr/bin/npx 8.15.0 /usr/bin/corepack 0.12.1 Recommended versions are nodejs 18.20.4 and npm 10.7.0 *** nodejs is NOT correctly installed *** Wrong installation path detected. This needs to be fixed. Please execute iob nodejs-update to fix these errors. MEMORY: total used free shared buff/cache available Mem: 1.8G 1.4G 135M 35M 300M 332M Swap: 99M 99M 0B Total: 1.9G 1.5G 135M Active iob-Instances: 20 Active repo(s): stable ioBroker Core: js-controller 4.0.23 admin 6.13.16 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 6827 States: 5615 Size of iob-Database: 27M /opt/iobroker/iobroker-data/objects.jsonl 8.1M /opt/iobroker/iobroker-data/states.jsonl Debian Release codenamed 'bullseye' reached its END OF LIFE and needs to be updated to the latest stable release '' NOW! =================== END OF SUMMARY ======================= Mark text until here for copying ===
iobroker@iobroker:~ $@Meister-Mopper : Sehr hilfreicher Kommentar....weil ich auch andere Dinge im Leben zu tun habe.... -
Bring das Ding auf Stand...
iob nodejs-update iob stop sudo apt update sudo apt full-upgrade sudo rebootUnd leg dir einen User an.
-
@thomas-braun
Ja, den Hinweis mit dem NodeJS habe ich auch gesehen - Update läuft gerade... -
So. NodeJS Update hat geklappt - auch die anderen Update/Upgrade Befehle habe ich ausgeführt.
Danke schonmal, Thomas, für Deine Hilfe!
Leider immer noch kein aktualisierter JS-Controller im Host sichtbar.Wie meinst Du das genau mit dem neuen User? Und zum Verständnis: Was ist das Problem mit dem bisherigen?
(Und ja, ich sollte ja nach Anleitung damals einen neuen User anlegen, der "pi" offensichtlich ersetzt hat...)Soll ich das mit dem gefixten NodeJS einfach nochmal probieren mit der JS-Controller Update-Routine?
Oder ist die eh identisch mit den Upgrade-Zeilen, die Du mir geschrieben hast? -
-
@thomas-braun ```
Copy text starting here:======================= SUMMARY ======================= v.2024-10-19 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 22 Nodejs-Installation: /usr/bin/nodejs v20.18.0 /usr/bin/node v20.18.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs 18.20.4 and npm 10.7.0 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 1.8G 1.1G 127M 37M 577M 600M Swap: 99M 5.0M 94M Total: 1.9G 1.1G 222M Active iob-Instances: 20 Active repo(s): stable ioBroker Core: js-controller 4.0.23 admin 6.13.16 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 6827 States: 5617 Size of iob-Database: 27M /opt/iobroker/iobroker-data/objects.jsonl 1.9M /opt/iobroker/iobroker-data/states.jsonl Debian 'bullseye' is the current oldstable version. Please upgrade to the latest stable release 'bookworm' in due time! =================== END OF SUMMARY ==================== -
iob update iob upgrade all -y iob stop iob upgrade self iob start -
SUPER. Herzlichen Dank, Thomas - scheint soweit nun alles geklappt zu haben.
Bei der ersten Runde von "iob upgrade all -y" hatte er noch einige Fehlermeldungen bezüglich der zu alten Version von JS-controller,
nach "upgrade self" hat er diesen aber nun auch brav auf 6.0.11 aktualisiert....!Sollte ich nun trotzdem noch eine neuen User anlegen? Oder ist das jetzt obsolet?
Hier nochmal die aktuellste Summary von "iob diag":
======================= SUMMARY ======================= v.2024-10-19 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.18.0 /usr/bin/node v20.18.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs 20.18.0 and npm 10.8.2 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 1.8G 1.2G 97M 38M 507M 498M Swap: 99M 99M 0.0K Total: 1.9G 1.3G 97M Active iob-Instances: 20 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.1.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 : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 6881 States: 5625 Size of iob-Database: 29M /opt/iobroker/iobroker-data/objects.jsonl 4.5M /opt/iobroker/iobroker-data/states.jsonl Debian 'bullseye' is the current oldstable version. Please upgrade to the latest stable release 'bookworm' in due time! =================== END OF SUMMARY ====================Was ja immer noch geblieben ist, ist die bullseye/bookworm Meldung.....Was mach ich damit?
-
@uliauer44 sagte in Passwort Iobroker über Mac-Terminal anders?:
Was mach ich damit?
@meister-mopper sagte in Passwort Iobroker über Mac-Terminal anders?:
Mach den ganzen Bums neu
Das kann man nicht updaten.
Bookworm ist intern deutlich verändert worden
Da geht nur eine Neuinstallation mit anschließendem Einspielen des Backups -
@uliauer44 sagte in Passwort Iobroker über Mac-Terminal anders?:
Sollte ich nun trotzdem noch eine neuen User anlegen? Oder ist das jetzt obsolet?
Nein, das ist nicht obsolet.
Denn im Zuge vonWas ja immer noch geblieben ist, ist die bullseye/bookworm Meldung.....Was mach ich damit?
wirst du von dem jetzigen Stand ein Backup anlegen und dann damit in ein frisch, von Grund auf neuinstalliertes 'Bookworm' umziehen. Dann auch gleich mit individuellem username.
https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht
-
Okay.
Hab jetzt beim Backup machen ein paar kleine Fehler bekommen...
16:13:10.980 WARN jarvis settings "theme" not found 16:13:13.822 WARN nodered no node-red database found!!Ist da was Wichtiges dabei, das ich vor dem Wechsel auf bookworm noch fixen sollte?
-
@uliauer44 sagte in Passwort Iobroker über Mac-Terminal anders?:
Ist da was Wichtiges dabei, das ich vor dem Wechsel auf bookworm noch fixen sollte?
Kann ich dir nicht sagen, verwende weder node-red noch jarvis.
-
@thomas-braun
Okay, dann ist es ja jedenfalls nix existenziell erforderliches
Sorry für die Noob-Frage: Wie lege ich jetzt den neuen User an?
Den Pi-Imager habe ich schon auf dem Mac am Start...Ah....sehe jetzt gerade erst in Deiner Anleitung, dass dort der user eingerichtet wird....also geh ich das mal komplett durch....
-
@uliauer44 sagte in Passwort Iobroker über Mac-Terminal anders?:
Den Pi-Imager habe ich schon auf dem Mac am Start...
Direkt im Imager macht man das. Nenn den uli oder sonst wie, aber NICHT iobroker.
-
@thomas-braun
Okay. Soweit in der Spur (Das "aktualisieren" nach dem Install läuft jetzt schon sehr lange, aber das ist vermutlich in Ordnung, nur langsam)Ich habe aber noch ein anderes Problem:
Ich kann mich aktuell (das habe ich VOR dem gerade laufenden Aktualisieren festgestellt) nur über die WLAN IP-Adresse anmelden.
Über die LAN-Verbindung bekomme ich folgende Meldung:ssh uli@192.168.178.22 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ED25519 key sent by the remote host is SHA256:/5CJrlsdDnAGxI3m86IinQQWAnl8aPr/ZuQYdpGCx7k. Please contact your system administrator. Add correct host key in /Users/ulimaxbook/.ssh/known_hosts to get rid of this message. Offending ED25519 key in /Users/ulimaxbook/.ssh/known_hosts:5 Host key for 192.168.178.22 has changed and you have requested strict checking. Host key verification failed.Hinweis: Beide IP-Adressen sind bei mir in der Fritzbox fest zugewiesen (22 für LAN, 180 für WLAN)
-
@uliauer44 sagte in Passwort Iobroker über Mac-Terminal anders?:
Add correct host key in /Users/ulimaxbook/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /Users/ulimaxbook/.ssh/known_hosts:5Die genannte Datei muss angepasst werden. Wenn du nur den Eintrag löschst wird bei erneuter Verbingsaufnahme der Schlüssel neugeschrieben.
-
@thomas-braun said in Passwort Iobroker über Mac-Terminal anders?:
Die genannte Datei muss angepasst werden. Wenn du nur den Eintrag löschst wird bei erneuter Verbingsaufnahme der Schlüssel neugeschrieben.
Wie mache ich das?
-
@uliauer44 sagte in Passwort Iobroker über Mac-Terminal anders?:
Wie mache ich das?
Mit einem Editor?
-
Ja, aber was? Die Datei besteht hieraus....
iobroker.local ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIB6C+A2ymodV55rvTFDxK3JjffFTd3EDdpu8NN6VakAo iobroker.local ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCnq8bu5eRJ8ec9DnUWn/Tvt9ZKVYX0xhJcQZGcXrsWWnLrY6TCl+RPy/KwpToxlRRSgqfil0H+SaWjyuFANPMH8Sm01qTcBb1tG33LugAw1WAq3Lw3J2x+rRh+Y4ub/vtKfG4JR/igHBoy8RNXjIIUFla5uoVxDtDpe8ixI5bAyHPz6Og39v3i//I20iBR5AqZV+xAxt8CicATcnE0FMsP2ml4f041rAJOqntUNTuwpKC8uR2JK/jelJHENtCgg0+zesbCX+AkVHfRKDI1wIsXWRsBg4lE5WWS+/hU/gkDajbRfV94qCdZ9SbKw6Msi5i8r3lz9t3zK0oFMc/OZ/heQCa9mwtWlrtAksrajQbZ7VxSCHcYpzjFC5PCm0lrqN193U/t8zMbHEvHRSR8Gf56/ZsfbrQrzpGL4ZaU+qcYdOQPEDuYfaGsSUOI217GQ8d9jxlCwHDfpAU3Pug/YBa4g1PdqRpKERPufF4yXKw6PoEivMRp5EDwMUdRdqJz0Ts= iobroker.local ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDTtZUIPIaqODccZayvOy0e4KmigwO9OTDZgyZhNlywVbT9SZI8Gt7rHgbvwk6mJkcb6Ipw2Wy98G4G6vEawUV0= sftp.hidrive.strato.com ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKj++KINkipb3Uh30rB+BpR0TArchTWDoetSEKpymo9o 192.168.178.22 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIB6C+A2ymodV55rvTFDxK3JjffFTd3EDdpu8NN6VakAo 192.168.178.222 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDZtpAs6MtXBqzlmDQnsoKVx1Q0j5s0detertziamCGUfCWnDSzfulfLq1QcFm/vT5xjbJyVsE038w0ric08eayv7hu3AJZ0QHdivzoZD0zDb/OdTT00e3MdS+TVI53yqRTGEl+up7tlcfy6kO0BhHuBILeiwgHAfLDT+KwgVtfFWFKFwcjEIaHtmQd1lClr9mtJZ+6uOZ63jsuN2o8hIC+v/rNsZRj7dHwhGQLagAngpjPD+tquORJpAC1XKyOIhlg5zzaNI1jZV6xJHsEB7yI47DwpNbyE60pi83JTIN1jb/mwdts3BiaRJ9tQjxU1Kt5vlDHoEVBC5KZtgxKAon9fVuEvJgX/mK6VGJhr1Pi242/DHTvVMAnOmWRWVpxXPu+HXY2UeDidzPEX4VaM5rMUzmH1gj91WAUaJmowrNf+CNqDoh6uedxxVRe6gLc0OU1YMZNSvBy1kYzADaMturEuIYtqpfnO0jdpRdQ1ipVNTS/ARb4FP+/3Xnw1xr1QyE= 192.168.178.180 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHqO6j6Mlm1GWCwtVXM4BcpetfY/i0JK0d3Ot9fkVI+8 192.168.178.180 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCjBGIWZayXiB6ow4INofNriYhxMIoso8ap5Xq+8vW4eF0flR7HdcoKD/1kLZV2o3/TAejemcMiCwR1gHrN8aHBeBA3OWHqzc6H/nZMolAlUjJuSk6ql+XtUQ7+1d5IkFym9/aWUPLOugkD2zNj98Ld8I5s7MzgbdY5idMUp3Mi6askoBkhgvtIv7ziruSnvVx1h/AQE2t/uCeQ/7tGehA+KQChhbuAeEEYKmyIb8svehPgdxapYXMWGrUXkUJ3hOBKHqp9ybFomLOCu/ -
Offending ED25519 key in /Users/ulimaxbook/.ssh/known_hosts:5
Also Zeile 5.
Die fängt ja auch mit der IP an, für die der Key sich geändert hat.
