Server Cannot start inMem-objects on port 9001
-
Bin jetzt mal hoch auf v16
woehrer@iobrokerifa:/opt/iobroker$ node -v v16.19.0 woehrer@iobrokerifa:/opt/iobroker$ npm -v 8.19.3 woehrer@iobrokerifa:/opt/iobroker$ iobroker fix library: loaded Library version=2022-12-09 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2022-12-09 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== OK:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease Holen:2 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] OK:3 https://deb.nodesource.com/node_16.x jammy InRelease Holen:4 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease [99,8 kB] Holen:5 http://de.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Es wurden 324 kB in 1 s geholt (576 kB/s). Paketlisten werden gelesen… Fertig Installed gcc-c++ ========================================================================== Checking ioBroker user and directory permissions (2/4) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Database maintenance (3/4) ========================================================================== 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 (4/4) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Bekomme immernoch die Fehlermeldung und der admin Adapter startet weiterhin nicht. Alles andere scheint aber zu laufen
-
-
@woehrer sagte in Server Cannot start inMem-objects on port 9001:
und der admin Adapter startet weiterhin nicht
iob logs --watchiob list instances -
======================= SUMMARY ======================= v.2022-12-13 Operatingsystem: Ubuntu 22.04.1 LTS Installation: microsoft Timezone: Europe/Berlin User-ID: 1000 X-Server: false Pending OS-Updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.19.0 /usr/bin/node v16.19.0 /usr/bin/npm 8.19.3 ioBroker Core: js-controller 4.0.23 admin 6.3.3 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Pending iob updates: 2 Active repo(s): stable Objects: 6726 States: 6193 Size of iob-Database: 7.5M /opt/iobroker/iobroker-data/objects.jsonl 4.7M /opt/iobroker/iobroker-data/objects.json.migrated 4.7M /opt/iobroker/iobroker-data/objects.json.bak.migrated 5.0M /opt/iobroker/iobroker-data/states.jsonl 1.2M /opt/iobroker/iobroker-data/states.json.migrated 1.2M /opt/iobroker/iobroker-data/states.json.bak.migrated ====================== END OF SUMMARY ==================2022-12-22 09:47:26.773 - info: host.iobrokerifa instance system.adapter.admin.0 started with pid 3788 2022-12-22 09:47:26.773 - info: host.iobrokerifa instance system.adapter.admin.0 started with pid 3788 2022-12-22 09:47:27.787 - info: admin.0 (3788) starting. Version 6.3.3 in /opt/iobroker/node_modules/iobroker.admin, node: v16.19.0, js-controller: 4.0.23 2022-12-22 09:47:27.814 - info: admin.0 (3788) requesting all states 2022-12-22 09:47:27.816 - info: admin.0 (3788) requesting all objects 2022-12-22 09:47:27.956 - warn: admin.0 (3788) Cannot check node.js versions: Error: unexpected end of file 2022-12-22 09:47:28.326 - info: admin.0 (3788) received all objects 2022-12-22 09:47:28.438 - info: admin.0 (3788) Request actual repository... 2022-12-22 09:47:28.523 - info: admin.0 (3788) http server listening on port 8081 2022-12-22 09:47:28.523 - info: admin.0 (3788) Use link "http://localhost:8081" to configure. 2022-12-22 09:47:28.527 - info: admin.0 (3788) socket.io server listening on port 8081 2022-12-22 09:47:28.539 - error: admin.0 (3788) uncaught exception: Cannot read properties of null (reading '_acl') 2022-12-22 09:47:28.539 - error: admin.0 (3788) TypeError: Cannot read properties of null (reading '_acl') at SocketCommandsAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:288:117) at SocketAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketAdmin.js:181:23) at initSocket (/opt/iobroker/node_modules/iobroker.admin/main.js:499:12) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/web.js:1048:29) at processImmediate (node:internal/timers:468:21) 2022-12-22 09:47:28.540 - error: admin.0 (3788) Cannot read properties of null (reading '_acl') 2022-12-22 09:47:28.556 - info: admin.0 (3788) terminating http server on port 8081 2022-12-22 09:47:28.560 - info: admin.0 (3788) terminating 2022-12-22 09:47:28.561 - warn: admin.0 (3788) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-12-22 09:47:28.779 - info: host.iobrokerifa Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: TypeError: Cannot read properties of null (reading '_acl') 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at SocketCommandsAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:288:117) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at SocketAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketAdmin.js:181:23) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at initSocket (/opt/iobroker/node_modules/iobroker.admin/main.js:499:12) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/web.js:1048:29) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at processImmediate (node:internal/timers:468:21) 2022-12-22 09:47:28.814 - error: host.iobrokerifa instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2022-12-22 09:47:28.814 - info: host.iobrokerifa Restart adapter system.adapter.admin.0 because enabled 2022-12-22 09:47:27.787 - info: admin.0 (3788) starting. Version 6.3.3 in /opt/iobroker/node_modules/iobroker.admin, node: v16.19.0, js-controller: 4.0.23 2022-12-22 09:47:27.814 - info: admin.0 (3788) requesting all states 2022-12-22 09:47:27.816 - info: admin.0 (3788) requesting all objects 2022-12-22 09:47:27.956 - warn: admin.0 (3788) Cannot check node.js versions: Error: unexpected end of file 2022-12-22 09:47:28.326 - info: admin.0 (3788) received all objects 2022-12-22 09:47:28.438 - info: admin.0 (3788) Request actual repository... 2022-12-22 09:47:28.523 - info: admin.0 (3788) http server listening on port 8081 2022-12-22 09:47:28.523 - info: admin.0 (3788) Use link "http://localhost:8081" to configure. 2022-12-22 09:47:28.527 - info: admin.0 (3788) socket.io server listening on port 8081 2022-12-22 09:47:28.539 - error: admin.0 (3788) uncaught exception: Cannot read properties of null (reading '_acl') 2022-12-22 09:47:28.539 - error: admin.0 (3788) TypeError: Cannot read properties of null (reading '_acl') at SocketCommandsAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:288:117) at SocketAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketAdmin.js:181:23) at initSocket (/opt/iobroker/node_modules/iobroker.admin/main.js:499:12) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/web.js:1048:29) at processImmediate (node:internal/timers:468:21) 2022-12-22 09:47:28.540 - error: admin.0 (3788) Cannot read properties of null (reading '_acl') 2022-12-22 09:47:28.556 - info: admin.0 (3788) terminating http server on port 8081 2022-12-22 09:47:28.560 - info: admin.0 (3788) terminating 2022-12-22 09:47:28.561 - warn: admin.0 (3788) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-12-22 09:47:28.779 - info: host.iobrokerifa Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: TypeError: Cannot read properties of null (reading '_acl') 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at SocketCommandsAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketCommands.js:288:117) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at SocketAdmin.subscribe (/opt/iobroker/node_modules/@iobroker/socket-classes/lib/socketAdmin.js:181:23) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at initSocket (/opt/iobroker/node_modules/iobroker.admin/main.js:499:12) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.admin/lib/web.js:1048:29) 2022-12-22 09:47:28.814 - error: host.iobrokerifa Caught by controller[0]: at processImmediate (node:internal/timers:468:21) 2022-12-22 09:47:28.814 - error: host.iobrokerifa instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2022-12-22 09:47:28.814 - info: host.iobrokerifa Restart adapter system.adapter.admin.0 because enabled -
Das ist WSL2 oder sowas?
-
@thomas-braun
Das ist eine virtuelle Maschine in der Ubuntu 22 läuft -
-
@woehrer selbiges ist auch hier
https://forum.iobroker.net/post/914523 -
@woehrer Admin 6.3.5 installieren!
-
Bei mir ist ein ähnliches Problem aufgetreten wie bei bischemer am 14. März 2022 und bei offensichtlich mehreren anderen.
Ich habe den RPI mit sudo shutdown -h 0 runtergefahren, die Stromversorgung abgeklemmt und mit Win32DiskImager die SD auf eine Backup Platte kopiert.
Nach dem erneuten Einlegen der SD und Anlegen der Versorgungsspannung startet der RPI und auch der ioBroker, der Zugriff über das Web Interface und Vis ist nicht mehr möglich.
Den gleichen Effekt hatte ich schon vor einigen Wochen, ich habe mich damit beholfen, dass ich mit einem früheren Backup alle zwischenzeitlichen Änderungen nachgezogen habe (was man einmal machen kann, was aber keine Dauerlösung ist).
Da der Effekt m.E. entweder mit dem Shutdown oder dem Abklemmen der Versorgung zu tun hat, kann dieses Problem immer wieder auftauchen, sei es bei einem regulären Backup oder bei einem Spannungsausfall im Versorgungsnetz.
Ich habe alles hier Geschriebene gelesen und nachvollzogen aber keine Lösung für mich gefunden!Angefügt einige Infos zu meinem Problem:
pi@raspberrypi:~ $ iob info Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2023-01-02 19:09:42.694 - error: host.raspberrypi No connection to databases possible, restart 2023-01-02 19:09:42.748 - info: host.raspberrypi iobroker _restart 2023-01-02 19:09:48.841 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting 2023-01-02 19:09:48.862 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-01-02 19:09:48.865 - info: host.raspberrypi hostname: raspberrypi, node: v14.19.1 2023-01-02 19:09:48.867 - info: host.raspberrypi ip addresses: 192.168.178.43 2003:ea:f10:b800:e3c1:cab5:4a9b:7a32 fe80::78fb:de3d:17ae:be62 2023-01-02 19:10:18.939 - error: host.raspberrypi No connection to databases possible, restartpi@raspberrypi:~ $ iob info Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!```pi@raspberrypi:/opt/iobroker/iobroker-data $ ls -l insgesamt 529504 drwxrwxrwx+ 2 iobroker iobroker 4096 Mai 2 2022 backitup drwxrwxrwx+ 2 iobroker iobroker 4096 Jan 2 09:26 backup-objects drwxrwxrwx+ 21 iobroker iobroker 4096 Nov 26 11:59 files drwxrwxrwx+ 185 iobroker iobroker 12288 Jan 2 00:02 history -rw-rwxrw-+ 1 iobroker iobroker 4715 Mai 2 2022 iobroker.json -rw-rw-rw-+ 1 iobroker iobroker 3 Jan 2 11:11 notifications.json -rw-rw-rw-+ 1 iobroker iobroker 3715730 Mai 2 2022 objects.json.bak.migrated -rw-rw-rw-+ 1 iobroker iobroker 524134421 Jan 2 10:52 objects.jsonl drwxrwxrwx+ 2 iobroker iobroker 4096 Jan 2 19:44 objects.jsonl.lock -rw-rw-rw-+ 1 iobroker iobroker 3718224 Mai 2 2022 objects.json.migrated -rw-rw-rw-+ 1 iobroker iobroker 442833 Mai 2 2022 states.json.bak.migrated -rw-rw-rw-+ 1 iobroker iobroker 9691615 Jan 2 11:11 states.jsonl -rw-rw-rw-+ 1 iobroker iobroker 442977 Mai 2 2022 states.json.migrated pi@raspberrypi:/opt/iobroker/iobroker-data $ -
@karl-1 Dann fang doch mal mit "iob fix" an ... danach sollte deine objects.jsonl kleiner sein ... gehts dann besser?
-
@apollon77 iob fix ändert nichts an der Größe der Daten!
iob fix wird innerhalb kürzester Zeit beendet. Kann es sein, dass es überhaupt nicht läuft? -
@karl-1 sagte in Server Cannot start inMem-objects on port 9001:
iob fix wird innerhalb kürzester Zeit beendet.
Mit welchen Meldungen?
-
@karl-1 sagte in Server Cannot start inMem-objects on port 9001:
iob fix wird innerhalb kürzester Zeit beendet. Kann es sein, dass es überhaupt nicht läuft?
Das gibt an sich eeeiniges aus .... Alternativ lass mal
curl -sLf https://iobroker.net/fix.sh | bash -laufen -
@apollon77 sagte in Server Cannot start inMem-objects on port 9001:
curl -sLf https://iobroker.net/fix.sh | bash -
Da scheint nichts zu passieren!
-
@thomas-braun Es gibt keine Meldungen!
-
@karl-1 Was sagt "curl https://iobroker.net/fix.sh"?
-
pi@raspberrypi:/ $ curl https://iobroker.net/fix.sh curl: (60) SSL certificate problem: certificate has expired More details here: https://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. -
@karl-1 ist bei dir alles aktuell. Auf dem
System? Alle Updates eingespielt? Wenn ja mach bei dem Curl ein „k“ bei den Parametern dazu. Aber warum
Du das bekommst weiß ich nicht weil s das as Zertifikat an sich passt. Sieht mit eher wie fehlende Systemupdates aus -
======================= SUMMARY ======================= v.2022-12-31 Operatingsystem: Raspbian GNU/Linux 9.13 (stretch) Installation: Native Timezone: Europe/Berlin User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Nodejs-Installation: /usr/bin/nodejs v14.21.1 /usr/bin/node v14.21.1 /usr/bin/npm 6.14.17 ioBroker Core: js-controller 4.0.23 admin 6.3.5 ioBroker Status: Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.j sonl"! Status admin: Pending iob updates: 0 No connection to databases possible ... Objects: 1 States: 1 Size of iob-Database: 500M /opt/iobroker/iobroker-data/objects.jsonl 3.6M /opt/iobroker/iobroker-data/objects.json.migrated 3.6M /opt/iobroker/iobroker-data/objects.json.bak.migrated 564K /opt/iobroker/iobroker-data/states.jsonl 436K /opt/iobroker/iobroker-data/states.json.migrated 436K /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ====================
