spants

I have just published unRaid-hole to my docker repository..... This doesn't use the same lists as Pi-Hole but it works the same way - just point your DNS addresses to your unRaid tower and it will forward the valid requests via Googles DNS servers and drop the rubbish ones.... These are the lists that it uses: #advertising http://hosts-file.net/ad_servers.txt #malware http://hosts-file.net/emd.txt #browser exploits http://hosts-file.net/exp.txt #fraud http://hosts-file.net/fsa.txt #spammers http://hosts-file.net/grm.txt #browser hijackers http://hosts-file.net/hjk.txt #misleading marketing (fake flash updates, similar trash) http://hosts-file.net/mmt.txt #illegal pharmacy sites (fake viagra spam?) http://hosts-file.net/pha.txt #phishing sites http://hosts-file.net/psh.txt It is based on https://github.com/arthurkay/sagittarius-A but will have lots of unRaid goodies soon!

It might cause problems with Nodes that have dependancies.

Great - lets see if he fixes that file quickly - if not I will do a workaround. I'm thinking of having an external text file with the required Nodes that gets loaded on restart. That way we can add Nodes without me rebuilding it. Will update soon....

I have notified the maintainer of that Node as I am doing a standard npm install for the Nodes. Were there any other dependancies ? (did you also have to do: npm install eibd)

I have now updated the version to v0.12.4. I had a problem with the EIBD node that you requested - a strange error in the .js file for that Node. Do you have it working elsewhere?

I have pushed an update to NodeRed v0.12.4 today!

I recently updated the docker with the node-red-contrib-npm node to allow you to add npm modules to the flow without a separate install: http://flows.nodered.org/node/ http://flows.nodered.org/flow/3c17c7bf227d1a8952b7 However this might only work for simple modules. Can you send me the Nodes that you need and I will add them for you. I am also working on an update to this docker to allow you to easily add your own.... Tony

not as simple as I had hoped - getting an error adding odbc to the dockerfile so it will need me to take a look in detail....

Looks interesting - I can't promise anything quickly as I'm porting my Node-Red into the linuxserver.io base and also working on some others......

Strange.... The docker is built on Linuxserver.io base and uses environment variables to set the PGID and PUID to suit Unraid (check the advanced view). If you miss these variables you will get this problem. I always use the docker page to start and stop the docker. To add passwords, create a passwords.txt file - do not edit the passwords.mqtt directly. Info in passwords.README file. The way I use it - create the /config directory and everything should be setup. Stop the docker, create a passwords.txt and then start the docker. It will encrypt the passwords, add it to the top of passwords.mqtt and then delete passwords.txt. I have a lot of devices using it - hope it works for you If you have to use the cmdline, try the following: docker run -t -i --net="bridge" -p 1883:1883/tcp -p 9001:9001 -v /mnt/cache/app_config/mqtt/:/config:rw -e PGID=100 -e PUID=99 spants/mqtt

Be aware that Openweather map and Forecast.io nodes do not seem to work correctly on the latest NodeRed.... I use the following code in Node Red to get the current temperature instead: (copy and then Import) [{"id":"9e1f670b.61e098","type":"mqtt-broker","broker":"localhost","port":"1883","clientid":""},{"id":"8c7d3ed4.7382c","type":"function","name":"Outside Temp","func":"\nif (msg.payload == \"\" ) {\n\treturn null;\n\t}\n\nvar weather = JSON.parse(msg.payload); \n//msg1 = {topic:\"Buxted/sunrise\", payload:weather.sys.sunrise};\n//msg2 = {topic:\"Buxted/sunset\", payload:weather.sys.sunset};\nweathertemp = Math.round( weather.main.temp * 10 ) / 10;\nmsg = {topic:\"House/Temp/Outside\", payload:weathertemp};\nreturn msg;","outputs":"1","x":607.638916015625,"y":222.74993896484375,"z":"a4d9ce41.5b263","wires":[["bd4969.ff42b698"]]},{"id":"c950f21e.36af1","type":"http request","name":"Openweathermap","method":"GET","ret":"txt","url":"http://api.openweathermap.org/data/2.5/weather?q=London,uk&units=metric","x":378.4167175292969,"y":222.08331298828125,"z":"a4d9ce41.5b263","wires":[["8c7d3ed4.7382c"]]},{"id":"9116d09f.6ee93","type":"inject","name":"1 Min Timer","topic":"","payload":"","payloadType":"date","repeat":"60","crontab":"","once":false,"x":194.0000457763672,"y":221.77777099609375,"z":"a4d9ce41.5b263","wires":[["c950f21e.36af1"]]},{"id":"bd4969.ff42b698","type":"mqtt out","name":"","topic":"","qos":"1","retain":"true","broker":"9e1f670b.61e098","x":825,"y":223,"z":"a4d9ce41.5b263","wires":[]}]

Thanks for that - hopefully fixed now.

MQTT completely updated - latest Mosquitto version 1.4.3, password support and more.

good catch on emoncms, I use it myself but missed it off the list. I will add it now. ***** now added ***** Thanks for the mosquitto hints. I have something in beta but will look at your notes. I need to add websockets support/ passwords and options for certificates Tony

I have updated the Node-Red container - added lots more nodes, updated Node-Red and Node to the latest versions. MQTT is next on my list. I would like to add username/password to the settings page - I'm reading up on that....

Sorry - I had forgotten about adding MQTT passwords, I will add it shortly. - I am also planning some updates to Node-Red nodes Tony

Glad its working!. I did a similar thing with my Tado heating system. Why not use emoncms as the back end for the energy data?. Actually that may be a great docker to build...... @Dallas.toth, which nodes would you like?

Great - that fixed it! Tony

Yes, I did the docker update and then when going back into owncloud, I get the upgrading database issue. It just stays there. I have to reinstall everything from scratch each time (deleting docker appdata)

Whenever I try and do an update to the owncloud docker, it tries to update my database and just gets stuck on the page that says: "This ownCloud instance is currently being updated, which may take a while. This page will refresh itself when the ownCloud instance is available again." I'm using a mariadb docker with this. Any ideas? Tony

This is where I will be hosting some dockers that I find useful, built on a Phusion or Linuxserver base. Add to your templates if you wish. https://github.com/spants/unraidtemplates/ *** Also added template support for the official NodeRed docker image - loads the latest version!!!. You can extra nodes through the Palette menu option. Therefore I will retire my unofficial version. Make a copy of your appdata directory and rename any 'flow' files to 'flows' *** NodeRed ====== This is THE Internet of Things package!. See http://www.nodered.org and http://flows.nodered.org for more info. I use this to link with my TADO heating system, Ciseco wireless sensors and Open weathermap linked with EmonCMS to produce heating graphs. It uses building blocks to manipulate data from devices/databases/twitter/http/mqtt etc etc - very powerful! MQTT *** Revert to Mosquitto 1.4.8 and Alpine Linux 3.3 27th Jan 2020 - due to timeout bug found *** ==== Please see Skylord123's excellent tutorial on setting this up https://skylar.tech/installing-mqtt-under-docker/ Setup for port 1883 and websockets on Port 9001. Supports usernames/passwords and certificates. To add authenticated users to MQTT, create a file named passwords.txt and save in the config directory. On restart, these will be encrypted and added to the top of the passwords.mqtt file. You might need to run NEWPERMS to edit the config file. Dashing *** Updated 08-Dec-2015, added dev tools *** ====================================== From dashing.io = Dashing is a Sinatra based framework that lets you build beautiful dashboards. Key features: Use premade widgets, or fully create your own with scss, html, and coffeescript. Widgets harness the power of data bindings to keep things DRY and simple. Powered by batman.js. Use the API to push data to your dashboards, or make use of a simple ruby DSL for fetching data. Drag & Drop interface for re-arranging your widgets. Host your dashboards on Heroku in less than 30 seconds. This project was created at Shopify for displaying custom dashboards on TVs around the office. Sample dashboards installed at IPaddress:3030/sample and IPaddress:3030/sampletv couchDB ======= unRaid template for the (semi)official Apache couchDB docker https://github.com/apache/couchdb-docker

Anyone tried a restore yet? I have a 100GB directory to restore and it is running at 300Kbps and estimating 31days!. I have a fully functioning 1000Mbs network card and other operations are really fast. The system has 16GB ram... Wondering if going back to the plugin would speed it up. ** SOLVED ** Crashplan docker was using the ip address of my vpn docker hence using the WAN profile.

I would fork this to a thread on its own and do a harder sell than that (with screenshots). Most people have no clue about MusicBrainz and Picard goodness and even the ones that do (me) have no clue why I would want to run a server for it. fork fork fork.. sell sell sell I get you!... I'm fed up with the '503 errors' when querying my 30000+ songs

I would love to see a MusicBrainz server running in a docker - to work with the headphones docker. Here is one on the docker site: https://registry.hub.docker.com/u/rickatnight11/musicbrainz-server/

I have just started getting the same in my logs: Oct 15 22:25:04 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 15 22:26:00 Tower cache_dirs: ============================================== Oct 15 22:26:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 15 22:26:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 15 22:26:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 15 22:26:00 Tower cache_dirs: max_depth=4 Oct 15 22:26:00 Tower cache_dirs: command=find -noleaf Oct 15 22:26:00 Tower cache_dirs: version=1.6.5 Oct 15 22:26:00 Tower cache_dirs: ---------- caching directories --------------- Oct 15 22:26:00 Tower cache_dirs: Videos Oct 15 22:26:00 Tower cache_dirs: ---------------------------------------------- Oct 15 22:26:00 Tower cache_dirs: cache_dirs process ID 4369 started, To terminate it, type: cache_dirs -q Oct 15 22:27:48 Tower kernel: mdcmd (203): spindown 0 (Routine) Oct 15 22:27:48 Tower kernel: mdcmd (204): spindown 2 (Routine) Oct 15 23:19:49 Tower kernel: mdcmd (205): spindown 4 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (206): spindown 1 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (207): spindown 2 (Routine) Oct 15 23:20:00 Tower kernel: mdcmd (208): spindown 3 (Routine) Oct 15 23:20:01 Tower kernel: mdcmd (209): spindown 5 (Routine) Oct 15 23:20:01 Tower kernel: mdcmd (210): spindown 6 (Routine) Oct 15 23:20:51 Tower kernel: mdcmd (211): spindown 7 (Routine) Oct 15 23:50:02 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 15 23:51:00 Tower cache_dirs: ============================================== Oct 15 23:51:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 15 23:51:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 15 23:51:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 15 23:51:00 Tower cache_dirs: max_depth=4 Oct 15 23:51:00 Tower cache_dirs: command=find -noleaf Oct 15 23:51:00 Tower cache_dirs: version=1.6.5 Oct 15 23:51:00 Tower cache_dirs: ---------- caching directories --------------- Oct 15 23:51:00 Tower cache_dirs: Videos Oct 15 23:51:00 Tower cache_dirs: ---------------------------------------------- Oct 15 23:51:00 Tower cache_dirs: cache_dirs process ID 30794 started, To terminate it, type: cache_dirs -q Oct 16 01:14:29 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 01:15:01 Tower cache_dirs: ============================================== Oct 16 01:15:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 01:15:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 01:15:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 01:15:01 Tower cache_dirs: max_depth=4 Oct 16 01:15:01 Tower cache_dirs: command=find -noleaf Oct 16 01:15:01 Tower cache_dirs: version=1.6.5 Oct 16 01:15:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 01:15:01 Tower cache_dirs: Videos Oct 16 01:15:01 Tower cache_dirs: ---------------------------------------------- Oct 16 01:15:01 Tower cache_dirs: cache_dirs process ID 24715 started, To terminate it, type: cache_dirs -q Oct 16 02:17:13 Tower kernel: mdcmd (212): spindown 0 (Routine) Oct 16 02:17:14 Tower kernel: mdcmd (213): spindown 1 (Routine) Oct 16 02:41:06 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 02:42:00 Tower cache_dirs: ============================================== Oct 16 02:42:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 02:42:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 02:42:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 02:42:00 Tower cache_dirs: max_depth=4 Oct 16 02:42:00 Tower cache_dirs: command=find -noleaf Oct 16 02:42:00 Tower cache_dirs: version=1.6.5 Oct 16 02:42:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 02:42:00 Tower cache_dirs: Videos Oct 16 02:42:00 Tower cache_dirs: ---------------------------------------------- Oct 16 02:42:00 Tower cache_dirs: cache_dirs process ID 18694 started, To terminate it, type: cache_dirs -q Oct 16 03:15:45 Tower kernel: mdcmd (214): spindown 0 (Routine) Oct 16 03:15:45 Tower kernel: mdcmd (215): spindown 1 (Routine) Oct 16 03:16:16 Tower kernel: mdcmd (216): spindown 2 (Routine) Oct 16 03:29:26 Tower kernel: mdcmd (217): spindown 3 (Routine) Oct 16 04:02:47 Tower kernel: mdcmd (218): spindown 3 (Routine) Oct 16 04:02:57 Tower kernel: mdcmd (219): spindown 4 (Routine) Oct 16 04:03:07 Tower kernel: mdcmd (220): spindown 5 (Routine) Oct 16 04:04:17 Tower kernel: mdcmd (221): spindown 7 (Routine) Oct 16 04:05:28 Tower kernel: mdcmd (222): spindown 2 (Routine) Oct 16 04:07:38 Tower kernel: mdcmd (223): spindown 1 (Routine) Oct 16 04:08:49 Tower kernel: mdcmd (224): spindown 6 (Routine) Oct 16 04:37:39 Tower kernel: mdcmd (225): spindown 1 (Routine) Oct 16 04:40:02 Tower su[13762]: Successful su for unraid-plex by root Oct 16 04:40:02 Tower su[13762]: + root:unraid-plex Oct 16 04:44:23 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 04:45:00 Tower cache_dirs: ============================================== Oct 16 04:45:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 04:45:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 04:45:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 04:45:00 Tower cache_dirs: max_depth=4 Oct 16 04:45:00 Tower cache_dirs: command=find -noleaf Oct 16 04:45:00 Tower cache_dirs: version=1.6.5 Oct 16 04:45:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 04:45:00 Tower cache_dirs: Videos Oct 16 04:45:00 Tower cache_dirs: ---------------------------------------------- Oct 16 04:45:00 Tower cache_dirs: cache_dirs process ID 14478 started, To terminate it, type: cache_dirs -q Oct 16 04:57:50 Tower kernel: mdcmd (226): spindown 3 (Routine) Oct 16 04:58:00 Tower kernel: mdcmd (227): spindown 5 (Routine) Oct 16 04:58:00 Tower kernel: mdcmd (228): spindown 6 (Routine) Oct 16 04:58:01 Tower kernel: mdcmd (229): spindown 7 (Routine) Oct 16 05:16:51 Tower kernel: mdcmd (230): spindown 1 (Routine) Oct 16 05:17:12 Tower kernel: mdcmd (231): spindown 4 (Routine) Oct 16 05:17:42 Tower kernel: mdcmd (232): spindown 6 (Routine) Oct 16 05:29:13 Tower kernel: mdcmd (233): spindown 2 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (234): spindown 3 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (235): spindown 5 (Routine) Oct 16 05:33:33 Tower kernel: mdcmd (236): spindown 7 (Routine) Oct 16 06:28:54 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 06:29:00 Tower cache_dirs: ============================================== Oct 16 06:29:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 06:29:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 06:29:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 06:29:00 Tower cache_dirs: max_depth=4 Oct 16 06:29:00 Tower cache_dirs: command=find -noleaf Oct 16 06:29:00 Tower cache_dirs: version=1.6.5 Oct 16 06:29:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 06:29:00 Tower cache_dirs: Videos Oct 16 06:29:00 Tower cache_dirs: ---------------------------------------------- Oct 16 06:29:00 Tower cache_dirs: cache_dirs process ID 8556 started, To terminate it, type: cache_dirs -q Oct 16 07:58:46 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 07:59:01 Tower cache_dirs: ============================================== Oct 16 07:59:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 07:59:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 07:59:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 07:59:01 Tower cache_dirs: max_depth=4 Oct 16 07:59:01 Tower cache_dirs: command=find -noleaf Oct 16 07:59:01 Tower cache_dirs: version=1.6.5 Oct 16 07:59:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 07:59:01 Tower cache_dirs: Videos Oct 16 07:59:01 Tower cache_dirs: ---------------------------------------------- Oct 16 07:59:01 Tower cache_dirs: cache_dirs process ID 2527 started, To terminate it, type: cache_dirs -q Oct 16 09:06:45 Tower kernel: mdcmd (237): spindown 3 (Routine) Oct 16 09:26:56 Tower kernel: mdcmd (238): spindown 2 (Routine) Oct 16 09:44:46 Tower kernel: mdcmd (239): spindown 2 (Routine) Oct 16 09:57:04 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 09:58:00 Tower cache_dirs: ============================================== Oct 16 09:58:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 09:58:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 09:58:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 09:58:00 Tower cache_dirs: max_depth=4 Oct 16 09:58:00 Tower cache_dirs: command=find -noleaf Oct 16 09:58:00 Tower cache_dirs: version=1.6.5 Oct 16 09:58:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 09:58:00 Tower cache_dirs: Videos Oct 16 09:58:00 Tower cache_dirs: ---------------------------------------------- Oct 16 09:58:00 Tower cache_dirs: cache_dirs process ID 29209 started, To terminate it, type: cache_dirs -q Oct 16 10:32:17 Tower kernel: mdcmd (240): spindown 2 (Routine) Oct 16 11:02:08 Tower kernel: mdcmd (241): spindown 2 (Routine) Oct 16 11:02:08 Tower kernel: mdcmd (242): spindown 7 (Routine) Oct 16 11:14:34 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 11:15:01 Tower cache_dirs: ============================================== Oct 16 11:15:01 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 11:15:01 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 11:15:01 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 11:15:01 Tower cache_dirs: max_depth=4 Oct 16 11:15:01 Tower cache_dirs: command=find -noleaf Oct 16 11:15:01 Tower cache_dirs: version=1.6.5 Oct 16 11:15:01 Tower cache_dirs: ---------- caching directories --------------- Oct 16 11:15:01 Tower cache_dirs: Videos Oct 16 11:15:01 Tower cache_dirs: ---------------------------------------------- Oct 16 11:15:01 Tower cache_dirs: cache_dirs process ID 23174 started, To terminate it, type: cache_dirs -q Oct 16 12:32:57 Tower cache_dirs: scheduling via at ./cache_dirs -w -m 1 -M 10 -d 4 -i "Videos" -B -u -a "-noleaf" Oct 16 12:33:00 Tower cache_dirs: ============================================== Oct 16 12:33:00 Tower cache_dirs: command-args=-w -m 1 -M 10 -d 4 -i Videos -B -u -a -noleaf Oct 16 12:33:00 Tower cache_dirs: vfs_cache_pressure=10 Oct 16 12:33:00 Tower cache_dirs: max_seconds=10, min_seconds=1 Oct 16 12:33:00 Tower cache_dirs: max_depth=4 Oct 16 12:33:00 Tower cache_dirs: command=find -noleaf Oct 16 12:33:00 Tower cache_dirs: version=1.6.5 Oct 16 12:33:00 Tower cache_dirs: ---------- caching directories --------------- Oct 16 12:33:00 Tower cache_dirs: Videos Oct 16 12:33:00 Tower cache_dirs: ---------------------------------------------- Oct 16 12:33:00 Tower cache_dirs: cache_dirs process ID 17108 started, To terminate it, type: cache_dirs -q