sturgismike

You can do this (its a bit slow on my system, be patient) docker container ls -sa --format 'table {{.Names}}\t{{.Size}}' If you want the full data you can drop the --format part. -s means size, -a means all (so that it will show both active and inactive containers)

You need to collect that stuff and shape it into a battleship. So that its.. naval lint.

If you have your router configured to give it a static IP, then you can leave dhcp on and it'll assign it for you. Also note, that on the screenshot you just posted, it says dns is static, but has no entries. As far as why it won't shut off VMs and docker when you apply... Not sure. I know that way back there were some weird issue in chrome with settings not sticking, but I doubt thats an issue any more. To get around this, you could go to the main tab and stop the array. Wait patiently for it to finish, then when you go to your network settings you should be able to make changes. Then go back and restart the array. Edit: I wonder if your drive issues might be causing issues with VM manager and docker not stopping when you apply.

I think you have dhcp off which would keep it from grabbing the dns settings too. Easy to check. Turn off docker and vms (in settings) then go to network settings and add your router and any other dns resolvers you normally use and see if it solves the install issue. From your log files: USE_DHCP="no" IPADDR="192.168.1.220" NETMASK="255.255.255.0" GATEWAY="192.168.1.1" BONDING="yes" BRIDGING="yes" DNS_SERVER1="..." <-- no dns Also, if you have bonding turned on (other than for fallback) your router would need to support whatever bonding mode you chose. For fallback it doesn't matter. (Think fallback is called "active-backup" in this case)

Looks like you have no dns server. And as pointed out by another, something is up with your drives.

You have to disable docker and vms before you can change your network settings. To do so, go to settings/ docker and turn docker off, then to settings/ vm manager and turn that off. Then you should be able to change your network settings.

I just went into exclusions and added the ip of my unraid server. Its sounding like that isn't it though if you completely disabled BD. For me, this also fixed the issue where cpu usage and "active" things on the dashboard page weren't updating correctly. I think there were recent messages about FF specifically causing problems. You might check a few messages up, also might make sure there isn't another update sitting there. Pretty sure squid did some type of FF specific fix recently.

You might try adding the ip of your unraid server to the exclusions in your antivirus software. My bitdefender causes issues with websockets and I think other AV do also. Despite adding the exclusion here, something in the last few updates (either ca, or unraid itself) have caused the number of screen updates on my system to drop off, but its still better than it was before the exclusion.

If I understand how things work, the available apps are packaged with settings specifically for unraid, and are maintained by unraid users. Nobody has done one for Paperless apparently. In settings, you can turn on "enable additional search results from dockerhub" at which point, you will be able to click the whale at the top of your search results to search dockerhub.

I just tried to hit the link directly and this is the response.. Error 503 Backend unavailable, connection timeout So it does look like its down at the moment.

You have a bunch of disk0 read errors. Might want to check for bad/loose cables to that drive.

Whitelist your server in your AV. Its likely the AV closing the required websockets that were recently implemented causing CPU stats to not display.

If you happen to have bitdefender, you might try momentarily disabling it, then try to do a docker install. If it works, add the ip of your unraid as an exception. (I ended up switching to something other than bitdefender because it became so disagreeable. Which is too bad because it has been my preference for quite a while)

I was doing a simple docker add using the community applications, and not a docker from outside the fold. The only entered repository is https://github.com/limetech/docker-templates I have just tried to updating one of my already installed dockers from the docker tab, and the same issue appears, so i'm now thinking its not CA specific. On the docker tab, I click to update a docker, the overlay that is supposed to show status updates appears, but similar to installing using CA, status updates are few and far between. It was working great, then stopped. My other machine (that is far less capable) still works as expected. Since its starting to appear that it isn't CA based, which forum should I take this to? If I haven't answered a question properly, its most likely that I don't yet have enough knowledge to understand the question. Edit: The only other thing I can think of that I did around the time this started to happen, is I provisioned an ssl cert through limetech, but since everything else is working amazingly well, i'm doubtful that there is a connection.

Thanks to some help, my drive is back up and going. (Thanks all.) Would you mind looking at my initial problem again? To get a better idea of what i'm talking about I slapped a program together so that I could record a container install with on screen timer, and attached diagnostics after completion. Attaching both to this message. First screen update happens after the minute mark, second happens just after the 3 minute mark. 3rd is pretty quick because the screen updates when the install finishes. So basically, 3 total screen updates for a couchDB install. EDIT: Well, the problem isn't on the server, apparently something has recently gone wonky with my system. I've worked around the issue by creating a browser docker that I can use with vnc, and everything works as expected. (Doesn't seem to be browser specific on my windows machine, all browsers behave the same, so i'll be cleaning up and trying to track down the problem) tower-diagnostics-20180310-1120.zip Stack 1520703279 _ 3_10_2018 11_11_30 AM.mp4

Well. One of my disks has just gone into an error state. I'm wondering if the weird delays were because of this impending failure. (Both my data drives are not nas drives, and are pretty old. Luckily my 4tb parity drive is a new acquisition. Time to buy a drive I guess. Off to research about drive replacement procedures, and to ask questions in another forum, but will ask here in this inappropriate place too.. I have enough space on the working drive to accept all the data that would be on the failed one. Is it possible to just remove the failed drive, and rebuild to the remaining drive while I wait for my replacement?

I figured that is what I'd need to do. Hate to move my cache drive to a sata II port, but I'll probably still be better off. (I don't have much using the cache as it is and write directly to the array for the most part, so not that big a loss actually) Thanks much for the tip, and confirmation.

First diagnostic is during a docker add. tower-diagnostics-20180309-1014.zip As i'm typing this, the screen still shows this.. The screen has now updated once so I've added another diagnostic post update. Its currently stuck and non-updating at the following screen. Updates do seem to be coming a bit faster since the server and windows reboot, but its not even remotely comparable to what it was before this started happening. (it has updated once more now, no need to add another pic, you get the gist. Once its done I'll post a final diagnostic.) I have a feeling that I've shot myself in the foot some way, I just don't know how. Still downloading (slow connection, around 4Mbps at the best of times.) Ok, done, and noticed that the last 4 digits of the first two diagnistics are the same. If this is a time tag, does it indicate nothing changed at all in the diags, or that it was less than a minute since the last one? (did I mention its running a little better?) I'm also wondering, I moved all my drives from the onboard controller to a flashed h310, and had a message that trim couldn't be done (I've since disabled the trim schedule while I decide what to do) Is it possible something got corrupted on the ssd that could be causing this? (Its the only other thing I can think of that happened around the same time) Thanks for looking into this! tower-diagnostics-20180309-1014 (2).zip tower-diagnostics-20180309-10373(3).zip

I've been looking for the answer to an issue with no luck, so I guess its time to ask. A few days ago, during a docker install using CA, my internet went down. I didn't realize it at first until I saw that the screen wasn't updating install progress. I gave things way longer than necessary to actually complete or fail, but the screen never updated, and I ended up going to a new tab, then back to apps (once my internet was back.) Just to make sure things were clean I used cleanup appdata and sure enough, there was an 'orphan' there. I removed it and assumed all was ready to try again. Unfortunately, ever since then, something has gone sideways. Doing docker installs does work, but the screen doesn't update properly, though eventually screen updates do occur. It can take 2 to 3 minutes before anything appears on screen (showing completed layers, and layers in progress) at which point there are again no updates for a few minutes. Its frustrating when it seems that a tiny layer is just NOT downloading. I have been forcing myself to just walk away and not look at the screen until the docker install is done, and the screen shows that it is so. I have rebooted, cleaned up appdata (as mentioned) and even used the programmers prayer (finger crossing) but am unsure how to get screen updates working as they should again. (hmm, though it just popped in to my head it might be a good idea to reboot my windows box too.. Perhaps its on my side, rather than server side. Will try that next) Any and all suggestions welcome, and I'll post an update here if I get it working (or if I don't) Oh, and I have a second unraid that I fired up and it does properly update the screen during docker installs, so there is that. EDIT: Nope, restarting my machine had no affect. Doing an install now, and still waiting for the initial screen update.

THANK YOU THANK YOU THANK YOU! (insert a whole bunch more thank yous here) This post has likely saved me from a bunch of hours and frustration, as well as keeping me from pulling my hair out. Thankfully, the ebay seller I got my card from knew enough to direct me to this post.