dlandon

How many shares are you trying to exclude? EDIT: I can increase the line length. It is currently set at 100 characters.

Answers: 1. Only the length of the ui input line. Can you do a wild card exclusion? 2. No. Only the complete share. You might be able to exclude the folder in the excluded files. I've not tried that. 3. No. The best source for the additional parameters is the samba documentation.

How do you specify a USB drive to the Docker to use for ripping?

So I guess I'm not being hacked then.

Yes. That is what the IP lookup says. What is it?

I looked up the 23.96.235.188 IP address again and see the ISP is Microsoft, so Plex is probably using a Microsoft server.

Yes. Two Windows 10 VMs for desktop use. As a test I stopped them both and the IP address still showed. Maybe I didn't keep them off long enough.

I have a Plex Docker installed, so this is possible. I allow no access from the WAN to my server IP address. I didn't expect that an outside IP address could access shares. What is it that Active Streams sees that thinks it is a stream IP address?

This is weird and I'd like a little help on what is happening. In Active Streams I see a weird (not LAN) IP address: The 23.96.235.188 IP address is of course not a LAN address. I looked up the IP address and it is a Microsoft Server in Chicago. I have several problems with this: How did this IP address get into my Active Streams? Is this another Microsoft behind the scenes snoop? I don't recall seeing any files being streamed by this IP address. Any ideas on where this is coming from and how it got to my server? Is there a way to block this IP address?

New release of the Recycle Bin plugin. The 'Shares' tab now displays only the shares with Recycle Bin contents. Each share has an 'Empty' button so you can empty the Recycle Bin trash for a single share.

I see one thing pretty obvious. You are loading an older version of the ntfs-3g driver: Jun 20 19:16:09 knox root: +============================================================================== Jun 20 19:16:09 knox root: | Upgrading ntfs-3g-2016.2.22-x86_64-1 package using /boot/packages/ntfs-3g-2015.3.14-x86_64-1.txz Jun 20 19:16:09 knox root: +============================================================================== Remove the ntfs-3g plugin. ntfs-3g is built into unRAID. I also see some disk hard link reset errors: Jun 20 19:39:10 knox kernel: ata1: hard resetting link Jun 20 19:39:10 knox kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 20 19:39:10 knox kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:10 knox kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:10 knox kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:10 knox kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:10 knox kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:10 knox kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:10 knox kernel: ata1.00: configured for UDMA/133 Jun 20 19:39:10 knox kernel: ata1: EH complete Jun 20 19:39:11 knox kernel: ata2: hard resetting link Jun 20 19:39:11 knox kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 20 19:39:11 knox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:11 knox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:11 knox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:11 knox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:11 knox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:11 knox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:11 knox kernel: ata2.00: configured for UDMA/133 Jun 20 19:39:11 knox kernel: ata2: EH complete Jun 20 19:39:12 knox kernel: ata3: hard resetting link Jun 20 19:39:12 knox kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 20 19:39:12 knox kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:12 knox kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:12 knox kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:12 knox kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:12 knox kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:12 knox kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:12 knox kernel: ata3.00: configured for UDMA/133 Jun 20 19:39:12 knox kernel: ata3: EH complete Jun 20 19:39:12 knox kernel: ata4: hard resetting link Jun 20 19:39:13 knox kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 20 19:39:13 knox kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:13 knox kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:13 knox kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:13 knox kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:13 knox kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:13 knox kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:13 knox kernel: ata4.00: configured for UDMA/133 Jun 20 19:39:13 knox kernel: ata4: EH complete Jun 20 19:39:13 knox kernel: ata5: hard resetting link Jun 20 19:39:14 knox kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 20 19:39:14 knox kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:14 knox kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:14 knox kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:14 knox kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:14 knox kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:14 knox kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:14 knox kernel: ata5.00: configured for UDMA/133 Jun 20 19:39:14 knox kernel: ata5: EH complete Jun 20 19:39:14 knox kernel: ata6: hard resetting link Jun 20 19:39:14 knox kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 20 19:39:14 knox kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:14 knox kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:14 knox kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:14 knox kernel: ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 20 19:39:14 knox kernel: ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 20 19:39:14 knox kernel: ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 20 19:39:14 knox kernel: ata6.00: configured for UDMA/133 Jun 20 19:39:14 knox kernel: ata6: EH complete Jun 20 19:39:58 knox emhttp: Spinning down all drives... I'm not a disk expert, so I don't know what these errors mean. Someone more knowledgeable can chime in here. Your /var/log has plenty of space so there is no problem there with UD writing a log.

Yes, the UD log. The log file is at /var/log. It is in the ram file system. You have another problem. Post your diagnostics.

I have no idea. Probably the best thing to do is reboot. The log will tell us what we need.

Click on the view log icon in the upper right on the UD page. Hover your mouse over the icons for a tool tip on what the icon does. See what the log says about why the drive won't mount. It is probably a hardware issue like a cable problem.

It's probably not a good idea to default the 'storage' to /mnt/user. Dockers should not access that area of the the mount points. It would be better to default to the Docker appdata folder. i.e. /mnt/user/appdata/MKVToolNix. The user can make changes from there and they are at least not in the /mnt/user area.

I haven't used cAdvisor for a while, but it did a nice job when I used t. If it's any consolation, I think you made a good choice.

Wow, here in the Midwest of the US of A when a man gets to that point, he throws his baseball cap on the ground. That's serious when that happens! I think you just did that.

Some UD lockups have been reported when remote mounted devices drop off-line. There were some changes made in UD so the UD gui would not get locked up, but there is an underlying problem that I cannot get around. It seems that when a mounted device drops off-line, the 'df' command used to get used and free space from devices locks up. I got around this by not issuing a 'df' command if the remote mounted share is off-line. This is all well and good for UD, but unRAID or any plug issuing the 'df' command when a device has dropped off-line will lock up unRAID. I think this is a very poor design issue in the 'df' command. It should time out or fail if a device is mounted, but drops off-line. EDIT: After doing some research on this issue, it seems that the remote mounting of NFS and CIFS shares is troublesome when the remote share goes off-line and there isn't much that can be done. It appears that the 'hang' that occurs when a remote share is off-line is by design. The 'mount' command used to mount the remote shares in UD uses a 'soft' parameter that is supposed to return errors to the client when the share is accessed and is not available. I'm going to review the unmount code to be sure a 'umount' is forcing the unmount of remote shares so the server does not hang when shutting down.

I've done some updates the the UD web page to be more compatible with the Azure and Gray themes in unRAID 6.4. I also did some alignment so the table elements line up better in all the themes. The UD plugin uses its own style sheets as well as the Dynamix style sheets. The Azure and Gray need some color adjustments, but I am not a style sheet guy. I'm hoping gfjardim can lend a hand. He authored the original UD style sheets. I think I have the colors work out on the spinny thing that shows when UD is busy

Works fine in rc4.

You can only access the webgui with https://. http:// won't work. Use https://Tower:port. Set the port value if you have changed the port from the default.

I don't have a lot of events, so I did not notice any delay. I added a permission check and if not correct, the permissions are corrected. While you had an unusual case, I like the idea of the docker correcting the permissions if they are not correct.

What are you having trouble with?

Let me look into that. That's not a bad idea.

Based on your feedback, I have redone the docker to set permissions and ownership only when the data/ directories are initially created. The downside to this is that if the permissions and/or ownership change, Zoneminder would have the problem you had. Any kind of copying of the data would have to preserve the ownership and permissions. I have moved my data/ storage to the array into a separate share. While this works fine, if the 'New Permissions' script was run on the share I set up for Zoneminder, the permissions would be changed, potentially messing up Zoneminder.