OrangeLoon

Members
  • Posts

    43
  • Joined

  • Last visited

Everything posted by OrangeLoon

  1. Forgive my ignorance but where how do you get to the setting ArturN showed above?
  2. Yeah, I have Syslog Server set up because I need to to diagnostics across multiple devices. I was hoping there was a tool (with the cool color highlights based on errors, etc.). Thanks for the replies.
  3. I enabled syslog (which is running well) and, I had expected a Syslog Viewer to be available on the Tools page but I did not see one. Is there a Syslog Viewer? Running Version 6.9.2 2021-04-07.
  4. Thanks! That's what I was missing. Sometimes it's painful when you don't know what you don't know. [2022-06-30 11:36:57] frigate.edgetpu INFO : Attempting to load TPU as usb [2022-06-30 11:37:00] frigate.edgetpu INFO : TPU found
  5. Thanks for the reply, yayitazale. To clarify, I just want to know if Frigate is using the USB TPU or not. I do not see any errors in the log and no real difference between having the TPU plugged in, restarted Frigate, and pulling it out and restart. Not sure what I am looking for. This is the log with the TPU plugged in and Frigate restarted: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [2022-06-30 08:22:35] frigate.app INFO : Starting Frigate (0.10.1-83481af) Starting migrations [2022-06-30 08:22:35] peewee_migrate INFO : Starting migrations There is nothing to migrate [2022-06-30 08:22:35] peewee_migrate INFO : There is nothing to migrate [2022-06-30 08:22:35] frigate.app INFO : Output process started: 225 [2022-06-30 08:22:35] frigate.app INFO : Camera processor started for Front_Yard: 227 [2022-06-30 08:22:35] detector.cpu INFO : Starting detection process: 223 [2022-06-30 08:22:35] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2022-06-30 08:22:35] frigate.app INFO : Camera processor started for Front_Entry: 228 [2022-06-30 08:22:35] frigate.app INFO : Capture process started for Front_Yard: 230 [2022-06-30 08:22:35] ws4py INFO : Using epoll [2022-06-30 08:22:35] frigate.app INFO : Capture process started for Front_Entry: 232 [2022-06-30 08:22:35] ws4py INFO : Using epoll [2022-06-30 08:22:42] frigate.record WARNING : Discarding a corrupt recording segment: {'cache_path': '/tmp/cache/Front_Yard-20220630082047.mp4', 'start_time': datetime.datetime(2022, 6, 30, 8, 20, 47)} [2022-06-30 08:22:43] frigate.record WARNING : Discarding a corrupt recording segment: {'cache_path': '/tmp/cache/Front_Yard-20220630082047.mp4', 'start_time': datetime.datetime(2022, 6, 30, 8, 20, 47)}
  6. Education request. I have a Coral USB TPU. When it's plug into the Unraid server (6.9.2) it shows up in the system device list as "Bus 002 Device 003:ID 1a6e:089a Global Unichip Corp." In the Frigate setup I have the TPU Mapping set to: /dev/bus/usb Bottom line is I can't tell the difference between when the Coral TPU is plugged in and when it's not. I am running a Intel® Core™ i5-7400 CPU @ 3.00GHz and all 4 CPU's are always in the high 90's. What should I see or more to the point, how to tell the TPU is working? GSN
  7. Hi - quasi-nubie here. (read: I know enough about unraid to get things done but just.) Running UNRAID: Version 6.9.2 2021-04-07 Base distro: docker: version 20.10.5 fuse3: version 3.10.2 nginx: version 1.19.9 samba: verson 4.12.14 (CVE-2020-27840 CVE-2020-27840) Linux kernel: version 5.10.28 include all CONFIG_NF_* modules oot: realtek r8125: version 9.005.01 I have a Coral USB TPU and I installed the Coral plugin (error free). From the system log: When I go to the Coral plug in I get this: Might I trouble y'all for a hint? Thanks GSN
  8. Hello, I am finding the following in my syslog: "Nov 15 03:27:03 PRETTYBOY kernel: Plex Media Scan[26396]: segfault at 10 ip 00001538e28f47ca sp 00001538ddb0f888 error 4 in ld-musl-x86_64.so.1[1538e28e4000+53000] Any idea why?
  9. I had used these when testing with an external drive. I removed the two Unassigned Devices plugs the memory issues have not reoccur over the last two nights. I'm calling this one done. Thanks everyone for the help.
  10. root@PRETTYBOY:~# ls -al /mnt total 16 drwxr-xr-x 14 root root 280 Oct 21 21:44 ./ drwxr-xr-x 20 root root 460 Nov 11 08:58 ../ drwxrwxrwx 1 nobody users 44 Nov 11 08:55 cache/ drwxrwxrwx 5 nobody users 63 Nov 11 04:40 disk1/ drwxrwxrwx 4 nobody users 45 Nov 11 08:57 disk2/ drwxrwxrwx 3 nobody users 19 Nov 11 04:40 disk3/ drwxrwxrwx 3 nobody users 19 Nov 11 04:40 disk4/ drwxrwxrwx 4 nobody users 45 Nov 11 04:40 disk5/ drwxrwxrwx 3 nobody users 19 Nov 11 04:40 disk6/ drwxrwxrwx 3 nobody users 19 Nov 11 04:40 disk7/ drwxrwxrwt 2 nobody users 40 Oct 21 21:40 disks/ drwxrwxrwt 2 nobody users 40 Oct 21 21:40 remotes/ drwxrwxrwx 1 nobody users 63 Nov 11 08:57 user/ drwxrwxrwx 1 nobody users 63 Nov 11 08:57 user0/ root@PRETTYBOY:~# root@PRETTYBOY:~# ls -al /mnt/user total 0 drwxrwxrwx 1 nobody users 63 Nov 11 08:57 ./ drwxr-xr-x 14 root root 280 Oct 21 21:44 ../ drwxrwxrwx 1 nobody users 18 Jun 10 2020 .Trash-99/ drwxrwxrwx 1 nobody users 6 Aug 30 22:52 Backup/ drwxrwxrwx 1 nobody users 62 Sep 1 11:10 Media/ drwxrwxrwx 1 nobody users 156 Nov 4 06:45 appdata/ drwxrwxrwx 1 nobody users 26 May 11 2021 system/ Per a request from Frank1940
  11. Interesting. I have 8 physical drives (parity + 7 data). I had a few shares listed in the shares tab and removed the ones that I know are no longer used, leaving me with appdata, Media, Backups, and system shares. Reran diagnostics and it shows a total of 13. No freakin' idea why or how to get rid of them or how they got there.
  12. Update: I have removed all dockers, disabled Mover, and still have the memory error. No idea why.
  13. Removed all dockers and still getting memory errors. Here is the log for the 2 days: Nov 4 16:01:11 PRETTYBOY sSMTP[8950]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=612 Nov 4 16:04:46 PRETTYBOY sSMTP[10142]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=696 Nov 5 00:00:27 PRETTYBOY root: /var/lib/docker: 12.8 GiB (13726203904 bytes) trimmed on /dev/loop2 Nov 5 00:00:27 PRETTYBOY root: /mnt/cache: 38.3 GiB (41159491584 bytes) trimmed on /dev/sdb1 Nov 5 00:10:07 PRETTYBOY sSMTP[31193]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=733 Nov 5 00:10:09 PRETTYBOY sSMTP[31233]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=725 Nov 5 00:20:03 PRETTYBOY sSMTP[1310]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=1480 Nov 5 03:00:01 PRETTYBOY Plugin Auto Update: Checking for available plugin updates Nov 5 03:00:04 PRETTYBOY Plugin Auto Update: community.applications.plg version 2021.11.04 does not meet age requirements to update Nov 5 03:00:04 PRETTYBOY Plugin Auto Update: unassigned.devices.plg version 2021.11.04 does not meet age requirements to update Nov 5 03:00:04 PRETTYBOY Plugin Auto Update: Checking for language updates Nov 5 03:00:05 PRETTYBOY Plugin Auto Update: Community Applications Plugin Auto Update finished Nov 5 03:40:16 PRETTYBOY crond[1694]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Nov 5 04:15:01 PRETTYBOY Docker Auto Update: Community Applications Docker Autoupdate running Nov 5 04:15:01 PRETTYBOY Docker Auto Update: Checking for available updates Nov 5 04:15:01 PRETTYBOY Docker Auto Update: No updates will be installed Nov 5 04:40:01 PRETTYBOY root: Fix Common Problems Version 2021.08.05 Nov 5 04:40:02 PRETTYBOY root: Fix Common Problems: Warning: unRaids built in FTP server is running Nov 5 04:40:07 PRETTYBOY root: Fix Common Problems: Error: Out Of Memory errors detected on your server Nov 5 04:40:08 PRETTYBOY root: Fix Common Problems: Warning: Write Cache is disabled on disk6 ** Ignored Nov 5 04:40:08 PRETTYBOY root: Fix Common Problems: Warning: Write Cache is disabled on disk7 ** Ignored Nov 5 04:40:11 PRETTYBOY sSMTP[4247]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=888 Nov 5 21:50:53 PRETTYBOY webGUI: Successful login user root from 192.168.3.33 Nov 6 00:00:22 PRETTYBOY root: /var/lib/docker: 9.8 GiB (10512777216 bytes) trimmed on /dev/loop2 Nov 6 00:00:22 PRETTYBOY root: /mnt/cache: 52.5 GiB (56403001344 bytes) trimmed on /dev/sdb1 Nov 6 00:10:07 PRETTYBOY sSMTP[12375]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=733 Nov 6 00:20:03 PRETTYBOY sSMTP[14826]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=1480 Nov 6 03:00:01 PRETTYBOY Plugin Auto Update: Checking for available plugin updates Nov 6 03:00:04 PRETTYBOY Plugin Auto Update: community.applications.plg version 2021.11.05 does not meet age requirements to update Nov 6 03:00:04 PRETTYBOY Plugin Auto Update: unassigned.devices.plg version 2021.11.04 does not meet age requirements to update Nov 6 03:00:04 PRETTYBOY Plugin Auto Update: Checking for language updates Nov 6 03:00:04 PRETTYBOY Plugin Auto Update: Community Applications Plugin Auto Update finished Nov 6 03:40:16 PRETTYBOY crond[1694]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Nov 6 04:15:01 PRETTYBOY Docker Auto Update: Community Applications Docker Autoupdate running Nov 6 04:15:01 PRETTYBOY Docker Auto Update: Checking for available updates Nov 6 04:15:01 PRETTYBOY Docker Auto Update: No updates will be installed Nov 6 04:40:01 PRETTYBOY root: Fix Common Problems Version 2021.08.05 Nov 6 04:40:02 PRETTYBOY root: Fix Common Problems: Warning: unRaids built in FTP server is running Nov 6 04:40:07 PRETTYBOY root: Fix Common Problems: Error: Out Of Memory errors detected on your server Nov 6 04:40:08 PRETTYBOY root: Fix Common Problems: Warning: Write Cache is disabled on disk6 ** Ignored Nov 6 04:40:08 PRETTYBOY root: Fix Common Problems: Warning: Write Cache is disabled on disk7 ** Ignored Nov 6 04:40:12 PRETTYBOY sSMTP[14984]: Sent mail for [email protected] (221 2.0.0 Bye) uid=0 username=root outbytes=888 Really the only things left running is NUT and I use the system as backup storage. The backup process is this: the Home Assistant, running on a separate computer, performs backup at 1:00AM and copies the backup to the Unraid system (about 107,000 KB) in a non-cached share, keeping only the latest 3 versions. That process takes about a minute. There is a windows 10 system (192.168.3.33), which is always mapped to my media share (non-cached), and every night at 2:00 AM, the windows system copies the newly written backup to a local drive - so a backup of a backup. Overkill but it makes me happy. I believe that's it. disabling the HA backup for today, and if the memory error persist, then the windows access, then I go find more to disable.
  14. Thanks for the replies. Regarding the 0G docker.img - I originally had Home Assistant running also when the memory errors started. One older posting suggested a larger docker.img. Enlarged it - same error. Moved Home Assistant off and didn't set the size back. I can see where zm is running out of memory e.b.: Out of memory: Killed process 7453 (zmc) but that occurred on the Oct 29th and I stopped all dockers on the morning of Nov 2nd and still had the memory error. When doing some problem analysis in the past I stopped zm for 24 hours and the memory error then occurred on Plex. So I stopped them both and still had the error. Hence the posting. Plex's error - yeah, not found a solution yet because the memory issue took priority - of course they could be related. I'll look at the plug-ins. Most likely I didn't configure something. Thanks again. I'll be back with an update in a day or so. GSN
  15. I have been getting out of memory errors daily for several months. Once in a while they disappear for a day or so then come back. I turned off all dockers and have no VM's running. I usually have only two dockers running: ZoneMinder and Plex - both turn off since yesterday. Any next step suggestions would be appreciated. Unraid Ver: Version: 6.9.2 prettyboy-diagnostics-20211103-0548.zip
  16. Unraid: Version: 6.9.2. When I go into the Unraid console and try the 'setcap' command (sudo setcap) I get 'setcap: command not found'. Seems 'setcap' is not available on my installation of Unraid so I have to ask: should setcap be available on Unraid?
  17. I found out the single quote character is incorrect. Once corrected I get the following error: sudo setcap 'cap_net_raw,cap_net_admin+eip' 'readlink -f /usr/bin/python3' sudo: setcap: command not found
  18. I am running Home Assistant on Unraid 6.9.2 and one of the components requires that I grant permissions for Python to have rootless access to the HCI interface. Being the newbie that I am, I do not know how to do that. Specifically, the installation of the component requires this line: sudo setcap 'cap_net_raw,cap_net_admin+eip' `readlink -f \`which python3\`` I know the folder for python3 but I don't understand the setcap parameters. In unraid when I specify "sudo getcap `readlink -f \usr\bin\python3\`" I get a '>'. Lost past this - Might I trouble the audience for a solution please?
  19. Hi, Partial-nubie here and I am a bit confused on the storage paths. First off, my system is up and running but I need a bit of education. My docker path: But when I look in Storage under Options in the Zoneminder it has this (which does not exist - leastwise according to krusader): If I put the Docker data path "/mnt/user/Media/Zoneminder/" as the Default in Options I get errors: So the system is working but I have no idea how. Here is the actual paths (cache & shares) according to krusader: So the question is: is the value in Options => Storage => Default correct or should it match the data path and what the hades is the path in the Default? OrangeLoon
  20. Yep - that takes me to "[support] dlandon - Zoneminder 1.34 - Docker Containers - Unraid" but there is no "New Topic" button available.
  21. Hi, Partial-nubie here and I am a bit confused on the storage paths. First off, my system is up and running but I need a bit of education. My docker path: But when I look in Storage under Options in the Zoneminder it has this (which does not exist - leastwise according to krusader): If I put the Docker data path "/mnt/user/Media/Zoneminder/" as the Default in Options I get errors: So the system is working but I have no idea how. Here is the actual paths (cache & shares) according to krusader: So the question is: is the value in Options => Storage => Default correct or should it match the data path and what the hades is the path in the Default?
  22. Many TB of data moved so swapping out the power supply seems to solve the problem! Thanks for the help.