dlandon

Click the Help and read while on the UD page.

CA is the right place to get the docker. Please just use the template defaults and get it working before changing things. Show me a screen shot of what happens when you click on the docker WebUI.

Install using the default template. Left click on the Docker icon and select WebUiI. Be sure you are not using port 8443 for Unraid. If you still cannot get it going, post your diagnostics.

Someone should post the solution to this situation on the Home Assistant forum so others can see how to resolve it.

See if this discussion helps: https://github.com/dlandon/zoneminder/issues/17

I saw where this particular log entry came from SMB 1.0 and 2.0, but I guess not. I've been noticing these kinds of log entries showing up lately. Not sure where they are coming from, but I suspect it's from changes being made to samba.

This is how CIFS works and I'm not sure UD can do anything about it. Please post a diagnostics when this happens and I'll see if there is a place I can add a timeout to at least stop the hang.

The best I can tell, this is from the changes lately to samba. Can you only mount the remote devices that use SMB 3.0 and see if the log messages stop? I believe that they are related to SMB 1.0 and SMB 2.0 mounts only.

For those of you having issues with Home Assistant, I would suggest getting a free Let's Encrypt certificate. Install your certificate in the keys/ folder. Be sure to change the keys/ServerName file to your FQDN so the Apache server name will match the certificate.

Because insecure access is no longer available for Zoneminder, you need to switch to secure access - https. I don't know how Home Assistant works, but secure access to a device should not be a problem. Be sure to use the same url you use to access the webui. Zoneminder has a self signed certificate that is used for secure access.

How does Hkme Assistant access Zoneminder?

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

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.

Yes.

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.

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.

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.

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.

You should close this as a bug, and post in the UD forum for some help.

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.

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.

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.

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

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

I don’t remember the :443 on the database ip address. Did you add that?