Hey there,
is anyone else experiencing issues with the Frigate app running on Electric Eel?
It worked smoothly for me on Dragonfish before. I am using a (Google) Coral Edge TPU USB device for detection purposes.
After the update to EE, Frigate almost always complained about not being able to find the TPU device at startup. In the rare cases it worked at startup, Frigate stopped working after some time.
Since the update to 24.10.0.2 not a single attempt succeeded anymore.
I checked the USB device then under Electric Eel and it seems to be unstable:
Nov 9 22:37:16 truenas kernel: usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 9 22:37:17 truenas kernel: usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 9 22:37:17 truenas kernel: usb 4-2: LPM exit latency is zeroed, disabling LPM.
Nov 9 22:37:17 truenas kernel: usb 4-2: device firmware changed
Nov 9 22:37:17 truenas kernel: usb 4-2: USB disconnect, device number 2
Nov 9 22:37:18 truenas kernel: usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd
Nov 9 22:37:18 truenas kernel: usb 4-2: LPM exit latency is zeroed, disabling LPM.
Nov 9 22:37:18 truenas kernel: usb 4-2: New USB device found, idVendor=18d1, idProduct=9302, bcdDevice= 1.00
Nov 9 22:37:18 truenas kernel: usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 9 22:41:25 truenas kernel: usb 1-6: USB disconnect, device number 2
Nov 9 22:41:27 truenas kernel: usb 4-2: USB disconnect, device number 3
Nov 9 22:59:40 truenas kernel: usb 4-2: new SuperSpeed USB device number 4 using xhci_hcd
Nov 9 22:59:40 truenas kernel: usb 4-2: New USB device found, idVendor=1a6e, idProduct=089a, bcdDevice= 1.00
Nov 9 22:59:40 truenas kernel: usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 9 23:02:12 truenas kernel: usb 4-2: reset SuperSpeed USB device number 4 using xhci_hcd
Nov 9 23:02:14 truenas kernel: usb 4-2: reset SuperSpeed USB device number 4 using xhci_hcd
Nov 9 23:02:14 truenas kernel: usb 4-2: LPM exit latency is zeroed, disabling LPM.
Nov 9 23:02:14 truenas kernel: usb 4-2: device firmware changed
Nov 9 23:02:14 truenas kernel: usb 4-2: USB disconnect, device number 4
Nov 9 23:02:14 truenas kernel: usb 4-2: new SuperSpeed USB device number 5 using xhci_hcd
Nov 9 23:02:14 truenas kernel: usb 4-2: LPM exit latency is zeroed, disabling LPM.
Nov 9 23:02:14 truenas kernel: usb 4-2: New USB device found, idVendor=18d1, idProduct=9302, bcdDevice= 1.00
Nov 9 23:02:14 truenas kernel: usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
The above was before (22:41) and after (22:59) I successfully checked the Coral USB device on a different machine running the most recent Proxmox and plugged it in again in my TrueNAS EE machine. Not sure whether it
I have decided to rollback to Dragonfish yesterday and I am on the last version now I had before I upgraded to EE, which is 24.04.2.1
Everything is working fine again.
Has anyone an idea or is experiencing similar issues?
Of course Iād prefer to go back to 24.10. when I can.
Update, got it working. Upgrade from DF to EE. Had Frigate config set to a hostpath. This had the Coral added in the config. After upgrade, Frigate config defaulted back to ixVolume, this did not have the Coral configed.
I have a similiar situation i think. Scale EE 24.10.
Frigate app starts just fine, finds the USB Coral but after some time crashes with
Dec 23 02:45:51 truenas kernel: [3041144] 0 3041144 622 96 45056 0 0 sleep
Dec 23 02:45:51 truenas kernel: oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=9704b43b3df9625462a22e37d267fa101cd2129fbd0689288628f80046bb7d34,mems_allowed=0,oom_memcg=/docker/9704b43b3df9625462a22e37d267fa101cd2129fbd0689288628f80046bb7d34,task_memcg=/docker/9704b43b3df9625462a22e37d267fa101cd2129fbd0689288628f80046bb7d34,task=python3,pid=1115451,uid=0
Dec 23 07:03:54 truenas kernel: vethe9f296c: renamed from eth0
Dec 23 07:03:54 truenas kernel: br-d7cbbc55c06b: port 1(vethcaa33c9) entered disabled state
Dec 23 07:03:54 truenas kernel: br-d7cbbc55c06b: port 1(vethcaa33c9) entered disabled state
Dec 23 07:03:54 truenas kernel: vethcaa33c9 (unregistering): left allmulticast mode
Dec 23 07:03:54 truenas kernel: vethcaa33c9 (unregistering): left promiscuous mode
Dec 23 07:03:54 truenas kernel: br-d7cbbc55c06b: port 1(vethcaa33c9) entered disabled state
Dec 23 07:03:56 truenas kernel: br-b829b1a37263: port 1(veth16c4151) entered blocking state
Dec 23 07:03:56 truenas kernel: br-b829b1a37263: port 1(veth16c4151) entered disabled state
Dec 23 07:03:56 truenas kernel: veth16c4151: entered allmulticast mode
Dec 23 07:03:56 truenas kernel: veth16c4151: entered promiscuous mode
Dec 23 07:03:56 truenas kernel: br-b829b1a37263: port 1(veth16c4151) entered blocking state
Dec 23 07:03:56 truenas kernel: br-b829b1a37263: port 1(veth16c4151) entered forwarding state
Dec 23 07:03:56 truenas kernel: br-b829b1a37263: port 1(veth16c4151) entered disabled state
Dec 23 07:03:57 truenas kernel: eth0: renamed from vethf842501
Dec 23 07:03:57 truenas kernel: br-b829b1a37263: port 1(veth16c4151) entered blocking state
Dec 23 07:03:57 truenas kernel: br-b829b1a37263: port 1(veth16c4151) entered forwarding state
Dec 23 07:04:00 truenas kernel: usb 2-3.3: reset SuperSpeed USB device number 4 using xhci_hcd
Dec 23 07:04:00 truenas kernel: usb 2-3.3: LPM exit latency is zeroed, disabling LPM.