dmacias

I compiled it since all the repo packages required ncurses 6.

Add this torrent to deluge. Then under Status/Tracker Status it will tell you your ip. http://checkmytorrentip.net/torrentip/checkMyTorrentIp.png.torrent

That will take longer since there's no pre built package or build script for slackware. I'll look into it.

Ok I added it.

Maybe edac or edac for amd is not enabled in the kernel configuration when it's compiled. See here http://www.linuxquestions.org/questions/slackware-14/edac-in-slackware-4175599408/

I compiled a newer version. I'm not sure what happened to the slack description. I'll have to repackage it later when I get to my laptop. But give it a try. https://github.com/dmacias72/unRAID-plugins/raw/master/source/packages/mcelog-148-x86_64-1.txz

Added tmux

Iperf 3. Edit oh I see you need iperf Try this one https://slackonly.com/pub/packages/14.1-x86_64/network/iperf/iperf-2.0.5-x86_64-1_slack.txz

You can always download them from my github to your flash drive then run installpkg /boot/iperf-3.1.6-x86_64-1cf.txz https://github.com/dmacias72/unRAID-plugins/raw/master/packages/6.3/iperf-3.1.6-x86_64-1cf.txz

Where you want to install it?

I added it.

IDLE is Python’s Integrated Development and Learning Environment. It has nothing to do with Western Digital idle3. I compiled idle3ctl. You don't need python to run it. I'll just add idle3-tools to Nerdpack. You'll need to run idle3ctl.

I'll check it out. Until then you need to install the version from Slackware 14.2 not Slackware Current. Many packages from Current rely on ncurses 6. UnRAID comes with 5.9. You could also upgradepkg ncurses 6. I believe it's backwards compatible.

Not sure. A bad download or something. I bumped the version to 2017.02.13 anyway cause I don't like the lettered versions. Check for updates and try again.

I set this up a couple days ago and went with xxx.servebeer.com/nextcloud these are my working settings. letsencrypt site-conf/default server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name xxx.servebeer.com; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; client_max_body_size 0; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; location /robot.txt { add_header Content-type text/plain; return 200 "User-agent: *\nDisallow: /\n"; } location = / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; try_files $uri $uri/ /index.html /index.php?$args =404; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.xx.1:444/nextcloud; } location /requests { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.xx.1:3000/requests; } } I think I only changed these in nextcloud site-conf/default # Path to the root of your installation #root /config/www/nextcloud/; root /config/www/; # set max upload size client_max_body_size 10G; fastcgi_buffers 64 4K; nextcloud config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'ocxvunynx6i5', 'passwordsalt' => 'xxx', 'secret' => 'xxx', 'trusted_domains' => array ( 0 => '192.168.xx.1', 1 => 'xxx.servebeer.com', ), 'trusted_proxies' => array ( 0 => '192.168.xx.1', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'xxx.servebeer.com', 'overwrite.cli.url' => 'https://192.168.xx.1:444', 'dbtype' => 'mysql', 'version' => '11.0.1.2', 'dbname' => 'nextcloud', 'dbhost' => '192.168.xx.1:3306', 'dbport' => '', 'dbtableprefix' => 'oc_', 'dbuser' => 'oc_sysadmin', 'dbpassword' => 'xxx', 'logtimezone' => 'UTC', 'installed' => true, ); And then I created a script to make the .htpasswd without apache for letsencrypt You just supply it a username then enter the password twice and the username:password hash are added to /appdata/letsencrypt/nginx/.htpasswd I put the script at /appdata/letsencrypt and then run htpasswd username #!/bin/bash if [ "$#" -ne 1 ]; then echo "Usage: " `basename "$0"` "username" exit 1 fi printf "$@:`openssl passwd -apr1`\n" >> nginx/.htpasswd echo "username:password written to nginx/.htpasswd" Thought I'd post these in case it helps someone or if anyone has some suggestions. But its working great so far. I pieced it together from a few different posts.

I can confirm the hourly setting is broke. Anyone who already had it set is fine. Just new settings don't work for hourly.

It should work. I would try changing the settings to something else apply then change them back and apply. I have mine run at 3am everyday. I will change it to hourly and report back.

I added Lynx text based browser. I tried a couple others but they would require a bunch of other packages.

It's got to be something with unRAID networking then. Maybe your settings vs a change in unRAID in Oct. I figure you probably haven't changed settings. So something in unRAID changed. Since the docker runs sivel 1.0.2 and you get the results you expect. But when you run the exact same 1.0.2 script on unRAID bare metal you get such a different result. I also noticed some 800ms pings on some of those tests. Who's repo is the docker in or did you add it manually? I can just add it to my own repo. But either way maybe I can support the output. Where do you get see the results when it's run, the docker's log?

It's included with 6.3. If you toggle a package on/off and click apply it should remove it from your config. Toggle it on and off from NerdPack plugin? Check the picture links below. inotify is nowhere to be found in the list. http://i.imgur.com/LXL8OIs.png http://i.imgur.com/44WYul1.png Just toggle any package on/off so the Apply button is not disabled. Then click apply. In the config file the package settings are saved by package-version. The plugin rebuilds the config file every time to get rid of older versions. This should get rid of inotify from the config. I'll add a fix to the plg file to remove inotify from the config on 6.3 installs or at least set it to no.

You mentioned that before. I currently access IPMI using the Java IPMI Viewer. My Router's DHCP service issued an IP address to the viewer, which I use to access. Is what you're suggesting the same thing? Under Settings in the ipmi plugin, change Enable Network Connections to yes and then enter the IP, username and password. Then click apply. You'll have to reselect any sensors in the display and footer settings too. However, I don't think the error will go away. I believe unRAID has the ipmi driver enabled by default. Before I had to enable it with modprobe.

I wouldn't use speedtest-linux at all. I posted an issue on his github but it hasn't been fixed yet. Using speedtest-xml is dependent on what script is selected on the settings page. So I'm not sure what you have selected. If you run just speedtest it will run sivel version 1.0.2. You can also run python /usr/local/emhttp/plugins/speedtest/scripts/speedtest-1.0.1.py or select another version the same way. I would run a few 'speedtest' runs then you could try specifying a server too.

I would just switch to network connection in the ipmi settings and forget about it. You don't lose any functionality.

It's included with 6.3. If you toggle a package on/off and click apply it should remove it from your config.

Sorry I'm not sure. It's sone kind of kernel problem with your BMC. You could try updating your BMC or try out unRAID 6.3 which just came out. Since it just happens once and if everything runs ok then it might be fine. If it's not running fine you could try using the network connection of your IPMI. I use networking even though local is available.