Is this log message of concern?

[dougransom]

Are these messages of concern?

2024-09-21 16:55:34.954528173  [2024-09-21 09:55:34] frigate.util.config            INFO    : frigate config does not need migration...
2024-09-21 16:55:38.007687068  2024/09/21 09:55:38 [error] 172#172: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2024-09-21 16:55:38.007710991  2024/09/21 09:55:38 [error] 172#172: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2024-09-21 16:55:43.038633815  2024/09/21 09:55:43 [error] 173#173: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2024-09-21 16:55:43.038653685  2024/09/21 09:55:43 [error] 173#173: *4 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"

from this log

6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-09-21 16:55:33.045398650  [INFO] Preparing Frigate...
2024-09-21 16:55:33.047400162  [INFO] Starting NGINX...
2024-09-21 16:55:33.048681689  [INFO] Preparing new go2rtc config...
2024-09-21 16:55:33.054873480  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-09-21 16:55:33.060811003  [INFO] Starting Frigate...
2024-09-21 16:55:33.091998121  [INFO] Got IP address from supervisor: 192.168.8.100
2024-09-21 16:55:33.133529551  [INFO] Got WebRTC port from supervisor: 8555
2024-09-21 16:55:33.547781802  [INFO] Starting go2rtc...
2024-09-21 16:55:33.666718992  09:55:33.666 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-21 16:55:33.666997846  09:55:33.666 INF config path=/dev/shm/go2rtc.yaml
2024-09-21 16:55:33.668089962  09:55:33.667 INF [api] listen addr=:1984
2024-09-21 16:55:33.668262094  09:55:33.668 INF [rtsp] listen addr=:8554
2024-09-21 16:55:33.668699108  09:55:33.668 INF [webrtc] listen addr=:8555/tcp
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2024-09-21 16:55:34.393826221  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-09-21 16:55:34.476646159  127.0.0.1 - - [21/Sep/2024:09:55:34 -0700] "" 400 0 "-" "-" "-"
2024-09-21 16:55:34.930228707  [2024-09-21 09:55:34] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-09-21 16:55:34.930367086  [2024-09-21 09:55:34] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-09-21 16:55:34.930511602  [2024-09-21 09:55:34] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-09-21 16:55:34.954528173  [2024-09-21 09:55:34] frigate.util.config            INFO    : frigate config does not need migration...
2024-09-21 16:55:38.007687068  2024/09/21 09:55:38 [error] 172#172: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2024-09-21 16:55:38.007710991  2024/09/21 09:55:38 [error] 172#172: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2024-09-21 16:55:43.038633815  2024/09/21 09:55:43 [error] 173#173: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2024-09-21 16:55:43.038653685  2024/09/21 09:55:43 [error] 173#173: *4 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2024-09-21 16:55:43.044698325  [INFO] Starting go2rtc healthcheck service...
2024-09-21 16:55:44.741912057  [2024-09-21 09:55:44] peewee_migrate.logs            INFO    : Starting migrations
2024-09-21 16:55:44.742098124  [2024-09-21 09:55:44] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-09-21 16:55:44.784337987  [2024-09-21 09:55:44] frigate.app                    INFO    : Recording process started: 374
2024-09-21 16:55:44.784343975  [2024-09-21 09:55:44] frigate.app                    INFO    : Recording process started: 377
2024-09-21 16:55:44.788037989  [2024-09-21 09:55:44] frigate.app                    INFO    : go2rtc process pid: 98
2024-09-21 16:55:44.823919971  [2024-09-21 09:55:44] frigate.app                    INFO    : Output process started: 407
2024-09-21 16:55:44.889732011  [2024-09-21 09:55:44] frigate.app                    INFO    : Camera processor started for reolink_doorbell_det: 422
2024-09-21 16:55:44.889737829  [2024-09-21 09:55:44] frigate.app                    INFO    : Camera processor started for reolink_doorbell_rec: 423
2024-09-21 16:55:44.893790546  [2024-09-21 09:55:44] frigate.app                    INFO    : Capture process started for reolink_doorbell_det: 431
2024-09-21 16:55:44.907219752  [2024-09-21 09:55:44] frigate.app                    INFO    : Capture process started for reolink_doorbell_rec: 432
2024-09-21 16:55:47.434086251  [2024-09-21 09:55:44] detector.coral                 INFO    : Starting detection process: 403
2024-09-21 16:55:47.438606599  [2024-09-21 09:55:44] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-09-21 16:55:47.438667674  [2024-09-21 09:55:47] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-09-21 16:56:34.532630177  127.0.0.1 - - [21/Sep/2024:09:56:34 -0700] "" 400 0 "-" "-" "-"
2024-09-21 16:56:59.914314594  [h264 @ 0x7f90a40e5140] error while decoding MB 47 80, bytestream -11

I am thinking possibly, as no object detections have been reported by frigate when I walk in front of camera.

[NickM-27]

That's usually just on frigate startup, not an issue