Server Cannot start inMem-objects on port 9001
-
iobroker is running on this host. Objects type: jsonl States type: jsonlEs läuft ja auch alles wieder normal :).
-
Eigentlich sollte das in regelmäßigen Intervallen automatisch komprimiert werden. Jedenfalls mit aktuellem js-controller.
-
Hallo zusammen,
ich habe seit heute dasselbe Problem. Habe auf meinen Raspberry nur iobroker laufen und das letzte Mal etwas vor ca. einem halben Jahr gemacht. Lief alles ohne Probleme.
Wollte eigentlich nur über die Weboberfläche für meine Automation etwas umstellen und gesehen das es neue Updates gibt.
Hab mich dann über Putty eingeloggt und „iobroker stop“ ausgeführt. Das war der Anfang vom Ende.Muss gestehen das ich ein absoluter Anfänger bin und schon über zwei Stunden den Forumseintrag hier lese ohne, dass ich ein Erfolg verzeichnen kann.
pi@raspberrypi4-iob:~ $ iobroker status
No connection to databases possible ...
pi@raspberrypi4-iob:~ $ iobroker stop
pi@raspberrypi4-iob:~ $ iobroker status
No connection to databases possible ...
pi@raspberrypi4-iob:~ $ iobroker start
pi@raspberrypi4-iob:~ $ iob start admin
No connection to databases possibleServer Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
pi@raspberrypi4-iob:~ $Iobroker Fix ohne erfolg.
Würde mich über Hilfe sehr freuen. -
======== Start marking the full check here ========= Skript v.2023-04-16 *** BASE SYSTEM *** Model : Raspberry Pi 4 Model B Rev 1.4 Architecture : armv7l Docker : false Virtualization : none Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" Systemuptime and Load: 18:30:28 up 1:21, 1 user, load average: 1.01, 1.08, 0.98 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=74.0'C volt=0.8700V *** Time and Time Zones *** Local time: Fri 2023-04-28 18:30:28 CEST Universal time: Fri 2023-04-28 16:30:28 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 7.9G 196M 6.3G 8.0M 1.4G 7.4G Swap: 99M 0B 99M Total: 8.0G 196M 6.4G 7898 M total memory 198 M used memory 1256 M active memory 258 M inactive memory 6253 M free memory 115 M buffer memory 1331 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 *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 59G 5.2G 51G 10% / devtmpfs devtmpfs 3.7G 0 3.7G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 3.9G 8.4M 3.9G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/mmcblk0p1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 790M 0 790M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Apr 28 17:09:06 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:BE:A6:4B vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=9fa8c098-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [Fri Apr 28 17:09:07 2023] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Fri Apr 28 17:09:07 2023] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Fri Apr 28 17:09:07 2023] EXT4-fs (mmcblk0p2): recovery complete [Fri Apr 28 17:09:07 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Fri Apr 28 17:09:07 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Fri Apr 28 17:09:09 2023] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 307M /var/ 109M /var/cache 104M /var/cache/apt 92M /var/lib 69M /var/lib/apt/lists Archived and active journals take up 8.0M in the file system. /opt/iobroker/backups: 312M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.7G /opt/iobroker/iobroker-data/ 147M /opt/iobroker/iobroker-data/files 97M /opt/iobroker/iobroker-data/backup-objects 42M /opt/iobroker/iobroker-data/files/vis 35M /opt/iobroker/iobroker-data/files/vis/widgets The five largest files in iobroker-data are: 1.5G /opt/iobroker/iobroker-data/objects.jsonl 16M /opt/iobroker/iobroker-data/files/vis.0/IMG/Grundriss 1 EG.jpg 12M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/2.ea6ad656.chunk.js.map 6.4M /opt/iobroker/iobroker-data/objects.json.migrated 6.4M /opt/iobroker/iobroker-data/objects.json.bak.migrated *** NodeJS-Installation *** /usr/bin/nodejs v16.15.1 /usr/bin/node v16.15.1 /usr/bin/npm 8.13.1 /usr/bin/npx 8.13.1 nodejs: Installed: 16.15.1-deb-1nodesource1 Candidate: 16.20.0-deb-1nodesource1 Version table: 16.20.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages *** 16.15.1-deb-1nodesource1 100 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected *** 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.1.9 javascript: 5.7.0 Adapters from github: 0 Adapter State Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 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://raspbian.raspberrypi.org/raspbian buster InRelease Hit:2 https://deb.nodesource.com/node_16.x buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Reading package lists... Pending Updates: 142 *** 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:22 0.0.0.0:* LISTEN 0 15294 560/sshd tcp6 0 0 :::22 :::* LISTEN 0 15296 560/sshd udp 0 0 0.0.0.0:34139 0.0.0.0:* 108 14057 387/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14989 552/dhcpcd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14055 387/avahi-daemon: r udp6 0 0 :::60976 :::* 108 14058 387/avahi-daemon: r udp6 0 0 :::5353 :::* 108 14056 387/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-04-28 18:30:10.471 - info: host.raspberrypi4-iob ip addresses: 192.168.188.44 fe80::4f78:66f9:8f3d:2aca 2023-04-28 18:30:40.494 - error: host.raspberrypi4-iob No connection to databases possible, restart 2023-04-28 18:30:40.509 - info: host.raspberrypi4-iob iobroker _restart 2023-04-28 18:30:46.435 - info: host.raspberrypi4-iob iobroker.js-controller version 4.0.23 js-controller starting 2023-04-28 18:30:46.443 - info: host.raspberrypi4-iob Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-04-28 18:30:46.444 - info: host.raspberrypi4-iob hostname: raspberrypi4-iob, node: v16.15.1 2023-04-28 18:30:46.445 - info: host.raspberrypi4-iob ip addresses: 192.168.188.44 fe80::4f78:66f9:8f3d:2aca 2023-04-28 18:31:16.477 - error: host.raspberrypi4-iob No connection to databases possible, restart 2023-04-28 18:31:16.499 - info: host.raspberrypi4-iob iobroker _restart 2023-04-28 18:31:22.410 - info: host.raspberrypi4-iob iobroker.js-controller version 4.0.23 js-controller starting 2023-04-28 18:31:22.417 - info: host.raspberrypi4-iob Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-04-28 18:31:22.418 - info: host.raspberrypi4-iob hostname: raspberrypi4-iob, node: v16.15.1 2023-04-28 18:31:22.419 - info: host.raspberrypi4-iob ip addresses: 192.168.188.44 fe80::4f78:66f9:8f3d:2aca 2023-04-28 18:31:52.441 - error: host.raspberrypi4-iob No connection to databases possible, restart 2023-04-28 18:31:52.455 - info: host.raspberrypi4-iob iobroker _restart 2023-04-28 18:31:58.463 - info: host.raspberrypi4-iob iobroker.js-controller version 4.0.23 js-controller starting 2023-04-28 18:31:58.470 - info: host.raspberrypi4-iob Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-04-28 18:31:58.471 - info: host.raspberrypi4-iob hostname: raspberrypi4-iob, node: v16.15.1 2023-04-28 18:31:58.472 - info: host.raspberrypi4-iob ip addresses: 192.168.188.44 fe80::4f78:66f9:8f3d:2aca 2023-04-28 18:32:28.520 - error: host.raspberrypi4-iob No connection to databases possible, restart 2023-04-28 18:32:28.534 - info: host.raspberrypi4-iob iobroker _restart 2023-04-28 18:32:34.447 - info: host.raspberrypi4-iob iobroker.js-controller version 4.0.23 js-controller starting 2023-04-28 18:32:34.454 - info: host.raspberrypi4-iob Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-04-28 18:32:34.456 - info: host.raspberrypi4-iob hostname: raspberrypi4-iob, node: v16.15.1 2023-04-28 18:32:34.457 - info: host.raspberrypi4-iob ip addresses: 192.168.188.44 fe80::4f78:66f9:8f3d:2aca ============ Mark until here for C&P ============= iob diag has finished.======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Raspbian GNU/Linux 10 (buster) Kernel: 5.10.63-v7l+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 142 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.15.1 /usr/bin/node v16.15.1 /usr/bin/npm 8.13.1 /usr/bin/npx 8.13.1 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.9G 78M 6.4G 8.0M 1.4G 7.6G Swap: 99M 0B 99M Total: 8.0G 78M 6.5G 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.1.9 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.5G /opt/iobroker/iobroker-data/objects.jsonl 6.4M /opt/iobroker/iobroker-data/objects.json.migrated 6.4M /opt/iobroker/iobroker-data/objects.json.bak.migrated 592K /opt/iobroker/iobroker-data/states.jsonl 500K /opt/iobroker/iobroker-data/states.json.migrated 500K /opt/iobroker/iobroker-data/states.json.bak.migrated 0 /opt/iobroker/iobroker-data/states.json.broken =================== END OF SUMMARY ====================Ergebnisse von
iob diagt -
-
Pending OS-Updates: 142Da würde ich zuerst Mal ran und das ganze System auf eine aktuelle Basis setzen. Dann das Bullseye-Release draufwerfen.
Die Kiste wird auch etwas zu warm
temp=74.0'CUnd die load ist mit 1 auch etwas hoch, der iobroker läuft ja nicht mal.
Was treibt da also die Auslastung so weit nach oben?Die Datenbank ist auch zu fett:
1.5G /opt/iobroker/iobroker-data/objects.jsonlHast du den Fixer schonmal ausgeführt?
-
@tungild iob fix ohne Erfolg? Zeig mal die Ausgaben bitte.
-
@apollon77 entschuldigt bitte meine späte Antwort.
Habe heute Nacht den Fixer nochmals laufen lassen, scheinbar diesmal mit Erfolg. Gestern hatte ich dies schon mehrfach ohne Erfolg versucht.
Die Weboberfläche läuft wieder und kann alles wie gewohnt benutzen. Wieso es nun auf einmal wieder geht, kann ich nicht sagen.pi@raspberrypi4-iob:~ $ iobroker stop pi@raspberrypi4-iob:~ $ iobroker fix library: loaded Library version=2022-12-09 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-04-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Holen:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15,0 kB] OK:2 http://archive.raspberrypi.org/debian buster InRelease OK:3 https://deb.nodesource.com/node_16.x buster InRelease Es wurden 15,0 kB in 1 s geholt (14,1 kB/s). Paketlisten werden gelesen... Fertig Installed gcc-c++ ========================================================================== 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/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberrypi4-iob:~ $ iobroker start pi@raspberrypi4-iob:~ $ iobroker start adminpi@raspberrypi4-iob:~ $ iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonl pi@raspberrypi4-iob:~ $Ich werde nun mal versuchen alles auf den neusten Stand zu bringen und hoffe das dann weiterhin alles läuft.
Danke euch schonmal für eure Beiträge.
Werde nochmals berichten. -
@tungild sagte in Server Cannot start inMem-objects on port 9001:
Wieso es nun auf einmal wieder geht, kann ich nicht sagen.
wahrscheinlich
@thomas-braun sagte in Server Cannot start inMem-objects on port 9001:
Die Datenbank ist auch zu fett:
diese hat der fixer komprimiert
-
So, hoffe ich habe nun alles auf dem neusten Stand. Aktuell funktioniert alles.
======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Raspbian GNU/Linux 10 (buster) Kernel: 5.10.63-v7l+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.9G 686M 4.3G 16M 2.9G 6.9G Swap: 99M 0B 99M Total: 8.0G 686M 4.4G Active iob-Instances: 11 Active repo(s): beta ioBroker Core: js-controller 4.0.24 admin 6.4.3 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi4-iob - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : raspberrypi4-iob - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 2058 States: 1693 Size of iob-Database: 9.7M /opt/iobroker/iobroker-data/objects.jsonl 6.4M /opt/iobroker/iobroker-data/objects.json.migrated 6.4M /opt/iobroker/iobroker-data/objects.json.bak.migrated 4.7M /opt/iobroker/iobroker-data/states.jsonl 500K /opt/iobroker/iobroker-data/states.json.migrated 500K /opt/iobroker/iobroker-data/states.json.bak.migrated 0 /opt/iobroker/iobroker-data/states.json.brokenBesten Dank nochmals
-
@tungild sagte in Server Cannot start inMem-objects on port 9001:
So, hoffe ich habe nun alles auf dem neusten Stand.
Active repo(s): beta
Dir ist schon bekannt , das du dein Repo auf BETA hast bzw. auch ein Beta Tester bist !?
EDIT :
ich denke mal unbewußt , denn du hast zuvor diese Versionen gehabt :
admin: 6.1.9 javascript: 5.7.0und
alles auf dem neusten Stand.
du hast noch Buster , Bullseye ist der aktuelle Stand !
-
Guten Abend,
Gleiches Problem auch bei mir..Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!Der Fix hat nix gebracht.
iob diag spuckt folgendes aus:======== Start marking the full check here ========= Skript v.2023-04-16 *** BASE SYSTEM *** Model : Raspberry Pi 3 Model B Rev 1.2 Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 23:12:09 up 1 min, 1 user, load average: 1.24, 0.46, 0.17 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=71.4'C volt=1.3438V *** Time and Time Zones *** Local time: Fri 2023-05-12 23:12:10 CEST Universal time: Fri 2023-05-12 21:12:10 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) 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 gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 909M 162M 156M 0.0K 590M 691M Swap: 99M 0B 99M Total: 1.0G 162M 256M 909 M total memory 162 M used memory 215 M active memory 458 M inactive memory 156 M free memory 19 M buffer memory 570 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 *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 15G 4.8G 8.9G 36% / devtmpfs devtmpfs 325M 0 325M 0% /dev tmpfs tmpfs 455M 0 455M 0% /dev/shm tmpfs tmpfs 182M 968K 181M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 91M 0 91M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri May 12 23:10:54 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=Composite-1:720x480@60i vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=0c797088-02 rootfstype=ext4 fsck.repair=yes rootwait [Fri May 12 23:10:57 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Fri May 12 23:10:57 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Fri May 12 23:11:00 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime,commit=600 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 993M /var/ 536M /var/log 521M /var/log/journal/556ce5c3a8d54c0c89d73703db3b1f8c 521M /var/log/journal 209M /var/cache Archived and active journals take up 520.1M in the file system. /opt/iobroker/backups: 33M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 704M /opt/iobroker/iobroker-data/ 169M /opt/iobroker/iobroker-data/files 64M /opt/iobroker/iobroker-data/backup-objects 51M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/telegram.admin The five largest files in iobroker-data are: 467M /opt/iobroker/iobroker-data/objects.jsonl 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 7.2M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js 6.9M /opt/iobroker/iobroker-data/files/telegram.admin/custom/static/js/vendors-node_modules_mui_icons-material_esm_index_js.8fdf8cb7.chunk.js.map 6.9M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.de0231c9.chunk.js.map *** NodeJS-Installation *** /usr/bin/nodejs v16.20.0 /usr/bin/node v16.20.0 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 nodejs: Installed: 16.20.0-deb-1nodesource1 Candidate: 16.20.0-deb-1nodesource1 Version table: *** 16.20.0-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://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected *** 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.3.5 javascript: 6.1.4 Adapters from github: 1 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://deb.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease Reading package lists... Pending Updates: 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 0.0.0.0:22 0.0.0.0:* LISTEN 0 14495 523/sshd: /usr/sbin tcp6 0 0 :::22 :::* LISTEN 0 14497 523/sshd: /usr/sbin udp 0 0 0.0.0.0:68 0.0.0.0:* 0 1794 623/dhcpcd udp 0 0 0.0.0.0:51820 0.0.0.0:* 0 1886 - udp 0 0 0.0.0.0:41124 0.0.0.0:* 108 14448 368/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14446 368/avahi-daemon: r udp6 0 0 :::51820 :::* 0 1887 - udp6 0 0 :::5353 :::* 108 14447 368/avahi-daemon: r udp6 0 0 :::49432 :::* 108 14449 368/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-05-12 23:14:20.573 - info: host.raspberrypi ip addresses: 192.168.30.6 fe80::6b2f:cbb4:2470:70a3 10.110.183.1 2023-05-12 23:14:50.621 - error: host.raspberrypi No connection to databases possible, restart 2023-05-12 23:14:50.656 - info: host.raspberrypi iobroker _restart 2023-05-12 23:14:57.929 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-05-12 23:14:57.944 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-12 23:14:57.946 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.0 2023-05-12 23:14:57.948 - info: host.raspberrypi ip addresses: 192.168.30.6 fe80::6b2f:cbb4:2470:70a3 10.110.183.1 2023-05-12 23:15:27.989 - error: host.raspberrypi No connection to databases possible, restart 2023-05-12 23:15:28.019 - info: host.raspberrypi iobroker _restart 2023-05-12 23:15:35.553 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-05-12 23:15:35.571 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-12 23:15:35.574 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.0 2023-05-12 23:15:35.577 - info: host.raspberrypi ip addresses: 192.168.30.6 fe80::6b2f:cbb4:2470:70a3 10.110.183.1 2023-05-12 23:15:37.722 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-05-12 23:15:44.388 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-05-12 23:15:44.405 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-12 23:15:44.408 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.0 2023-05-12 23:15:44.411 - info: host.raspberrypi ip addresses: 192.168.30.6 fe80::6b2f:cbb4:2470:70a3 10.110.183.1 2023-05-12 23:15:46.561 - error: host.raspberrypi-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-05-12 23:15:53.085 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-05-12 23:15:53.101 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-12 23:15:53.103 - info: host.raspberrypi hostname: raspberrypi, node: v16.20.0 2023-05-12 23:15:53.106 - info: host.raspberrypi ip addresses: 192.168.30.6 fe80::6b2f:cbb4:2470:70a3 10.110.183.1 2023-05-12 23:16:23.156 - error: host.raspberrypi No connection to databases possible, restart 2023-05-12 23:16:23.213 - info: host.raspberrypi iobroker _restart ============ Mark until here for C&P ============= iob diag has finished. Press any key for a summaryWoran kanns liegen?
-
@uncleb Und "iob fix" hat echt nichts geholfen? Bitte versuch nochmal und poste noch die Ausgabe von fix und diag danach. Wenn dein "Objects.jsonl" so gross bleibt hast Du dir einiges an Objekten angesammelt
-
Hallo zusammen,
ich habe den gleichen Fehler. Zuerst lief alles wie gewünscht. Doch nach einiger Zeit (Monate? Hab es nicht konstant geprüft) konnte ich nicht mehr auf das Webinterface von iobroker zugreifen. Jetzt untersuche ich es genauer und bekomme bei "iob status" den Fehler:
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!Nach "iob fix" und "reboot" funktioniert es immer noch nicht
Die "iob diag" gibt folgendes aus:
======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Raspbian GNU/Linux 11 (bullseye) Kernel: 5.15.68-v7+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 105 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.17.0 /usr/bin/node v16.17.0 /usr/bin/npm 8.15.0 /usr/bin/npx 8.15.0 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 922M 234M 74M 0.0K 613M 632M Swap: 99M 1.0M 98M Total: 1.0G 235M 173M 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.2.22 ioBroker Status: No connection to databases possible ... Status admin and web instance: Objects: 1 States: 1 Size of iob-Database: 628M /opt/iobroker/iobroker-data/objects.jsonl 88K /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Jemand eine Idee was ich noch machen kann? Wollte nicht wirklich den ganzen Rasperry neu aufsetzen.
Ich dachte erst durch mein dauerndest Loggen von Messwerten in meiner HomeAutomation wäre der Speicher vollgelaufen. Das scheint aber nicht zu sein:
df Filesystem 1K-blocks Used Available Use% Mounted on /dev/root 14563544 5695448 8243064 41% / devtmpfs 340548 0 340548 0% /dev tmpfs 472132 0 472132 0% /dev/shm tmpfs 188856 988 187868 1% /run tmpfs 5120 4 5116 1% /run/lock /dev/mmcblk0p1 261108 50962 210146 20% /boo -
@bot1000 sagte in Server Cannot start inMem-objects on port 9001:
eine Idee was ich noch machen kann?
-
@bot1000 Die Ausgabe von iob fix würde mich echt interessieren bei so einem großen objects file ... lass nochmal fixlaufen und schon ob das kleiner wird.
-
Pending OS-Updates: 105 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.17.0System aktuell halten.
Und was ist /boo für ein mountpunkt?
-
@thomas-braun
System aktualisiert -> Fehler ist gleichboo hatte ich abgeschnittenb es ist "boot"
-
@crunchip
Timeout beide auf 30000 gesetzt. Immer noch der gleiche Fehler -
@bot1000 sagte in Server Cannot start inMem-objects on port 9001:
System aktualisiert -> Fehler ist gleich
keine Nacherzählungen sonder auch jetzt wieder zeigen:
iob diag
