iobroker startet nicht mehr - Server Cannot start inMem

wusa

@thomas-braun sagte in iobroker startet nicht mehr - Server Cannot start inMem:

sudo lsof /opt/iobroker/iobroker-data/objects.jsonl

Ich habe jetzt genau das selbe Problem wieder.
Führe ich den Befehl aus kommt folgende Ausgabe:

pi@iobroker:~ $ sudo lsof /opt/iobroker/iobroker-data/objects.jsonl
COMMAND    PID     USER   FD   TYPE DEVICE  SIZE/OFF   NODE NAME
iobroker. 1307 iobroker   19u   REG    8,2 300182523 391702 /opt/iobroker/iobroker-data/objects.jsonl

Warte ich kurz und führe den Befehl erneut aus:

pi@iobroker:~ $ sudo lsof /opt/iobroker/iobroker-data/objects.jsonl
COMMAND    PID     USER   FD   TYPE DEVICE  SIZE/OFF   NODE NAME
iobroker. 1341 iobroker   19u   REG    8,2 300182523 391702 /opt/iobroker/iobroker-data/objects.jsonl

Und nochmal nach kurzer Zeit:

pi@iobroker:~ $ sudo lsof /opt/iobroker/iobroker-data/objects.jsonl
COMMAND    PID     USER   FD   TYPE DEVICE  SIZE/OFF   NODE NAME
iobroker. 1385 iobroker   19u   REG    8,2 300182523 391702 /opt/iobroker/iobroker-data/objects.jsonl

Das ist doch nicht normal, dass sich die PID immer ändert?

Der ioBroker kommt übrigens nicht mehr hoch. Auch über die Weboberfläche nicht zu erreichen.

Thomas Braun

@wusa

sudo systemctl stop iobroker

wusa

@thomas-braun

Habe ich ausgeführt.
Ich habe mir jetzt auch nochmal die Ausgabe von

pi@iobroker:~ $ sudo lsof /opt/iobroker/iobroker-data/objects.jsonl

angesehen.
Hier kommt keine Ausgabe zurück.
Sollte somit gestoppt sein.

wusa

Hier noch die Ausgabe von

pi@iobroker:~ $ sudo systemctl status iobroker
● iobroker.service - ioBroker Server
   Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-08-03 10:45:58 CEST; 4min 52s ago
     Docs: http://iobroker.net
  Process: 1666 ExecStart=/usr/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobroker.js-controller/controller.js (code=exited, status=1/FAILURE)
 Main PID: 1666 (code=exited, status=1/FAILURE)

Aug 03 10:45:29 iobroker systemd[1]: Started ioBroker Server.
Aug 03 10:45:57 iobroker systemd[1]: Stopping ioBroker Server...
Aug 03 10:45:58 iobroker systemd[1]: iobroker.service: Main process exited, code=exited, status=1/FAILURE
Aug 03 10:45:58 iobroker systemd[1]: iobroker.service: Failed with result 'exit-code'.
Aug 03 10:45:58 iobroker systemd[1]: Stopped ioBroker Server.

Thomas Braun

@wusa

iobroker fix
sudo ln -s /usr/bin/node /usr/bin/nodejs
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs

wusa

@thomas-braun

pi@iobroker:~ $ iobroker fix
library: loaded
Library version=2022-06-15

==========================================================================

    Welcome to the ioBroker installation fixer!
    Script version: 2022-06-03

    You might need to enter your password a couple of times.

==========================================================================


==========================================================================
    Installing prerequisites (1/3)
==========================================================================

Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:2 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Hit:3 https://deb.nodesource.com/node_16.x buster InRelease
Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Get:5 http://archive.raspberrypi.org/debian buster/main armhf Packages [391 kB]
Fetched 13.4 MB in 16s (851 kB/s)
Reading package lists... Done
Installed gcc-c++

==========================================================================
    Checking ioBroker user and directory permissions (2/3)
==========================================================================

Created /etc/sudoers.d/iobroker
Fixing directory permissions...

==========================================================================
    Checking autostart (3/3)
==========================================================================

Enabling autostart...
Autostart enabled!

==========================================================================

    Your installation was fixed successfully
    Run iobroker start to start ioBroker again!

==========================================================================

pi@iobroker:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs
ln: failed to create symbolic link '/usr/bin/nodejs': File exists

pi@iobroker:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
armv7l
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.16.0
v16.16.0
8.11.0
pi
/home/pi
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_16.x buster InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
nodejs:
  Installed: 16.16.0-deb-1nodesource1
  Candidate: 16.16.0-deb-1nodesource1
  Version table:
 *** 16.16.0-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x buster/main armhf Packages
        100 /var/lib/dpkg/status
     10.24.0~dfsg-1~deb10u1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages

Soll ich wieder Starten?

Thomas Braun

@wusa

Ja, starte mal komplett durch. Also den pi sauber rebooten.

wusa

@thomas-braun

Selbes Spiel wieder.

pi@iobroker:~ $ sudo systemctl status iobroker
● iobroker.service - ioBroker Server
   Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2022-08-03 11:19:06 CEST; 35s ago
     Docs: http://iobroker.net
 Main PID: 546 (iobroker.js-con)
    Tasks: 18 (limit: 2059)
   CGroup: /system.slice/iobroker.service
           ├─546 iobroker.js-controller
           └─599 node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js _restart

Aug 03 11:19:06 iobroker systemd[1]: Started ioBroker Server.

pi@iobroker:~ $ sudo lsof /opt/iobroker/iobroker-data/objects.jsonl
COMMAND   PID     USER   FD   TYPE DEVICE  SIZE/OFF   NODE NAME
iobroker. 609 iobroker   19u   REG    8,2 300182523 391702 /opt/iobroker/iobroker-data/objects.jsonl

Kurz gewartet und dann diese Ausgabe:

pi@iobroker:~ $ sudo lsof /opt/iobroker/iobroker-data/objects.jsonl
COMMAND   PID     USER   FD   TYPE DEVICE  SIZE/OFF   NODE NAME
iobroker. 631 iobroker   19u   REG    8,2 300182523 391702 /opt/iobroker/iobroker-data/objects.jsonl

Weboberfläche ist auch nicht erreichbar.

Thomas Braun

@wusa

sudo systemctl stop iobroker
iobroker status
iobroker start

wusa

@thomas-braun

pi@iobroker:~ $ sudo systemctl stop iobroker
pi@iobroker:~ $ iobroker status
No connection to databases possible ...

wusa

@Thomas-Braun
Ich habe jetzt mal unter

/var/log/syslog

geschaut, was dort alles steht.

Aug  3 12:34:25 iobroker systemd[1]: iobroker.service: Main process exited, code=exited, status=1/FAILURE
Aug  3 12:34:25 iobroker systemd[1]: iobroker.service: Failed with result 'exit-code'.
Aug  3 12:34:28 iobroker systemd[1]: iobroker.service: Service RestartSec=3s expired, scheduling restart.
Aug  3 12:34:28 iobroker systemd[1]: iobroker.service: Scheduled restart job, restart counter is at 67.
Aug  3 12:34:28 iobroker systemd[1]: Stopped ioBroker Server.
Aug  3 12:34:28 iobroker systemd[1]: Started ioBroker Server.
Aug  3 12:35:03 iobroker systemd[1]: iobroker.service: Main process exited, code=exited, status=1/FAILURE
Aug  3 12:35:03 iobroker systemd[1]: iobroker.service: Failed with result 'exit-code'.
Aug  3 12:35:07 iobroker systemd[1]: iobroker.service: Service RestartSec=3s expired, scheduling restart.
Aug  3 12:35:07 iobroker systemd[1]: iobroker.service: Scheduled restart job, restart counter is at 68.
Aug  3 12:35:07 iobroker systemd[1]: Stopped ioBroker Server.

Und das geht die ganze Zeit so weiter.

wusa

pi@iobroker:~ $ sudo systemctl status iobroker
● iobroker.service - ioBroker Server
   Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 2022-08-03 13:39:42 CEST; 2s ago
     Docs: http://iobroker.net
  Process: 707 ExecStart=/usr/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobroker.js-controller/controller.js (code=exited, status=1/FAILURE)
 Main PID: 707 (code=exited, status=1/FAILURE)

Der Status ist kurz "active" und bricht sofort wieder ab.

Process: 707 ExecStart=/usr/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobroker.js-controller/controller.js (code=exited, status=1/FAILURE)

Ist hier der js-controller das Problem?

Community Forum

NEWS

iobroker startet nicht mehr - Server Cannot start inMem

Support us

518

32.9k

83.0k

1.3m