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.

Looks like my ups is on 0000:00:1d.1 , and I can unbind it, but as expected, unbinding it makes the ups stop showing up at all. Rebinding brings it back and it starts doing intermittent resets again. So, I'm stumped. As for re-directing the error messages, while they don't show up in the unraid interface any more, they still show up in syslog, so if errors every 30 seconds or so is a bad thing, I do need to find a solution. Worst case, I guess I can hook the ups to a different machine and use it to control shutdown. I did just try to do this using a raspberry pi, but ended up with the same resets going on. So now i'm wondering if I have a bad ups. (I've tried multiple cables, so am pretty sure its not a cabling issue) Guess i'll hook it up to my windows box and see what happens. Thanks for all the input. I do think I will start saving for a replacement server. I'd like better performance anyway, so throwing money at a system that may be going flaky is probably not the best idea. Edit: Managed to unbind using this command.. root@Tower:/sys/bus/pci/drivers/ehci-pci# echo -n "0000:00:1d.7" > unbind The usb still resets, but it has gone from 1 every 20 to 30 seconds to around a minute + between resets. Still no clue how to actually FIX the issue. Any suggestions welcome. 0000:00:1d.7 is the controller in question. The flash drive is on 0000:00:1a.7 so appears unaffected.

I had looked up possibilities on the ups fix, basically what I read said that you could blacklist the hid (ok, so I don't remember exactly which driver it was at the moment) forcing things to run at 1.1 and it would get things working. Unfortunately, the info I found referred to a module, and from what I understand, that module is now part of the kernel, so the instructions I found to blacklist/disable the module no longer apply. I do have some 1.1 ports, but it doesn't seem to matter if I plug into those, or a 2.0. Functionally, the ups mostly works fine (I've tested it several times to make sure) Setting to 30 seconds on UPS triggering a shutdown DOES create false triggers. Since the port reset never takes much more than 30 seconds, I have it set to 60 and have had no issues since. Other than the incredibly annoying message that I don't know how to get rid of. As for the flash, this is the first time I've had an issue with it. The system has pretty much been a rock since I got it going. The reason I wonder about the way I was re-directing to syslog is that it is a a new thing I've been doing, and the system had been up since the 6.6.6 upgrade. Possibly long enough to cause an issue? Honestly, I'd LOVE to figure out how to fix the ups issue, but I just haven't been able to find an answer that I can make work. I'll see if I can re-locate the answer I found, (that I can't make work) and post it here on the off chance someone has an idea.

No usb 3 ports on this system, its old. But that does tell me, if I buy an addon card I should go with usb2. I was also running a couple rPis using usb, as well as having a keyboard and mouse hooked up that never get used, so I have removed everything except the flash drive and the ups. Stupid question.. Since I was getting the usb resets for the UPS, I redirected the messages to syslog (changing the setting to /usr/bin/logger) Works good and keeps me from seeing the errors that I know are there. Is it possible things went haywire because of log overload? After things went wonky I tried a reboot (using unraid) and couldn't boot, but things worked again after a full shutdown and then reboot. I've temporarily redirected those messages to /dev/null instead, so log overload shouldn't be an issue. (I'm hoping I did it right. I set it to go to cat > /dev/null rather than /usr/bin/logger) As long as i'm here, is there a way to make the change stick between boots? I'm not sure how to edit files on the actual flash so that changes stay changed.

I just had a weird issue with my unraid. All screens went white (though they still worked) and on checking logs, there were a ton of "can't find directory" errors regarding sda1 (the flash drive boot partition) I attempted, and failed to restart. No monitor available at the moment, so I couldn't see the console. After shutting down and shifting the drive to a new usb port, everything seemes to be working great again. Boot up was fine, no errors, no problems that I can see at all. My suspicion of course, is that the specific usb port has decided to blow chunks and die. I fear that others may kick the bucket soon, so my question is.. Would it be reasonable to buy a usb card so that I stop using the onboard usb ports, on the assumption that it will solve the issue, or should I worry that a failed port might indicate a motherboard that is thinking about failing. The worry about choice 2 (the motherboard going bad) is not good. My finances are extremely tight, yet I want a decent amount of cores/ability to play with. (currently i'm on a HP z800 with dual 6core cpus, for a total of 24 threads. Not the fastest, but it has worked really well for me) Could anyone recommend an affordable motherboard/cpu combo that would be comparable or better? By affordable I mean 500 or less including memory. (unless I can transfer my z800 memory over) I will probably take a plunge and just get a pci (or pcie, not sure) usb card and cross my fingers, unless you all think its likely that a failure is imminent. I suspect that these messages are a bad sign.. Dec 27 16:07:30 Tower kernel: usb 7-2: reset low-speed USB device number 2 using uhci_hcd Dec 27 16:08:22 Tower kernel: usb 7-2: reset low-speed USB device number 2 using uhci_hcd Device 2 is where my ups is hooked up.

I finally managed to afford a UPS, and chose one from tripp lite. Unfortunately, my system keeps doing low speed usb resets, and I don't know how this will affect the functioning of the ups. I did some research, and learned that it used to be possible to use modprobe and basically force the usb ports to 1.1 bypassing the issue (at the cost of usb speed) but the ehci part of that fix is no longer a module, so its not an option. I don't think the reset is specific to the ups, and have noticed keyboard lights flashing and being reset too. (though not nearly as often I don't think) So first question, does anyone know what might be causing the resets, and how to fix the issue? (or is it not really an issue despite the large number of resets?) If not, I have an alternate idea. I have an orange pi pc not being used, I guess I could hook the ups to it, and have it act as intermediary so that the ups isn't directly cabled (usb) to my unraid box. Is there any issue with this method that i'm not seeing? The machine in question is an HP z800 with the 850 watt power supply. Currently 3.5" drives and an ssd cache drive. Thanks in advance for any help.

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)

Thank you both! On the subject of the ambulance, cost would be prohibitive. The pass through to the drivers side is small, so I'd have to figure out how to get to and from the drivers seat, and then I'd have to have a lift to get the chair in and out. My f250 van has a lift and a 6 way seat making transfers easy. Though I don't need them yet, it also has hand controls. The van is old, but it works far better than the car I had that I could no longer use. I had reached the point where I only got out of the house about 3 times in a 6 month period. Not a fun situation. (thankfully I have good people in my life that help out) We're usually pretty good at finding answers to problems. The most recent being an inability to do tub transfers. (yes we're getting WAY off the unRaid topic here..) After researching lifts/tracks etc through medical supply shops, the answer I would need to solve the problem was going to run around 6k before install costs. (And no, they wont just sell you parts, they insist on installing.) Instead, we rolled our own solution. A small ibeam track, heavy duty trolly, and hoist, with a harness I made myself. Installed the thing ended up costing around 800 for everything, with the added benefit that if I need to, I can change out a car engine in my bathroom if need be. In fact, I used the lift to get my z800 from floor level onto a spare wheeled walker, then used the walker to get the thing into its final position. While I wouldn't call it "fun", but knowing where i'm headed as far as ability goes, it is definitely interesting to plan ahead as much as I can so that I can manage as much as possible on my own for as long as possible. (on my own, but with help to figure things out and implement solutions) I'm attaching a picture of our home grown ceiling lift and the ambulance, in case anyone is curious. Again, thanks to you both. Much to ponder now.

I think you hit it on the nose. For short term (1 day maybe 2) emergency power, I'm set. Longer than that, and I should indeed skedaddle. I had intended setting the ambulance up as a camper for long term, middle of nowhere camping but not long after I bought it and started the project my health took a major turn to the point where I can't even get into the darn thing now. (I now have a van with a wheelchair lift to make me mobile again) ITs too bad, the ambulance is nothing short of awesome. (diesel, electrical already run, so adding the solar was easy enough, tons of storage, already has cabinets etc built in) Perhaps it'd make sense to shift the solar to the van so that I can get back on track as far as camping goes. Not nearly as much space for panels though. (there is room for about 6 more panels on the ambulance roof) Time to consider a "for real" solar system now I guess. (grid tie/hybrid) so that I still have my battery bank for emergencies. Guess its time also to think about selling the ambulance. No sense having a vehicle I can't drive any more. Thanks very much for all the input. It always helps to figure out a plan of action prior to diving in. You've been lots of help!

You're right, it is pretty complex. I'm going to have to think about this a bit more. One of my concerns with the dual charging is that both the charger, and the solar charge controller adjust based on sensed voltage, and I read somewhere (I'll have to find it again) that this can cause a type of oscillation, where both sources spike/drop/spike/drop in an apposing pattern based on what the OTHER charger is doing. Lets see. First, if I drop to bare minimum usage (medical equipment only,) and if days are sunny (pretty likely where I live) I can run my medical stuff about 18 hours a day for about 3 weeks. If I were to add 1 more panel, I should cross the threshold of indefinate running. My current equipment can handle another panel, and yes, that is in the works. To really improve the system, I'd need to switch my battery bank to 24 volts allowing me to run twice the panels with the same charge controller, but then that would require an investment in a 24v inverter. Might be worthwhile, since it would remove my need to have extra charging capacity (so I could run more equipment for longer.) As far whether turning the charge off during the day vs the night.. If I understand correctly, placing a draw on the system during the day while the sun is out will draw from the panels even if the batteries are topped. Running the charger during the day would mean that a) I'd be running off of my mains, and b) the charger would be doing most of the work topping off the batteries. (IE wasted sunlight) Ignoring the whole "will it oscillate" issue. My personal thought is that a combination of the 2 options would be best. Turn on mains/charging in the evening when the panels can no longer keep up, minimizing battery wear and tear, while ensuring they stay close enough to full charge in case of power emergencies. Then, figure out WHEN to turn the mains back off based on all the things you pointed out. My usage, solar generation capabilities, and whether I can end the most productive part of the day with full or nearly full batteries. Thank you very much for the thoughts, I'm now officially in the "add more panels" camp. Add enough panels and the mains charging ability becomes much less of an issue. (though it would still be nice to have a way to auto swap from mains to battery and back, but I can probably pick up a simple relay of some type for that.

The ambulance itself needs to remain mobile, but I do like the idea of running proper wire in a conduit. I can probably have a post placed that has the plugins I need so at least I can shorten the cord run. (similar to an RV's setup, but with with both plugs, in and out, run to the same box on the post) I'm now wondering if I can save a few pennies here and there by switching to the solar a few hours each day. (could put a timer on the mains power.) I'll have to think on this. Thanks for the input!

I'm looking for a UPS solution, and think I have an idea that might work pretty well. Looking for input as far as whether its a bad idea to do what i'm thinking or not. First some background. I have a decommissioned ambulance with solar panels on the roof, and 600AH worth of batteries. It also has a tripp-lite inverter/charger. Currently I have a heavy duty extension cord run to the house from the ambulance solar, and when power fails I can switch my medical equipment over to the battery bank. So, here is my idea. Since the tripp-lite is an inverter/charger, I an run a second heavy duty cord back out to the ambulance and plug the inverter in to the house mains. (which would help ensure the batteries were always at full charge) In this way, anything I plug in to the ambulance is running off of the mains, passed through the tripp-lite. IF power fails, it will be auto switched to the battery bank. At this point, all I need to do is add a cheap apc ups and plug it into the wall somewhere, then connect it to my unRaid server. (I can have my router/etc hooked to the cheap ups as far as that goes) When power fails, the ups signals my server and it shuts down, and use the solar for my medical stuff. I have a call in to an electrical engineer friend who can hopefully tell me how dangerous this is. (2 extension cords, 2 charge sources to a really large battery bank.. He'll probably laugh at me) Assuming the idea is at least feasable, and my friend can help ensure acceptable levels of safety, does anyone see any other potential issues I might face?

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