Mosquitto (MQTT-Broker) ist abgestürzt

Fragen zur Nutzung, Features, usw..
Antworten
yankee
Beiträge: 399
Registriert: Sa Mai 16, 2020 11:34 am

Mosquitto (MQTT-Broker) ist abgestürzt

Beitrag von yankee »

Das hier ist weniger eine Frage und mehr eine Dokumentation von Fehlverhalten um, sollte das ganze häufiger auftreten oder auch andere Leute betreffen wir das mitbekommen und die Fehlerursache finden können.

Demletzt hat das Webinterface meiner oWB nicht mehr reagiert. Auf der Suche in den Logs finde ich Hinweise darauf, dass der MQTT-Broker nicht läuft. Hier ist was ich dann getan habe:

Code: Alles auswählen

$ sudo ls /var/log/mosquitto/
mosquitto.log.1  mosquitto.log.2.gz  mosquitto.log.3.gz  mosquitto.log.4.gz  mosquitto.log.5.gz  mosquitto.log.6.gz  mosquitto.log.7.gz  mosquitto.log.8.gz

$ sudo tail /var/log/mosquitto/mosquitto.log.1
1639560385: Socket error on client 57787de8-158e-4ff2-8089-247cc27b6c42, disconnecting.
1639560385: New client connected from 192.168.178.137 as 57787de8-158e-4ff2-8089-247cc27b6c42 (c1, k15).
1639560385: Socket error on client 57787de8-158e-4ff2-8089-247cc27b6c42, disconnecting.
1639560390: Saving in-memory database to /var/lib/mosquitto/mosquitto.db.
1639560410: New connection from ::1 on port 1883.
1639560425: New connection from ::1 on port 1883.
1639560428: New connection from ::1 on port 1883.
1639560462: Connecting bridge cloud (web.openwb.de:1883)
1639560523: New client connected from ::1 as openWB-mqttsub-0000000016e3acce (c1, k60).
1639560525: Client openWB-mqttsub-0000000016e3acce already connected, closing old connection.

$ sudo service mosquitto status
● mosquitto.service - LSB: mosquitto MQTT v3.1 message broker
   Loaded: loaded (/etc/init.d/mosquitto; generated; vendor preset: enabled)
   Active: active (exited) since Sun 2021-06-20 02:20:56 CEST; 6 months 7 days ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5801 ExecReload=/etc/init.d/mosquitto reload (code=exited, status=0/SUCCESS)
  Process: 296 ExecStart=/etc/init.d/mosquitto start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/mosquitto.service
   
$ sudo service mosquitto stop
pi@openWB:/var/www/html/openWB $ sudo service mosquitto status
● mosquitto.service - LSB: mosquitto MQTT v3.1 message broker
   Loaded: loaded (/etc/init.d/mosquitto; generated; vendor preset: enabled)
   Active: inactive (dead) since Mon 2021-12-27 10:05:45 CET; 6s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 32599 ExecStop=/etc/init.d/mosquitto stop (code=exited, status=0/SUCCESS)
  Process: 5801 ExecReload=/etc/init.d/mosquitto reload (code=exited, status=0/SUCCESS)
  Process: 296 ExecStart=/etc/init.d/mosquitto start (code=exited, status=0/SUCCESS)

Dez 27 10:05:45 openWB systemd[1]: Stopping LSB: mosquitto MQTT v3.1 message broker...
Dez 27 10:05:45 openWB mosquitto[32599]: Stopping network daemon:: mosquittostart-stop-daemon: warning: failed to kill 355: No such process
Dez 27 10:05:45 openWB mosquitto[32599]: .
Dez 27 10:05:45 openWB systemd[1]: Stopped LSB: mosquitto MQTT v3.1 message broker.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

$ sudo service mosquitto start

$ sudo service mosquitto status
● mosquitto.service - LSB: mosquitto MQTT v3.1 message broker
   Loaded: loaded (/etc/init.d/mosquitto; generated; vendor preset: enabled)
   Active: active (running) since Mon 2021-12-27 10:06:02 CET; 3s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 32599 ExecStop=/etc/init.d/mosquitto stop (code=exited, status=0/SUCCESS)
  Process: 5801 ExecReload=/etc/init.d/mosquitto reload (code=exited, status=0/SUCCESS)
  Process: 2049 ExecStart=/etc/init.d/mosquitto start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/mosquitto.service
           └─2055 /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf

Dez 27 10:06:02 openWB systemd[1]: Starting LSB: mosquitto MQTT v3.1 message broker...
Dez 27 10:06:02 openWB mosquitto[2049]: Starting network daemon:: mosquitto.
Dez 27 10:06:02 openWB systemd[1]: Started LSB: mosquitto MQTT v3.1 message broker.
Das hat scheinbar das Problem erstmal gefixt. Ich habe dann noch ein Update auf die aktuelle Nightly gemacht, wodurch ein "Neustart" ausgelöst wird und es sieht alles richtig aus...
Antworten