Squid

Yeah you did. Don't use ubooquity that often except for when I'm looking for something new to read, but Fix Common Problems immediately complained about it since the template now has 2202 in it whereas before it didn't

I think you broke something with the docker. Java is installed inside the docker. Getting unRAID to install java by putting it in the extra folder will not help anything. If the latest version of the .jar is not compatible with the java installed in the docker then it is not going to work. Ahhh, that explains it since the Dockers are self-contained. Yeah, version 1.10.1 now requires Java 8 to run. I"m sorry to hear things are chaotic for HurricaneHrndz. Positive energies your way. Template has been updated. Please update the template. New container. Will auto update features enabled. Container will be set to autobuild on new releases as well. No longer will the user need to update the jar file by hand. Hope everyone likes it. You've got to actually delete the container and then re-add it, not just update it as the ubooquity now communicate on 2202 instead of the original 8085, and an update via dockerMan won't pull down the updated template

Not sure what the problem might be. Can you install it via the community app? - Go to the Apps tab - Click on the Plugins button (the last one) - Look for unBALANCE - Click Install If that doesn't work either, can you check if there are any errors in the Chrome console (click on View > Developer > Javascript console) ? Ad blocker installed? Fix Common Problems plugin should hopefully detect it and tell you to whitelist your server

Try just giving it static DNS addresses (whatever your router uses or 8.8.8.8 and 8.8.4.4) instead of pointing it at the router for them.

There's a browser for excluded folders in the appdata backup settings. If you need more refinements (only exclude a sub of a sub) then just add it to the rsync options Sent from my LG-D852 using Tapatalk

6.2 has slave options for volume passing which also solves this problem Sent from my LG-D852 using Tapatalk

Thanks. Far easier solution than using rotating backup sets. Give me a couple of days.

Probably right there... It was just a ton easier to handle it at the time

I disagree there. Simply because they are still issues that the user has chosen to ignore for whatever reason. And if they are not put into the syslog, then any assistance the user is seeking via the forums will not have all of the relevant information. ie: a user is having issues accessing shares, but has chosen to ignore the fact that there is myShare and MyShare coexisting at the same time. I just don't want people completely turning off notifications simply because they have a valid use case (or completely disagree with) those warnings. If you still think that I'm wrong here, I'll make it optional to log the ignored issues.

You'll have to wait for aptalca or someone else who knows this app to pipe in

Shot in the dark, but try it without a space in the folder name. Same issue as what I posted, but updating the webUI is a better solution than changing the folder name

http://lime-technology.com/forum/index.php?topic=40937.msg463355#msg463355

I'll stop wearing black when they make a darker colour - Fixed false positive HPA warnings when using Areca controllers (hopefully) - Ability to ignore errors Every error / warning now has an Ignore button next to it. If you're 100% sure that you don't want to be bugged about it again, then just ignore it. This does not ignore all errors of the class, but rather that specific error. All the ignore really does is prevent any notifications from being sent because of that error. They will still display on the GUI screen under the ignored errors section (and be logged into the syslog if found). To reenable notifications for it, you can re-add the specific error, or re-add all of them. Now, a question for the uber-linux geeks out there: Is it possible to redirect (or tee) stderr for the local attached console from any random bash shell to a file? My online searches aren't yielding any help for it, and all of my attempts thus far either have no effects. If that's impossible, how can I redirect (or tee) all stderr outputs for the local attached console from the local console? The reason I want to do this is because I want to add in an option for random reboots / crash detection and offer up a tail of the syslog to the flash. However, in much of the cases where this has been deemed necessary, the syslog yields no useful information about the crash, and I'm hoping that the local display does, but that information is lost on a reboot, and who among us sits in front of the monitor waiting for a crash with a camera?

what doeshdparm -N /dev/sdX where sdx is one of those drives so I know how to exclude them This is a retail 2TB Seagate drive (ST2000DM001 - 2 TB (sdf)) Linux 4.1.18-unRAID. root@Tower:~# hdparm -N /dev/sdf /dev/sdf: SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled root@Tower:~# fixed next rev

what doeshdparm -N /dev/sdX where sdx is one of those drives so I know how to exclude them

I've also found that times you just have to say screw it. Its my utility and this is the way I'm going to do it. If you want it done differently go write your own. Politely of course It was a general statement. Nothing at all to do with this plugin... I find it so boring to post update dates Sent from my LG-D852 using Tapatalk

Stuck at a kiddie birthday party so not much going to happen today but I had a thought looking for comments. Random reboot detection / unclean shutdown detection. Optional for random reset issues automatic syslog capture (to docker image to save wear and tear) unsure if I want to do a tail or a copy every minute due to possible corruption issues Sent from my LG-D852 using Tapatalk

Created the folder (root:root) Implied permissions (and as reported by Shares) is public. No problem accessing files within, modifying the files within, deleting etc over SMB Changed the share to Private (and left root:root). Could do the exact same things Even created a file owned by root:root and could still do everything over SMB to it. I do realize that some docker apps by default (CP, sonarr) move files to the array and use a different user (can't remember what it is), but in my tests, root:root is perfectly acceptable (or maybe I'm just special ) yes, but have you looked at the Linux level permissions? If you switch off the 'world' access (which if set means anyone can access the file) at the Linux level then I think you will find you fail at the share level. ok that's a different story. Now we're down to permissions and not ownership / groups. (Sorry for being daft -> not a linux guy so when you originally said world permissions I thought you were talking share permissions, not linux permission of 770) And with permissions set to 770 you are indeed correct - the share becomes inaccessible. Now that I know what the problem is I can incorporate checks Thx

Created the folder (root:root) Implied permissions (and as reported by Shares) is public. No problem accessing files within, modifying the files within, deleting etc over SMB Changed the share to Private (and left root:root). Could do the exact same things Even created a file owned by root:root and could still do everything over SMB to it. I do realize that some docker apps by default (CP, sonarr) move files to the array and use a different user (can't remember what it is), but in my tests, root:root is perfectly acceptable (or maybe I'm just special )

Here's the problem with /user Paths in /user do NOT support the symlinks that many (if not a majority) of docker apps create. There are many documented cases of apps not working at all if they are set to /user, but set it to /cache (or diskX) and they will work perfectly. In this case, I guess its because of the fact that the appdata already existed in /user with invalid symlinks and once the symlinks started working the way that they were supposed to it through plex for a loop. I've got this down as a warning because I anticipated a situation like yours (and I've tried to set up warnings so that you can safely be ok to not receive notifications on them), but going forward, set up any new installs as /cache as this is the proper way to do it and it will minimize any/all issues with containers (and the strange little bugs that sometimes pop up with containers that no one has a clue about what's causing it could possibly be traced back to the symlink issue)

As I've grown older, I've come to realize that pleasing everyone is impossible, but pissing every one off is a piece of cake - Remove checks for control characters in filenames - Add checks for dockers not running in same network mode as what author intended - Added in checks for HPA * - Added in checks for illegal suffixes on cache floor settings - Added in checks for cache floor larger than cache drive - Added in checks for cache free space less than cache floor - Added in check for array started - Added in check for flash drive getting full - Fix false positive for implied array only files sitting on cache drive - Fix false positive if docker template had no default ports * HPA if found will generate an error if its on the parity drive. If its on any other drive, it will only generate an "other comment" since IMO its not that big a deal to worry about (and not even worth the time to fix). Parity on the other hand is a big deal.

Actually just found that myself 5 minutes ago

Maybe I'm missing something here... What exactly is the issue with this? I just created a new share owned by root, group root, and I can browse, add, delete, modify files all day long within it over smb

Problem with this threads (and the posts within) is nobody is specifying whether or not these are the average speed as reported at the end, or a sample speed from looking at the Main tab 5 minutes into the check / rebuild.

Not a network guy.. All I did was post that some other users were having problems with docker and jumbo frames. Presumably if you never enabled them and set a large frame size on your network then this is not your issue Sent from my LG-D852 using Tapatalk