matt0013

Members
  • Posts

    22
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

matt0013's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thank you for your help. Everything seems to be working great now. I did some searching and ended up getting rid of the extended permissions using setfacl -Rb /mnt/user/appdata/zoneminder. That took away the '+' sign that you called my attention to. ACL: Using Access Control Lists on Linux
  2. I did set some permissions with WinSCP a long time ago; not related to Zoneminder though but it may have had an unintended consequence... The issue is currently fixed. I did some things to remove extended permissions and I also updated the docker since I noticed the option was available. Not sure what exactly fixed it, the update or my removing of extended permissions.
  3. Looks like owner was changed. I have HomeAssistant running with no issues. That's the only other active one running.
  4. These were correct. No luck with this. Still have the same errors in the log.
  5. Not sure what this means exactly. How do I set these?
  6. Thanks for helping me troubleshoot this. Here is what I received.
  7. I didn't change any settings. My docker.img is not full and there are no orphaned docker images. Should I have a directory /usr/share/zoneminder in mystem? If I am supposed to, I currently do not.
  8. I deleted the docker and 'appdata/Zoneminder' folder and did another fresh installation. I'm getting the same errors in my log over and over. web_php 8492 ERR Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user /usr/share/zoneminder/www/index.php 159 web_php 8490 ERR disk_total_space returned false. Verify the web account user has access to events /usr/share/zoneminder/www/includes/functions.php 145
  9. I haven't changed any settings. Those errors were generated from a default setting installation. I looked at (didn't change) my zm.conf file and saw these paths which match the errors I'm receiving. Are these correct? # Path to installed data directory, used mostly for finding DB upgrade scripts ZM_PATH_DATA=/usr/share/zoneminder # Path to ZoneMinder web files ZM_PATH_WEB=/usr/share/zoneminder/www
  10. I deleted my old docker and did a fresh installation. I am getting these errors in my log upon startup. Any ideas? Should this path be /usr/share/appdata/zoneminder/www/? 2017-05-28 10:04:24.812157 web_php 8492 ERR Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user /usr/share/zoneminder/www/index.php 159 2017-05-28 10:00:22.938535 web_php 8490 ERR disk_total_space returned false. Verify the web account user has access to events /usr/share/zoneminder/www/includes/functions.php 145
  11. Thank you for this! Very helpful. I have to reinstall the extpack every time my server restarts. Any idea how to prevent that?
  12. Nevermind on the shares questions. I see now that I needed to enable them. I'm still curious why it reset all my settings but if it's not causing any issues I guess it's not a big deal. After the issues I had, if anyone wants to browse my syslog I posted previously and check for potential problems I would really appreciate it. Thanks!
  13. So I was able to restore almost all of my files and re-organized them back into the shares they were in. Thanks for all the help. However, now I have upgraded to 4.5.6 and when I plugged my flash drive back in all of my settings were lost. The server name has gone back to "Tower" and I don't have the ability to create user shares. When I go to the Shares section, there is nothing but white space below the Export Settings box. The Main page looks like it did before (I had to go in and re-assign the drives like the readme instructed) and all my files are viewable in the disk folders. I just can't create shares... I attached my syslog in case that will be any help. syslog.txt
  14. Yes, disk3 is still empty. I am not sure what is going on with this disk. When I started this whole mess, I added disk3 and disk4... disk3 was a 1TB drive originally (disk4 was a 1.5TB drive and works fine). I thought disk3 was a failed disk (appeared red), so I replaced it with a new, 1.5TB drive. It is still red. Maybe this means the cabling or port is defective? I think I have one more SATA port available on the motherboard, should I shut down and plug disk3 into another port? So you are saying I can move from a disk folder to a share folder, right (after I create my shares)? My question/concern here is that the disk folder is one hard drive, but the share folder may be multiple hard drives... Unraid will figure this part out?