Frigate démarre puis s'arrête immédiatement

Bonjour,

Mon problème

Frigate refuse de se lancer. Les logs sont simples

frigate  | 2024-10-25 18:41:19.192470744  [INFO] Starting Frigate...                                                                                          
frigate  | s6-rc: info: service go2rtc-healthcheck successfully started
frigate  | s6-rc: info: service nginx successfully started
frigate  | s6-rc: info: service certsync: starting    
frigate  | s6-rc: info: service certsync successfully started    
frigate  | s6-rc: info: service legacy-services: starting                                                                                                     
frigate  | 2024-10-25 18:41:19.273430530  [INFO] Starting certsync...
frigate  | s6-rc: info: service legacy-services successfully started
frigate  | 2024-10-25 18:41:19.419843096  127.0.0.1 - - [25/Oct/2024:18:41:19 +0200] "" 400 0 "-" "-" "-"
frigate  | 2024-10-25 18:41:19.685952061  [INFO] Starting go2rtc...
frigate  | 2024-10-25 18:41:19.811843640  18:41:19.811 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
frigate  | 2024-10-25 18:41:19.811865335  18:41:19.811 INF config path=/dev/shm/go2rtc.yaml
frigate  | 2024-10-25 18:41:19.812297855  18:41:19.812 INF [api] listen addr=:1984
frigate  | 2024-10-25 18:41:19.812472113  18:41:19.812 INF [rtsp] listen addr=:8554
frigate  | 2024-10-25 18:41:19.812667659  18:41:19.812 INF [webrtc] listen addr=:8555/tcp
frigate  | 2024-10-25 18:41:20.648109146  [2024-10-25 18:41:20] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
frigate  | 2024-10-25 18:41:20.648218676  [2024-10-25 18:41:20] frigate.util.config            INFO    : Checking if frigate config needs migration...
frigate  | 2024-10-25 18:41:20.701196134  [2024-10-25 18:41:20] frigate.util.config            INFO    : frigate config does not need migration...
frigate  | 2024-10-25 18:41:20.770564237  [2024-10-25 18:41:20] peewee_migrate.logs            INFO    : Starting migrations
frigate  | 2024-10-25 18:41:20.771315592  [2024-10-25 18:41:20] peewee_migrate.logs            INFO    : There is nothing to migrate
frigate  | 2024-10-25 18:41:20.776234281  [2024-10-25 18:41:20] frigate.app                    INFO    : Recording process started: 341
frigate  | 2024-10-25 18:41:20.781587196  [2024-10-25 18:41:20] frigate.app                    INFO    : Recording process started: 343
frigate  | 2024-10-25 18:41:20.785491589  [2024-10-25 18:41:20] frigate.app                    INFO    : go2rtc process pid: 96
frigate  | 2024-10-25 18:41:20.815580492  [2024-10-25 18:41:20] detector.coral                 INFO    : Starting detection process: 370
frigate  | s6-rc: info: service legacy-services: stopping         
frigate  | s6-rc: info: service legacy-services successfully stopped 
frigate  | s6-rc: info: service go2rtc-healthcheck: stopping
frigate  | s6-rc: info: service certsync: stopping            
frigate  | 2024-10-25 18:41:20.846305924  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
frigate  | s6-rc: info: service go2rtc-healthcheck successfully stopped 
frigate  | 2024-10-25 18:41:20.849147288  [INFO] Service CERTSYNC exited with code 256 (by signal 15)

et cela continue en stoppant tous les services. De tous les logs, aucun problème n’est affiché. docker container ls montre qu’il redémarre toutes les 70 secondes environ. Au cas ou, j’ai réinstallé un fichier config.yml sauvegardé et connu fonctionnel, pas d’amélioration. J’ai retiré le dongle coral, toujours le même état. J’ai au final redémarré le serveur, pas mieux.

Comment débugger le problème? Si une idée surgit, je suis prêt à la tester :wink:

Daniel

Ma configuration


[center]## System Information

version core-2024.9.2
installation_type Home Assistant Container
dev false
hassio false
docker true
user root
virtualenv false
python_version 3.12.4
os_name Linux
os_version 6.1.0-26-amd64
arch x86_64
timezone Europe/Paris
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.1
Stage running
Available Repositories 1520
Downloaded Repositories 6
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Dashboards
dashboards 4
resources 4
views 2
mode storage
Recorder
oldest_recorder_run 15 octobre 2024 à 14:41
current_recorder_run 25 octobre 2024 à 18:29
estimated_db_size 112.70 MiB
database_engine sqlite
database_version 3.45.3
[/center]

Le problème vient de network_mode: host dans docker_compose.yml pour frigate. Le problème est qu’à présent frigate n’arrive plus à parler à MQTT

error 2024-10-26 17:53:34 frigate.comms.mqtt
Unable to publish to events: client is not connected
error 2024-10-26 17:53:35 frigate.comms.mqtt
Unable to publish to camera_activity: client is not connected
error 2024-10-26 17:53:35 frigate.comms.mqtt
Unable to publish to camera_activity: client is not connected
error 2024-10-26 17:53:35 frigate.comms.mqtt
Unable to publish to camera_activity: client is not connected

J’ai tenté dans le frigate config yml chapitre mqtt, d’échanger le host: localhost avec les IP du bridge docker ou du docker de mqtt: dans ce cas à nouveau frigate ne démarre plus. Une idée?
Daniel

Le problème de redémarrage incessant avec frigate, mode network host ou non, est qu’il n’arrive pas à se connecter à MQTT/mosquitto ici. Pour régler le problème, il a suffit de changer le topic_prefix dans le config.yaml de frigate, chapitre mqtt pour que cela refonctionne. Incompréhensible ! :unamused:

hello Dash
tu dis qu’il suffit de changer les topic_prefix dans le config , c est a dire ?

Merci pour ton aide

Dans la configuration de frigate !

/opt/homeassistant/frigate$ cat config.yml                                                                                                          
mqtt:                                                                                                                                                         
  enabled: true                                                                                                                                  
  topic_prefix: frigate0
  [...]