Jonwork88

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by Jonwork88

  1. I am having the same issue - the Redis container is being rebooted as part of this. When I try to follow the directions and run the command 'sysctl vm.overcommit_memory=1' in the container terminal I get the following response 'sysctl: setting key "vm.overcommit_memory": Read-only file system'. I also can't seem to find the files for Redis within my "AppData" share so I can't modify /etc/sysctl.conf either. Any suggestions? Thanks!
  2. For those who updated to V0.9.2 from 0.9.1 and found their config.yml file was no longer valid.... In V0.9.1, I didn't have RTMP included in my config.yml and I would get an error "Camera (camera name) has rtmp enabled, but rtmp is not assigned to an input." but it would still work fine. With the change to V0.9.2, it no longer works - lists it as a configuration error and shuts down the docker. Under each camera section, I added the lines below that seemed to fix it. I no longer get the error in my logs and frigate is working fine again. "rtmp:" should line up with your "ffmpeg", "detect", "record" etc. You'll need the below lines for every camera. rtmp: enabled: false Here is the error message I was getting in my logs - again - solved with the above yml code. Camera deck has rtmp enabled, but rtmp is not assigned to an input. (type=value_error) ************************************************************* *** End Config Validation Errors *** ************************************************************* [cmd] python3 exited 1 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
  3. @JonathanM - thanks for the explanation. I recognize that you can't guarantee anything, but should this be a safe update to make? This is all I could find about it (https://github.com/linuxserver/docker-unifi-controller/releases)
  4. I have also been on 6.4.54 for a few weeks and everything is fine. However, for the first time I can remember, Unraid is telling me there is a docker update ready - I thought I wouldn't receive these if I set a tag? Or is it possible this is an update to 6.5.54? Here is the tag I am using on my docker: linuxserver/unifi-controller:version-6.4.54 Thanks in advance for any feedback.
  5. Thanks for taking the plunge for the rest of us - I'm holding off until I see some feedback
  6. @Salotz - Thanks for the tip - I'm a newbie and this specific issue is killing me, I have been unable to get a synced folder on my desktop to save to shares on my array (and vice versa - share to desktop). So just setting the default path to /media would enable files from a synced folder from my desktop to sync to a share on my array? For example, a synced folder at C:\Users\Name\Documents\sync from my desktop computer that I sync with my unraid server should save to /mnt/user/sync? Thanks Salotz... and Binhex - love your Containers, thanks for everything you do. Thanks!
  7. I also struggle with how to properly backup a VM. The CA Backup/Restore AppData plugin is great for Dockers, would love to see something similar for VMs or as asked by Newbie - a clear guide on what files/folders to backup in order to do a proper config/settings etc backup including instructions on how to restore if needed. I recently had some errors on my cache drive and I am troubleshooting, and have backed up my appdata, but would like to be able to ensure my Home Assistant VM is recoverable as well. Really appreciate everyone's contributions by the way - love Unraid!!