Keine Verbindung mehr zu iobroker
-
Hallo,
es gab vorgestern einen kurzen Stromausfall und seitdem erreiche ich den iobroker nicht mehr. Ich nutze eine Raspberry Pi 4, alle anderen Programme wie Grafana, Weewx etc. laufen seit dem ungewollten Neustart normal.
Folgende Sachen habe ich getestet:pi@raspberrypi:~ $ ps -A | grep iobroker 29300 ? 00:00:09 iobroker.js-conpi@raspberrypi:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs 2023-12-27 10:32:09.223 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 10:32:09.236 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 10:32:09.239 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.1 2023-12-27 10:32:09.240 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fd00::6d7d:35d4:5427:1bde fe80::aa74:964:1a9c:1acd 2023-12-27 10:32:39.273 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 10:32:39.288 - info: host.raspberrypi iobroker _restartBei
netstat -n -a -p TCPfehlen die Adressen beiden folgenden Adressen:
TCP 0.0.0.0:9000 0.0.0.0:0 LISTENING TCP 0.0.0.0:9001 0.0.0.0:0 LISTENINGich abe vor dem Stromausfall nichts verändert. Ich vermute also, dass das unkontrollierte Abschalten irgendetwas durcheinander gebracht hat.
Wie kann ich die database wieder erreichbar machen?
Ein Backup müsste ich haben vom iobroker.
Es wäre schön, wenn mir jemand helfen könnte. Ich bin leider auch kein Linuxexperte. Danke!
Viele Geüße
Thomas@obstbauer sagte in Keine Verbindung mehr zu iobroker:
Ein Backup müsste ich haben vom iobroker.
wäre wohl die einfachste Variante
zumal der js-Controller als auch nodejs bei dir veraltet sind, wahrscheinlich dann auch der Rest
-
Hallo,
es gab vorgestern einen kurzen Stromausfall und seitdem erreiche ich den iobroker nicht mehr. Ich nutze eine Raspberry Pi 4, alle anderen Programme wie Grafana, Weewx etc. laufen seit dem ungewollten Neustart normal.
Folgende Sachen habe ich getestet:pi@raspberrypi:~ $ ps -A | grep iobroker 29300 ? 00:00:09 iobroker.js-conpi@raspberrypi:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs 2023-12-27 10:32:09.223 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 10:32:09.236 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 10:32:09.239 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.1 2023-12-27 10:32:09.240 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fd00::6d7d:35d4:5427:1bde fe80::aa74:964:1a9c:1acd 2023-12-27 10:32:39.273 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 10:32:39.288 - info: host.raspberrypi iobroker _restartBei
netstat -n -a -p TCPfehlen die Adressen beiden folgenden Adressen:
TCP 0.0.0.0:9000 0.0.0.0:0 LISTENING TCP 0.0.0.0:9001 0.0.0.0:0 LISTENINGich abe vor dem Stromausfall nichts verändert. Ich vermute also, dass das unkontrollierte Abschalten irgendetwas durcheinander gebracht hat.
Wie kann ich die database wieder erreichbar machen?
Ein Backup müsste ich haben vom iobroker.
Es wäre schön, wenn mir jemand helfen könnte. Ich bin leider auch kein Linuxexperte. Danke!
Viele Geüße
Thomas -
Copy text starting here: ======================= SUMMARY ======================= v.2023-10-25 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 58 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.20.1 /usr/bin/node v16.20.1 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 /usr/bin/corepack 0.17.0 Recommended versions are nodejs Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! and npm No connection to databases possible ... Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 934M 445M 72M 2.4G 2.8G Swap: 99M 2.0M 97M Total: 3.9G 936M 543M Active iob-Instances: 0 Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! ioBroker Core: js-controller 4.0.23 admin 6.12.0 ioBroker Status: Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Status admin and web instance: Objects: 1 States: 1 Size of iob-Database: 1.6G /opt/iobroker/iobroker-data/objects.jsonl 476K /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================diesen Fehler scheine ich zu haben:
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! -
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
Ein Backup müsste ich haben vom iobroker.
wäre wohl die einfachste Variante
zumal der js-Controller als auch nodejs bei dir veraltet sind, wahrscheinlich dann auch der Rest
-
Copy text starting here: ======================= SUMMARY ======================= v.2023-10-25 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 58 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.20.1 /usr/bin/node v16.20.1 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 /usr/bin/corepack 0.17.0 Recommended versions are nodejs Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! and npm No connection to databases possible ... Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 934M 445M 72M 2.4G 2.8G Swap: 99M 2.0M 97M Total: 3.9G 936M 543M Active iob-Instances: 0 Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! ioBroker Core: js-controller 4.0.23 admin 6.12.0 ioBroker Status: Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Status admin and web instance: Objects: 1 States: 1 Size of iob-Database: 1.6G /opt/iobroker/iobroker-data/objects.jsonl 476K /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================diesen Fehler scheine ich zu haben:
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!Schalt den Desktop aus und halte das System auf einem aktuellen Stand.
-
Schalt den Desktop aus und halte das System auf einem aktuellen Stand.
@thomas-braun und wie bekomme ich nun mein Problem gelöst?
der Desktop ist halt praktisch für Anfänger...
das System update ich eigentlich regelmäßig mit sudo apt update und sudo apt upgrade
-
@thomas-braun und wie bekomme ich nun mein Problem gelöst?
der Desktop ist halt praktisch für Anfänger...
das System update ich eigentlich regelmäßig mit sudo apt update und sudo apt upgrade
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
der Desktop ist halt praktisch für Anfänger...
Im Gegenteil. So bleibst du nämlich immer nur ein Mausschubser und bist nur Passagier auf dem System.
sudo systemctl set-default multi-user.target sudo reboot -
@thomas-braun und wie bekomme ich nun mein Problem gelöst?
der Desktop ist halt praktisch für Anfänger...
das System update ich eigentlich regelmäßig mit sudo apt update und sudo apt upgrade
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
das System update ich eigentlich regelmäßig mit sudo apt update und sudo apt upgrade
Dann machst du es deutlich nicht regelmäßig genug. Da hängen mehr als 50 Updates in der Luft.
-
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
das System update ich eigentlich regelmäßig mit sudo apt update und sudo apt upgrade
Dann machst du es deutlich nicht regelmäßig genug. Da hängen mehr als 50 Updates in der Luft.
@thomas-braun ok, das mit dem Mausschubsen leuchtet mir ein... ich werde versuchen das in Zukunft zu ändern um mich daran zu gewöhnen
ich bin halt wie viele verwindowsedzu den Updates: mache ich mit den Befehlen etwas falsch oder fehlt etwas?
zu meinem iobroker Problem: Gibt es hier noch Lösungsansätze oder liegt es an den fehlenden Updates?
-
@thomas-braun ok, das mit dem Mausschubsen leuchtet mir ein... ich werde versuchen das in Zukunft zu ändern um mich daran zu gewöhnen
ich bin halt wie viele verwindowsedzu den Updates: mache ich mit den Befehlen etwas falsch oder fehlt etwas?
zu meinem iobroker Problem: Gibt es hier noch Lösungsansätze oder liegt es an den fehlenden Updates?
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
zu meinem iobroker Problem: Gibt es hier noch Lösungsansätze oder liegt es an den fehlenden Updates?
Zumindest schaffst du mit den Updates und dem headless-Betrieb eine stabilere Basis.
-
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
zu meinem iobroker Problem: Gibt es hier noch Lösungsansätze oder liegt es an den fehlenden Updates?
Zumindest schaffst du mit den Updates und dem headless-Betrieb eine stabilere Basis.
-
@thomas-braun ich habe vermutlich dieses grafana key Problem bei den updates, werde mich erstmal darum kümmern
-
-
@thomas-braun ich habe das nach ihrer Anleitung abgearbeitet mit dem key, jetzt sind die Updates sauber durchgelaufen, waren einige...
iobroker läuft aber immer noch nicht
soll ich die Langfassung hier einfügen ? -
@thomas-braun
ich weiß der Desktop läuft noch, ich werde das ändern, wenn alles wieder stabil läuft======== Start marking the full check here ========= Skript v.2023-10-25 *** BASE SYSTEM *** Static hostname: raspberrypi 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.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 22:23:36 up 7:48, 2 users, load average: 1.76, 1.51, 1.47 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 22:23:36 CET Universal time: Wed 2023-12-27 21:23:36 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 render netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: true Desktop: LXDE-pi Terminal: x11 Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 1.0G 365M 65M 2.4G 2.6G Swap: 99M 0B 99M Total: 3.9G 1.0G 465M 3794 M total memory 1024 M used memory 1589 M active memory 1563 M inactive memory 368 M free memory 7 M buffer memory 2393 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 *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 59G 18G 39G 31% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 7.8M 1.9G 1% /dev/shm tmpfs tmpfs 759M 1.3M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 ext4 3.7T 2.8T 772G 79% /mount/toshiba_1 /dev/mmcblk0p1 vfat 253M 31M 222M 13% /boot tmpfs tmpfs 380M 28K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Dec 27 14:35:18 2023] 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=E4:5F:01:A8:66:23 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=33928f17-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Wed Dec 27 14:35:19 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Dec 27 14:35:19 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed Dec 27 14:35:22 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. [Wed Dec 27 14:35:24 2023] EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended [Wed Dec 27 14:35:25 2023] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236870 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236868 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236864 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236869 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236867 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236865 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): error count since last fsck: 2616 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): initial error at time 1679237384: ext4_lookup:1840: inode 232962 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): last error at time 1703684179: ext4_lookup:1839: inode 232962 Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=1678472k,nr_inodes=419618,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=29,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=777080k,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=388536k,nr_inodes=97134,mode=700,uid=1000,gid=1000 | `-/run/user/1000/gvfs gvfsd-fuse fuse.gvfsd-fus rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 |-/mount/toshiba_1 /dev/sda1 ext4 rw,relatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remoun Files in neuralgic directories: /var: 6.9G /var/ 5.2G /var/log 4.0G /var/log/journal/8c1e10bfe3864fdca0aaa920fec2e173 4.0G /var/log/journal 1.1G /var/lib Archived and active journals take up 3.9G in the file system. /opt/iobroker/backups: 3.2G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.8G /opt/iobroker/iobroker-data/ 153M /opt/iobroker/iobroker-data/files 62M /opt/iobroker/iobroker-data/history 52M /opt/iobroker/iobroker-data/files/javascript.admin 35M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 1.6G /opt/iobroker/iobroker-data/objects.jsonl 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map 9.1M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/2.bbf74d5f.chunk.js.map 8.9M /opt/iobroker/iobroker-data/files/echarts/static/js/2.3d2d025f.chunk.js.map 8.9M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/2.3d2d025f.chunk.js.map 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_Single_Serial_558E108164-if00 *** NodeJS-Installation *** /usr/bin/nodejs v16.20.2 /usr/bin/node v16.20.2 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 /usr/bin/corepack 0.17.0 nodejs: Installed: 16.20.2-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 100 /var/lib/dpkg/status 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 Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Core adapters versions js-controller: 4.0.23 admin: 6.12.0 javascript: 7.0.3 Adapters from github: 0 Adapter State No connection to databases possible ... Enabled adapters with bindings ioBroker-Repositories Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Installed ioBroker-Instances Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Objects and States Please stand by - This may take a while Objects: 1 States: 1 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://archive.raspbian.org/raspbian buster InRelease Hit:6 https://apt.grafana.com stable InRelease Get:7 https://deb.nodesource.com/node_16.x bullseye InRelease [4586 B] Hit:8 https://repos.influxdata.com/debian stable InRelease Hit:9 https://repos.influxdata.com/debian bullseye InRelease Hit:10 http://weewx.com/apt/python3 buster InRelease Fetched 4586 B in 5s (842 B/s) Reading package lists... Done N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'contrib/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'non-free/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' Pending Updates: 0 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process udp UNCONN 0 0 0.0.0.0:631 0.0.0.0:* users:(("cups-browsed",pid=735,fd=7)) udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("avahi-daemon",pid=440,fd=12)) udp UNCONN 0 0 0.0.0.0:34224 0.0.0.0:* users:(("avahi-daemon",pid=440,fd=14)) udp UNCONN 0 0 0.0.0.0:68 0.0.0.0:* users:(("dhcpcd",pid=508,fd=13)) udp UNCONN 0 0 *:546 *:* users:(("dhcpcd",pid=508,fd=16)) udp UNCONN 0 0 *:5353 *:* users:(("avahi-daemon",pid=440,fd=13)) udp UNCONN 0 0 *:39262 *:* users:(("avahi-daemon",pid=440,fd=15)) tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=757,fd=6),("nginx",pid=756,fd=6),("nginx",pid=755,fd=6),("nginx",pid=754,fd=6),("nginx",pid=753,fd=6)) tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=591,fd=7)) tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=646,fd=3)) tcp LISTEN 0 1024 0.0.0.0:2812 0.0.0.0:* users:(("monit",pid=566,fd=5)) tcp LISTEN 0 4096 127.0.0.1:8088 0.0.0.0:* users:(("influxd",pid=603,fd=3)) tcp LISTEN 0 80 127.0.0.1:3306 0.0.0.0:* users:(("mariadbd",pid=732,fd=21)) tcp LISTEN 0 5 0.0.0.0:5900 0.0.0.0:* users:(("vncserver-x11-c",pid=636,fd=12)) tcp LISTEN 0 511 [::]:80 [::]:* users:(("nginx",pid=757,fd=7),("nginx",pid=756,fd=7),("nginx",pid=755,fd=7),("nginx",pid=754,fd=7),("nginx",pid=753,fd=7)) tcp LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=646,fd=4)) tcp LISTEN 0 1024 [::]:2812 [::]:* users:(("monit",pid=566,fd=6)) tcp LISTEN 0 4096 *:3000 *:* users:(("grafana",pid=1238,fd=9)) tcp LISTEN 0 2 [::1]:3350 [::]:* users:(("xrdp-sesman",pid=641,fd=11)) tcp LISTEN 0 128 [::1]:631 [::]:* users:(("cupsd",pid=591,fd=6)) tcp LISTEN 0 2 *:3389 *:* users:(("xrdp",pid=733,fd=11)) tcp LISTEN 0 511 *:8080 *:* users:(("node /home/Shin",pid=1217,fd=21)) tcp LISTEN 0 4096 *:8086 *:* users:(("influxd",pid=603,fd=29)) tcp LISTEN 0 5 [::]:5900 [::]:* users:(("vncserver-x11-c",pid=636,fd=11)) *** Log File - Last 25 Lines *** 2023-12-27 22:24:52.282 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:24:52.283 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:24:52.284 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:25:22.310 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 22:25:22.324 - info: host.raspberrypi iobroker _restart 2023-12-27 22:25:27.732 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:25:27.738 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:25:27.739 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:25:27.740 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:25:57.766 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 22:25:57.783 - info: host.raspberrypi iobroker _restart 2023-12-27 22:26:03.868 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:03.880 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:03.882 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:03.884 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:26:06.035 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-12-27 22:26:10.857 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:10.868 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:10.869 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:10.871 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:26:13.043 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-12-27 22:26:17.742 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:17.752 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:17.754 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:17.756 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd============ Mark until here for C&P =============
-
@thomas-braun
ich weiß der Desktop läuft noch, ich werde das ändern, wenn alles wieder stabil läuft======== Start marking the full check here ========= Skript v.2023-10-25 *** BASE SYSTEM *** Static hostname: raspberrypi 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.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 22:23:36 up 7:48, 2 users, load average: 1.76, 1.51, 1.47 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 22:23:36 CET Universal time: Wed 2023-12-27 21:23:36 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 render netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: true Desktop: LXDE-pi Terminal: x11 Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 1.0G 365M 65M 2.4G 2.6G Swap: 99M 0B 99M Total: 3.9G 1.0G 465M 3794 M total memory 1024 M used memory 1589 M active memory 1563 M inactive memory 368 M free memory 7 M buffer memory 2393 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 *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 59G 18G 39G 31% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 7.8M 1.9G 1% /dev/shm tmpfs tmpfs 759M 1.3M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 ext4 3.7T 2.8T 772G 79% /mount/toshiba_1 /dev/mmcblk0p1 vfat 253M 31M 222M 13% /boot tmpfs tmpfs 380M 28K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Dec 27 14:35:18 2023] 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=E4:5F:01:A8:66:23 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=33928f17-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Wed Dec 27 14:35:19 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Dec 27 14:35:19 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed Dec 27 14:35:22 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. [Wed Dec 27 14:35:24 2023] EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended [Wed Dec 27 14:35:25 2023] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236870 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236868 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236864 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236869 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236867 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236865 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): error count since last fsck: 2616 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): initial error at time 1679237384: ext4_lookup:1840: inode 232962 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): last error at time 1703684179: ext4_lookup:1839: inode 232962 Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=1678472k,nr_inodes=419618,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=29,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=777080k,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=388536k,nr_inodes=97134,mode=700,uid=1000,gid=1000 | `-/run/user/1000/gvfs gvfsd-fuse fuse.gvfsd-fus rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 |-/mount/toshiba_1 /dev/sda1 ext4 rw,relatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remoun Files in neuralgic directories: /var: 6.9G /var/ 5.2G /var/log 4.0G /var/log/journal/8c1e10bfe3864fdca0aaa920fec2e173 4.0G /var/log/journal 1.1G /var/lib Archived and active journals take up 3.9G in the file system. /opt/iobroker/backups: 3.2G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.8G /opt/iobroker/iobroker-data/ 153M /opt/iobroker/iobroker-data/files 62M /opt/iobroker/iobroker-data/history 52M /opt/iobroker/iobroker-data/files/javascript.admin 35M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 1.6G /opt/iobroker/iobroker-data/objects.jsonl 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map 9.1M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/2.bbf74d5f.chunk.js.map 8.9M /opt/iobroker/iobroker-data/files/echarts/static/js/2.3d2d025f.chunk.js.map 8.9M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/2.3d2d025f.chunk.js.map 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_Single_Serial_558E108164-if00 *** NodeJS-Installation *** /usr/bin/nodejs v16.20.2 /usr/bin/node v16.20.2 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 /usr/bin/corepack 0.17.0 nodejs: Installed: 16.20.2-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 100 /var/lib/dpkg/status 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 Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Core adapters versions js-controller: 4.0.23 admin: 6.12.0 javascript: 7.0.3 Adapters from github: 0 Adapter State No connection to databases possible ... Enabled adapters with bindings ioBroker-Repositories Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Installed ioBroker-Instances Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Objects and States Please stand by - This may take a while Objects: 1 States: 1 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://archive.raspbian.org/raspbian buster InRelease Hit:6 https://apt.grafana.com stable InRelease Get:7 https://deb.nodesource.com/node_16.x bullseye InRelease [4586 B] Hit:8 https://repos.influxdata.com/debian stable InRelease Hit:9 https://repos.influxdata.com/debian bullseye InRelease Hit:10 http://weewx.com/apt/python3 buster InRelease Fetched 4586 B in 5s (842 B/s) Reading package lists... Done N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'contrib/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'non-free/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' Pending Updates: 0 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process udp UNCONN 0 0 0.0.0.0:631 0.0.0.0:* users:(("cups-browsed",pid=735,fd=7)) udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("avahi-daemon",pid=440,fd=12)) udp UNCONN 0 0 0.0.0.0:34224 0.0.0.0:* users:(("avahi-daemon",pid=440,fd=14)) udp UNCONN 0 0 0.0.0.0:68 0.0.0.0:* users:(("dhcpcd",pid=508,fd=13)) udp UNCONN 0 0 *:546 *:* users:(("dhcpcd",pid=508,fd=16)) udp UNCONN 0 0 *:5353 *:* users:(("avahi-daemon",pid=440,fd=13)) udp UNCONN 0 0 *:39262 *:* users:(("avahi-daemon",pid=440,fd=15)) tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=757,fd=6),("nginx",pid=756,fd=6),("nginx",pid=755,fd=6),("nginx",pid=754,fd=6),("nginx",pid=753,fd=6)) tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=591,fd=7)) tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=646,fd=3)) tcp LISTEN 0 1024 0.0.0.0:2812 0.0.0.0:* users:(("monit",pid=566,fd=5)) tcp LISTEN 0 4096 127.0.0.1:8088 0.0.0.0:* users:(("influxd",pid=603,fd=3)) tcp LISTEN 0 80 127.0.0.1:3306 0.0.0.0:* users:(("mariadbd",pid=732,fd=21)) tcp LISTEN 0 5 0.0.0.0:5900 0.0.0.0:* users:(("vncserver-x11-c",pid=636,fd=12)) tcp LISTEN 0 511 [::]:80 [::]:* users:(("nginx",pid=757,fd=7),("nginx",pid=756,fd=7),("nginx",pid=755,fd=7),("nginx",pid=754,fd=7),("nginx",pid=753,fd=7)) tcp LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=646,fd=4)) tcp LISTEN 0 1024 [::]:2812 [::]:* users:(("monit",pid=566,fd=6)) tcp LISTEN 0 4096 *:3000 *:* users:(("grafana",pid=1238,fd=9)) tcp LISTEN 0 2 [::1]:3350 [::]:* users:(("xrdp-sesman",pid=641,fd=11)) tcp LISTEN 0 128 [::1]:631 [::]:* users:(("cupsd",pid=591,fd=6)) tcp LISTEN 0 2 *:3389 *:* users:(("xrdp",pid=733,fd=11)) tcp LISTEN 0 511 *:8080 *:* users:(("node /home/Shin",pid=1217,fd=21)) tcp LISTEN 0 4096 *:8086 *:* users:(("influxd",pid=603,fd=29)) tcp LISTEN 0 5 [::]:5900 [::]:* users:(("vncserver-x11-c",pid=636,fd=11)) *** Log File - Last 25 Lines *** 2023-12-27 22:24:52.282 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:24:52.283 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:24:52.284 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:25:22.310 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 22:25:22.324 - info: host.raspberrypi iobroker _restart 2023-12-27 22:25:27.732 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:25:27.738 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:25:27.739 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:25:27.740 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:25:57.766 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 22:25:57.783 - info: host.raspberrypi iobroker _restart 2023-12-27 22:26:03.868 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:03.880 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:03.882 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:03.884 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:26:06.035 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-12-27 22:26:10.857 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:10.868 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:10.869 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:10.871 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:26:13.043 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-12-27 22:26:17.742 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:17.752 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:17.754 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:17.756 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd============ Mark until here for C&P =============
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
1.6G /opt/iobroker/iobroker-data/objects.jsonl
die json ist zu groß , deshalb geht es nicht
mache mal
iob stop iob fix sudo reboot -
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
1.6G /opt/iobroker/iobroker-data/objects.jsonl
die json ist zu groß , deshalb geht es nicht
mache mal
iob stop iob fix sudo reboot@glasfaser super klasse, es geht wieder, vielen Dank!
Kann mir noch jemand fürs Verständis erklären wie das passieren konnte (wie gesagt es gab einen Stromausfall) ? Und woher weiß ich dass die 1.6 GB zu groß sind ?
-
@thomas-braun
ich weiß der Desktop läuft noch, ich werde das ändern, wenn alles wieder stabil läuft======== Start marking the full check here ========= Skript v.2023-10-25 *** BASE SYSTEM *** Static hostname: raspberrypi 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.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 22:23:36 up 7:48, 2 users, load average: 1.76, 1.51, 1.47 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 22:23:36 CET Universal time: Wed 2023-12-27 21:23:36 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 render netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: true Desktop: LXDE-pi Terminal: x11 Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 1.0G 365M 65M 2.4G 2.6G Swap: 99M 0B 99M Total: 3.9G 1.0G 465M 3794 M total memory 1024 M used memory 1589 M active memory 1563 M inactive memory 368 M free memory 7 M buffer memory 2393 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 *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 59G 18G 39G 31% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 7.8M 1.9G 1% /dev/shm tmpfs tmpfs 759M 1.3M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 ext4 3.7T 2.8T 772G 79% /mount/toshiba_1 /dev/mmcblk0p1 vfat 253M 31M 222M 13% /boot tmpfs tmpfs 380M 28K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Dec 27 14:35:18 2023] 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=E4:5F:01:A8:66:23 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=33928f17-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Wed Dec 27 14:35:19 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Dec 27 14:35:19 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed Dec 27 14:35:22 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. [Wed Dec 27 14:35:24 2023] EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended [Wed Dec 27 14:35:25 2023] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236870 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236868 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236864 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236869 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236867 [Wed Dec 27 14:36:18 2023] EXT4-fs error (device sda1): ext4_lookup:1839: inode #232962: comm stat: deleted inode referenced: 236865 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): error count since last fsck: 2616 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): initial error at time 1679237384: ext4_lookup:1840: inode 232962 [Wed Dec 27 14:40:34 2023] EXT4-fs (sda1): last error at time 1703684179: ext4_lookup:1839: inode 232962 Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=1678472k,nr_inodes=419618,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=29,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=777080k,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=388536k,nr_inodes=97134,mode=700,uid=1000,gid=1000 | `-/run/user/1000/gvfs gvfsd-fuse fuse.gvfsd-fus rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 |-/mount/toshiba_1 /dev/sda1 ext4 rw,relatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remoun Files in neuralgic directories: /var: 6.9G /var/ 5.2G /var/log 4.0G /var/log/journal/8c1e10bfe3864fdca0aaa920fec2e173 4.0G /var/log/journal 1.1G /var/lib Archived and active journals take up 3.9G in the file system. /opt/iobroker/backups: 3.2G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.8G /opt/iobroker/iobroker-data/ 153M /opt/iobroker/iobroker-data/files 62M /opt/iobroker/iobroker-data/history 52M /opt/iobroker/iobroker-data/files/javascript.admin 35M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 1.6G /opt/iobroker/iobroker-data/objects.jsonl 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map 9.1M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/2.bbf74d5f.chunk.js.map 8.9M /opt/iobroker/iobroker-data/files/echarts/static/js/2.3d2d025f.chunk.js.map 8.9M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/2.3d2d025f.chunk.js.map 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_Single_Serial_558E108164-if00 *** NodeJS-Installation *** /usr/bin/nodejs v16.20.2 /usr/bin/node v16.20.2 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 /usr/bin/corepack 0.17.0 nodejs: Installed: 16.20.2-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 100 /var/lib/dpkg/status 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 Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Core adapters versions js-controller: 4.0.23 admin: 6.12.0 javascript: 7.0.3 Adapters from github: 0 Adapter State No connection to databases possible ... Enabled adapters with bindings ioBroker-Repositories Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Installed ioBroker-Instances Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Objects and States Please stand by - This may take a while Objects: 1 States: 1 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://archive.raspbian.org/raspbian buster InRelease Hit:6 https://apt.grafana.com stable InRelease Get:7 https://deb.nodesource.com/node_16.x bullseye InRelease [4586 B] Hit:8 https://repos.influxdata.com/debian stable InRelease Hit:9 https://repos.influxdata.com/debian bullseye InRelease Hit:10 http://weewx.com/apt/python3 buster InRelease Fetched 4586 B in 5s (842 B/s) Reading package lists... Done N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'contrib/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'non-free/binary-arm64/Packages' as repository 'https://archive.raspbian.org/raspbian buster InRelease' doesn't support architecture 'arm64' Pending Updates: 0 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process udp UNCONN 0 0 0.0.0.0:631 0.0.0.0:* users:(("cups-browsed",pid=735,fd=7)) udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("avahi-daemon",pid=440,fd=12)) udp UNCONN 0 0 0.0.0.0:34224 0.0.0.0:* users:(("avahi-daemon",pid=440,fd=14)) udp UNCONN 0 0 0.0.0.0:68 0.0.0.0:* users:(("dhcpcd",pid=508,fd=13)) udp UNCONN 0 0 *:546 *:* users:(("dhcpcd",pid=508,fd=16)) udp UNCONN 0 0 *:5353 *:* users:(("avahi-daemon",pid=440,fd=13)) udp UNCONN 0 0 *:39262 *:* users:(("avahi-daemon",pid=440,fd=15)) tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=757,fd=6),("nginx",pid=756,fd=6),("nginx",pid=755,fd=6),("nginx",pid=754,fd=6),("nginx",pid=753,fd=6)) tcp LISTEN 0 128 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=591,fd=7)) tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=646,fd=3)) tcp LISTEN 0 1024 0.0.0.0:2812 0.0.0.0:* users:(("monit",pid=566,fd=5)) tcp LISTEN 0 4096 127.0.0.1:8088 0.0.0.0:* users:(("influxd",pid=603,fd=3)) tcp LISTEN 0 80 127.0.0.1:3306 0.0.0.0:* users:(("mariadbd",pid=732,fd=21)) tcp LISTEN 0 5 0.0.0.0:5900 0.0.0.0:* users:(("vncserver-x11-c",pid=636,fd=12)) tcp LISTEN 0 511 [::]:80 [::]:* users:(("nginx",pid=757,fd=7),("nginx",pid=756,fd=7),("nginx",pid=755,fd=7),("nginx",pid=754,fd=7),("nginx",pid=753,fd=7)) tcp LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=646,fd=4)) tcp LISTEN 0 1024 [::]:2812 [::]:* users:(("monit",pid=566,fd=6)) tcp LISTEN 0 4096 *:3000 *:* users:(("grafana",pid=1238,fd=9)) tcp LISTEN 0 2 [::1]:3350 [::]:* users:(("xrdp-sesman",pid=641,fd=11)) tcp LISTEN 0 128 [::1]:631 [::]:* users:(("cupsd",pid=591,fd=6)) tcp LISTEN 0 2 *:3389 *:* users:(("xrdp",pid=733,fd=11)) tcp LISTEN 0 511 *:8080 *:* users:(("node /home/Shin",pid=1217,fd=21)) tcp LISTEN 0 4096 *:8086 *:* users:(("influxd",pid=603,fd=29)) tcp LISTEN 0 5 [::]:5900 [::]:* users:(("vncserver-x11-c",pid=636,fd=11)) *** Log File - Last 25 Lines *** 2023-12-27 22:24:52.282 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:24:52.283 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:24:52.284 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:25:22.310 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 22:25:22.324 - info: host.raspberrypi iobroker _restart 2023-12-27 22:25:27.732 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:25:27.738 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:25:27.739 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:25:27.740 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:25:57.766 - error: host.raspberrypi No connection to databases possible, restart 2023-12-27 22:25:57.783 - info: host.raspberrypi iobroker _restart 2023-12-27 22:26:03.868 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:03.880 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:03.882 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:03.884 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:26:06.035 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-12-27 22:26:10.857 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:10.868 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:10.869 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:10.871 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd 2023-12-27 22:26:13.043 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-12-27 22:26:17.742 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-12-27 22:26:17.752 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-27 22:26:17.754 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.2 2023-12-27 22:26:17.756 - info: host.raspberrypi ip addresses: 192.168.178.72 2003:de:a713:a200:9644:8a14:166b:382f fe80::aa74:964:1a9c:1acd============ Mark until here for C&P =============
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
wenn alles wieder stabil läuft
js-controller: 4.0.23
der ist aber schon sehr alt .. und auch vom letzten Stand "4.0.24" auch nicht aktuell
Neu ist JS 5
dazu aber erst ein Backup machen zur Sicherheit dann
iob stop iob update iob upgrade self iob start/usr/bin/nodejs v16.20.2
/usr/bin/node v16.20.2
/usr/bin/npm 8.19.4
/usr/bin/npx 8.19.4Auch sehr alt .
dazu :
iob nodejs-update -
@glasfaser super klasse, es geht wieder, vielen Dank!
Kann mir noch jemand fürs Verständis erklären wie das passieren konnte (wie gesagt es gab einen Stromausfall) ? Und woher weiß ich dass die 1.6 GB zu groß sind ?
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
Kann mir noch jemand fürs Verständis erklären wie das passieren konnte
Das liegt erstmal am Stromausfall von dir ... Daten wurden noch nicht weggeschrieben und du hast noch die alte 4.0.23 dort wurde es noch nicht damit abgefangen !
-
@obstbauer sagte in Keine Verbindung mehr zu iobroker:
diesen Fehler scheine ich zu haben:
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!@obstbauer sagte in Keine Verbindung mehr zu iobroker:
Und woher weiß ich dass die 1.6 GB zu groß sind ?Dazu gibt es einen Thread
siehe hier :
https://forum.iobroker.net/topic/53378/server-cannot-start-inmem-objects-on-port-9001@glasfaser super klasse, es geht wieder, vielen Dank!
Klar ...funktioniert es wieder ...
ein bekannter Fehler ( Stromausfall ) ;)
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden586
Online32.8k
Benutzer82.8k
Themen1.3m
Beiträge