dlandon

Yes, but they do not get removed unless you delete them.

You are having a lot of USB errors. Jan 6 00:37:18 Olympus kernel: usb 1-3: device descriptor read/64, error -71 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 6 00:37:19 Olympus kernel: usb 1-3: new high-speed USB device number 4 using xhci_hcd Jan 6 00:37:19 Olympus kernel: usb 1-3: device descriptor read/64, error -71 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 6 00:37:20 Olympus kernel: usb usb1-port3: attempt power cycle Jan 6 00:37:20 Olympus kernel: usb 1-3: new high-speed USB device number 5 using xhci_hcd Jan 6 00:37:25 Olympus kernel: usb 1-3: Device not responding to setup address. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 6 00:37:30 Olympus kernel: usb 1-3: device not accepting address 5, error -71 Jan 6 00:37:31 Olympus kernel: usb 1-3: new high-speed USB device number 6 using xhci_hcd Jan 6 00:37:36 Olympus kernel: usb 1-3: Device not responding to setup address. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 6 00:37:41 Olympus kernel: usb 1-3: device not accepting address 6, error -71 Jan 6 00:37:41 Olympus kernel: usb usb1-port3: unable to enumerate USB device Jan 6 00:37:42 Olympus kernel: usb usb1-port5: Cannot enable. Maybe the USB cable is bad? ### [PREVIOUS LINE REPEATED 1 TIMES] ### Jan 6 00:37:43 Olympus kernel: usb usb1-port5: attempt power cycle Jan 6 00:37:45 Olympus kernel: usb usb1-port5: Cannot enable. Maybe the USB cable is bad?

Post diagnostics.

Add more shared memory. It needs to be much lower. Set it to half your installed memory.

ES is updated whenever the Docker is restarted. Go to the 6.1.5 documentation link posted earlier for help with ES.

Go to the Zoneminder forum for help with the database issues. Go to the link posted earlier about ES 6.1.5.

Yep. Fixed in next release.

ES has been upgraded to 6.1.5. You probably need to make some changes. Several posts up is a link to the documentation.

You can always do a restore from your backup.

ES has been updated to 6.1.5. You'll probably need to update your configuration. See the documentation mentioned above for help.

For anyone having issues with ES, this documentation may help: https://zmeventnotification.readthedocs.io/en/latest/guides/hooks.html#understanding-detection-configuration

Log stuff is no longer needed. Go to Docker settings, stop dockers and you'll see:

That's a message from hook processing. I normally turn this off in the zmeventnotification.ini file, but it was left on and causes that message: # send event end notifications (default: no) # Note that if you are using hooks for end notifications, they may change # the final decision. This needs to be yes if you want end notifications with # or without hooks send_event_end_notification = no Be sure it's set to no. For some reason pliablepixels sets it to yes in the ES release.

Building a new docker with a fix. You create the 99-mysql.conf from the zm.default file in the appdata/conf/ folder. The file actually gets copied to /etc/zm/conf.d/ inside the container.

When automount is set, UD will mount it whenever the array is started. You should not have to manually mount it. If you are referring to Unraid as the NAS, UD will never unmount a device unless the array is stopped.

I think this got broken over the last few changes. I'll take a look and update the docker if necessary.

Set php to 7.3.

You don't have a backup to recover?

Looks good.

ES has been updated to 6.1.5. You probably need to make some changes for the newer version.

Works fine for me.

That would be best.

Database issues are difficult. You might try the Zoneminder forums for some help.

Those of you with database issues, it may be due to you restarting the docker and updating Zoneminder in the process. Zoneminder will get updated whenever the docker is restarted if there is a new version of Zoneminder. Part of the update to Zoeminder is an update to the database. If that failed because of the issues with shared memory, the database may have gotten corrupted.

Sorry, I was thinking of another docker of mine.