[Support]: tempio: command not found #11755

greyman12 · 2024-06-05T01:41:22Z

greyman12
Jun 5, 2024

Describe the problem you are having

Have tried several of the dev builds since beta2 and frigate no longer starts. Receiving tempio: command not found and just loops. I don't know if this is related to this commit #11691 but was the only reference that I could find.

Steps to reproduce

Update to dev build.

Version

0.14.0

Frigate config file

n/a

Relevant log output

2024-06-05 10:52:16.418170123  [INFO] Starting Frigate...
2024-06-05 10:52:16.674539116  [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually
2024-06-05 10:52:16.708878820  [INFO] Starting go2rtc...
2024-06-05 10:52:16.849558674  10:52:16.849 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-06-05 10:52:16.849832849  10:52:16.849 INF config path=/dev/shm/go2rtc.yaml
2024-06-05 10:52:16.850235370  10:52:16.850 INF [rtsp] listen addr=:8554
2024-06-05 10:52:16.851255413  10:52:16.850 INF [webrtc] listen addr=:8555
2024-06-05 10:52:16.851258081  10:52:16.850 INF [api] listen addr=:1984
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:17.967209955  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:18.067117755  [2024-06-05 10:52:18] frigate.app                    INFO    : Starting Frigate (0.14.0-36ae42a)
2024-06-05 10:52:18.067186962  [2024-06-05 10:52:18] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-06-05 10:52:18.067238067  [2024-06-05 10:52:18] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-06-05 10:52:18.144678546  [2024-06-05 10:52:18] frigate.util.config            INFO    : frigate config does not need migration...
2024-06-05 10:52:18.230208632  [2024-06-05 10:52:18] peewee_migrate.logs            INFO    : Starting migrations
2024-06-05 10:52:18.230323122  [2024-06-05 10:52:18] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-06-05 10:52:18.403988921  [2024-06-05 10:52:18] frigate.app                    INFO    : Recording process started: 176
2024-06-05 10:52:18.409402011  [2024-06-05 10:52:18] frigate.app                    INFO    : Recording process started: 178
2024-06-05 10:52:18.412537104  [2024-06-05 10:52:18] frigate.app                    INFO    : go2rtc process pid: 97
2024-06-05 10:52:18.444121337  [2024-06-05 10:52:18] detector.coral                 INFO    : Starting detection process: 205
2024-06-05 10:52:18.979166857  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:19.054407991  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:20.083641693  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:20.165009811  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:21.089291046  [2024-06-05 10:52:18] detector.coral_pci             INFO    : Starting detection process: 207
2024-06-05 10:52:21.089726006  [2024-06-05 10:52:18] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-06-05 10:52:21.090686746  [2024-06-05 10:52:18] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as pci
2024-06-05 10:52:21.090690303  [2024-06-05 10:52:18] frigate.app                    INFO    : Output process started: 212
2024-06-05 10:52:21.090693698  [2024-06-05 10:52:18] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-06-05 10:52:21.090695503  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for garage: 244
2024-06-05 10:52:21.090712403  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for Driveway: 247
2024-06-05 10:52:21.090714108  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for carport: 250
2024-06-05 10:52:21.090715423  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for Deck: 255
2024-06-05 10:52:21.090738179  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for front-door: 270
2024-06-05 10:52:21.090739595  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for house-rear: 277
2024-06-05 10:52:21.090741157  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for Backyard2: 282
2024-06-05 10:52:21.090742382  [2024-06-05 10:52:18] frigate.app                    INFO    : Camera processor started for Side: 287
2024-06-05 10:52:21.090755144  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for garage: 300
2024-06-05 10:52:21.090756400  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for Driveway: 319
2024-06-05 10:52:21.090757685  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for carport: 326
2024-06-05 10:52:21.090758881  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for Deck: 335
2024-06-05 10:52:21.090770973  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for front-door: 340
2024-06-05 10:52:21.090772225  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for house-rear: 347
2024-06-05 10:52:21.090773449  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for Backyard2: 355
2024-06-05 10:52:21.090774647  [2024-06-05 10:52:18] frigate.app                    INFO    : Capture process started for Side: 361
2024-06-05 10:52:21.093786178  [2024-06-05 10:52:21] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-06-05 10:52:21.170403436  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:21.256465666  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:22.267717033  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:22.349869871  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:23.365026332  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:23.448326587  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:24.582012578  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:24.665894603  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:25.684021847  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:25.799391165  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:26.412032008  [INFO] Starting go2rtc healthcheck service...
2024-06-05 10:52:26.824570145  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:26.946860158  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:27.964319628  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:28.054360076  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:29.102950124  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:29.201691907  [INFO] Service NGINX exited with code 127 (by signal 0)
2024-06-05 10:52:30.206832421  [INFO] Starting NGINX...
./run.user: line 41: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
2024-06-05 10:52:30.288137553  [INFO] Service NGINX exited with code 127 (by signal 0)

Operating system

Proxmox

Install method

Docker CLI

Network connection

Wired

Camera make and model

n/a

Any other information that may be helpful

No response

Answered by blakeblackshear

Jun 5, 2024

Do you run portainer? If so, this is probably just another case of portainer doing insane things like saving the PATH environment variable and overwriting updates in future images.

View full answer

blakeblackshear · 2024-06-05T01:56:13Z

blakeblackshear
Jun 5, 2024
Maintainer

Do you run portainer? If so, this is probably just another case of portainer doing insane things like saving the PATH environment variable and overwriting updates in future images.

8 replies

eyeni Aug 8, 2024

Hej,
can you be a bit more specific? I am running on Portrainer too, but only use it when i am updating. How to create a new container? How can i safe my config if doing that? I just tried reparing it by deleting the Path in Env in the edit/duplicate-Menu: Frigate starts, but no cameras are shown and i cant see anything in the menu like my configuration-file - it just keeps loading.

christianonpele Aug 9, 2024

Hi friends,

I guess I'm facing the same problemn. Some expaination and how to workaround will be nice. I'm running the HA Addon what wont start since 0.14. I had portainer in the past. But Its not running or even installed.

HASS OS at Debian based Linux Host. Addon Frigate (Full Access) 0.14.0

Logs flooded with:

[INFO] Starting NGINX... ./run.user: line 42: quota / period: division by 0 (error token is "period") [INFO] Service NGINX exited with code 1 (by signal 0)

andbad Aug 9, 2024

Go to portainer
On left menu click on "Containers"
Click on Frigate container name
Duplicate/edit
Scroll down to "Advanced container settings" section, click on "Env" tab
Find row with "Path" in name field (value is something like "/usr/lib/btbn-ffmpeg/bin......") and click on trash bin icon
Click "Deploy the container" button

By(t)e

eyeni Aug 9, 2024

that doesent do the trick for me - GUI is loading but i dont see any camera and i cant even open the config editor or the logs, I just see a loadingsymbol. Do i need to edit something on my config file in advance before perhaps? The Portainer-Log contains some errors like this:

2024-08-09 16:07:19.022113268 2024/08/09 16:07:19 [error] 159#159: *823 auth request unexpected status: 502 while sending to client, client: 192.168.5.55, server: , request: "GET /api/stats HTTP/1.1", host: "192.168.5.51:5000" 2024-08-09 16:07:19.250023504 127.0.0.1 - - [09/Aug/2024:16:07:19 +0200] "" 400 0 "-" "-" "-" 2024-08-09 16:07:19.487011071 2024/08/09 16:07:19 [error] 159#159: *826 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.5.122, server: , request: "GET /api/config HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "192.168.5.51:5000", referrer: "http://192.168.5.51:5000/config"

Here my portainer env before i delete the path field and deployed it again:

eyeni Aug 10, 2024

ok, found the issue:
My Frigate-Yaml was to blame. I had mask-coordinates defined which had been way to high for my camera-resolution. After deleting the masks it updated without issues by deleting the Path in "Env" like mentioned above. Thanks for the help!

jorisroovers · 2024-08-11T07:53:33Z

jorisroovers
Aug 11, 2024
Sponsor

Just in case removing the old PATH env var config isn't working and you still need to set it explicitely, this is what worked for me (on Synology DSM7):

{
         "key" : "PATH",
         "value" : "/usr/lib/btbn-ffmpeg/bin:/usr/local/go2rtc/bin:/usr/local/nginx/sbin:/usr/local/tempio/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
}

1 reply

hedrickbt Dec 3, 2024

This worked for me as well on Synology DSM. Not just removing PATH, but replacing PATH with the contents specified in this message. I was upgrading from an older version ( at least 1 year old ghcr image ) to the latest ghcr image.

christianonpele · 2024-08-11T11:17:43Z

christianonpele
Aug 11, 2024

I wasn’t successful with the PATH attempt, getting frigate back on. My thinking to switch from Home assistant addon to the docker-version but same errors showed off.
My host system is maybe misconfigured then. But where to start troubleshooting? Wiping the box isn’t an option (yet).

Debian based Linux with supervised Home Assistant OS (unsupported install)
I switched to frigates default config
Portainer is showing the container unhealthy:

curl: (7) Failed to connect to 127.0.0.1 port 5000: Connection refused

mqtt:
  enabled: false

cameras:
  name_of_your_camera: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://10.0.10.10:554/rtsp # <----- The stream you want to use for detection
          roles:
            - detect
    detect:
      enabled: false # <---- disable detection until you have a working camera feed
      width: 1280
      height: 720
version: 0.14

Log output is excatly the same on Frigates Homeassistiant Addon & the Frigate Docker Container. (Frigate (Full Access) & frigate:stable)

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 go2rtc-log successfully started
s6-rc: info: service go2rtc: 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 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-08-11 01:43:15.135283518  [INFO] Preparing Frigate...
2024-08-11 01:43:15.137314713  [INFO] Starting NGINX...
2024-08-11 01:43:15.137539899  [INFO] Preparing new go2rtc config...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:15.145174870  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:15.145880946  [INFO] Starting Frigate...
2024-08-11 01:43:15.509750152  [INFO] Starting go2rtc...
2024-08-11 01:43:15.652997277  01:43:15.652 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-08-11 01:43:15.653018472  01:43:15.652 INF config path=/dev/shm/go2rtc.yaml
2024-08-11 01:43:15.653522170  01:43:15.653 INF [rtsp] listen addr=:8554
2024-08-11 01:43:15.653731646  01:43:15.653 INF [api] listen addr=:1984
2024-08-11 01:43:15.653734681  01:43:15.653 INF [webrtc] listen addr=:8555/tcp
2024-08-11 01:43:16.162390682  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:16.182211991  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:16.645513066  [2024-08-11 01:43:16] frigate.app                    INFO    : Starting Frigate (0.14.0-da913d8)
2024-08-11 01:43:16.645687460  [2024-08-11 01:43:16] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-08-11 01:43:16.656812991  [2024-08-11 01:43:16] frigate.util.config            INFO    : frigate config does not need migration...
2024-08-11 01:43:16.828592739  [2024-08-11 01:43:16] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2024-08-11 01:43:16.855135493  [2024-08-11 01:43:16] peewee_migrate.logs            INFO    : Starting migrations
2024-08-11 01:43:16.855975848  [2024-08-11 01:43:16] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-08-11 01:43:16.861467529  [2024-08-11 01:43:16] frigate.app                    INFO    : Recording process started: 220
2024-08-11 01:43:16.867343505  [2024-08-11 01:43:16] frigate.app                    INFO    : Recording process started: 222
2024-08-11 01:43:16.870887816  [2024-08-11 01:43:16] frigate.app                    INFO    : go2rtc process pid: 98
2024-08-11 01:43:16.895064178  [2024-08-11 01:43:16] frigate.app                    INFO    : Output process started: 250
2024-08-11 01:43:16.898038376  [2024-08-11 01:43:16] detector.cpu                   INFO    : Starting detection process: 248
2024-08-11 01:43:16.898437811  [2024-08-11 01:43:16] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2024-08-11 01:43:16.910368292  [2024-08-11 01:43:16] frigate.app                    INFO    : Camera processor started for name_of_your_camera: 265
2024-08-11 01:43:16.919508056  [2024-08-11 01:43:16] frigate.app                    INFO    : Capture process started for name_of_your_camera: 267
2024-08-11 01:43:17.188396420  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:17.196674652  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:18.201639074  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:18.209979622  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:19.216396296  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:19.224456060  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:20.230658919  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:20.238926071  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:21.245764761  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:21.254751141  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:21.956550892  [2024-08-11 01:43:21] frigate.video                  ERROR   : name_of_your_camera: Unable to read frames from ffmpeg process.
2024-08-11 01:43:21.956674478  [2024-08-11 01:43:21] frigate.video                  ERROR   : name_of_your_camera: ffmpeg process is not running. exiting capture thread...
2024-08-11 01:43:22.261204305  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:22.269897913  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:23.277017504  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:23.286618832  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:24.293636775  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:24.302733846  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:25.135677073  [INFO] Starting go2rtc healthcheck service...
2024-08-11 01:43:25.308251240  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:25.316059146  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:26.321399699  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:26.330053442  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:27.334942034  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:27.343270726  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:28.348693984  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:28.356828412  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:29.366088391  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:29.373998101  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:30.380418191  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:30.388442690  [INFO] Service NGINX exited with code 1 (by signal 0)
2024-08-11 01:43:31.393404012  [INFO] Starting NGINX...
./run.user: line 42: quota / period: division by 0 (error token is "period")
2024-08-11 01:43:31.401850196  [INFO] Service NGINX exited with code 1 (by signal 0)

13 replies

NickM-27 Aug 22, 2024
Collaborator Sponsor

#13271 should fix the issue. For some reason the cgroup is showing there is a total of 0 cpu cores on the system which is certainly unusual / impossible and might indicate there is some issue on your and the other user's host system, but in any case we can catch it on the frigate side.

NickM-27 Aug 22, 2024
Collaborator Sponsor

It would be nice if posts like christianonpele's could be split off into a new thread.

I didn't see it before this morning, given that we have the new release we have been getting about 100 GitHub emails a day the last 2 weeks plus posts on other sites as well

Wheemer Aug 22, 2024

Thank you, if there is something I need to run on the server to fix the underlying issue I'd be more than happy to, couldn't find much.

I appreciate all the effort put into this fabulous project. If I had not come to rely on it so much I would not have be so startled when updating it brought it down.

Wheemer Aug 22, 2024

I updated my original docker container to dev-e01b6ee and I am back in business. Thanks for the quick fix. Sorry for conflating this with the previous different issue.

NickM-27 Aug 22, 2024
Collaborator Sponsor

Thanks for confirming the fix

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Support]: tempio: command not found #11755

{{title}}

Replies: 3 comments 22 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Support]: tempio: command not found #11755

Describe the problem you are having

Steps to reproduce

Version

Frigate config file

Relevant log output

Operating system

Install method

Network connection

Camera make and model

Any other information that may be helpful

Replies: 3 comments · 22 replies

blakeblackshear Jun 5, 2024 Maintainer

jorisroovers Aug 11, 2024 Sponsor

NickM-27 Aug 22, 2024 Collaborator Sponsor

NickM-27 Aug 22, 2024 Collaborator Sponsor

NickM-27 Aug 22, 2024 Collaborator Sponsor

Replies: 3 comments 22 replies

blakeblackshear
Jun 5, 2024
Maintainer

jorisroovers
Aug 11, 2024
Sponsor

NickM-27 Aug 22, 2024
Collaborator Sponsor

NickM-27 Aug 22, 2024
Collaborator Sponsor

NickM-27 Aug 22, 2024
Collaborator Sponsor