jj_uk

OK so it's been a while and i've decided to set this up. I've logged in with a VNC client. The google login was there, so i logged in with my google credentials. After that, the screen went black and that's all that's there. Just a black screen. Any ideas? The login was successful becasue I received an email from google me of the login

My unRAID server has a root user, and that has a password. Is that what you mean? http://<ServerIP>:6080/vnc.html is always available without a password.

Is there a way to secure the WebUI ? Having an app as powerful as this that is not behind a password makes me nervous. I only start the app in unRAID when required, but leaving this on by mistake coupled with teenagers is just a disaster waiting to happen. This seems to be the same for most Apps that use VNC. They all appear to be unsecured which is just a bad idea.

This is a syncthing issue, not a docker issue, but thought I'd ask here in case someone has also had this issue: I've just installed Syncthing on 2 unRAID servers. The use-case here is one of the servers is a snapshot backup of the main server. So My main server (sender) sends all data to the other (receiver) unraid server, with versioning enabled. On the sender server, i've given syncthing readonly access to the whole array /sync/ -> /mnt/user/ and on the receiver server, I've created a share, and given syncthing read/write access /sync/ -> /mnt/user/syncthing/ I've created a folder in the GUI as follows: source: /sync/MediaServer/Home Videos send only, no versioning at the moment. Share with receiver server. This fails because the SOURCE is read-only and syncthing attempts to write to the source folder I'm not going to give syncthing read/write access to all my data. It should only need read access to read and send the data to the other server. Anyone know how to do this? Syncthing Error message:

What is the difference between this container and the official plex container? Apart from the great support in this thread, of course.

I restored a DB from a month ago. And also reinstalled plex. Now i see this: I'll have to dig in to my appdata auto-backups to get a DB older than that to try (from offsite storage). I'll update this once i've tried an older DB.

My logs have this in there: Is this what's causing the meta to fail ? I can't restore the DB as I can't find a backup. When i restart plex docker, I see some other errors in the log, but it scrolls past so fast i cant capture it.

Is anyone else having issues with "plex server is not available" from the plex settings, and newly added movies don't download meta, e.g. no cover art etc.? The server is running, i can watch movies, add movies etc, but can't get to the server settings or update any meta.

Sorry, I was referring to the WebUI for Google Music Manager, which this thread also covers. Maybe the author (rix) could start another separate thread for GMM support. How do you access VNC for this container?

How do i get to the webgui for this?

I tried that, and having now done it again, they are clearing. However, the 1st disk is clearing at 143MB/s, the other 5 preclear processes are around 10MB/s. Previously, they all ran at full speed.

The recent update to the preclear plugin seems to have broken it for me. I an trying to "erase and clear" 6 disks. Only one of the disks is actually doing something, the others are stuck with message "Starting...". Thoughts?

Ahh It is the win10 VM stopping the array from stopping. If i stop the VM, then stop the array, the array stops. If I dont stop the VM, so unraid should stop the vm, the array doesn't ever stop. I've installed the guest agent, but it still doesn't stop. Atleast i know know whats causing it.

Squid- sell your plugin to the unRAID team This plugin should come pre-installed with unRAID.

In windows VM CD drive (virtio-win-0.1.1) I have a folder called "guest-agent". Is this the guest tools? In the VMs -> Windows 10 -> Edit, i can't see a shutdown method. The only reference to shutting down VMs I can find is in the "unradi GUI -> Settings -> VM Manager -> Upon host shutdown", and it's already set to Hibernate.

root@tower1:~# lsof /mnt/disk1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME bash 11502 root 0u CHR 136,4 0t0 7 /dev/pts/4 bash 11502 root 1u CHR 136,4 0t0 7 /dev/pts/4 bash 11502 root 2u CHR 136,4 0t0 7 /dev/pts/4 bash 11502 root 255u CHR 136,4 0t0 7 /dev/pts/4 lsof 11620 root 0u CHR 136,4 0t0 7 /dev/pts/4 lsof 11620 root 1u CHR 136,4 0t0 7 /dev/pts/4 lsof 11620 root 2u CHR 136,4 0t0 7 /dev/pts/4 preclear_ 11634 root 0u CHR 136,2 0t0 5 /dev/pts/2 ttyd 12438 root 9u CHR 5,2 0t0 31 /dev/ptmx bash 15944 root 0u CHR 136,2 0t0 5 /dev/pts/2 bash 15944 root 1u CHR 136,2 0t0 5 /dev/pts/2 bash 15944 root 2u CHR 136,2 0t0 5 /dev/pts/2 bash 15944 root 255u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15955 root 0u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15955 root 1u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15964 root 1u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15964 root 2u CHR 136,2 0t0 5 /dev/pts/2 qemu-syst 21174 root 10u CHR 5,2 0t0 31 /dev/ptmx qemu-syst 21174 root 22r REG 254,0 316628992 2166604 /mnt/disk1/isos/virtio-win-0.1.141-1.iso (deleted) qemu-syst 21174 root 23r REG 254,0 316628992 2166604 /mnt/disk1/isos/virtio-win-0.1.141-1.iso (deleted) preclear_ 21632 root 0u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 21632 root 1u CHR 136,2 0t0 5 /dev/pts/2 tmux:\x20 22245 root 7u CHR 5,2 0t0 31 /dev/ptmx tmux:\x20 22245 root 10u CHR 5,2 0t0 31 /dev/ptmx tmux:\x20 22245 root 11u CHR 5,2 0t0 31 /dev/ptmx bash 22246 root 0u CHR 136,1 0t0 4 /dev/pts/1 bash 22246 root 1u CHR 136,1 0t0 4 /dev/pts/1 bash 22246 root 2u CHR 136,1 0t0 4 /dev/pts/1 bash 22246 root 255u CHR 136,1 0t0 4 /dev/pts/1 bash 32057 root 0u CHR 136,3 0t0 6 /dev/pts/3 bash 32057 root 1u CHR 136,3 0t0 6 /dev/pts/3 bash 32057 root 2u CHR 136,3 0t0 6 /dev/pts/3 bash 32057 root 255u CHR 136,3 0t0 6 /dev/pts/3 root@tower1:~# lsof /mnt/cache COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME bash 11502 root 0u CHR 136,4 0t0 7 /dev/pts/4 bash 11502 root 1u CHR 136,4 0t0 7 /dev/pts/4 bash 11502 root 2u CHR 136,4 0t0 7 /dev/pts/4 bash 11502 root 255u CHR 136,4 0t0 7 /dev/pts/4 ttyd 12438 root 9u CHR 5,2 0t0 31 /dev/ptmx bash 15944 root 0u CHR 136,2 0t0 5 /dev/pts/2 bash 15944 root 1u CHR 136,2 0t0 5 /dev/pts/2 bash 15944 root 2u CHR 136,2 0t0 5 /dev/pts/2 bash 15944 root 255u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15955 root 0u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15955 root 1u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15964 root 1u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 15964 root 2u CHR 136,2 0t0 5 /dev/pts/2 sleep 17657 root 0u CHR 136,2 0t0 5 /dev/pts/2 sleep 17657 root 1u CHR 136,2 0t0 5 /dev/pts/2 lsof 17711 root 0u CHR 136,4 0t0 7 /dev/pts/4 lsof 17711 root 1u CHR 136,4 0t0 7 /dev/pts/4 lsof 17711 root 2u CHR 136,4 0t0 7 /dev/pts/4 qemu-syst 21174 root 10u CHR 5,2 0t0 31 /dev/ptmx qemu-syst 21174 root 20u REG 0,33 107374182400 335 /mnt/cache/domains/001 Windows 10/vdisk1.img qemu-syst 21174 root 21u REG 0,33 107374182400 335 /mnt/cache/domains/001 Windows 10/vdisk1.img preclear_ 21632 root 0u CHR 136,2 0t0 5 /dev/pts/2 preclear_ 21632 root 1u CHR 136,2 0t0 5 /dev/pts/2 tmux:\x20 22245 root 7u CHR 5,2 0t0 31 /dev/ptmx tmux:\x20 22245 root 10u CHR 5,2 0t0 31 /dev/ptmx tmux:\x20 22245 root 11u CHR 5,2 0t0 31 /dev/ptmx bash 22246 root 0u CHR 136,1 0t0 4 /dev/pts/1 bash 22246 root 1u CHR 136,1 0t0 4 /dev/pts/1 bash 22246 root 2u CHR 136,1 0t0 4 /dev/pts/1 bash 22246 root 255u CHR 136,1 0t0 4 /dev/pts/1 bash 32057 root 0u CHR 136,3 0t0 6 /dev/pts/3 bash 32057 root 1u CHR 136,3 0t0 6 /dev/pts/3 bash 32057 root 2u CHR 136,3 0t0 6 /dev/pts/3 bash 32057 root 255u CHR 136,3 0t0 6 /dev/pts/3 root@tower1:~# I don't know what to look for? I've just tried to stop the array and again it won't stop.

Would Krusader do this? I was browsing around with krusader earlier, but can't recall what dir I was in. I also used the unraid "Shares -> Browse Files" (right side of share listing) to look into a few folders. Maybe one of the above could cause this?

I've looked in syslog.txt and I see that 'Disk 1' and 'cache' are causing the issue with unmounting: Aug 26 11:08:27 tower1 emhttpd: Unmounting disks... Aug 26 11:08:27 tower1 emhttpd: shcmd (1152): umount /mnt/disk1 Aug 26 11:08:27 tower1 root: umount: /mnt/disk1: target is busy. Aug 26 11:08:27 tower1 emhttpd: shcmd (1152): exit status: 32 Aug 26 11:08:27 tower1 emhttpd: shcmd (1153): umount /mnt/disk2 Aug 26 11:08:27 tower1 kernel: XFS (dm-1): Unmounting Filesystem Aug 26 11:08:27 tower1 emhttpd: shcmd (1154): rmdir /mnt/disk2 Aug 26 11:08:27 tower1 emhttpd: shcmd (1155): umount /mnt/disk3 Aug 26 11:08:27 tower1 kernel: XFS (dm-2): Unmounting Filesystem Aug 26 11:08:27 tower1 emhttpd: shcmd (1156): rmdir /mnt/disk3 Aug 26 11:08:27 tower1 emhttpd: shcmd (1157): umount /mnt/disk4 Aug 26 11:08:27 tower1 kernel: XFS (dm-3): Unmounting Filesystem Aug 26 11:08:27 tower1 emhttpd: shcmd (1158): rmdir /mnt/disk4 Aug 26 11:08:27 tower1 emhttpd: shcmd (1159): umount /mnt/cache Aug 26 11:08:27 tower1 root: umount: /mnt/cache: target is busy. Aug 26 11:08:27 tower1 emhttpd: shcmd (1159): exit status: 32 Aug 26 11:08:27 tower1 emhttpd: Retry unmounting disk share(s)... Aug 26 11:08:32 tower1 emhttpd: Unmounting disks... Aug 26 11:08:32 tower1 emhttpd: shcmd (1160): umount /mnt/disk1 Aug 26 11:08:32 tower1 root: umount: /mnt/disk1: target is busy. Aug 26 11:08:32 tower1 emhttpd: shcmd (1160): exit status: 32 Aug 26 11:08:32 tower1 emhttpd: shcmd (1161): umount /mnt/cache Aug 26 11:08:32 tower1 root: umount: /mnt/cache: target is busy. Aug 26 11:08:32 tower1 emhttpd: shcmd (1161): exit status: 32 Aug 26 11:08:32 tower1 emhttpd: Retry unmounting disk share(s)...

I have CA set to update plugins automaticly, but to wait 3 days before doing so. I've now updated it, thanks!

I rely on Preclear to stress-test new drives with intense read/writes for a week before adding them to the array. /boot/logs/ contains the following files: - tower1-diagnostics-20180826-1137.zip - unbalance.log Do you need these?

I followed the above and turned off docker in settings, but it still didn't stop so I used the GUI to shutdown. It has now restarted and diagnostics are attached. Any ideas? tower1-diagnostics-20180826-1149.zip

Did you solve this? I have the same issue..

ok so I went into the duplicati docker console and did this: apt-get update apt-get install nano and it succeeded. # ls run lock mount s6 systemd utmp Which file is the run file that I need to edit?