snowy00

Hello, since I upgraded frigeate to v15 I have some error log with --> "Too many unprocessed recording segments" The camera recording stops and after a restart the container works for hours sometimes for 1-2 days normally. Have someone a ideas how can I solve that issue? Is there a need to increase the swap? I found that this code in the compose file can solve the issue but how can I add that in unraid: mem_swappiness: 0 memswap_limit: 7.5gb deploy: resources: limits: memory: 7.5gb

Leider geht das nicht so einfach - ich habe das schon probiert und ich kann die Daten nicht wiederherstellen, da ich eine Fehler Meldung bekommen. Ich bin hier leider nur ein leihe aber da wird irgendwie ein volume per Docker erzeugt , welches man löschen muss # Drop existing data and reinitialize (Don't forget to replace first teslamate if using different TM_DB_USER) docker compose exec -T database psql -U teslamate teslamate << . DROP SCHEMA public CASCADE; CREATE SCHEMA public; CREATE EXTENSION cube WITH SCHEMA public; CREATE EXTENSION earthdistance WITH SCHEMA public; . # Restore docker compose exec -T database psql -U teslamate -d teslamate < teslamate.bck # Remove the old database volume: Docker Volume ls wenn ich das eingeben dann bekomme ich lauter kryptische volumes, die ich nicht zuordnen kann Bei reddit haben user für die Synology NAS geschrieben, dass es mit diesen befehlen geht: docker rm teslamate-database-1 docker volume prune Wie das Datenbank bzw. das volume bei Unraid heißt weiß ich nicht.

Ok, werde ich mache!

Hallo zusammen, hat jemand eine Anleitung, wie man Teslamate auf die Version 2.0 in Unraid updatet? Backup der Datenbank bekomme ich hin, scheitere aber leider an diesem Punkt: Delete the database volume. Be careful, this will delete all your previously recorded data! Make sure that your backup can be restored before you start. docker volume rm "$(basename "$PWD")_teslamate-db" Vielen Dank schon mal

Hallo, ich habe immer wieder das Problem, dass nach einem Neustart der Vhost0 nicht geladen wird. Somit kann ich aus der virtuellen Maschine nicht auf Unraid zugreifen. Kann mit jemand helfen, wie ich dieses Problem lösen kann?

Hi, I have those error messages mostly at night in my frigate los. Is that a configuration issue or it results due to unstable stream? Error 2024-03-22 01:50:27.305718991 [2024-03-22 01:50:27] ffmpeg.doorbird.detect ERROR : Last message repeated 1 times 2024-03-22 01:50:32.425703756 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:32.425705908 [2024-03-22 01:50:32] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:37.319557649 [2024-03-22 01:50:37] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:37.319567635 [2024-03-22 01:50:37] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:37.319611590 [2024-03-22 01:50:37] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Invalid data found when processing input 2024-03-22 01:50:40.358113961 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: Unable to read frames from ffmpeg process. 2024-03-22 01:50:40.358220082 [2024-03-22 01:50:40] frigate.video ERROR : doorbird: ffmpeg process is not running. exiting capture thread... 2024-03-22 01:50:47.325184697 [2024-03-22 01:50:47] watchdog.doorbird ERROR : Ffmpeg process crashed unexpectedly for doorbird. 2024-03-22 01:50:47.325202542 [2024-03-22 01:50:47] watchdog.doorbird ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-03-22 01:50:47.325211543 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : [rtsp @ 0x5586f00bd100] method DESCRIBE failed: 404 Not Found 2024-03-22 01:50:47.325331886 [2024-03-22 01:50:47] ffmpeg.doorbird.detect ERROR : rtsp://127.0.0.1:8554/doorbird: Server returned 404 Not Found 2024-03-22 07:38:37.857388889 [2024-03-22 07:38:37] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 07:38:37.857399654 [2024-03-22 07:38:37] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 07:39:07.887486615 [2024-03-22 07:39:07] root INFO : Detection process didnt exit. Force killing... 2024-03-22 07:39:07.890948093 [2024-03-22 07:39:07] root INFO : Detection process has exited... 2024-03-22 07:39:07.901002708 [2024-03-22 07:39:07] detector.coral INFO : Starting detection process: 23549 2024-03-22 07:39:07.908221679 [2024-03-22 07:39:07] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 07:39:10.726405811 [2024-03-22 07:39:10] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 09:06:47.964609337 [2024-03-22 09:06:47] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 09:06:47.964611572 [2024-03-22 09:06:47] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 09:07:17.994352506 [2024-03-22 09:07:17] root INFO : Detection process didnt exit. Force killing... 2024-03-22 09:07:18.002138068 [2024-03-22 09:07:18] root INFO : Detection process has exited... 2024-03-22 09:07:18.012648975 [2024-03-22 09:07:18] detector.coral INFO : Starting detection process: 6156 2024-03-22 09:07:20.620061572 [2024-03-22 09:07:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 09:07:20.622411381 [2024-03-22 09:07:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-03-22 11:20:48.104918569 [2024-03-22 11:20:48] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... 2024-03-22 11:20:48.104946957 [2024-03-22 11:20:48] root INFO : Waiting for detection process to exit gracefully... 2024-03-22 11:21:18.115158164 [2024-03-22 11:21:18] root INFO : Detection process didnt exit. Force killing... 2024-03-22 11:21:18.121643469 [2024-03-22 11:21:18] root INFO : Detection process has exited... 2024-03-22 11:21:18.132285625 [2024-03-22 11:21:18] detector.coral INFO : Starting detection process: 28132 2024-03-22 11:21:20.740620712 [2024-03-22 11:21:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-03-22 11:21:20.742499265 [2024-03-22 11:21:20] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found frigate config: mqtt: enabled: true host: 192.168.178.32 user: *************** password: ****************** topic_prefix: frigate birdseye: enabled: False detectors: coral: type: edgetpu device: usb objects: track: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: person: min_area: 5000 max_area: 24000000 go2rtc: streams: # doorbird: # - rtsp://******:**********@192.168.178.125:554/mpeg/media.amp doorbird: - rtsp://************:***********@192.168.178.125:554/mpeg/1080p/media.amp cameras: doorbird: enabled: true ffmpeg: hwaccel_args: preset-vaapi output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/doorbird input_args: preset-rtsp-restream roles: - detect - record detect: enabled: true width: 1920 height: 1080 stationary: interval: 50 threshold: 50 max_frames: objects: car: 1000 record: enabled: true retain: days: 5 mode: all events: required_zones: - zone_hof - zone_street retain: default: 15 snapshots: enabled: true required_zones: - zone_hof - zone_street retain: default: 20 zones: zone_hof: coordinates: 1920,1080,1920,744,1764,737,1664,778,751,833,269,783,0,834,0,1080 objects: - person - car - cat - dog - motorcycle - bicycle - umbrella filters: car: threshold: 0.75 zone_street: coordinates: 574,833,1331,804,1863,684,1863,598,210,603,213,748,281,780 objects: - person motion: mask: - 0,0,299,786,0,843 - 0,0,1920,0,1920,427,1920,613,1256,614,211,578 I also see those messages in the unraid log, that the coral sometimes connected and disconnected from the usb port. Is there any connection between the errors? Mar 22 07:39:09 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 07:39:09 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 08:15:06 Tower emhttpd: read SMART /dev/sdc Mar 22 08:37:31 Tower emhttpd: spinning down /dev/sdc Mar 22 09:07:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 09:07:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM. Mar 22 09:20:06 Tower emhttpd: read SMART /dev/sdc Mar 22 09:42:28 Tower emhttpd: spinning down /dev/sdc Mar 22 10:25:07 Tower emhttpd: read SMART /dev/sdc Mar 22 10:47:25 Tower emhttpd: spinning down /dev/sdc Mar 22 11:21:19 Tower kernel: usb 2-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 22 11:21:19 Tower kernel: usb 2-3: LPM exit latency is zeroed, disabling LPM.

I found this kind of messages in the Log - is that normal? Mar 6 21:34:42 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 6 21:34:42 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM. Mar 7 06:44:33 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 7 06:44:33 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM. Mar 7 16:01:14 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 7 16:01:14 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM. Mar 7 17:29:44 Tower kernel: usb 4-3: reset SuperSpeed USB device number 2 using xhci_hcd Mar 7 17:29:44 Tower kernel: usb 4-3: LPM exit latency is zeroed, disabling LPM. Nope I started the server after the crash and did the diagnostics - the mirror logfile to flash was activated during the crash. As mentioned by itimpi (and my understanding is) that the logfile should survives a reboot, so I am confused that the log ist not available in this diagnostics.

Hi, today the serve crashed again! Could you please have a look... tower-diagnostics-20240306-2038.zip

Hi itimpi, thanks for the information - pleas find attached the diagnostics from my system. I have already configured the syylog server but not the copy to the flash drive. Maybe you are able to finde some reasons for the crash. Thanks a lot! tower-diagnostics-20240304-1703.zip

Hi, something happend this night and the Server was not reachable from the local network. After hard reset ""power off" the server starts running properly. This is the last log that received from server: It seems there a lot network issues? By the way at 1:00 it starts a backup of my Docker appdata. (Appdata.Backup) Mar 4 01:01:04 Tower kernel: veth30a58bb: renamed from eth0 Mar 4 01:01:04 Tower kernel: veth00da9cf: renamed from eth0 Mar 4 01:01:06 Tower kernel: vethcd6745b: renamed from eth0 Mar 4 01:01:06 Tower kernel: veth60d5d03: renamed from eth0 Mar 4 01:01:07 Tower kernel: vethbb4d0b3: renamed from eth0 Mar 4 01:01:07 Tower kernel: vethe8a0781: renamed from eth0 Mar 4 01:01:12 Tower kernel: veth628ba8c: renamed from eth0 Mar 4 01:01:13 Tower kernel: veth710ddf1: renamed from eth0 Mar 4 01:01:13 Tower kernel: veth2c67992: renamed from eth0 Mar 4 01:01:14 Tower kernel: veth68e5056: renamed from eth0 Mar 4 01:01:15 Tower kernel: vethb6d5f57: renamed from eth0 Mar 4 01:01:20 Tower kernel: veth0a6f738: renamed from eth0 Mar 4 01:01:26 Tower kernel: veth8afb35f: renamed from eth0 Mar 4 01:01:26 Tower kernel: vethf50f2c4: renamed from eth0 Mar 4 01:01:28 Tower kernel: docker0: port 1(vethd9eada9) entered disabled state Mar 4 01:01:28 Tower kernel: veth7ebc59c: renamed from eth0 Mar 4 01:01:29 Tower kernel: docker0: port 1(vethd9eada9) entered disabled state Mar 4 01:01:29 Tower kernel: device vethd9eada9 left promiscuous mode Mar 4 01:01:29 Tower kernel: docker0: port 1(vethd9eada9) entered disabled state Mar 4 01:01:33 Tower kernel: veth8147789: renamed from eth0 Mar 4 01:01:42 Tower kernel: veth3fb5ef5: renamed from eth0 Mar 4 01:01:44 Tower kernel: vethad0725a: renamed from eth0 Mar 4 01:01:55 Tower kernel: vethd22e44c: renamed from eth0 Mar 4 01:02:10 Tower kernel: vethbe7b9d3: renamed from eth0 Mar 4 01:02:11 Tower kernel: docker0: port 1(veth1c51ad7) entered blocking state Mar 4 01:02:11 Tower kernel: docker0: port 1(veth1c51ad7) entered disabled state Mar 4 01:02:11 Tower kernel: device veth1c51ad7 entered promiscuous mode Mar 4 01:02:14 Tower kernel: eth0: renamed from veth4422939 Mar 4 01:02:14 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1c51ad7: link becomes ready Mar 4 01:02:14 Tower kernel: docker0: port 1(veth1c51ad7) entered blocking state Mar 4 01:02:14 Tower kernel: docker0: port 1(veth1c51ad7) entered forwarding state Mar 4 01:02:17 Tower kernel: eth0: renamed from veth4d295c1 Mar 4 01:02:17 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:19 Tower kernel: eth0: renamed from vethff47134 Mar 4 01:02:19 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:22 Tower kernel: eth0: renamed from veth6398c38 Mar 4 01:02:22 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:27 Tower kernel: eth0: renamed from veth64e7d71 Mar 4 01:02:27 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:31 Tower kernel: eth0: renamed from veth04c1a21 Mar 4 01:02:31 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:34 Tower kernel: eth0: renamed from veth3d1be86 Mar 4 01:02:34 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:37 Tower kernel: eth0: renamed from veth11676dd Mar 4 01:02:37 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:41 Tower kernel: eth0: renamed from vethd3fa0d0 Mar 4 01:02:41 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:44 Tower kernel: eth0: renamed from veth2fe8a48 Mar 4 01:02:44 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:47 Tower kernel: eth0: renamed from vethf6a7292 Mar 4 01:02:47 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:51 Tower kernel: eth0: renamed from veth09e4ce5 Mar 4 01:02:51 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:54 Tower kernel: eth0: renamed from veth3a4776a Mar 4 01:02:54 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:02:58 Tower kernel: eth0: renamed from veth6ca1441 Mar 4 01:02:58 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:02 Tower kernel: eth0: renamed from veth5a641ad Mar 4 01:03:02 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:05 Tower kernel: eth0: renamed from veth6702d54 Mar 4 01:03:05 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:09 Tower kernel: eth0: renamed from veth45a5fdc Mar 4 01:03:09 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:13 Tower kernel: eth0: renamed from veth8ead0f1 Mar 4 01:03:13 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:17 Tower kernel: eth0: renamed from vethd7596cf Mar 4 01:03:17 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 4 01:03:25 Tower kernel: eth0: renamed from veth81bff7d Mar 4 01:03:25 Tower kernel: 8021q: adding VLAN 0 to HW filter on device eth0

Thanks a lot for the support - what ist the best way to replace it. Rather to rebuild by parity or other way.

here is the reporttower-smart-20240215-1856.zip

hi, I did the test and the result looks quite positive. Any idea what happened or what to do?

Hello together, Since a crash of my server I have some read errors on my second HDD. Could someone help me to solve it? tower-diagnostics-20240214-2220.zip