Can not start inMem-objects on port 9001

Thomas Braun

Den Backitup-Adapter kann man auf alle möglichen Medien schreiben lassen.
SMB, NFS, GoogleDrive usw...

systemctl status iobroker.service

sagt?

NFTVirus

@thomas-braun

● iobroker.service - ioBroker Server
     Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2022-11-01 13:23:57 GMT; 16s ago
       Docs: http://iobroker.net
   Main PID: 29763 (iobroker.js-con)
      Tasks: 11 (limit: 1598)
        CPU: 20.004s
     CGroup: /system.slice/iobroker.service
             └─29763 iobroker.js-controller

Nov 01 13:23:57 raspberrypi systemd[1]: Started ioBroker Server.

Thomas Braun

@nftvirus

sudo systemctl stop iobroker.service
iobroker status

NFTVirus

@thomas-braun

No connection to databases possible ...

Thomas Braun

@nftvirus

Bitte immer vollständige Ein- wie Ausgaben.
Ich kann nicht erkennen auf welches Kommando das jetzt die Rückgabe ist.

NFTVirus

@thomas-braun sorry war der iob status:

pi@raspberrypi:/opt/iobroker $ sudo systemctl stop iobroker.service
pi@raspberrypi:/opt/iobroker $ iobroker status
No connection to databases possible ...

Thomas Braun

@nftvirus

systemctl status iobroker.service

NFTVirus

@thomas-braun

pi@raspberrypi:/opt/iobroker $ systemctl status iobroker.service
● iobroker.service - ioBroker Server
     Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)
     Active: inactive (dead) (Result: exit-code) since Tue 2022-11-01 13:25:46 GMT; 6min ago
       Docs: http://iobroker.net
    Process: 30534 ExecStart=/usr/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobroker.js-controller/controller.js (code=exited, status=1/FAILURE)
   Main PID: 30534 (code=exited, status=1/FAILURE)
        CPU: 41.915s

Nov 01 13:25:44 raspberrypi systemd[1]: iobroker.service: Consumed 41.915s CPU time.
Nov 01 13:25:46 raspberrypi systemd[1]: Stopped ioBroker Server.
Nov 01 13:25:46 raspberrypi systemd[1]: iobroker.service: Consumed 41.915s CPU time.

Thomas Braun

@nftvirus

sudo systemctl mask iobroker.service
sudo apt update

NFTVirus

@thomas-braun

pi@raspberrypi:/opt/iobroker $ sudo systemctl mask iobroker.service
Created symlink /etc/systemd/system/iobroker.service → /dev/null.
pi@raspberrypi:/opt/iobroker $ sudo apt update
Hit:1 http://phoscon.de/apt/deconz bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
90 packages can be upgraded. Run 'apt list --upgradable' to see them.
pi@raspberrypi:/opt/iobroker $

Thomas Braun

@nftvirus sagte in Can not start inMem-objects on port 9001:

90 packages can be upgraded.

Neben dem Backup auch regelmäßiger das System auf Stand halten!!

sudo apt full-upgrade
sudo reboot

Wenn das System wieder auf die Beine gekommen ist dürfte der

iobroker status

'nicht laufend' ausgeben.
Dann mit

iobroker start

nachhelfen.

Wenn das funktionieren sollte die Maske wieder abnehmen:

sudo systemctl unmask iobroker.service

NFTVirus

@thomas-braun Vielen Dank für die ganze Unterstützung!!! Ich update jetzt noch alles und gebe dann nochmal kurz Rückmeldung ob wieder alles läuft.

NFTVirus

@thomas-braun Leider scheint es nicht geholfen zu haben:


pi@raspberrypi:~ $ iob status
No connection to databases possible ...
pi@raspberrypi:~ $ iobroker start
Failed to start iobroker.service: Unit iobroker.service is masked.
pi@raspberrypi:~ $ iobroker status
No connection to databases possible ...
pi@raspberrypi:~ $ sudo systemctl unmask iobroker.service
Removed /etc/systemd/system/iobroker.service.
pi@raspberrypi:~ $ iobroker start
pi@raspberrypi:~ $ iobroker status
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iob                                                 roker/iobroker-data/objects.jsonl"!
pi@raspberrypi:~ $

NFTVirus

Leider konnte ich es bisher nicht reparieren. Nun wollte ich ein älteres Backup nutzen und bekomme leider wieder nur no connection to databases possible..... Hat jemand noch eine Idee wie ich um ein komplettes Neuaufsetzen herum komme?


pi@raspberrypi:~ $ iobroker stop
pi@raspberrypi:~ $ iobroker restore 0
No connection to databases possible ...
pi@raspberrypi:~ $

Glasfaser

@nftvirus sagte in Can not start inMem-objects on port 9001:

iobroker. 26626 iobroker 19u REG 179,2 501587560 136879 /opt/iobroker/iobroker-data/objects.jsonl

kannst du mal bitte es aktuell zeigen , denn so sieht deine Datei riesig aus

du -sh  /opt/iobroker/iobroker-data/objects.jsonl

und

du -sh  /opt/iobroker/iobroker-data/backup-objects/*objects*

NFTVirus

@glasfaser

pi@raspberrypi:/opt/iobroker/iobroker-data $ du -sh  /opt/iobroker/iobroker-data/objects.jsonl
479M    /opt/iobroker/iobroker-data/objects.jsonl
pi@raspberrypi:/opt/iobroker/iobroker-data $ du -sh  /opt/iobroker/iobroker-data/backup-objects/*objects*
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-27_21-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-27_23-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_01-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_03-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_05-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_07-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_09-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_11-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_13-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_15-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_17-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_19-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_21-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-28_23-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_01-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_03-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_05-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_07-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_09-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_11-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_13-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_15-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_17-47_objects.jsonl.gz
1.7M    /opt/iobroker/iobroker-data/backup-objects/2022-10-29_19-47_objects.jsonl.gz
pi@raspberrypi:/opt/iobroker/iobroker-data $

Glasfaser

@nftvirus

Du kannst mal ein Backup versuchen

iobroker stop

cd /opt/iobroker/iobroker-data/
mv objects.jsonl objects.jsonl.old

cd backup-objects/
gunzip -ck 2022-10-29_19-47_objects.jsonl.gz > /opt/iobroker/iobroker-data/objects.jsonl

iobroker start

EDIT

NFTVirus

@glasfaser da bekomme ich wieder einen Fehler:

pi@raspberrypi:/opt/iobroker/iobroker-data $ iobroker stop
pi@raspberrypi:/opt/iobroker/iobroker-data $ cd /opt/iobroker/iobroker-data/
pi@raspberrypi:/opt/iobroker/iobroker-data $ mv objects.json objects.jsonl.old
mv: cannot stat 'objects.json': No such file or directory
pi@raspberrypi:/opt/iobroker/iobroker-data $

Glasfaser

@nftvirus

ja habe EDIT gemacht .... siehe oben

NFTVirus

@glasfaser Hey super VIELEN DANK!!! Es läuft wieder hat mir wirklich super geholfen.

Community Forum

NEWS

Can not start inMem-objects on port 9001

Support us

261

32.8k

82.9k

1.3m