ein Fhem macht seit dem November update dauernd restart

[mikawood]

Hallo,

ich habe Probleme mit meiner Raspbian Instanz. Ich habe den Raspberry aus der Unterverteilung ausgebaut um die Konsolenmeldung zu sehen, die beiden USB Sticks CUL868 und CUL433 habe ich abgezogen.

Hier die logs:
pi@raspberry60:~ $ tail -n 200 /opt/fhem/log/fhem-$(date '+%Y-%m').log
2024.01.30 13:34:41 1: Including fhem.cfg
2024.01.30 13:34:45 3: WEB: port 8083 opened
2024.01.30 13:34:47 2: eventTypes: loaded 0 lines from ./log/eventTypes.txt
2024.01.30 13:34:47 3: Opening CUL_433 device /dev/ttyACM0
2024.01.30 13:34:48 1: CUL_433: Can't open /dev/ttyACM0: No such file or directory
2024.01.30 13:34:48 3: Opening CUL_868 device /dev/ttyACM1
2024.01.30 13:34:48 1: CUL_868: Can't open /dev/ttyACM1: No such file or directory
2024.01.30 13:34:48 2: Switched CUL_868 rfmode to HomeMatic
2024.01.30 13:35:10 3: Sub BleTagBattery_Define (gTagBattery) - defined
2024.01.30 13:35:12 3: WiffiPump2: Defined with URL http://192.168.10.76/?json and interval 60 featurelevel 6.2
2024.01.30 13:35:16 3: Opening myJeeLink device /dev/ttyUSB0
2024.01.30 13:35:16 1: myJeeLink: Can't open /dev/ttyUSB0: No such file or directory
2024.01.30 13:35:16 3: NN_SZ2_TH1: I/O device is myJeeLink
2024.01.30 13:35:16 3: NN_BK2_TH1: I/O device is myJeeLink
2024.01.30 13:35:36 3: LGTV_WebOS (TV) - defined with host 192.168.10.123
2024.01.30 13:35:48 3: NN_WZ2_TH1: I/O device is myJeeLink
2024.01.30 13:35:49 3: eq3: Defined with URL https://update.homematic.com/firmware/api/firmware/search/DEVICE and interval 604800 featurelevel 6.2
2024.01.30 13:36:02 3: TABLETUI: new ext defined infix:ftui/: dir:./www/tablet/:
2024.01.30 13:36:02 3: Registering HTTPSRV TABLETUI for URL /ftui   and assigned link ftui/ ...
2024.01.30 13:36:03 1: MQTT2_FHEM_Server: Can't open server port at 1883: Address already in use. Exiting.
2024.01.30 13:36:09 1: PERL WARNING: "my" variable $device masks earlier declaration in same scope at ./FHEM/99_myUtils.pm line 106.
2024.01.30 13:36:10 1: Including fhem.cfg
2024.01.30 13:36:14 3: WEB: port 8083 opened
2024.01.30 13:36:16 2: eventTypes: loaded 0 lines from ./log/eventTypes.txt
2024.01.30 13:36:16 3: Opening CUL_433 device /dev/ttyACM0
2024.01.30 13:36:17 1: CUL_433: Can't open /dev/ttyACM0: No such file or directory
2024.01.30 13:36:17 3: Opening CUL_868 device /dev/ttyACM1
2024.01.30 13:36:17 1: CUL_868: Can't open /dev/ttyACM1: No such file or directory
2024.01.30 13:36:17 2: Switched CUL_868 rfmode to HomeMatic
pi@raspberry60:~ $ ^C
pi@raspberry60:~ $ tail -f /var/log/syslog
Jan 30 19:54:42 raspberry60 systemd[1]: Starting FHEM Home Automation...
Jan 30 19:54:49 raspberry60 systemd[1]: Started FHEM Home Automation.
Jan 30 19:56:10 raspberry60 systemd[1]: fhem.service: Main process exited, code=exited, status=1/FAILURE
Jan 30 19:56:10 raspberry60 systemd[1]: fhem.service: Failed with result 'exit-code'.
Jan 30 19:56:10 raspberry60 systemd[1]: fhem.service: Consumed 1min 25.805s CPU time.
Jan 30 19:56:10 raspberry60 systemd[1]: fhem.service: Scheduled restart job, restart counter is at 1075.
Jan 30 19:56:10 raspberry60 systemd[1]: Stopped FHEM Home Automation.
Jan 30 19:56:10 raspberry60 systemd[1]: fhem.service: Consumed 1min 25.805s CPU time.
Jan 30 19:56:10 raspberry60 systemd[1]: Starting FHEM Home Automation...
Jan 30 19:56:16 raspberry60 systemd[1]: Started FHEM Home Automation.
Jan 30 19:57:37 raspberry60 systemd[1]: fhem.service: Main process exited, code=exited, status=1/FAILURE
Jan 30 19:57:37 raspberry60 systemd[1]: fhem.service: Failed with result 'exit-code'.
Jan 30 19:57:37 raspberry60 systemd[1]: fhem.service: Consumed 1min 25.573s CPU time.
Jan 30 19:57:38 raspberry60 systemd[1]: fhem.service: Scheduled restart job, restart counter is at 1076.
Jan 30 19:57:38 raspberry60 systemd[1]: Stopped FHEM Home Automation.
Jan 30 19:57:38 raspberry60 systemd[1]: fhem.service: Consumed 1min 25.573s CPU time.
Jan 30 19:57:38 raspberry60 systemd[1]: Starting FHEM Home Automation...
Jan 30 19:57:44 raspberry60 systemd[1]: Started FHEM Home Automation.

Kann mir bitte jemand helfen den Fhem wieder zum laufen zu bringen. Ich bin am verzweifeln.
Vielen Dank
mikawood

[betateilchen]

Versuche mal rauszufinden, warum der port 1883 auf der Kiste schon belegt ist.

Der Neustart erfolgt nach dem gescheiterten Versuch, den MQTT2 Server einzurichten.

[mikawood]

hier die Konfigurationsdateien.

[mikawood]

in der fhem.cfg war ein MQTT device definiert. ich habe in der Konfiguration die MQTT Einträge gelöscht und Versuche zu starten.

[mikawood]

scheint wieder zu laufen
Danke für den tip.

Mikawood