Salut,
Je répond déjà à quelques questions posées mais en voyant ceci, je me doute que c’est pas la peine d’aller plus loin
mosquitto.conf: No such file or directory
J’ai fait une recherche avant de publier et je suis tombé sur → CECI
Peux tu en ssh me donner le résultat de la commande
cat /etc/mosquitto/mosquitto.conf
cat: /etc/mosquitto/mosquitto.conf: No such file or directory
Peux tu toujours en ssh me donner le résultat de la commande
ls -la /etc/mosquitto/conf.d/
total 12
drwxr-xr-x 2 root root 4096 Sep 26 17:21 .
drwxr-xr-x 5 root root 4096 Sep 26 17:21 ..
-rw-r--r-- 1 root root 72 Sep 26 17:21 jMQTT.conf
sudo systemctl status mosquitto.service
* mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker
Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2022-09-26 17:27:46 CEST; 14min ago
Docs: man:mosquitto.conf(5)
man:mosquitto(8)
Process: 1938 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf (code=exited, status=3)
Main PID: 1938 (code=exited, status=3)
Sep 26 17:27:46 JeedomAtlas systemd[1]: mosquitto.service: Service RestartSec=100ms expired, scheduling restart.
Sep 26 17:27:46 JeedomAtlas systemd[1]: mosquitto.service: Scheduled restart job, restart counter is at 5.
Sep 26 17:27:46 JeedomAtlas systemd[1]: Stopped Mosquitto MQTT v3.1/v3.1.1 Broker.
Sep 26 17:27:46 JeedomAtlas systemd[1]: mosquitto.service: Start request repeated too quickly.
Sep 26 17:27:46 JeedomAtlas systemd[1]: mosquitto.service: Failed with result 'exit-code'.
Sep 26 17:27:46 JeedomAtlas systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1.1 Broker.
Un peu d’aide serait la bienvenue