dlandon

Community Developer
  • Content Count

    6580
  • Joined

  • Last visited

  • Days Won

    10

dlandon last won the day on January 9

dlandon had the most liked content!

Community Reputation

631 Guru

About dlandon

  • Rank
    Advanced Member
  • Birthday 07/31/1946

Converted

  • Gender
    Male
  • Location
    Cincinnati, Ohio

Recent Profile Visitors

7267 profile views
  1. Because of this announcement: https://forums.zoneminder.com/viewtopic.php?t=30996, ES will stop working with ZmNinja after the end of the year. I'll continue this Docker container as best I can without the ES addon, but I'm not sure what value if any it will have.
  2. The lightning icon shows up when there is a script defined. If you want to remove the script, click the three gears icon under 'Settings' and then click the 'Delete' button at the bottom and the script will be removed.
  3. You see the partition information because that is the default when a new device is installed. The lightning icon is there so you can test your device script. It is not meant to imply that you have to click that icon. You'll also find that the mount point can be clicked to browse the device when it is mounted. Click on the three gears icon under the 'Settings' column and turn off the 'Show Partitions' switch. That will collapse the partition.
  4. You can set up a script to run when the drive is installed by clicking on the three gears icon. The lightning icon runs that script just like the drive was first plugged in.
  5. That's probably an issue with Zoneminder, and you should use the Zoneminder forum to get help.
  6. When that happens go here and scroll down to the bottom and follow the instructions when you have a container failure. https://github.com/dlandon/zoneminder.machine.learning Let me know if you can get it going using this method.
  7. ownCloud doesn't just randomly self destruct.
  8. Sounds like a hardware failure.
  9. You'll need to load the driver for the Ryzen 5 processor. I don't have a Ryzen MB, so I can't help. Take a look at this and see if it helps: https://bbs.archlinux.org/viewtopic.php?id=237244
  10. The most common problem with file activity not starting is not enough inotify watches. Look in your log and see if there is a log about not having enough. Several suggestions: Cut down on what you are monitoring. Don't include Unassigned Devices or Cache and Pool devices. Install the Tips and Tweaks plugin and increase the 'Max Watches'.
  11. The serial numbers for both drives are the same. UD has to have unique serial numbers: It doesn't matter that the sdX designations are different.
  12. UD tracks individual disks by the disk serial number. Each disk has to have a unique serial number. Your drive enclosure is probably presenting the complete enclosure with one serial number for all the drives. It doesn't matter that the drives have different sdX designations. UD doesn't track devices by the sdX designation, because they can change at each reboot.