[gelöst] iobroker lässt sich nicht richtig installieren
-
curl -L -o diag.sh https://iobroker.net/diag.sh && bash diag.sh -
@thomas-braun
liefertpi@ubuntu:/$ curl -L -o diag.sh https://iobroker.net/diag.sh && bash diag.sh % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 169 100 169 0 0 800 0 --:--:-- --:--:-- --:--:-- 800 Warning: Failed to create the file diag.sh: Permission denied 69 23302 69 16126 0 0 37502 0 --:--:-- --:--:-- --:--:-- 37502 curl: (23) Failed writing body (0 != 16126) -
Bitte immer die vollständigen Ein- wie Ausgaben inkl. LoginPrompt posten.
-
@mipl sagte in iobroker lässt sich nicht richtig installieren:
nicht als root
wieso dann
@mipl sagte in iobroker lässt sich nicht richtig installieren:
System ist mit apt-get update und apt-upgrade aktualisiert.
ohne sudo?
-
@homoran
update und upgrade wurde mit sudo ausgeführt. -
@mipl Danke!
hmm, wo klemmt's denn dann mit den Rechten? -
Stell dich in das home-Verzeichnis vom pi. Der darf (zum Glück) nicht in / schreiben.
-
@thomas-braun
Du meintest so?pi@ubuntu:/$ cd /home/pi pi@ubuntu:~$ pwd /home/pi pi@ubuntu:~$ ls -l total 1872 -rw-rw-r-- 1 pi pi 1800 Mar 1 2023 Cron-Send-new-IP.sh -rw-rw-r-- 1 pi pi 70 Mar 1 2023 IP-per-Email.txt -rw-rw-r-- 1 pi pi 1908226 Sep 20 2023 get-pip.py -
Natürlich... Was treibst du eigentlich im root? Da haste nix zu wollen.
-
@thomas-braun
ok, curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh liefert nun:======== Start marking the full check here ========= Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: ubuntu Icon name: computer Operating System: Ubuntu 20.04.6 LTS Kernel: Linux 5.4.0-1111-raspi Architecture: arm64 Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 20:45:23 up 1:34, 1 user, load average: 0.25, 0.12, 0.12 CPU threads: 4 *** Time and Time Zones *** Local time: Mon 2024-07-01 20:45:23 CEST Universal time: Mon 2024-07-01 18:45:23 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 render netdev gpio spi i2c iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev gpio i2c *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 906M 223M 186M 2.0M 496M 588M Swap: 0B 0B 0B Total: 906M 223M 186M Active iob-Instances: 1 906 M total memory 223 M used memory 472 M active memory 111 M inactive memory 186 M free memory 38 M buffer memory 457 M swap cache 0 M total swap 0 M used swap 0 M free swap *** top - Table Of Processes *** top - 20:45:24 up 1:34, 1 user, load average: 0.25, 0.12, 0.12 Tasks: 149 total, 1 running, 148 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.2 us, 6.1 sy, 0.0 ni, 92.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 906.1 total, 186.2 free, 223.5 used, 496.5 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 589.0 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * systemd-networkd-wait-online.service loaded failed failed Wait for Network to be Configured 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. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 405M 0 405M 0% /dev tmpfs tmpfs 91M 3.0M 88M 4% /run /dev/mmcblk0p2 ext4 15G 6.7G 7.1G 49% / tmpfs tmpfs 454M 16K 454M 1% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 454M 0 454M 0% /sys/fs/cgroup /dev/loop0 squashfs 60M 60M 0 100% /snap/core20/2107 /dev/loop2 squashfs 62M 62M 0 100% /snap/lxd/22761 /dev/loop1 squashfs 60M 60M 0 100% /snap/core20/2321 /dev/loop4 squashfs 36M 36M 0 100% /snap/snapd/20674 /dev/loop5 squashfs 34M 34M 0 100% /snap/snapd/21761 /dev/loop3 squashfs 92M 92M 0 100% /snap/lxd/24065 /dev/mmcblk0p1 vfat 253M 121M 132M 48% /boot/firmware tmpfs tmpfs 91M 0 91M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon Jul 1 19:10:44 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 elevator=deadline net.ifnames=0 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash quiet splash [Mon Jul 1 19:10:50 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Mon Jul 1 19:10:53 2024] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,relatime |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/unified cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd | | |-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | | |-/sys/fs/cgroup/rdma cgroup cgroup rw,nosuid,nodev,noexec,relatime,rdma | | |-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event | | |-/sys/fs/cgroup/hugetlb cgroup cgroup rw,nosuid,nodev,noexec,relatime,hugetlb | | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer | | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct | | |-/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio | | |-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuset | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | `-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime | `-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=1192 | `-/proc/sys/fs/binfmt_misc binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime |-/dev udev devtmpfs rw,nosuid,noexec,relatime,size=414248k,nr_inodes=103562,mode=755 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/hugepages hugetlbfs hugetlbfs rw,relatime,pagesize=2M | `-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime |-/run tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=92792k,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | |-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=92788k,mode=700,uid=1000,gid=1003 | `-/run/snapd/ns tmpfs[/snapd/ns] tmpfs rw,nosuid,nodev,noexec,relatime,size=92792k,mode=755 | `-/run/snapd/ns/lxd.mnt nsfs[mnt:[4026533439]] nsfs rw |-/snap/core20/2107 /dev/loop0 squashfs ro,nodev,relatime |-/snap/lxd/22761 /dev/loop2 squashfs ro,nodev,relatime |-/snap/core20/2321 /dev/loop1 squashfs ro,nodev,relatime |-/snap/snapd/20674 /dev/loop4 squashfs ro,nodev,relatime |-/snap/snapd/21761 /dev/loop5 squashfs ro,nodev,relatime |-/snap/lxd/24065 /dev/loop3 squashfs ro,nodev,relatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 3.1G /var/ 1.8G /var/log 1.5G /var/log/journal/4d4f67eb4fe2458ca82aed624af367f8 1.5G /var/log/journal 1016M /var/lib Archived and active journals take up 1.4G in the file system. /opt/iobroker/backups: du: cannot access '/opt/iobroker/backups/': No such file or directory /opt/iobroker/iobroker-data: 228K /opt/iobroker/iobroker-data/ 4.0K /opt/iobroker/iobroker-data/states.jsonl.lock 4.0K /opt/iobroker/iobroker-data/objects.jsonl.lock 4.0K /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 188K /opt/iobroker/iobroker-data/states.jsonl 16K /opt/iobroker/iobroker-data/objects.jsonl 8.0K /opt/iobroker/iobroker-data/iobroker.json 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 *** /usr/bin/nodejs v20.15.0 /usr/bin/node v20.15.0 /usr/bin/npm 10.7.0 /usr/bin/npx 10.7.0 /usr/bin/corepack 0.28.1 nodejs: Installed: 20.15.0-1nodesource1 Candidate: 20.15.0-1nodesource1 Version table: *** 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 10.19.0~dfsg-3ubuntu1.6 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports focal-security/universe arm64 Packages 10.19.0~dfsg-3ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status Cannot read system.config: null (OK when migrating or restoring) iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.17.14 javascript: "javascript" not found nodejs modules from github: 0 Adapter State Cannot read system.config: null (OK when migrating or restoring) + instance is alive Enabled adapters with bindings ioBroker-Repositories Cannot read system.config: null (OK when migrating or restoring) List is empty Installed ioBroker-Instances Cannot read system.config: null (OK when migrating or restoring) Error: Object "system.config" not found Objects and States Please stand by - This may take a while Objects: 33 States: 26 *** OS-Repositories and Updates *** Hit:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Done Pending Updates: 2 *** 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:111 0.0.0.0:* LISTEN 0 15414 1/init tcp 0 0 127.0.0.1:8081 0.0.0.0:* LISTEN 0 25397 864/motion tcp 0 0 127.0.0.1:8082 0.0.0.0:* LISTEN 0 25398 864/motion tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 24040 621/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 29099 1054/sshd: /usr/sbi tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 0 26854 657/python2 tcp 0 0 127.0.0.1:7999 0.0.0.0:* LISTEN 0 25399 864/motion tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 50450 5240/iobroker.js-co tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 50445 5240/iobroker.js-co tcp6 0 0 :::111 :::* LISTEN 0 15252 1/init tcp6 0 0 :::22 :::* LISTEN 0 29101 1054/sshd: /usr/sbi udp 0 0 127.0.0.53:53 0.0.0.0:* 101 24039 621/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 15415 1/init udp6 0 0 :::111 :::* 0 15418 1/init *** Log File - Last 25 Lines *** 2024-07-01 19:27:48.803 - info: host.ubuntu iobroker.js-controller version 5.0.19 js-controller starting 2024-07-01 19:27:48.817 - info: host.ubuntu Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-07-01 19:27:48.820 - info: host.ubuntu hostname: ubuntu, node: v20.15.0 2024-07-01 19:27:48.822 - info: host.ubuntu ip addresses: 10.56.78.100 2024-07-01 19:27:49.080 - info: host.ubuntu Objects protocol version has changed, disconnecting! 2024-07-01 19:27:49.154 - error: host.ubuntu Cannot read system.config: null (OK when migrating or restoring) 2024-07-01 19:27:49.225 - error: host.ubuntu Cannot find view "system" for search "host" 2024-07-01 19:27:49.371 - info: host.ubuntu connected to Objects and States 2024-07-01 19:27:49.454 - info: host.ubuntu Node.js version has changed from unknown to 20.15.0 2024-07-01 19:27:49.542 - info: host.ubuntu added notifications configuration of host 2024-07-01 19:27:49.547 - info: host.ubuntu Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2024-07-01 19:27:49.614 - error: host.ubuntu Cannot find view "system" for search "instance" 2024-07-01 19:27:49.617 - error: host.ubuntu Could not add notifications config of this host: Could not get notifications setup from instances: Cannot find view "system" 2024-07-01 19:27:49.697 - info: host.ubuntu Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2024-07-01 19:27:49.716 - error: host.ubuntu Cannot find view "system" for search "host" 2024-07-01 19:27:49.737 - error: host.ubuntu Cannot find view "system" for search "state" 2024-07-01 19:27:49.739 - error: host.ubuntu Cannot find view "system" for search "instance" 2024-07-01 19:27:49.741 - error: host.ubuntu Could not collect system.host.ubuntu states to check for obsolete states: Cannot find view "system" 2024-07-01 19:27:49.743 - error: host.ubuntu _design/system missing - call node iobroker.js setup 2024-07-01 19:27:49.744 - info: host.ubuntu no instances found 2024-07-01 19:27:49.745 - info: host.ubuntu no instances found 2024-07-01 19:27:50.339 - info: host.ubuntu Created UUID: 67b55ea4-7e7d-e632-81e0-66bd95578b60 ============ Mark until here for C&P ============= iob diag has finished. -
@mipl sagte in iobroker lässt sich nicht richtig installieren:
Raspberry Pi 3 Model B Rev 1.2
und dann
@mipl sagte in iobroker lässt sich nicht richtig installieren:
auf ein laufendes System "hinzuinstalliert".
und das bei nur 1GB RAM, und dann ausgerechnet
@mipl sagte in iobroker lässt sich nicht richtig installieren:
motion
??
das auch noch die Ports blockiert -
@homoran
läuft auf einem Raspi 4 problemlos - iobroker auf Port 8083.Und auf diesem Raspi 3 ist (derzeit zumindest) noch Ram verfügbar. Daran kann es noch nicht klemmen, oder?
Kann man iobroker nicht aus der shell auf Port 8083 installieren?
Liegt es denn nicht eventuell an
*** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * systemd-networkd-wait-online.service loaded failed failed Wait for Network to be Configured 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. -
@mipl sagte in iobroker lässt sich nicht richtig installieren:
Liegt es denn nicht eventuell an
möglich.
aber du kommst doch übers Netzwerk drauf@mipl sagte in iobroker lässt sich nicht richtig installieren:
Kann man iobroker nicht aus der shell auf Port 8083 installieren?
man könnte den Port ändern wenn es installiert ist.
@mipl sagte in iobroker lässt sich nicht richtig installieren:
Und auf diesem Raspi 3 ist (derzeit zumindest) noch Ram verfügbar.
oder wieder!
Und während der Installation war es zu wenig.
Warum ist da kein SWAP.
da würde man sehen wenn auch der swap verbraucht wäre -
@homoran
ich habe es jetzt (grundlegend) hinbekommen:iobroker deinstalliert
motion gestoppt
Das Directory /home/iobroker von Hand angelegt. Owner und Group = iobroker
Dann Installation neu angestoßen - läuft ohne Probleme durch
iobroker gestartet über Port 8083 und Ersteinrichtung durchgeführt.
Port in Admin-Adapter auf 8083 geändert.
motion gestartet
Adapter lassen sich im iobroker installieren.Grundlegend, weil im Protokoll momentan noch Fehlermeldungen und Warnungen auftraten. Das werde ich zunächst beobachten, ob diese dauerhaft kommen.
Ich setze erstmal auf Erledigt. Danke für Eure Zeit und Hilfe.
