Frigate Doesn't Boot Up If Enable Auto Tracking Start Up Calibration

[nchlstoo]

Hi

As per the title, whenever I enable the 'Start Up Calibration' for onvif auto tracking, it keeps giving me this error.

Other than that if I disable it. It boots up just fine and works normally.

Using SD1A404XB-GNR

2024-09-25 20:14:49.990754323 2024/09/26 04:14:49 [error] 181#181: *22 auth request unexpected status: 502 while sending to client, client: 172.30.32.1, server: , request: "GET /api/stats HTTP/1.1", host: "ccab4aaf-frigate-fa:5000" 2024-09-25 20:14:51.343297654 [2024-09-26 04:14:51] frigate.ptz.autotrack INFO : Calibration for Front_Door in progress: 3% complete 2024-09-25 20:14:52.083167684 2024/09/26 04:14:52 [error] 181#181: *24 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-25 20:14:52.083173528 2024/09/26 04:14:52 [error] 181#181: *24 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-25 20:14:54.646391045 [2024-09-26 04:14:54] frigate.ptz.autotrack INFO : Calibration for Front_Door in progress: 7% complete

[hawkeye217]

From the note in the docs:

Frigate's web UI and all other cameras will be unresponsive while calibration is in progress. This is expected and normal to avoid excessive network traffic or CPU usage during calibration. Calibration for most PTZs will take about two minutes. The Frigate log will show calibration progress and any errors.

Do you see log messages after Calibration for Front_Door in progress: 7% complete?

[hawkeye217]

What's the timestamp at the 0% complete compared to the timestamp at 90% complete?

[nchlstoo]

2024-09-25 20:59:53.373853917 [2024-09-26 04:59:53] frigate.ptz.autotrack INFO : Calibration for Front_Door in progress: 0% complete

2024-09-25 21:01:57.915729137 [2024-09-26 05:01:57] frigate.ptz.autotrack INFO : Calibration for Front_Door in progress: 90% complete s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service certsync: stopping 2024-09-25 21:01:57.934431289 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)

From 90% on it just started to stop all services and restarts the whole starting of frigate again.

[hawkeye217]

Thanks.

This is happening because the calibration period takes longer than the docker healthcheck start period (120s). I've pushed a fix for this that increases the initial timeout to 5 minutes. The fix will be available in the dev builds and in the next version of Frigate.

#13968

[nchlstoo]

Thank you very much! Will try it !

[hawkeye217]

For now, you can run your autotracking without calibration. There won't be a massive difference between calibrated and uncalibrated unless you're trying to autotrack faster moving objects.