Jump to content

dlandon

Community Developer
  • Content Count

    4028
  • Joined

  • Last visited

  • Days Won

    6

dlandon last won the day on September 5

dlandon had the most liked content!

Community Reputation

248 Very Good

6 Followers

About dlandon

Converted

  • Gender
    Male
  • Location
    Cincinnati, Ohio

Recent Profile Visitors

1677 profile views
  1. dlandon

    [support] dlandon - Zoneminder 1.32

    What error do you get? Show me your port mappings:
  2. dlandon

    Use a Network Port for Dockercontainer?

    When you set a static IP address, the ports used will depend on the Docker.
  3. Try this forum https://www.snbforums.com/forums/. Also consider the Merlin firmware. Much improved and great support on this forum.
  4. Your NFS server is going off line. Could be a server or network issue. UD can't do anything if the server goes off line.
  5. dlandon

    [support] dlandon - Zoneminder 1.32

    Because of the recent changes to the image, I recommend going to CA and re-installing the Zoneminder docker with the default template and make any adjustments for your particular situation.
  6. dlandon

    [support] dlandon - Zoneminder 1.32

    It works for me. I suspect your server is not connecting to the Internet. I don't know how Unraid pulls the images from Docker.
  7. dlandon

    [support] dlandon - Zoneminder 1.32

    Security. It's time to move to more secure access. zmNinja is an example of external access and security is getting more important these days. The Docker creates self signed certs for you. I don't understand this. What limit? Yes, any manual changes will be lost when you upgrade. Just use https:// instead of http://. I don't see it as a big deal.
  8. Please change the status to closed. It is not an urgent issue, even though you feel that you need an immediate answer. LT places a lot of importance on urgent issues and an urgent status for this issue is not warranted.
  9. You should close this as a bug, and post in the UD forum for some help.
  10. dlandon

    [support] dlandon - Zoneminder 1.32

    I've updated the Docker and removed insecure access to Zoneminder. You can now only access Zoneminder with https://IP/zm. Be sure to change your zmNinja apps for secure access to your Zoneminder server. Zoneminder version 1.32.3 has been released. When you update your Docker, version 1.32.2 will be updated to 1.32.3.
  11. It looks like your disk(s) have a lot of btrfs errors: Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): forced readonly Dec 9 01:50:08 Highlander kernel: BTRFS: error (device sda1) in btrfs_finish_ordered_io:3074: errno=-5 IO failure Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14581760 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14585856 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14577664 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14594048 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14577664 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14598144 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14581760 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14602240 Dec 9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14581760 Dec 9 01:50:08 Highlander kernel: BTRFS: error (device sda1) in btrfs_finish_ordered_io:3074: errno=-5 IO failure Dec 9 01:50:08 Highlander unassigned.devices: benchmark: shell_exec(/usr/sbin/hdparm -C /dev/sda 2>/dev/null | /bin/grep -c standby) took 106.512354s. Dec 9 01:50:08 Highlander kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Dec 9 01:50:08 Highlander kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 9 01:50:08 Highlander kernel: BTRFS: error (device sda1) in btrfs_run_delayed_refs:3058: errno=-5 IO failure Dec 9 01:50:08 Highlander kernel: BTRFS error (device sda1): pending csums is 21020672 Dec 9 01:50:08 Highlander kernel: usb 3-1: new high-speed USB device number 3 using xhci_hcd Dec 9 01:50:13 Highlander kernel: btrfs_dev_stat_print_on_error: 12786 callbacks suppressed Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555024, rd 11332069, flush 304, corrupt 81, gen 1 Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 1, rd 7704, flush 0, corrupt 0, gen 0 Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555025, rd 11332069, flush 304, corrupt 81, gen 1 Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 2, rd 7704, flush 0, corrupt 0, gen 0 Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555025, rd 11332070, flush 304, corrupt 81, gen 1 Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 2, rd 7705, flush 0, corrupt 0, gen 0 Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555025, rd 11332071, flush 304, corrupt 81, gen 1 Dec 9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 2, rd 7706, flush 0, corrupt 0, gen 0 I can't make any sense of your log with regards to UD, but it appears you have disks with a lot of errors. If the SSD (sda) is on a USB port, you may have port or cable problem.
  12. Maybe, but currently it can cause problems. Correct, but any Docker networking that uses the Unraid IP address can potentially create a conflict. We have some users that are not network savvy. I'd just like to have a way to warn the user or avoid the conflict.
  13. dlandon

    [support] dlandon - ownCloud

    Glad you finally got it going. I hail from the US.
  14. dlandon

    [support] dlandon - ownCloud

    Change the 172.17.0.2:443 to 'localhost'. Like this: