repomanz

I have same issue here: deleted app and image, re-installed from community apps. @dlandon any suggestions? I was not running a separate db previously. My configuration is with GPU enabled hardware. ** edit: i see in previous page to update size of shm - going to make it 10G to see if that works.

quick question about the GPU enabled container. I changed cpu pinning on the container today and it appears to have started an install again. Do I need to run the ./opencv.sh script again?

did you run this after compile/building step? (21% building atm)

yes - my plex container works fine. I am going back through all steps again as I figured i screwed up something somewhere. Currently running ./opencv.sh again and hoping for different result this time (changed the deb file versions for this process).

ok -so regardless of opencv with or without gpu support i should still see my graphics card? I believe I have everything setup properly in the container (got the run time added, go the two variables added). Is there some kind of debugging I can enable to figure out why my graphics card isn't seen by zoneminder? as you can see a few posts above are my settings, even showing gpu is working with plex container. The script displays the gpu if it's seen or not then echos yes into the opencv_ok file if you continue. My GPU is missing oddly.

trying this now. Can you add this point in your GPU support section of the first post? Also given the ES 6x changes, may also want to point out the yolo configuration attribute "object_processor=gpu # or cpu"

@dlandon - I was curious if the order in the two nvidia variables was to blame. When watching the re-install after updating parameters I noticed this:

yes

Working on recompiling with GPU support. I've added the two variables mentioned in the link GPU thread @dlandon include in his GPU support section of the first post. How can I tell if the ZM container sees the graphics card? I don't see any ZM related GPU processes using "watch nvidia-smi". Is there another method? Could this be related to my monitor settings (moddetect/nodetect)? ** update ** I guess I have some other problem here. Towards the end of the opencv.sh script +-----------------------------------------------------------------------------+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=============================================================================| +-----------------------------------------------------------------------------+ ################################################################################## Verify your Nvidia GPU is seen and the driver is loaded. If not, stop the script and fix the problem. plex related container working fine:

Hey @dlandon, Apologies, about 4.3 (not working) I noticed you updated to opencv 4.5 yesterday. Just confirming back to you that yolov4 is working with opencv 4.5. Thanks for the support!

Hey @dlandon Is it possible to update to opencv4.3 in the container? I was wanting to use yolov4 but the opencv version is 4.2 (not supported). https://zmeventnotification.readthedocs.io/en/latest/guides/breaking.html " Version 5.15.6 onwards .... If you plan to use YoloV4 (full or Tiny) the minimum version requirement is the version after 4.3.0. As of Jul 11,2020, that is the master branch of openCV as 4.3.0 is the latest stable version. The updated version of YoloV4 that requires certain functions that were committed on Apr 30. See here. So if you suddently see an error like: Unsupported activation: mish in function 'ReadDarknetFromCfgStream' popping up with YoloV4, that is a sign that you need to get a later version of OpenCV. Note that TinyYoloV4 was merged after Jul 6, so if you get errors with TinyYoloV4, you’ll need to upgrade Open CV master. .... "

totally missed that previously. Updated now think we're all good here.

That's correct. My previous SSD started reporting reported uncorrected errors, within 6 hours the drive was completely dead. Do you have any tips on how to properly backup the VM lib and docker img files (basically containers and vm information)? I'm already using the plugin that backs up appdata (which i restored from).

my steps above are correct, right? Also what does this mean? Total to scrub is bad or just a metric? Ran brtfs scrub previously; came back with no errors.

guess i needed a step 7. reboot. Don't see the errors in my logs anymore. attaching diags.

ok - i'm guessing I did something wrong then. I had an ssd (formerly sdg - sandisk) that crashed. 1) shutdown system 2) removed bad ssd 3) added new ssd 4) brought up system 5) stopped array 6) changed cache to the new samsung ssd Did I do something wrong here?

output of this btrfs dev stats /mnt/cache root@cybertron:~# btrfs dev stats /mnt/cache [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs 0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 0 [/dev/sdg1].generation_errs 0 I can't find it again but when was reading could be a kernel bug for read ahead?

Aug 2 21:29:56 cybertron kernel: BTRFS error (device sdi1): bdev /dev/sdi1 errs: wr 0, rd 62020, flush 0, corrupt 0, gen 0 Hey Unraid team - can you tell me what this is about? New samsung ssd 1tb drive. Ran a btrfs scrub, no errors. Smart also not reporting any issues.

Hi binhex. Where is this set within the xml during install? For my own clarity is that running as root within the container or root under unraid os?

@Djoss just wanted to make sure you got this notice today. Please note the path changes coming up in the next version. Not sure if this will break our current container installs or not. https://support.code42.com/Administrator/Small_Business/Troubleshooting/Code42_app_version_8.2.0_changes_for_Small_Business repo

That's good enough for me, was thinking with the changes to unraid would have opened up a few doors. Didn't realize there was other things like licensing going on.

I was secretly hoping you'd add docker config to make it 'easymode'.

@dlandon Hey dlandon, with unraid's announcement of making nvidia's drivers native to the unraid OS, do you plan on aligning to this change for those that want to use GPU to configure this as part of the base install (similar to your ML/ES configuration?) repo

Thanks for the consideration!

Never seen this one before: I have an IP entered as well as port defined but they are not showing up in UI. Further; getting into console of container, i can't ping anything either. What can i look at to fix? I've stopped all containers, disabled docker and brought back up with no changes.