iobroker startet nicht mehr - Server Cannot start inMem

Thomas Braun

Hau den tot:

sudo pkill -u iobroker

wusa

@thomas-braun

Sorry für die späte Rückmeldung.
Ich habe deinen letzten Befehl gestern leider nicht mehr ausgeführt.

Gestern Abend, nachdem eine ganze Zeit vergangen ist, lief dann iobroker wieder.

Allerdings sind jetzt 2 Dinge komisch.
Mein iot und Google Home verbinden sich nicht mehr. Fehler bei der Verbindung mit iobroker.

Und wegen dem Update auf Influx 3.
Habe ich jetzt 2 unterschiedliche Stände.

Einmal in der Adapter Übersicht wird 3.1.7 angezeigt:

Bei den Instanzen wird allerdings 2.6.3 angezeigt.

Kann man das gerade ziehen, oder sollte ich ein Backup versuchen einzuspielen?

Thomas Braun

@wusa

Schau in der Konsole

iobroker update -i
iobroker list adapters
iobroker list instances

wusa

@thomas-braun

pi@iobroker:~ $ iobroker update -i
Used repository: stable
Adapter    "admin"        : 5.3.8    , installed 5.3.8
Adapter    "backitup"     : 2.4.9    , installed 2.4.9
Adapter    "chromecast"   : 2.3.1    , installed 2.3.1
Adapter    "devices"      : 1.0.12   , installed 1.0.12
Adapter    "discovery"    : 3.0.5    , installed 3.0.5
Adapter    "ical"         : 1.13.1   , installed 1.13.1
Adapter    "influxdb"     : 3.1.7    , installed 3.1.7
Adapter    "iot"          : 1.11.8   , installed 1.11.4 [Updatable]
Adapter    "javascript"   : 5.7.0    , installed 5.7.0
Controller "js-controller": 4.0.23   , installed 4.0.23
Adapter    "mqtt"         : 3.0.6    , installed 3.0.6
Adapter    "parser"       : 1.1.7    , installed 1.1.7
Adapter    "sayit"        : 1.12.3   , installed 1.12.3
Adapter    "shelly"       : 5.3.2    , installed 5.3.2
Adapter    "simple-api"   : 2.7.0    , installed 2.7.0
Adapter    "smartmeter"   : 3.3.4    , installed 3.3.4
Adapter    "socketio"     : 4.2.0    , installed 4.2.0
Adapter    "sonoff"       : 2.5.1    , installed 2.5.1
Adapter    "tahoma"       : 0.7.1    , installed 0.7.1
Adapter    "tankerkoenig" : 2.1.1    , installed 2.1.1
Adapter    "telegram"     : 1.13.0   , installed 1.13.0
Adapter    "trashschedule": 2.0.2    , installed 2.0.2
Adapter    "vis"          : 1.4.15   , installed 1.4.15
Adapter    "web"          : 4.3.0    , installed 4.3.0
Adapter    "wled"         : 0.6.7    , installed 0.6.7
Adapter    "ws"           : 1.3.0    , installed 1.3.0
Adapter    "zigbee"       : 1.7.5    , installed 1.7.5

pi@iobroker:~ $ iobroker list adapters
system.adapter.admin                   : admin          - v5.3.8
system.adapter.backitup                : backitup       - v2.4.9
system.adapter.chromecast              : chromecast     - v2.3.1
system.adapter.devices                 : devices        - v1.0.12
system.adapter.discovery               : discovery      - v3.0.5
system.adapter.ical                    : ical           - v1.13.1
system.adapter.influxdb                : influxdb       - v2.6.3
system.adapter.iot                     : iot            - v1.11.4
system.adapter.javascript              : javascript     - v5.7.0
system.adapter.mqtt                    : mqtt           - v3.0.6
system.adapter.parser                  : parser         - v1.1.7
system.adapter.sayit                   : sayit          - v1.12.3
system.adapter.shelly                  : shelly         - v5.3.2
system.adapter.simple-api              : simple-api     - v2.7.0
system.adapter.smartmeter              : smartmeter     - v3.3.4
system.adapter.socketio                : socketio       - v4.2.0
system.adapter.sonoff                  : sonoff         - v2.5.1
system.adapter.tahoma                  : tahoma         - v0.7.1
system.adapter.tankerkoenig            : tankerkoenig   - v2.1.1
system.adapter.telegram                : telegram       - v1.13.0
system.adapter.trashschedule           : trashschedule  - v2.0.2
system.adapter.vis                     : vis            - v1.4.15
system.adapter.web                     : web            - v4.3.0
system.adapter.wled                    : wled           - v0.6.7
system.adapter.zigbee                  : zigbee         - v1.7.5

pi@iobroker:~ $ iobroker list instances
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, compact disabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.backitup.0               : backitup              : iobroker                                 -  enabled, compact enabled (group 1)
+ system.adapter.chromecast.0             : chromecast            : iobroker                                 -  enabled, compact disabled
  system.adapter.devices.0                : devices               : iobroker                                 -  enabled
+ system.adapter.discovery.0              : discovery             : iobroker                                 -  enabled, compact disabled
  system.adapter.ical.0                   : ical                  : iobroker                                 - disabled, compact enabled (group 1)
+ system.adapter.influxdb.0               : influxdb              : iobroker                                 -  enabled, compact enabled (group 1), port: 8086
  system.adapter.iot.0                    : iot                   : iobroker                                 - disabled, compact enabled (group 1)
+ system.adapter.javascript.0             : javascript            : iobroker                                 -  enabled, compact disabled
+ system.adapter.mqtt.0                   : mqtt                  : iobroker                                 -  enabled, compact enabled (group 1), port: 1884, bind: 192.168.111.10
+ system.adapter.parser.0                 : parser                : iobroker                                 -  enabled
+ system.adapter.sayit.0                  : sayit                 : iobroker                                 -  enabled, compact enabled (group 1), port: 0
+ system.adapter.shelly.0                 : shelly                : iobroker                                 -  enabled, compact enabled (group 1), port: 1882, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : iobroker                                 -  enabled, compact enabled (group 1), port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.smartmeter.0             : smartmeter            : iobroker                                 -  enabled, compact enabled (group 1)
+ system.adapter.sonoff.0                 : sonoff                : iobroker                                 -  enabled, compact enabled (group 1), port: 1883, bind: 0.0.0.0
+ system.adapter.tahoma.0                 : tahoma                : iobroker                                 -  enabled, compact enabled (group 1)
+ system.adapter.tankerkoenig.1           : tankerkoenig          : iobroker                                 -  enabled, compact enabled (group 1)
+ system.adapter.telegram.0               : telegram              : iobroker                                 -  enabled, compact disabled, port: 8443, bind: 0.0.0.0
  system.adapter.trashschedule.0          : trashschedule         : iobroker                                 - disabled, compact enabled (group 1)
  system.adapter.vis.0                    : vis                   : iobroker                                 - disabled, compact disabled
+ system.adapter.web.0                    : web                   : iobroker                                 -  enabled, compact disabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.wled.0                   : wled                  : iobroker                                 -  enabled, compact enabled (group 1)
+ system.adapter.zigbee.0                 : zigbee                : iobroker                                 -  enabled, compact disabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0c8a15a4093bec11a27d9c957a0af07f-if00-port0

+ instance is alive

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

359

32.9k

83.0k

1.3m