dlandon

I haven't heard any feedback yet from the latest changes to the recycle bin, but I am pleased with the responsiveness of the web page now. I hated the blank white screen when the server was busy and/or there was a large recycle bin. The web page is now very quick to load and if the cron trash size script takes a long time to get the trash sizes, it will only show a '?' for the trash size and not hang the web page. Another advantage is that because the trash size is done every minute, the file references are cached and the disks don't spin up when looking at the recycle bin web page.

The old way of doing things was to find empty .Recycle.Bin directories on the array mount points directly using a find with a wild card to search and delete the folder from the user shares. I never liked this because of the potential of things going wrong and removing things that shouldn't be removed. I do recycle bin operations on a mount point with symlinks to the array and UD .Recycle.Bin folders at /mnt/RecycleBin/. This was created initially for proper file browsing, but now all operations are on this mount point. This will provide at least a little protection if things go awry. The one thing that has come from this is that the share .Recycle.Bin folder will remain after the first file has been deleted from a share. Clicking on the Trash Can icon will show the shares with empty .Recycle.Bin folders, but the 'Shares' tab will only show a share with recycle bin contents. With the addition of the 'Shares' tab and being able to browse the shares individually, I am considering removing the Trash Can icon browse. It is more cumbersome to use and really doesn't offer anything that can't be done in the 'Shares' tab.

Yes.

The .Recycle.Bin folder is no longer deleted when the trash is emptied. Only the contents are removed. If the directory was empty, the recycle bin would not see that any files were deleted and nothing would be saved to the .Recycle.Bin folder.

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Zoneminder' --net='bridge' --log-opt max-size='10m' --log-opt max-file='1' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'SHMEM'='50%' -p '8443:443/tcp' -p '9000:9000/tcp' -v '/mnt/cache/appdata/Zoneminder':'/config':'rw' -v '/mnt/user/appdata/Zoneminder/data':'/var/cache/zoneminder':'rw' --log-opt max-size=50m --log-opt max-file=1 'dlandon/zoneminder' 5f0db268221cf47d66db6f54b2e2bc03293e14af2c1475515dbd0c0887c8e547 The command finished successfully! Works for me. Is your server connected to the Internet? It looks like the docker did not get downloaded.

You cannot format an encrypted drive with UD, but you can read an encrypted drive taken out of the array. Why don't you add the drives to the array and encrypt them? You can then set up disk shares to read/write to those disks. Exclude those drives from all other shares. The advantage is that they will be parity protected.

That appears to be an issue with the sleep plugin. Ud sees the drives just fine.

Ok. I'm good with that.

I would delete the docker container and install it again.

You need to delete the docker image and the appdata folder and start over.

Mariadb is built in to the Docker. You can optionally use an external database. When you start the docker the first time, leave the 'localhost' alone and enter 'owncloud' for all the other fields. You will then be using the internal database. EDIT: Like this:

I've just updated the recycle bin plugin. I've implemented a cron trash size update every minute so the recycle bin UI will be more responsive when you have a busy server with a large recycle bin. You can turn this off if you'd like, but I recommend leaving it on. I did not find that disks would spin up with this cron task running. This will eliminate the dreaded empty page for an extended length of time on busy servers with a large recycle bin. You may at times see a ? in the recycle bin trash size. This indicates that the trash size determination timed out and the size could not be determined in a reasonable amount of time. It still allows all the recycle bin functionality to operate normally. When a file is deleted on a share, it may take up to a minute for the trash size to update and the file to show in the recycle bin. Just refresh the page and the trash size and contents will eventually update.

Yes. Make sure you reference it properly when you set up ownCloud the first time.

Changed Status to Solved

Looks like a database issue. Restore your database from a backup?

Must have been an existing file from earlier rc.

One of the really cool things about the Syslog server is that you can enable it on the server, put the server IP address in the 'Remote syslog server' field and logs will be continuously captured and potentially help with a lockup or unresponsive server situation. I've updated Tips and Tweaks and added this as a Tip. All of you that have servers becoming unresponsive should set this up so you can capture the logs and see if it doesn't help with finding problems.

Remove these lines from the smb-extra.conf. [rootshare] path = /mnt/user comment = browseable = yes # Public public = yes writeable = yes vfs objects = Why are they there? The 'vfs_objects' in particular is probably the one causing the problem. I believe this global setting overrides the share settings, which would turn off the share recycle bin capability.

Really liking the Syslog server feature. Could you sort the list of logs in the Syslog viewer?

Click the + by the device ID and hover your mouse over the mount point. Only if you want to browse it. Go to Settings->Unassigned Devices and set the SMB security. Yes. VMs will shutdown before UD unmounts the disk.

The best way to get an answer it to post in the user scripts plugin forum and someone will help you there. This really isn't the place to get the help you need.

The cron entries are removed by the user scripts plugin when the array is stopped. It's not a problem.

Remove your cron entries on the appropriate array event.