Squid

I don't know if you will get a response from bonienl or not. S3 sleep is/has been a source of problems for the past few years. Some people have absolutely not problems using it and other have absolutely no luck! Microsoft can't even get it right all the time.... I have yet to have a desktop / laptop that will consistently go to sleep and/or wakeup properly

Been different all my life, why change! Anyway, it works fine now, on my differentexceptional system. At least I know that anytime you post a false positive I know where my coding mistake lies And if anyone ever called me "normal" I'd probably be insulted...

BTW, if anyone knows any quick and dirty checks for VM settings (and ideally willing to give me code fragments - or the checking procedure written out in english if you don't know how to code), feel free to post as I have no fundamental reason to run a VM and therefore don't include any checks against their settings, etc.

ok. This is what I've done for the next release (possibly tonight - depends on how much I enjoy my long weekend ) is this: If there are no errors already logged when entering the plugin, then it will do a scan for errors. If there are errors already logged, then it will display the time of the last scan and not rescan anything unless you hit rescan. Note however that even with this, the adBlocker detection (and applicable popup) is always tested, simply because the background checks cannot figure this one out.

Give a man a gun and he can rob a bank. Give a man a bank and he can rob the world - Should be fixed: False positive on array not started when not using user shares (because RobJ insists on being different) - Added in to troubleshooting mode: output of free and ps aux (only processes with CPU % > 0) - Added in hack attempts in progress Hack Attempts: Checks for invalid login attempts. Defaults to a grace value of 10 per day allowed. Note: I only have a single syslog that I could easily find that had a hack attempt (http://lime-technology.com/forum/index.php?topic=49177.msg472096#msg472096) (btw there were 5417 attempts to break into buddy's server within a 15 hour period (one attempt every 10 seconds), and this check looks for those messages which were logged. The usual protect my a$$ disclaimer: If this plugin does not catch anything, it does not necessarily mean that you are not being actively hacked, nor that you have not already been hacked. Also, this is only detecting hacks to log in to your server. If someone has already hacked their way onto your network and are trying to hack their way into your shares, then those invalid logins are not logged, and at present cannot be detected. If you have (or know of) a syslog somewhere on this forum that shows active hack attempts beyond what these checks find, forward me the appropriate link and detection for it will be added.

Now that I think about it, that annoy's me also when I'm testing too late for today's update, but the next one

Just a little comment regarding permissions If everything else is correct (owner as nobody, group as users), you will not have a problem with permission of 077x However if the owner is root, you will have an issue with any share over the network that is not set to 0xx7 (or 0xx6) The justification for this check is that when creating a share, permissions are set to 0777, and when running the New Permissions tool included with unRaid, permissions are set across the board to 0777. PhAzE-Common has its permissions set to 0755. No idea what the ownership is with that folder. But as the suggestion states "You may have problems...over the network". After seeing this post, I thought about including an exception for phaze common set to 0755, and then decided that since LT has decided that the appropriate permissions for a share is 0777 to let the warning stand. Its a warning, not an error because there may be specific reasons for differing permissions set, that this plugin is not aware of.

Hit edit next to those volumes. Change them to one of the slave options. Doing so will fix having to stop and restart the docker service to get plex to work after a reboot Sent from my LG-D852 using Tapatalk

Actually AFAIK you should be removing shell in a box as it has been superseded by Command Line. That share I don't know what made it so I can't give you any advice there. If everything is ok just add it to the ignore list Sent from my LG-D852 using Tapatalk

Can't check atm but it's probably because you don't run user shares. I'll fix As far as the adblocker warning is concerned it popped up because it DID change a particular item (non displayed) on this page. The error Only pops up when going to the page and cannot be detected during background checks. But net result is your mileage may vary if the blocker does affect your unraid gui. Sent from my LG-D852 using Tapatalk

No? http://lime-technology.com/forum/index.php?topic=40262.msg471536.msg#471536 Sent from my LG-D852 using Tapatalk

The plugin doesn't change anything. It's a warning that the permissions are not set to what it's set to when you run the newpermissions utility. Admittedly I never checked to see what the permissions are set to if you create a new share. Sent from my LG-D852 using Tapatalk

Install the community applications plugin Sent from my LG-D852 using Tapatalk

Tools syslog and just scroll through that Sent from my LG-D852 using Tapatalk

Its --cpuset-cpus, and yes it does work on a per container basis, along with a bunch of other nifty docker run options to prioritize one docker app over another, etc http://lime-technology.com/forum/index.php?topic=36257.0

Could you please explain what steps i need to take to achieve "removing the drive and rebuilding parity". Do i need to take a backup of the contents of the drive first, or are you suggesting that the rebuilding of the parity will recover the data from the drive and add it to the array? Few steps i need to take would be appreciated, im a noob here haha. http://lime-technology.com/wiki/index.php/UnRAID_6/Storage_Management#Replace_a_failed_disk

Having a dirty mind makes ordinary conversations much more interesting - Added in improper shutdown checks - Check user shares for standard LT permissions of 0777 - Added in "Troubleshooting mode" Troubleshooting mode would generally only get used when you're having weird crashing issues, complete lock ups of the server, random reboots, etc What it'll do is Run unRaid's diagnostics every 30 minutes - file(s) saved to /config/logs/ on the flash drive Run a subset of this plugin's checks every 10 minutes - Currently just available free space on /var/log and rootfs - also reports in syslog the current used space Runs uptime every 10 minutes - so that the sysload is logged Starts a tail on the syslog (file stored in config/logs/syslog.txt on the flash drive so that in the event of a crash / lockup, a syslog up to the actual crash can be retrieved In other words, I've made this (with some extra features) into a plugin http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog - still trying to figure out how to capture (if its even possible) the crash dump messages that get output to the local monitor to a file. (ie: I want to permanently redirect stderr for a currently running bash instance to a file if anyone wants a challenge) The point in running multiple diagnostics, the subset of tests, and logging the sysload is so that when asking for help and posting the diagnostics (some or all), a trend leading up to the crash can hopefully be discerned Note that once this mode is entered the only way to abort it is to restart the server. If you've entered this mode looking for help on the forums, make sure you post at least the last diagnostic file generated, and the syslog.txt file Other changes - a scan for problems is now automatically done with every start of the array - temporarily removed HPA checks as my secondary server is having a very weird issue with them (disabling a disk when its run), and I don't want to cause anybody any issues til I sort out what's happening.

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

Won't get fixed within CA until the next appfeed scan (within 2 hours)

getting an error about URL trying to install from CA: plugin: installing: https://github.com/dlandon/unassigned.devices/raw/master/tips.and.tweaks.plg plugin: downloading https://github.com/dlandon/unassigned.devices/raw/master/tips.and.tweaks.plg plugin: downloading: https://github.com/dlandon/unassigned.devices/raw/master/tips.and.tweaks.plg ... failed (Invalid URL / Server error response) plugin: wget: https://github.com/dlandon/unassigned.devices/raw/master/tips.and.tweaks.plg download failure (Invalid URL / Server error response) Error in the template: plugin: installing: https://github.com/dlandon/unassigned.devices/raw/master/tips.and.tweaks.plg Works installing it manually

You can create a new folder within the plugins folder on the flash and toss a file in there called xXxX.cron. dynamix will add the cron entry in there every boot Sent from my LG-D852 using Tapatalk

I didn't check that one out. (never use the drop downs to go there) Guess I can have fcp check for webUi ports Sent from my LG-D852 using Tapatalk

Won't matter... The complaint is about a blank screen on the settings to allow you to enable it Sent from my LG-D852 using Tapatalk

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