iobroker cmd in Konsole geht nicht
-
@hukio sagte in iobroker cmd in Konsole geht nicht:
pi@raspibull:~ $ iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh
was soll das iob_diag: davor?
-
@hukio
So eingeben:curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh -
======== Start marking the full check here =========
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: raspibull Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 18:03:11 up 3:13, 2 users, load average: 6.03, 2.30, 1.14 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Fri 2024-07-19 18:03:11 CEST Universal time: Fri 2024-07-19 16:03:11 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 i2c spi iobroker User that is running 'js-controller': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 2.5G 318M 1.0M 966M 1.4G Swap: 2.0G 0B 2.0G Total: 5.8G 2.5G 2.3G Active iob-Instances: 0 3793 M total memory 2508 M used memory 2599 M active memory 691 M inactive memory 318 M free memory 96 M buffer memory 869 M swap cache 2027 M total swap 0 M used swap 2027 M free swap *** top - Table Of Processes *** top - 18:03:11 up 3:13, 2 users, load average: 6.03, 2.30, 1.14 Tasks: 188 total, 1 running, 187 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.4 us, 5.6 sy, 0.0 ni, 93.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3793.3 total, 318.6 free, 2508.3 used, 966.5 buff/cache MiB Swap: 2028.0 total, 2028.0 free, 0.0 used. 1354.1 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 30G 20G 8.2G 71% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 759M 1.2M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda3 ext4 439G 3.9G 413G 1% /mnt/hukdata /dev/sda1 vfat 256M 32M 225M 13% /boot tmpfs tmpfs 380M 0 380M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Jul 19 14:49:43 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:12:1E:93 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=ttyAMA0,115200 console=tty1 root=PARTUUID=4d904d30-02 rootfstype=ext4 fsck.repair=yes rootwait rootdelay=5 [Fri Jul 19 14:49:51 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Fri Jul 19 14:49:51 2024] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Fri Jul 19 14:49:53 2024] EXT4-fs (sda2): re-mounted. Quota mode: none. [Fri Jul 19 14:49:55 2024] EXT4-fs (sda3): mounted filesystem with ordered data mode. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=1677960k,nr_inodes=419490,mode=755 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | `-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf bpf 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/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime | `-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime |-/run tmpfs tmpfs rw,nosuid,nodev,size=776876k,nr_inodes=819200,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=388436k,nr_inodes=97109,mode=700,uid=1000,gid=1000 |-/mnt/hukdata /dev/sda3 ext4 rw,noatime `-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 5.9G /var/ 3.1G /var/log 3.0G /var/log/journal/1ffd49df1b3a44ffb614b2c58029c285 3.0G /var/log/journal 630M /var/cache Archived and active journals take up 2.9G in the file system. /opt/iobroker/backups: 7.2G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 858M /opt/iobroker/iobroker-data/ 356M /opt/iobroker/iobroker-data/files 342M /opt/iobroker/iobroker-data/history 138M /opt/iobroker/iobroker-data/files/javascript.admin 129M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 29M /opt/iobroker/iobroker-data/objects.jsonl 26M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.8947f24d.js.map 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.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-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_323adb3b74d9eb11b6e6178e6fe9f4d9-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.20.4 /usr/bin/node v18.20.4 /usr/bin/npm 10.7.0 /usr/bin/npx 10.7.0 /usr/bin/corepack 0.28.0 nodejs: Installed: 18.20.4-1nodesource1 Candidate: 18.20.4-1nodesource1 Version table: *** 18.20.4-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.20.3-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status Core adapters versions js-controller: admin: javascript: nodejs modules from github: 1 +-- iobroker.rtspstream@0.0.4 (git+ssh://git@github.com/dbweb-ch/ioBroker.rtspStream.git#adff9611d3ab1871cd94d2e779b9fd4fcc937353) Adapter State Enabled adapters with bindings ioBroker-Repositories Installed ioBroker-Instances Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** 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://archive.raspberrypi.org/debian bullseye InRelease Hit:4 http://security.debian.org/debian-security bullseye-security InRelease Hit:5 https://repos.influxdata.com/debian stable InRelease Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Done 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 192.168.178.78:8100 0.0.0.0:* LISTEN 1000 16018 1419/io.doorbird.0 tcp 0 0 192.168.178.78:8087 0.0.0.0:* LISTEN 1000 16143 1495/io.simple-api. tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 110 15380 540/redis-server 12 tcp 0 0 127.0.0.1:5037 0.0.0.0:* LISTEN 1000 17981 1523/adb tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 2012 1101/iobroker.js-co tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1000 17891 1408/io.shelly.1 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1000 17626 1291/io.mqtt.0 tcp 0 0 0.0.0.0:1889 0.0.0.0:* LISTEN 1000 17761 1366/io.sonoff.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 3518 548/sshd: /usr/sbin tcp 0 0 127.0.0.1:8088 0.0.0.0:* LISTEN 999 1805 777/influxd tcp6 0 0 :::8082 :::* LISTEN 1000 15245 1532/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1000 16403 1118/io.admin.0 tcp6 0 0 :::8086 :::* LISTEN 999 3698 777/influxd tcp6 0 0 :::8084 :::* LISTEN 1000 15223 1514/io.socketio.0 tcp6 0 0 ::1:6379 :::* LISTEN 110 15381 540/redis-server 12 tcp6 0 0 :::22 :::* LISTEN 0 3520 548/sshd: /usr/sbin tcp6 0 0 :::3000 :::* LISTEN 111 15671 1049/grafana tcp6 0 0 :::51989 :::* LISTEN 1000 16644 1325/io.nuki-extend udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14160 429/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1000 15014 1351/io.shelly.0 udp 0 0 0.0.0.0:36430 0.0.0.0:* 1000 153027 1336/io.onkyo.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14462 773/dhcpcd udp 0 0 0.0.0.0:45834 0.0.0.0:* 1000 151987 1336/io.onkyo.0 udp 0 0 0.0.0.0:33672 0.0.0.0:* 108 14162 429/avahi-daemon: r udp6 0 0 :::5353 :::* 108 14161 429/avahi-daemon: r udp6 0 0 :::546 :::* 0 1753 773/dhcpcd udp6 0 0 :::52066 :::* 108 14163 429/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-07-19 17:06:30.780 - info: javascript.0 (1186) script.js.Sensoren.Waschmaschine: vEnergy_start: 701.39 2024-07-19 17:06:30.780 - info: javascript.0 (1186) script.js.Sensoren.Waschmaschine: Zählerstand Strom: 31164.17 2024-07-19 17:33:56.909 - info: javascript.0 (1186) script.js.Sensoren.Trockner: Verbrauch (plug): 0.4 kWh 2024-07-19 17:33:56.909 - info: javascript.0 (1186) script.js.Sensoren.Trockner: totaler Verbrauch Zählerdifferenz: 1.3 kWh 2024-07-19 17:33:56.966 - info: signal-cmb.0 (1484) Send Karin der Trockner ist seit 17:33 fertig. to f98af11f-c3df-4b54-9f1e-0454df85f8bd 2024-07-19 17:53:52.316 - info: javascript.0 (1186) script.js.Sensoren.Proximity_Sensor_Echo: true 2024-07-19 17:57:36.227 - info: zigbee.0 (1397) Device '0xec1bbdfffe79e066' announced itself 2024-07-19 18:02:30.140 - warn: influxdb.0 (1171) Error on writePoint("{"value":5.6,"time":"2024-07-19T16:02:00.131Z","from":"system.adapter.shelly.1","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:31.681 - warn: influxdb.0 (1171) Error on writePoint("{"value":584,"time":"2024-07-19T16:02:01.675Z","from":"system.adapter.javascript.0","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:34.365 - warn: influxdb.0 (1171) Error on writePoint("{"value":8.3,"time":"2024-07-19T16:02:04.358Z","from":"system.adapter.shelly.1","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:38.418 - warn: influxdb.0 (1171) Error on writePoint("{"value":7.3,"time":"2024-07-19T16:02:08.407Z","from":"system.adapter.shelly.1","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:38.572 - warn: influxdb.0 (1171) Error on writePoint("{"value":2383,"time":"2024-07-19T16:02:08.561Z","from":"system.adapter.javascript.0","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:40.147 - info: influxdb.0 (1171) Connecting http://localhost:8086/ ... 2024-07-19 18:02:40.148 - info: influxdb.0 (1171) Influx DB Version used: 1.x 2024-07-19 18:02:45.287 - warn: influxdb.0 (1171) Error on writePoint("{"value":1033,"time":"2024-07-19T16:02:15.274Z","from":"system.adapter.javascript.0","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:45.288 - info: influxdb.0 (1171) Add point that had error for javascript.0.gStromc to buffer again, error-count=4 2024-07-19 18:02:48.495 - info: influxdb.0 (1171) Store 8 buffered influxDB history points 2024-07-19 18:02:53.190 - warn: influxdb.0 (1171) Error on writePoint("{"value":359,"time":"2024-07-19T16:02:23.184Z","from":"system.adapter.javascript.0","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:53.191 - info: influxdb.0 (1171) Add point that had error for javascript.0.gStromc to buffer again, error-count=5 2024-07-19 18:02:58.759 - warn: influxdb.0 (1171) Error on writePoint("{"value":349,"time":"2024-07-19T16:02:28.748Z","from":"system.adapter.javascript.0","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:58.760 - info: influxdb.0 (1171) Add point that had error for javascript.0.gStromc to buffer again, error-count=6 2024-07-19 18:02:59.711 - warn: influxdb.0 (1171) Error on writePoint("{"value":31165.8,"time":"2024-07-19T16:02:28.578Z","from":"system.adapter.sonoff.0","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:59.712 - info: influxdb.0 (1171) Add point that had error for sonoff.0.Stromzähler._Zählerstand to buffer again, error-count=1 2024-07-19 18:02:59.713 - warn: influxdb.0 (1171) Error on writePoint("{"value":31165.81,"time":"2024-07-19T16:02:29.702Z","from":"system.adapter.sonoff.0","q":0,"ack":true}): Error: ESOCKETTIMEDOUT / "ESOCKETTIMEDOUT"" 2024-07-19 18:02:59.714 - info: influxdb.0 (1171) Add point that had error for sonoff.0.Stromzähler._Zählerstand to buffer again, error-count=2 -
@hukio sagte in iobroker cmd in Konsole geht nicht:
User that is running 'js-controller':
piDas muss der user 'iobroker' sein.
Was haste da bitte gemacht? -
@thomas-braun
Habe ich in der ersten mail skizziert. Mehr Einzelheiten kann ich chronologisch nicht sagen. Wie kann ich den Fehler ändern? -
systemctl status iobroker.service -
pi@raspibull:~ $ systemctl status iobroker.service ● iobroker.service Loaded: masked (Reason: Unit iobroker.service is masked.) Active: inactive (dead) -
systemctl status mask iobroker.service systemctl status unmask iobroker.service -
@hukio sagte in iobroker cmd in Konsole geht nicht:
Ich habe ein update/upgrade des OS gemacht. Das in einen dpkg Fehler lief (problem mit node 18.20.4 update (war 18.19.x)). IOB startete nicht mehr. Habe dann nodejs alleine upgrade gemacht.
Kannst du ggfs. die letzten Befehle in der Konsole mal posten, also die die obiges betreffen. In der Konsole sollte man diese sehen, mit der Pfeiltaste nach oben bzw. nach unten.
Ro75.
-
pi@raspibull:~ $ systemctl status mask iobroker.service Unit mask.service could not be found. ● iobroker.service Loaded: masked (Reason: Unit iobroker.service is masked.) Active: inactive (dead) pi@raspibull:~ $ systemctl status unmask iobroker.service Unit unmask.service could not be found. ● iobroker.service Loaded: masked (Reason: Unit iobroker.service is masked.) Active: inactive (dead) -
Sorry, Quatsch von mir...
sudo systemctl mask iobroker.service sudo systemctl unmask iobroker.service -
@ro75
Habe aus Versehen diesen Befehl abgesetzt.sudo ln -s /usr/bin/node /usr/bin/nodejsvorher diesen
sudo dpkg --configure -amehr finde ich nicht
-
pi@raspibull:~ $ sudo systemctl mask iobroker.service Created symlink /etc/systemd/system/iobroker.service → /dev/null. pi@raspibull:~ $ sudo systemctl unmask iobroker.service Removed /etc/systemd/system/iobroker.service. -
Da frag ich mir nur... WARUM??
Mit dpgk direkt hast du in der Regel nix am Hut.
systemctl status iobroker.servicesagt nun?
-
pi@raspibull:~ $ systemctl status iobroker.service ● iobroker.service Loaded: masked (Reason: Unit iobroker.service is masked.) Active: inactive (dead)weil ich einen Fehler mit dpkg hatte.
-
@hukio sagte in iobroker cmd in Konsole geht nicht:
weil ich einen Fehler mit dpkg hatte.
Und genau was wurde von dpkg bemängelt?
sudo apt install --reinstall nodejs sudo reboot -
pi@raspibull:~ $ sudo apt install --reinstall nodejs Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/28.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 59474 files and directories currently installed.) Preparing to unpack .../nodejs_18.20.4-1nodesource1_arm64.deb ... Detected old npm client, removing... Unpacking nodejs (18.20.4-1nodesource1) over (18.20.4-1nodesource1) ... Setting up nodejs (18.20.4-1nodesource1) ... Processing triggers for man-db (2.9.4-2) ...nach reboot iobroker startet nicht. cmd geht nicht
-
sudo -u iobroker id systemctl status iobroker.serviceJag den Fixer mal über das System:
curl -fsL https://iobroker.net/fix.sh | bash - -
@thomas-braun
Das war es! cmd und iobroker laufen wieder.pi@raspibull:~ $ sudo -u iobroker id uid=1001(iobroker) gid=1001(iobroker) groups=1001(iobroker),5(tty),20(dialout),29(audio),44(video),46(plugdev),112(bluetooth),114(redis),997(gpio),998(i2c) pi@raspibull:~ $ systemctl status iobroker.service ● iobroker.service Loaded: masked (Reason: Unit iobroker.service is masked.) Active: inactive (dead) pi@raspibull:~ $ curl -fsL https://iobroker.net/fix.sh | bash - library: loaded Library version=2024-05-24 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2024-01-04 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== 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://repos.influxdata.com/debian stable InRelease Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Done ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 1 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again!Vielen Dank für die Mühe. Ich frage immer zu spät, bzw. ich versuche es erst mal selbst. Habe aber nicht den background.
Nochmals Danke
HUK -
Dann bring die Kiste nun auf nodejs@20 und zeig dann nochmal die Langfassung von
iob nodejs-update 20 iob diag
