Merijeek

Well, that didn't help much. Near as I can tell, everything either ends up as: drwxrwxrwx 1 nobody users and is fine, or ends up: drwxr-xr-x 1 root root Which means I can't do anything with it via Windows, though I can do it from UnRAID CLI since, obviously, I'm logged in as root. After running the "New Permissions" tool those same folders are: drwxrwxrwx 1 nobody users

I had a few credentials I deleted just to be thorough, but there were none for the Unraid server. All my shares are, for the moment, public shares, so I never get asked for credentials. I'm waiting on Sickrage to download something, at which point I'll see who that file's owner is.

The ones that were added by me via the AutoAdd. The Sickrage ones are fine.

Hi all - I was just pursuing this in the general support thread and was told I should look here. I've basically got an issue with DelugeVPN. There are two ways I get torrents into it - via Sickrage, or via me dumping a .torrent file into an auto add folder. Both of these work as they should. If it's a torrent that has been inserted by Sickrage, everything works perfectly. Torrents come in, files go out into the proper media directories. Only complaint here is that Sickrage doesn't seem to know how to let a torrent sit a bit before moving it away, which obviously breaks the seeding. However, the BIG problem is just plain torrent downloads. After the download is complete, and I want to move the file (via Windows), I can't. I get a "You require permission from UNRAID\root to make changes to this file". Checking the file ownership I'm getting: Any suggestions on how I can make these files not owned by root? Currently, I'm having to go under Tools and do the "New Permissions" command. Which works, but is obviously annoying.

Allrighty, I guess I'll give it a shot on their support threads, then. Thanks for the help guys.

OK, so, here's what I get. A file that was downloaded via DelugeVPN (but not involving Sickrage): However, from a Windows machine I can copy the folder, and when I do I can do whatever I want with it, and the permissions are: So, clearly what we're looking at is that root is the owner when I'm using DeluveVPN-not-Sickrage. But I don't have any idea how to get around that.

I guess getting a more detailed listing of the file in question when it happens again to determine owner would be the smartest thing? Or is there something else that I should also check when the time comes?

Yes, definitely complete and no torrent has been deleted out of DelugeVPN. Keep in mind the error isn't a file in use error, it's a lack of permissions error.

No, some are just torrents I've manually retrieved with DelugeVPN. I have noticed, FWIW (probably not much) that stuff that Sickrage is responsible for is successfully getting moved automatically from the download folder and to the appropriate Sickrage library folder with no issues.

Plex Media Server and CrashPlan (which don't look at that share), binhex's Sickrage and DelugeVPN, and Tonido.

Ah, right. Well, I tried that but could never get it to talk correctly to DelugeVPN. Which was annoying, but I managed to survive my disappointment. So, it's not like I see an option in the docker setup as to how to set default file permissions. So, how can I accomplish that?

Top of my head I can't figure out what CP is, so I'll need you to expand a bit in your explanation.

"You require permission from UNRAID\root to make changes to this file". So far as I've noticed, this only happens when it's a file that was written by binhex's DelugeVPN. If I go under Tools and New Permissions, and let that run, it'll eventually fix it, and I'm good. But this is a regular reoccurring problem. Anyone have a suggestion on how to fix it?

That's what I thought. Thanks for all your help. Maybe I'll be super lucky and the beta will resolve my randomly quitting GUI. I can hope, anyway.

So, assuming I do that, what exactly do I lose? Fact of the matter is that all the possible directories are various user shares...so what do I lose when I wipe and redo the docker.img?

Well, the good news is that I managed to update everything apart from binhex-delugevpn. The somewhat good news is that an attempt to update binhex-delugevpn doesn't seem to have killed my web GUI. The bad news is, when I try to update binhex-delugevpn (which is there and functional), I get: Configuration not found. Was this container created using this plugin?

That's done. I'm now updating my dockers one at a time. I believe it'll be binhex's deluge-vpn that will make things go berserk, if anything does, so I'm saving that one for last...

Alrighty, updated CA and that took care of that. There was an update available for Powerdown so I got that updated as well.

I did, just before you posted. So, I bounced it. And for the hell of it I put myself on the newest beta. Is there anything I can be running to determine what exactly is killing the GUI? ...also, I've now got a screenshot of the weirdness with Apps.

Because I didn't think of it. Also, I'm now two hours into the powerdown script. The drives are presumably unmounted, since none of the dockers or SMB work anymore. I also can't telnet at this point. However, still pinging away.

I did not have the USB key in so that I could move it to this PC so that I could upload the syslog. When I ran the powerdown command I forgot that I had had the USB key in this machine, rather than the unRAID box.

I actually do have that installed - and in a situation like this (where things have gone funny) it doesn't seem to have help. For example, to see if I had it installed (I thought I had, wanted to make sure), I just ran powerdown, expecting a list of command line switches. And I get this: root@UnRAID:~# powerdown Powerdown initiated mkdir: cannot create directory ‘/boot/logs/’: Input/output error Powerdown V2.20 mkdir: cannot create directory ‘/boot/logs/’: Input/output error Capture diagnostics to /boot/logs Starting diagnostics collection... mkdir: cannot create directory ‘/boot/logs’: Input/output error done. ZIP file '/boot/logs/unraid-diagnostics-20160508-0746.zip' created. mkdir: cannot create directory ‘/boot/logs/’: Input/output error mkdir: cannot create directory ‘/boot/logs/’: Input/output error Broadcast message from root@UnRAID (pts/0) (Sun May 8 07:46:53 2016): The system is going down for system halt NOW! ^C I didn't have the USB key in, which explains the error messages you see. After 15 minutes I have finally lost SMB, but it's still pinging away.

I am having an issue where my system seems to run just fine, and then, poof, GUI becomes inaccessible. I've seen what seem to be two flavors of this. The first seems to involve Docker. I'll try to update or stop a container, and it will hang. From then, GUI is inaccessible. However, the GUI of any running dockers respond perfectly normally. Sometimes I can use the CLI to kill or stop the docker processes and get myself through a clean reboot. Sometimes I'm having to do a 'shutdown -n -r now' to get the system to actually reboot. I know this isn't a good thing, but apart from an actual forced power down I don't see any other way around it. As near as I can remember, I have seen this happen ONLY when I had just tried to do something to a Docker container. Which means I can (generally) avoid it, as long as I'm not stopping or updating a container via CLI. When I have this first issue, when I try to access my unRAID box I get an http connection refused. The second flavor of losing the GUI is just...losing the GUI. It happened yesterday around 2040PM or so, when the system hadn't been up for even an hour yet. This is the one I've got the syslog attached for. When I have this second issue, I just get http timeouts when I try to access the box. From a performance perspective, the only thing I've really noticed on the system is that if I (going by memory here since I have no GUI at the moment) go under applications, and try to use one of the default searches, it throws an error that lists about 5 lines of code. Which is obviously not all that helpful without my having the code to share. I've actually got time to work on this issue today, as opposed to my usual schedule, so I am actually try to chase answers instead of just flipping the switch here. Any help is greatly appreciated. unraid-diagnostics-20160508-0726.zip

I seem to have an issue with DelugeVPN refusing to shutdown. I tell it to restart, and it doesn't. I tell it to shut down, it doesn't. I try to kill it via command line, and the command runs and the command line just sits. Further, when I do that it SEEMS (not confirmed 100%) to then knock the GUI offline, and I can't even reboot the unRAID box from the CLI. Anyone seen anything like this? Any idea how I could have something misconfigured here?

This has happened once before, but that time I just flipped the power switch and suffered through a parity recheck. However, now that this is a reoccurring issue I have to take it a bit more seriously. I seem to be having something fairly identical to this issue: http://lime-technology.com/forum/index.php?topic=47549.0 I have telnet access. Via SMB, only /flash is accessible. With Web GUI it seems like I can get to Deluge and that's it. Main GUI refuses connections, as does any Docker apart from Deluge. So...if I do an update to the files on the /flash drive, how can I reboot? If I do a shutdown -r now it says it's rebooting, but it doesn't actually do so. Anyone have any suggestions? NOTE: Just double-checked, and I'm actually already running 6.1.9, so an update may not help me. But still looking for suggestions as far as how to make this device stable again.