openHAB hängt sich immer wieder nach einer Woche auf.

Einrichtung der openHAB Umgebung und allgemeine Konfigurationsthemen.

Moderatoren: seppy, udo1toni

Quautiputzli
Beiträge: 364
Registriert: 29. Okt 2020 19:53
Answers: 2

openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von Quautiputzli »

Hallo miteinander

Ich benutze einen pi 4 mit 4GB. Seit einiger Zeit habe ich das Problem, dass sich openHAB nach ca. 1 Woche Laufzeit aufhängt. Es werden dann keine rules mehr ausgeführt, Schaltungen über die Oberfläche oder Eingänge/zigbee sind nicht mehr möglich. Der raspberry ist über SSH erreichbar, jedoch weiß ich nicht, nach was ich dabei suchen soll. Größere Änderungen die ich in letzter Zeit gemacht habe sind: update auf OH3.3, neue zigbe2mqtt version, ipcamera Binding incl. ffmpeg. Ansonsten nur bestehende rules geändert, Items dazugefügt.

Ich habe hier mal nachträglich versucht das aufzulisten was zeitlich passiert ist bzw. geändert wurde:

Code: Alles auswählen

04.09. 11:30 Image von OH3.2
18.09. 14:30 update auf OH3.3, ffmpeg
24.09. 14:15 Image von OH3.3
29.09. neue zigbe2mqtt Version 1.26.0
29.09. VOC Sensor eingefügt. mehrere Werte pro sec.
30.09. 11:30 aufgehägt --> zurück auf Image vom 24.09. (andere SD-Karte) (Verdacht auf VOC Sensor)
08.10. 19:00 aufgehägt --> reboot (Daten weg)
09.10. 16:30 Test --> shutdown (Daten da)
09.10. 16:35 neues Netzteil, original PI4
16.10. 19:00 aufgehägt --> shutdown (die meisten Daten sind da)
Der letzte log Eintrag:

Code: Alles auswählen

2022-10-16 18:59:12.674 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.openhab.core.io.monitor.internal.EventLogger@4ca49f' takes more than 5000ms.
2022-10-16 19:00:00.863 [INFO ] [org.openhab.core.model.script.rules ] - WP aWattar - wird nicht ausgeführt, Temperatur zu hoch. Aktuelle Temperatur (17.95 °C)
2022-10-16 19:00:00.971 [ERROR] [internal.handler.ScriptActionHandler] - Script execution of rule with UID 'ShellykWh-1' failed: Could not cast NULL to java.lang.Number; line 8, column 23, length 17 in ShellykWh
2022-10-16 19:03:39.977 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:03:40.001 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:03:41.739 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:03:41.748 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:04:10.763 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:04:10.811 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:04:41.206 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:04:41.235 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:05:11.725 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:05:11.766 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:05:42.214 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:05:42.250 [WARN ] [apache.cxf.jaxrs.utils.ResourceUtils] - No resource methods have been found for resource class javax.ws.rs.core.Response
2022-10-16 19:05:42.722 [INFO ] [miio.internal.cloud.MiCloudConnector] - Error logging on to Xiaomi cloud (0): Error getting logon location URL. Return code: 0
==> /var/log/openhab/events.log <==
2022-10-16 19:09:58.720 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'NetworkDevice19216821_Zuletztgesehen' changed from 2022-10-16T18:58:03.649+0200 to 2022-10-16T18:59:03.979+0200
2022-10-16 19:09:58.730 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Aussenluftfeuchte' changed from 93.8 % to 93.5 %
2022-10-16 19:09:58.738 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Zuluftfeuchte' changed from 75.6 to 75.9
2022-10-16 19:09:58.746 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WP_Boilertemperatur4' changed from 43.1 to 41.5
2022-10-16 19:09:58.755 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Fortlufttemperatur' changed from 18.7 °C to 18.8 °C
2022-10-16 19:09:58.763 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WP_Boilertemperatur3' changed from 44.5 to 44.4
2022-10-16 19:09:58.771 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Abluftfeuchte' changed from 75.6 to 75.8
2022-10-16 19:09:58.780 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WP_Boilertemperatur1' changed from 20.9 to 20.2
2022-10-16 19:09:58.789 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Ablufttemperatur' changed from 24.2 °C to 24.3 °C
==> /var/log/openhab/openhab.log <==
2022-10-16 19:09:59.763 [INFO ] [org.openhab.core.model.script.rules ] - Schalter Büro wurde betätigt (null)
==> /var/log/openhab/events.log <==
2022-10-16 19:09:59.005 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WP_Boilertemperatur2' changed from 45.2 to 45.1
2022-10-16 19:09:59.017 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Aussenlufttaupunkt' changed from 15 °C to 14.9 °C
2022-10-16 19:09:59.025 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Fortlufttaupunkt' changed from 16.7 to 16.9
2022-10-16 19:09:59.033 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Ablufttaupunkt' changed from 19.6 to 19.7
2022-10-16 19:09:59.041 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'C_Luft_Fortluftfeuchte' changed from 88.4 to 88.6
2022-10-16 19:09:59.048 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'shellyplug2_power' changed from 42.61 W to 42.92 W
2022-10-16 19:09:59.073 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'shellyplug2_temperature' changed from 29.52 to 29.69
2022-10-16 19:09:59.081 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'shellyplug2_energy' changed from 11.98205 to 11.982766666666667
2022-10-16 19:09:59.089 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'FF_KidsRoom_M_Blind_temperature' changed from 45.82 to 45.19
2022-10-16 19:09:59.098 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Stromstecker1_StromsteckerEmpfang' changed from 110 to 52
2022-10-16 19:09:59.124 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'KFZ_Heat_on' received command OFF
2022-10-16 19:09:59.133 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'WP_on' received command OFF
2022-10-16 19:09:59.754 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'WakeUp' received command ON
2022-10-16 19:09:59.777 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'C_heatpump' received command 2
==> /var/log/openhab/openhab.log <==
2022-10-16 19:10:00.718 [INFO ] [org.openhab.core.model.script.rules ] - Schalter Büro wurde betätigt (button_2_single)
==> /var/log/openhab/events.log <==
2022-10-16 19:10:00.725 [INFO ] [openhab.event.ChannelTriggeredEvent ] - mqtt:topic:broker:gf_office_switch:office_switch_trigger triggered button_2_single
==> /var/log/openhab/openhab.log <==
2022-10-16 19:10:01.429 [INFO ] [org.openhab.core.model.script.rules ] - Schalter Büro wurde betätigt (button_4_single)
2022-10-16 19:10:01.519 [INFO ] [org.openhab.core.model.script.rules ] - Schalter Büro wurde betätigt (button_4_single)
2022-10-16 19:10:01.547 [INFO ] [org.openhab.core.model.script.rules ] - Schalter Büro wurde betätigt (button_3_single)
2022-10-16 19:10:01.600 [INFO ] [org.openhab.core.model.script.rules ] - Schalter Büro wurde betätigt (button_6_single)
==> /var/log/openhab/events.log <==
2022-10-16 19:10:01.469 [INFO ] [openhab.event.ChannelTriggeredEvent ] - mqtt:topic:broker:gf_office_switch:office_switch_trigger triggered button_4_single
2022-10-16 19:10:01.525 [INFO ] [openhab.event.ChannelTriggeredEvent ] - mqtt:topic:broker:gf_office_switch:office_switch_trigger triggered button_4_single
2022-10-16 19:10:01.554 [INFO ] [openhab.event.ChannelTriggeredEvent ] - mqtt:topic:broker:gf_office_switch:office_switch_trigger triggered button_3_single
2022-10-16 19:10:01.652 [INFO ] [openhab.event.ChannelTriggeredEvent ] - mqtt:topic:broker:gf_office_switch:office_switch_trigger triggered button_6_single
==> /var/log/openhab/openhab.log <==
2022-10-16 19:10:02.257 [INFO ] [org.openhab.core.model.script.rules ] - Schalter Büro wurde betätigt (button_2_single)
==> /var/log/openhab/events.log <==
2022-10-16 19:10:02.274 [INFO ] [openhab.event.ChannelTriggeredEvent ] - mqtt:topic:broker:gf_office_switch:office_switch_trigger triggered button_2_single
==> /var/log/openhab/openhab.log <==
2022-10-16 19:10:07.274 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.openhab.core.io.monitor.internal.EventLogger@4ca49f' takes more than 5000ms.
Wenn ich mich mit ssh verbinde kommt folgendes:

Code: Alles auswählen

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct  9 17:35:11 2022 from 192.168.2.114

###############################################################################
###############  openhabian  ##################################################
###############################################################################
##        Ip = 192.168.2.222
##   Release = Raspbian GNU/Linux 11 (bullseye)
##    Kernel = Linux 5.15.61-v7l+
##  Platform = Raspberry Pi 4 Model B Rev 1.2
##    Uptime = 0 day(s). 0:3:41
## CPU Usage = 96.76% avg over 4 cpu(s) (4 core(s) x 1 socket(s))
##  CPU Load = 1m: 3.00, 5m: 1.71, 15m: 0.72
##    Memory = Free: 2.72GB (72%), Used: 1.07GB (28%), Total: 3.79GB
##      Swap = Free: 2.99GB (100%), Used: 0.00GB (0%), Total: 2.99GB
##      Root = Free: 19.92GB (71%), Used: 7.93GB (29%), Total: 29.07GB
##   Updates = 11 apt updates available.
##  Sessions = 1 session(s)
## Processes = 138 running processes of 32768 maximum processes
###############################################################################

                          _   _     _     ____   _
  ___   ___   ___   ___  | | | |   / \   | __ ) (_)  ____   ___
 / _ \ / _ \ / _ \ / _ \ | |_| |  / _ \  |  _ \ | | / _  \ / _ \
| (_) | (_) |  __/| | | ||  _  | / ___ \ | |_) )| || (_) || | | |
 \___/|  __/ \___/|_| |_||_| |_|/_/   \_\|____/ |_| \__|_||_| | |
      |_|                  openHAB 3.3.0 - Release Build

Looking for a place to get started? Check out 'sudo openhabian-config' and the
documentation at https://www.openhab.org/docs/installation/openhabian.html
The openHAB dashboard can be reached at http://openhabian:8080
To interact with openHAB on the command line, execute: 'openhab-cli --help'

openhabian@openhabian:~ $ sudo systemctl status openhab
[sudo] password for openhabian:
● openhab.service - openHAB - empowering the smart home
     Loaded: loaded (/lib/systemd/system/openhab.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/openhab.service.d
             └─override.conf
     Active: active (running) since Sun 2022-10-09 16:16:50 CEST; 1 weeks 0 days ago
       Docs: https://www.openhab.org/docs/
             https://community.openhab.org
   Main PID: 645 (java)
      Tasks: 320 (limit: 4915)
        CPU: 1d 9h 42min 26.634s
     CGroup: /system.slice/openhab.service
             ├─ 645 /usr/bin/java -XX:-UsePerfData -Dopenhab.home=/usr/share/openhab -Dopenhab.conf=/etc/openhab -Dopenhab.runtime=/usr/share/openh>
             ├─5026 /usr/bin/ffmpeg -rtsp_transport tcp -hide_banner -loglevel warning -i rtsp://192.168.2.134/ch0_0.h264 -q:v 5 -r 2 -vf scale=640>
             ├─5985 ping -w 5 -c 1 192.168.2.25
             └─5987 arping -w 5 -C 1 -i eth0 192.168.2.25

Warning: journal has been rotated since unit was started, output may be incomplete.
lines 1-17/17 (END)...skipping...
● openhab.service - openHAB - empowering the smart home
     Loaded: loaded (/lib/systemd/system/openhab.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/openhab.service.d
             └─override.conf
     Active: active (running) since Sun 2022-10-09 16:16:50 CEST; 1 weeks 0 days ago
       Docs: https://www.openhab.org/docs/
             https://community.openhab.org
   Main PID: 645 (java)
      Tasks: 320 (limit: 4915)
        CPU: 1d 9h 42min 26.634s
     CGroup: /system.slice/openhab.service
             ├─ 645 /usr/bin/java -XX:-UsePerfData -Dopenhab.home=/usr/share/openhab -Dopenhab.conf=/etc/openhab -Dopenhab.runtime=/usr/share/openhab/runtime -Dopenhab.us>
             ├─5026 /usr/bin/ffmpeg -rtsp_transport tcp -hide_banner -loglevel warning -i rtsp://192.168.2.134/ch0_0.h264 -q:v 5 -r 2 -vf scale=640:-2 -update 1 http://12>
             ├─5985 ping -w 5 -c 1 192.168.2.25
             └─5987 arping -w 5 -C 1 -i eth0 192.168.2.25

Warning: journal has been rotated since unit was started, output may be incomplete.
Nochmal Verbindung getrennt und wieder über ssh:

Code: Alles auswählen

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Oct  9 17:35:11 2022 from 192.168.2.114

###############################################################################
###############  openhabian  ##################################################
###############################################################################
##        Ip = 192.168.2.222
##   Release = Raspbian GNU/Linux 11 (bullseye)
##    Kernel = Linux 5.15.61-v7l+
##  Platform = none
##    Uptime = 7 day(s). 1:37:45
## CPU Usage = 79.85% avg over 4 cpu(s) (4 core(s) x 1 socket(s))
##  CPU Load = 1m: 11.15, 5m: 8.10, 15m: 5.48
##    Memory = Free: 0.12GB (3%), Used: 3.67GB (97%), Total: 3.79GB
##      Swap = Free: 2.99GB (100%), Used: 0.00GB (0%), Total: 2.99GB
##      Root = Free: 19.90GB (71%), Used: 7.95GB (29%), Total: 29.07GB
##   Updates = 15 apt updates available.
##  Sessions = 1 session(s)
## Processes = 142 running processes of 32768 maximum processes
###############################################################################

                          _   _     _     ____   _
  ___   ___   ___   ___  | | | |   / \   | __ ) (_)  ____   ___
 / _ \ / _ \ / _ \ / _ \ | |_| |  / _ \  |  _ \ | | / _  \ / _ \
| (_) | (_) |  __/| | | ||  _  | / ___ \ | |_) )| || (_) || | | |
 \___/|  __/ \___/|_| |_||_| |_|/_/   \_\|____/ |_| \__|_||_| | |
      |_|                  openHAB 3.3.0 - Release Build

Looking for a place to get started? Check out 'sudo openhabian-config' and the
documentation at https://www.openhab.org/docs/installation/openhabian.html
The openHAB dashboard can be reached at http://openhabian:8080
To interact with openHAB on the command line, execute: 'openhab-cli --help'

openhabian@openhabian:~ $ sudo systemctl status openhab
[sudo] password for openhabian:
● openhab.service - openHAB - empowering the smart home
     Loaded: loaded (/lib/systemd/system/openhab.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/openhab.service.d
             └─override.conf
     Active: active (running) since Sun 2022-10-09 16:16:50 CEST; 1 weeks 0 days ago
       Docs: https://www.openhab.org/docs/
             https://community.openhab.org
   Main PID: 645 (java)
      Tasks: 317 (limit: 4915)
        CPU: 1d 10h 44min 55.751s
     CGroup: /system.slice/openhab.service
             ├─  645 /usr/bin/java -XX:-UsePerfData -Dopenhab.home=/usr/share/openhab -Dopenhab.conf=/etc/openhab -Dopenhab.runtime=/usr/s>
             └─10029 /usr/bin/ffmpeg -rtsp_transport tcp -hide_banner -loglevel warning -i rtsp://192.168.2.134/ch0_0.h264 -q:v 5 -r 2 -vf>

Warning: journal has been rotated since unit was started, output may be incomplete.
lines 1-15/15 (END)...skipping...
● openhab.service - openHAB - empowering the smart home
     Loaded: loaded (/lib/systemd/system/openhab.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/openhab.service.d
             └─override.conf
     Active: active (running) since Sun 2022-10-09 16:16:50 CEST; 1 weeks 0 days ago
       Docs: https://www.openhab.org/docs/
             https://community.openhab.org
   Main PID: 645 (java)
      Tasks: 317 (limit: 4915)
        CPU: 1d 10h 44min 55.751s
     CGroup: /system.slice/openhab.service
             ├─  645 /usr/bin/java -XX:-UsePerfData -Dopenhab.home=/usr/share/openhab -Dopenhab.conf=/etc/openhab -Dopenhab.runtime=/usr/share/openhab/runtime -Dopenhab.u>
             └─10029 /usr/bin/ffmpeg -rtsp_transport tcp -hide_banner -loglevel warning -i rtsp://192.168.2.134/ch0_0.h264 -q:v 5 -r 2 -vf scale=640:-2 -update 1 http://1>

Warning: journal has been rotated since unit was started, output may be incomplete.


openhabian@openhabian:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  8.0G   20G  29% /
devtmpfs        1.9G     0  1.9G   0% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           778M  2.1M  776M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/mmcblk0p1  253M   50M  203M  20% /boot
/dev/zram1      721M  283M  386M  43% /opt/zram/zram1
overlay1        721M  283M  386M  43% /var/lib/openhab/persistence
/dev/zram2      974M  680M  227M  76% /opt/zram/zram2
overlay2        974M  680M  227M  76% /var/log
tmpfs           389M     0  389M   0% /run/user/1000
Wie es aussieht ist ja die CPU Last und auch der Arbeitsspeicher extrem hoch.
Was kann ich checken wenn der Fehler wieder auftritt? Bzw. auch jetzt schon, so lange es noch läuft?
Servus

Benutzeravatar
scotty
Beiträge: 676
Registriert: 28. Apr 2020 04:44
Answers: 0

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von scotty »

Auf den ersten Blick würde ich mal vermuten, dass der Speicher voll ist. Du hast ein Camera eingebunden, wo werden denn die Aufnahmen gespeichert? Versuch mal, diese abzuschalten und beobachte weiter.
OH 3.4.5 im Docker auf Synology DS918+ mit USV, Reolink-RLC-511WA, Philips Hue, AVM Fritz!Box 6591C, Alexa, Logitech Harmony und diversen Shelly's

Quautiputzli
Beiträge: 364
Registriert: 29. Okt 2020 19:53
Answers: 2

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von Quautiputzli »

Hi,
die Camera speichert die Filmchen auf der eigenen SD-Karten. Was das ffmpeg und das ip-camera-Binding auf dem openHAB raspberry macht, weiß ich nicht. Ich hab da die Standard Einstellungen.

Auf der Übersicht beim einloggen über ssh deutet aber nichts auf vollen Speicher hin oder?
Servus

Benutzeravatar
udo1toni
Beiträge: 15242
Registriert: 11. Apr 2018 18:05
Answers: 242
Wohnort: Darmstadt

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von udo1toni »

Die Prozessorlast erscheint mir auch etwas hoch. Hast Du htop installiert (sudo apt install htop)? Alternativ geht auch top, das Interface von htop ist aber gefälliger.
Mit htop kannst Du nachschauen, welche Prozesse die Ressourcen verbraten, im Falle der CPU-Last über die verbrauchte Rechenzeit.
Allerdings ist das nur insofern hilfreich, falls openHAB nicht der Übeltäter ist, ansonsten hast Du nur eine Liste mit über 100 Threads, die alle einen identischen Namen tragen, also nicht der jeweiligen Aufgabe zugeordnet werden können.
openHAB4.3.3 stable in einem Debian-Container (bookworm) (Proxmox 8.3.5, LXC), mit openHABian eingerichtet

Quautiputzli
Beiträge: 364
Registriert: 29. Okt 2020 19:53
Answers: 2

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von Quautiputzli »

Ja, normalerweise ist die Prozessorlast immer unter 1%
Screenshot (13).png
htop ist woh Standardmässig installiert. Muss ich da auf das TIME+ schauen. Dann muss ich mal ne Woche warten, bis es wieder auftritt.

So sieht es derzeit aus:
Bild_2022-10-17_151919015.png
ffmpeg und der Videokram scheint schon im Normalzustand am meisten Resourcen zu verbrauchen.
Du hast keine ausreichende Berechtigung, um die Dateianhänge dieses Beitrags anzusehen.
Servus

Benutzeravatar
udo1toni
Beiträge: 15242
Registriert: 11. Apr 2018 18:05
Answers: 242
Wohnort: Darmstadt

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von udo1toni »

Ja, das ist nicht weiter verwunderlich, Video Encoding ist eben rechenintensiv.
openHAB4.3.3 stable in einem Debian-Container (bookworm) (Proxmox 8.3.5, LXC), mit openHABian eingerichtet

Quautiputzli
Beiträge: 364
Registriert: 29. Okt 2020 19:53
Answers: 2

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von Quautiputzli »

So, eine Woche später wieder das gleiche Spiel. htop ist für mich nun nicht sehr aufschlussreich:
Bild_2022-10-23_145124896.png
Du hast keine ausreichende Berechtigung, um die Dateianhänge dieses Beitrags anzusehen.
Servus

Quautiputzli
Beiträge: 364
Registriert: 29. Okt 2020 19:53
Answers: 2

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von Quautiputzli »

Hier mal Infos zum Arbeitsspeicher:

Code: Alles auswählen

openhabian@openhabian:~ $ free -h
               total        used        free      shared  buff/cache   available
Mem:           3.8Gi       1.5Gi       371Mi       2.0Mi       1.9Gi       2.2Gi
Swap:          3.0Gi          0B       3.0Gi
Servus

Quautiputzli
Beiträge: 364
Registriert: 29. Okt 2020 19:53
Answers: 2

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von Quautiputzli »

unter:

Code: Alles auswählen

 sudo journalctl -e
war ein haufen zeug über "Zigbee2MQTT" drin. Zigbee2mqtt läuft aber. Ich hab trotzdem mal fogendes gemacht:

Code: Alles auswählen

systemctl stop zigbee2mqtt
systemctl start zigbee2mqtt
läuft aber nun nicht mehr an. Also hab ich mir mosquitto angesehen.

Code: Alles auswählen

openhabian@openhabian:~ $ sudo systemctl status mosquitto
● mosquitto.service - Mosquitto MQTT Broker
     Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-10-16 20:09:38 CEST; 6 days ago
       Docs: man:mosquitto.conf(5)
             man:mosquitto(8)
    Process: 593 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto (code=exited, status=0/SUCCESS)
    Process: 595 ExecStartPre=/bin/chown mosquitto /var/log/mosquitto (code=exited, status=0/SUCCESS)
    Process: 596 ExecStartPre=/bin/mkdir -m 740 -p /run/mosquitto (code=exited, status=0/SUCCESS)
    Process: 597 ExecStartPre=/bin/chown mosquitto /run/mosquitto (code=exited, status=0/SUCCESS)
   Main PID: 598 (mosquitto)
      Tasks: 1 (limit: 4915)
        CPU: 13min 51.167s
     CGroup: /system.slice/mosquitto.service
             └─598 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf

Warning: journal has been rotated since unit was started, output may be incomplete.
Sah für mich in Ordnung aus. Also auch mal gestoppt und wieder gestartet.

Code: Alles auswählen

openhabian@openhabian:~ $ sudo systemctl stop mosquitto
openhabian@openhabian:~ $ sudo systemctl start mosquitto
Läuft aber nicht mehr an:

Code: Alles auswählen

openhabian@openhabian:~ $ sudo systemctl start mosquitto
Job for mosquitto.service failed because the control process exited with error code.
See "systemctl status mosquitto.service" and "journalctl -xe" for details.
openhabian@openhabian:~ $ systemctl status mosquitto.service
● mosquitto.service - Mosquitto MQTT Broker
     Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-10-23 15:25:48 CEST; 20s ago
       Docs: man:mosquitto.conf(5)
             man:mosquitto(8)
    Process: 6470 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto (code=exited, status=0/SUCCESS)
    Process: 6471 ExecStartPre=/bin/chown mosquitto /var/log/mosquitto (code=exited, status=1/FAILURE)
        CPU: 29ms
openhabian@openhabian:~ $ journalctl -xe
Oct 23 03:46:55 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:46:55: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:00 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:00: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:06 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:06: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:11 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:11: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:17 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:17: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:22 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:22: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:27 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:27: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:33 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:33: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:38 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:38: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:44 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:44: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:49 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:49: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:47:54 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:47:54: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:00 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:00: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:05 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:05: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:11 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:11: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:16 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:16: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:21 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:21: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:27 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:27: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:32 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:32: MQTT publish: topic 'zigbee2mqtt/GF_Greenhouse_Temp', payload '{"battery":100,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"GF_Greenho>
Oct 23 03:48:32 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:32: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:38 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:38: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:43 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:43: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:48 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:48: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:54 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:54: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:48:59 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:48:59: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:05 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:05: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:10 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:10: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:15 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:15: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:18 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:18: MQTT publish: topic 'zigbee2mqtt/Temp_1', payload '{"battery":100,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"Temp_1","ieeeAddr":"0x>
Oct 23 03:49:18 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:18: MQTT publish: topic 'zigbee2mqtt/Temp_1', payload '{"battery":100,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"Temp_1","ieeeAddr":"0x>
Oct 23 03:49:18 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:18: MQTT publish: topic 'zigbee2mqtt/Temp_1', payload '{"battery":100,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"Temp_1","ieeeAddr":"0x>
Oct 23 03:49:21 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:21: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:22 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:22: MQTT publish: topic 'zigbee2mqtt/Temp_2', payload '{"battery":97,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"Temp_2","hardwareVersio>
Oct 23 03:49:26 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:26: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:32 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:32: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:37 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:37: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:42 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:42: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:48 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:48: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:53 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:53: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:49:59 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:49:59: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:04 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:04: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:09 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:09: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:15 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:15: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:20 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:20: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:26 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:26: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:31 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:31: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:36 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:36: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:42 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:42: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:43 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:43: MQTT publish: topic 'zigbee2mqtt/Temp_2', payload '{"battery":97,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"Temp_2","hardwareVersio>
Oct 23 03:50:43 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:43: MQTT publish: topic 'zigbee2mqtt/Temp_2', payload '{"battery":97,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"Temp_2","hardwareVersio>
Oct 23 03:50:43 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:43: MQTT publish: topic 'zigbee2mqtt/Temp_2', payload '{"battery":97,"device":{"applicationVersion":5,"dateCode":"20191205","friendlyName":"Temp_2","hardwareVersio>
Oct 23 03:50:47 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:47: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:53 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:53: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:50:58 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:50:58: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:04 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:04: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:09 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:09: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:14 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:14: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:20 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:20: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:25 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:25: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:31 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:31: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:36 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:36: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>
Oct 23 03:51:41 openhabian npm[1037]: Zigbee2MQTT:info  2022-10-23 03:51:41: MQTT publish: topic 'zigbee2mqtt/Plug_1', payload '{"device":{"applicationVersion":22,"dateCode":"09-10-2019","friendlyName":"Plug_1","hardwareVersion":1,"ieee>

Servus

Quautiputzli
Beiträge: 364
Registriert: 29. Okt 2020 19:53
Answers: 2

Re: openHAB hängt sich immer wieder nach einer Woche auf.

Beitrag von Quautiputzli »

Im htop ist nun

Code: Alles auswählen

npn
node index.js
stark vertreten.
Bild_2022-10-23_154429416.png
Hat das mit zigbee2mqtt zu tun?

Code: Alles auswählen

openhabian@openhabian:~ $ systemctl status zigbee2mqtt
● zigbee2mqtt.service - zigbee2mqtt
     Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-10-23 15:45:44 CEST; 12s ago
   Main PID: 10233 (npm)
      Tasks: 23 (limit: 4915)
        CPU: 14.137s
     CGroup: /system.slice/zigbee2mqtt.service
             ├─10233 npm
             ├─10246 sh -c node index.js
             └─10247 node index.js
Du hast keine ausreichende Berechtigung, um die Dateianhänge dieses Beitrags anzusehen.
Servus

Antworten