Täglicher Absturz ioBroker + Zugriff auf Raspi [gelöst]

searcher57

Hallo!
Seit einigen Tagen stürzt mein ioBroker täglich ab. Ich habe dann auch keinen Zugang mehr über SSH auf den Raspi. Dann hilft nur noch ein Hardware-Reset (Ein- und Ausschalten)!
Die letzten Log-Einträge vor dem Crash heute:

2023-05-14 16:17:13.274  - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewest"
2023-05-14 16:17:13.344  - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewestNext"
2023-05-14 16:17:13.408  - info: host.raspberrypi Some obsolete host states deleted.
2023-05-14 16:17:15.188  - error: admin.0 (666) admin.0 already running
2023-05-14 16:17:15.193  - warn: admin.0 (666) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 16:17:15.787  - error: host.raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 16:17:15.788  - info: host.raspberrypi Restart adapter system.adapter.admin.0 because enabled
2023-05-14 16:17:17.020  - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 826
2023-05-14 16:17:20.284  - error: javascript.0 (826) javascript.0 already running
2023-05-14 16:17:20.287  - warn: javascript.0 (826) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 16:17:20.878  - error: host.raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 16:17:20.879  - info: host.raspberrypi Restart adapter system.adapter.javascript.0 because enabled
2023-05-14 16:17:21.019  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 838
2023-05-14 16:17:23.485  - error: telegram.0 (838) telegram.0 already running
2023-05-14 16:17:23.490  - warn: telegram.0 (838) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 16:17:24.070  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 16:17:24.071  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2023-05-14 16:17:25.256  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 849
2023-05-14 16:17:25.327  - info: host.raspberrypi instance system.adapter.history.0 started with pid 856
2023-05-14 16:17:27.183  - error: history.0 (856) history.0 already running
2023-05-14 16:17:27.189  - warn: history.0 (856) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 16:17:27.793  - error: host.raspberrypi instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 16:17:27.794  - info: host.raspberrypi Restart adapter system.adapter.history.0 because enabled
2023-05-14 16:17:28.358  - info: telegram.0 (849) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.16.0, js-controller: 4.0.24
2023-05-14 16:17:29.019  - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 875
2023-05-14 16:17:30.692  - error: alexa2.0 (875) alexa2.0 already running
2023-05-14 16:17:30.697  - warn: alexa2.0 (875) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 16:17:31.271  - error: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 16:17:31.271  - info: host.raspberrypi Restart adapter system.adapter.alexa2.0 because enabled
2023-05-14 16:17:33.013  - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 886
2023-05-14 18:07:48.687  - error: hm-rega.0 (886) hm-rega.0 already running
2023-05-14 18:07:48.691  - warn: hm-rega.0 (886) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 18:07:49.268  - error: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 18:07:49.268  - info: host.raspberrypi Restart adapter system.adapter.hm-rega.0 because enabled
2023-05-14 18:07:50.819  - info: host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 897
2023-05-14 18:07:52.359  - error: hm-rpc.0 (897) hm-rpc.0 already running
2023-05-14 18:07:52.363  - warn: hm-rpc.0 (897) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 18:07:52.936  - error: host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 18:07:52.937  - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled
2023-05-14 18:07:54.810  - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 908
2023-05-14 18:07:56.331  - error: hm-rpc.1 (908) hm-rpc.1 already running
2023-05-14 18:07:56.335  - warn: hm-rpc.1 (908) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 18:07:56.964  - error: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 18:07:56.965  - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled
2023-05-14 18:07:58.826  - info: host.raspberrypi instance system.adapter.shelly.0 started with pid 923
2023-05-14 18:07:59.657  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 930
2023-05-14 18:08:00.997  - error: shelly.0 (923) shelly.0 already running
2023-05-14 18:08:01.002  - warn: shelly.0 (923) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-14 18:08:01.605  - error: host.raspberrypi instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-14 18:08:01.606  - info: host.raspberrypi Restart adapter system.adapter.shelly.0 because enabled
2023-05-14 18:08:02.218  - info: admin.0 (930) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24
2023-05-14 18:08:02.275  - info: admin.0 (930) requesting all states
2023-05-14 18:08:02.276  - info: admin.0 (930) requesting all objects

Hängt das eventuell mit meinem Doorbird Adapter, den ich im Beta-Respositorie installiert habe zusammen? Die Instanz habe ich gestern gestoppt, trotzdem war heute der Crash.
Meine Daten:
Plattform: linux
Betriebssystem: linux
Architektur: arm64
CPUs: 4
Geschwindigkeit: 1800 MHz
Modell: Cortex-A72
RAM: 1.8 GB
System-Betriebszeit: 00:35:46
Node.js: v18.16.0
time: 1684082577496
timeOffset: -120
Adapter-Anzahl: 473
NPM: v9.5.1
Datenträgergröße: 29.0 GB
Freier Festplattenspeicher: 23.2 GB
Betriebszeit: 02:25:50
Aktive Instanzen: 17
Pfad: /opt/iobroker/
aktiv:

Ich bitte um Hilfe an einen Laien, der wenig Linux-Erfahrung hat und kaum englische Hinweise versteht.

Vielen Dank im voraus
Rainer

Thomas Braun

@searcher57

Führ mal

iob diag

aus. Dann sieht man evtl. mehr

searcher57

@thomas-braun said in Täglicher Absturz ioBroker + Zugriff auf Raspi:

iob diag

Hallo Thomas,
danke für die schnelle Antwort!

======================= SUMMARY =======================
                     v.2023-04-16


Operatingsystem:        Debian GNU/Linux 11 (bullseye)
Kernel:                 6.1.21-v8+
Installation:           Native
Timezone:               Europe/Berlin (CEST, +0200)
User-ID:                1000
X-Server:               false
Boot Target:            multi-user.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:            1.8G        1.4G        147M        0.0K        324M        404M
Swap:            99M         99M        0.0K
Total:          1.9G        1.5G        147M

Active iob-Instances:   18
Active repo(s): stable

ioBroker Core:          js-controller           4.0.24
                        admin                   6.3.5

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : raspberrypi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects:                8696
States:                 7391

Size of iob-Database:

23M     /opt/iobroker/iobroker-data/objects.jsonl
11M     /opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

Thomas Braun

@searcher57

Grundsätzlich schaut das gut aus, ich vermute allerdings, dass dir bei bestimmten Aktionen der Speicher ausgehen könnte. Die Langfassung schaut wie aus?

searcher57

@thomas-braun
Sorry, wie kann ich Dir die Langfassung kopieren?

Thomas Braun

@searcher57
Genauso wie Zusammenfassung.

searcher57

@thomas-braun
Ich hoffe das meinst Du!

Skript v.2023-04-16

*** BASE SYSTEM ***
Model           : Raspberry Pi 4 Model B Rev 1.4
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:
 20:18:56 up  2:11,  1 user,  load average: 0.61, 0.63, 0.46
CPU threads: 4

Raspberry only:
throttled=0x0
Other values than 0x0 hint to temperature/voltage problems
temp=47.7'C
volt=0.9360V

*** Time and Time Zones ***
               Local time: Sun 2023-05-14 20:18:56 CEST
           Universal time: Sun 2023-05-14 18:18:56 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:            1.8G        1.3G        155M        0.0K        357M        439M
Swap:            99M         99M        0.0K
Total:          1.9G        1.4G        155M

         1849 M total memory
         1336 M used memory
          351 M active memory
         1219 M inactive memory
          155 M free memory
           22 M buffer memory
          335 M swap cache
           99 M total swap
           99 M used swap
            0 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       29G  5.8G   23G  21% /
devtmpfs       devtmpfs  667M     0  667M   0% /dev
tmpfs          tmpfs     925M     0  925M   0% /dev/shm
tmpfs          tmpfs     370M  1.1M  369M   1% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1 vfat      255M   31M  225M  13% /boot
/dev/sda1      exfat      29G 1023M   28G   4% /mnt/usb0
tmpfs          tmpfs     185M     0  185M   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Sun May 14 18:07:11 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  smsc95xx.macaddr=E4:5F:01:15:C8:D1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=c4978b94-02 rootfstype=ext4 fsck.repair=yes rootwait
[Sun May 14 18:07:12 2023] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[Sun May 14 18:07:12 2023] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[Sun May 14 18:07:12 2023] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[Sun May 14 18:07:12 2023] EXT4-fs (mmcblk0p2): 1 orphan inode deleted
[Sun May 14 18:07:12 2023] EXT4-fs (mmcblk0p2): recovery complete
[Sun May 14 18:07:12 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
[Sun May 14 18:07:12 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[Sun May 14 18:07:14 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.

Show mounted filesystems (real ones only):
TARGET      SOURCE         FSTYPE OPTIONS
/           /dev/mmcblk0p2 ext4   rw,noatime
|-/boot     /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
`-/mnt/usb0 /dev/sda1      exfat  rw,nosuid,nodev,noexec,relatime,fmask=0000,dmask=0000,allow_utime=0022,iocharset=utf8,errors=remount-ro

Files in neuralgic directories:

/var:
1.2G    /var/
721M    /var/log
697M    /var/log/journal/5348baed3ac54f7a91359e7c297fe9a9
697M    /var/log/journal
179M    /var/cache

Archived and active journals take up 696.1M in the file system.

/opt/iobroker/backups:
1.4G    /opt/iobroker/backups/
4.0K    /opt/iobroker/backups/redistmp

/opt/iobroker/iobroker-data:
434M    /opt/iobroker/iobroker-data/
266M    /opt/iobroker/iobroker-data/files
71M     /opt/iobroker/iobroker-data/history
68M     /opt/iobroker/iobroker-data/backup-objects
51M     /opt/iobroker/iobroker-data/files/javascript.admin

The five largest files in iobroker-data are:
33M     /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.10538062.js.map
23M     /opt/iobroker/iobroker-data/objects.jsonl
19M     /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.904d455f.js.map
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
9.7M    /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.bbfeb1bf.js.map

*** 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


nodejs:
  Installed: 18.16.0-deb-1nodesource1
  Candidate: 18.16.0-deb-1nodesource1
  Version table:
 *** 18.16.0-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_18.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
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

MULTIHOSTSERVICE/enabled: false

Core adapters versions
js-controller:  4.0.24
admin:          6.3.5
javascript:     6.1.4

Adapters from github:   0

Adapter State
+ system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.alexa2.0                 : alexa2                : raspberrypi                              -  enabled
  system.adapter.alias-manager.0          : alias-manager         : raspberrypi                              - disabled
+ system.adapter.backitup.0               : backitup              : raspberrypi                              -  enabled
+ system.adapter.broadlink2.0             : broadlink2            : raspberrypi                              -  enabled
  system.adapter.devices.0                : devices               : raspberrypi                              -  enabled
+ system.adapter.discovery.0              : discovery             : raspberrypi                              -  enabled
  system.adapter.doorbird.0               : doorbird              : raspberrypi                              - disabled
  system.adapter.flot.0                   : flot                  : raspberrypi                              -  enabled
+ system.adapter.history.0                : history               : raspberrypi                              -  enabled
+ system.adapter.hm-rega.0                : hm-rega               : raspberrypi                              -  enabled
+ system.adapter.hm-rpc.0                 : hm-rpc                : raspberrypi                              -  enabled, port: 0
+ system.adapter.hm-rpc.1                 : hm-rpc                : raspberrypi                              -  enabled, port: 0
+ system.adapter.iot.0                    : iot                   : raspberrypi                              -  enabled
+ system.adapter.javascript.0             : javascript            : raspberrypi                              -  enabled
+ system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : raspberrypi                              -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.tankerkoenig.0           : tankerkoenig          : raspberrypi                              -  enabled
+ system.adapter.telegram.0               : telegram              : raspberrypi                              -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.text2command.0           : text2command          : raspberrypi                              -  enabled
  system.adapter.vis.0                    : vis                   : raspberrypi                              -  enabled
+ system.adapter.web.0                    : web                   : raspberrypi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
  system.adapter.yr.0                     : yr                    : raspberrypi                              -  enabled

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.hm-rpc.0                 : hm-rpc                : raspberrypi                              -  enabled, port: 0
+ system.adapter.hm-rpc.1                 : hm-rpc                : raspberrypi                              -  enabled, port: 0
+ system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : raspberrypi                              -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.telegram.0               : telegram              : raspberrypi                              -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : raspberrypi                              -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

ioBroker-Repositories
stable        : http://download.iobroker.net/sources-dist.json
beta          : http://download.iobroker.net/sources-dist-latest.json

Active repo(s): stable

Installed ioBroker-Instances
Used repository: stable
Adapter    "admin"        : 6.3.5    , installed 6.3.5
Adapter    "alexa2"       : 3.23.2   , installed 3.23.2
Adapter    "alias-manager": 1.2.4    , installed 1.2.4
Adapter    "backitup"     : 2.6.19   , installed 2.6.19
Adapter    "broadlink2"   : 2.1.5    , installed 2.1.5
Adapter    "devices"      : 1.1.2    , installed 1.1.2
Adapter    "discovery"    : 3.1.0    , installed 3.1.0
Adapter    "echarts"      : 1.0.12   , installed 1.0.12
Adapter    "flot"         : 1.11.0   , installed 1.11.0
Adapter    "history"      : 2.2.4    , installed 2.2.4
Adapter    "hm-rega"      : 3.0.46   , installed 3.0.46
Adapter    "hm-rpc"       : 1.15.16  , installed 1.15.16
Adapter    "influxdb"     : 3.2.0    , installed 3.2.0
Adapter    "iot"          : 1.14.2   , installed 1.14.2
Adapter    "javascript"   : 6.1.4    , installed 6.1.4
Controller "js-controller": 4.0.24   , installed 4.0.24
Adapter    "sbfspot"      : 4.1.4    , installed 4.1.4
Adapter    "shelly"       : 6.3.1    , installed 6.3.1
Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
Adapter    "socketio"     : 4.2.0    , installed 6.3.1
Adapter    "tankerkoenig" : 3.3.7    , installed 3.3.7
Adapter    "telegram"     : 1.15.2   , installed 1.15.2
Adapter    "text2command" : 2.3.0    , installed 2.3.0
Adapter    "vis"          : 1.4.16   , installed 1.4.16
Adapter    "web"          : 4.3.0    , installed 5.3.1
Adapter    "ws"           : 1.3.0    , installed 2.3.1
Adapter    "yr"           : 5.3.0    , installed 5.3.0

Objects and States
Please stand by - This may take a while
Objects:        8696
^

Thomas Braun

@searcher57

Das ist nicht die vollständige Ausgabe.

searcher57

@thomas-braun
Bitte sag mir, mit welchem Befehl ich an die Langfassung komme. Ich muss es sonst an irgend einem Punkt unterbrechen.

Thomas Braun

@searcher57

Es gibt eine Kopie davon in /home/iobroker
Aber man kann das auch direkt aus dem Terminalprogramm kopieren. Aus gescheiten jedenfalls.

searcher57

@thomas-braun
Also, ich gehe mit Putty auf den Raspi. Beim letzten Versuch dir die vollständige Ausgabe zu kopieren, ist er schon wieder abgestürzt. Soll ich ihn wieder reseten? Wenn ich den Befehl iob diag ausführe, dann läuft das bis zur Zusammenfassung automatisch durch. Wann soll ich das unterbrechen?

Thomas Braun

@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:

Beim letzten Versuch dir die vollständige Ausgabe zu kopieren, ist er schon wieder abgestürzt.

Das ist natürlich alles andere als normal.

Wenn ich den Befehl iob diag ausführe, dann läuft das bis zur Zusammenfassung automatisch durch. Wann soll ich das unterbrechen?

Auch das ist nicht normal. Das Skript erwartet zwei Bestätigungen per Tastatur fortzufahren. Vor der zweiten Bestätigung kann man die Langfassung aus dem Terminal kopieren.