smashingtool Posted July 22, 2016 Share Posted July 22, 2016 If this close to stable? I'm getting daily updates for the container itself, and it's starting to get old. Quote Link to comment
thomast_88 Posted July 23, 2016 Share Posted July 23, 2016 the better solution is to run the docker under a specific user that is in the docker group. Still working on this! Any progress on this? :-) Quote Link to comment
roland Posted July 24, 2016 Author Share Posted July 24, 2016 If this close to stable? I'm getting daily updates for the container itself, and it's starting to get old. Hi there are 2 factors at play here. [*]netdata is in constant development and the docker dev is trying to keep up with the new releases. https://hub.docker.com/r/titpetric/netdata/builds/ [*]there is the bug between unRAID and the docker-hub that shows updates available when there is actually no change. I can't remember now what release fixes the bug. So apologies for the frequent updates, but after all, they are bringing us forward. Quote Link to comment
roland Posted July 24, 2016 Author Share Posted July 24, 2016 the better solution is to run the docker under a specific user that is in the docker group. Still working on this! Any progress on this? :-) Sorry, life got a bit busy around here. Work and school holidays and skiing (yes, it is winter down here) ... I added this to the go file: chmod 666 /var/run/docker.sock Yes, not a good solution, but a workaround. I will need to get in touch with the docker dev to see if he can implement the specific user/group settings like the linuxserver.io guys do. Will keep you posted. Quote Link to comment
bstegemiller Posted August 5, 2016 Share Posted August 5, 2016 Any progress on reverse proxy config? I've played around with it a little in NGINX, but haven't really gotten anywhere useful. Quote Link to comment
roland Posted August 7, 2016 Author Share Posted August 7, 2016 Any progress on reverse proxy config? I've played around with it a little in NGINX, but haven't really gotten anywhere useful. Thanks for the reminder. I use the "Nginx-letsencrypt" docker and I managed to get it to work like this: nginx/site-confs/default upstream backend { # the netdata server server 192.168.2.130:19999; keepalive 64; } server { listen 80; listen 443 ssl http2; # server_name mysecretdomain.com www.mysecretdomain.com; include /config/nginx/proxy.conf; include /config/nginx/auth.conf; ssl_certificate /config/keys/fullchain.pem; ssl_certificate_key /config/keys/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'; ssl_prefer_server_ciphers on; location / { root /config/www; index index.html index.htm index.php; } # This exposes the unraid GUI, not a good idea ! # location / { # proxy_pass http://192.168.2.130/; # proxy_buffering off; # } location /coach { proxy_pass http://192.168.2.130:5050/coach; } location /sonarr { proxy_pass http://192.168.2.130:8989/sonarr; } location ~ /netdata/(?<ndpath>.*) { proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://backend/$ndpath$is_args$args; proxy_http_version 1.1; proxy_pass_request_headers on; proxy_set_header Connection "keep-alive"; proxy_store off; } } the URL needs to have a trailing /, I couldn't work that out yet. Hope it works for you. there are also official ngnix, apache, lighttpd and caddy examples https://github.com/firehol/netdata/wiki/Running-behind-nginx https://github.com/firehol/netdata/wiki/Running-behind-apache https://github.com/firehol/netdata/wiki/Running-behind-lighttpd https://github.com/firehol/netdata/wiki/Running-behind-caddy Quote Link to comment
bstegemiller Posted August 7, 2016 Share Posted August 7, 2016 Any progress on reverse proxy config? I've played around with it a little in NGINX, but haven't really gotten anywhere useful. Thanks for the reminder. I use the "Nginx-letsencrypt" docker and I managed to get it to work like this: nginx/site-confs/default upstream backend { # the netdata server server 192.168.2.130:19999; keepalive 64; } server { listen 80; listen 443 ssl http2; # server_name mysecretdomain.com www.mysecretdomain.com; include /config/nginx/proxy.conf; include /config/nginx/auth.conf; ssl_certificate /config/keys/fullchain.pem; ssl_certificate_key /config/keys/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'; ssl_prefer_server_ciphers on; location / { root /config/www; index index.html index.htm index.php; } # This exposes the unraid GUI, not a good idea ! # location / { # proxy_pass http://192.168.2.130/; # proxy_buffering off; # } location /coach { proxy_pass http://192.168.2.130:5050/coach; } location /sonarr { proxy_pass http://192.168.2.130:8989/sonarr; } location ~ /netdata/(?<ndpath>.*) { proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://backend/$ndpath$is_args$args; proxy_http_version 1.1; proxy_pass_request_headers on; proxy_set_header Connection "keep-alive"; proxy_store off; } } the URL needs to have a trailing /, I couldn't work that out yet. Hope it works for you. there are also official ngnix, apache, lighttpd and caddy examples https://github.com/firehol/netdata/wiki/Running-behind-nginx https://github.com/firehol/netdata/wiki/Running-behind-apache https://github.com/firehol/netdata/wiki/Running-behind-lighttpd https://github.com/firehol/netdata/wiki/Running-behind-caddy Brilliant, that worked! Thank you! Quote Link to comment
smashingtool Posted August 10, 2016 Share Posted August 10, 2016 If this close to stable? I'm getting daily updates for the container itself, and it's starting to get old. Hi there are 2 factors at play here. [*]netdata is in constant development and the docker dev is trying to keep up with the new releases. https://hub.docker.com/r/titpetric/netdata/builds/ [*]there is the bug between unRAID and the docker-hub that shows updates available when there is actually no change. I can't remember now what release fixes the bug. So apologies for the frequent updates, but after all, they are bringing us forward. I guess I'm just not used to docker updates being tied to the application updates themselves. Many apps have a built in updater or update notification, which doesn't require a container update whatsoever. Additionally, all of my linuxserver.io dockers are independent from the apps themselves. So if the guys at linuxserver change something about how the docker itself works, there is an update. But if, for example, Plex itself has an update available, it will just automatically install the next time the container is restarted. The container itself doesn't need to be updated in that scenario. Quote Link to comment
kri kri Posted August 18, 2016 Share Posted August 18, 2016 Any progress on reverse proxy config? I've played around with it a little in NGINX, but haven't really gotten anywhere useful. Thanks for the reminder. I use the "Nginx-letsencrypt" docker and I managed to get it to work like this: nginx/site-confs/default upstream backend { # the netdata server server 192.168.2.130:19999; keepalive 64; } server { listen 80; listen 443 ssl http2; # server_name mysecretdomain.com www.mysecretdomain.com; include /config/nginx/proxy.conf; include /config/nginx/auth.conf; ssl_certificate /config/keys/fullchain.pem; ssl_certificate_key /config/keys/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'; ssl_prefer_server_ciphers on; location / { root /config/www; index index.html index.htm index.php; } # This exposes the unraid GUI, not a good idea ! # location / { # proxy_pass http://192.168.2.130/; # proxy_buffering off; # } location /coach { proxy_pass http://192.168.2.130:5050/coach; } location /sonarr { proxy_pass http://192.168.2.130:8989/sonarr; } location ~ /netdata/(?<ndpath>.*) { proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://backend/$ndpath$is_args$args; proxy_http_version 1.1; proxy_pass_request_headers on; proxy_set_header Connection "keep-alive"; proxy_store off; } } the URL needs to have a trailing /, I couldn't work that out yet. Hope it works for you. there are also official ngnix, apache, lighttpd and caddy examples https://github.com/firehol/netdata/wiki/Running-behind-nginx https://github.com/firehol/netdata/wiki/Running-behind-apache https://github.com/firehol/netdata/wiki/Running-behind-lighttpd https://github.com/firehol/netdata/wiki/Running-behind-caddy Thanks for this. Did you manually create the proxy.conf and auth.conf files? I am trying to wrap my head around this reverse proxy stuff. Quote Link to comment
roland Posted August 18, 2016 Author Share Posted August 18, 2016 Yes, I "copied" them manually from the Let's Encrypt thread (I think I used this example: http://lime-technology.com/forum/index.php?topic=43696.msg437353#msg437353) There are a few more examples in that thread and there is also an interesting approach to have a docker that generates the reverse proxy automatically. Start reading from here: http://lime-technology.com/forum/index.php?topic=43696.msg476068#msg476068 But you need to be able to define more subdomains. Good luck! Quote Link to comment
numbnu7s Posted September 30, 2016 Share Posted September 30, 2016 Hi, I recently upgraded to unraid 6.2 and had to re-install netdata. It installs fine but when I open a browser it displays only one line of text. Access to file '/usr/share/netdata/web/' is not permitted. I read through this post and I didn't see anything related to this and I don't see any netdata directory in /usr/share/ any ideas? thx Quote Link to comment
boxland Posted September 30, 2016 Share Posted September 30, 2016 Hi, I recently upgraded to unraid 6.2 and had to re-install netdata. It installs fine but when I open a browser it displays only one line of text. Access to file '/usr/share/netdata/web/' is not permitted. I read through this post and I didn't see anything related to this and I don't see any netdata directory in /usr/share/ any ideas? thx Same problem here also. Quote Link to comment
BlackDwarf Posted September 30, 2016 Share Posted September 30, 2016 Hi, I recently upgraded to unraid 6.2 and had to re-install netdata. It installs fine but when I open a browser it displays only one line of text. Access to file '/usr/share/netdata/web/' is not permitted. I read through this post and I didn't see anything related to this and I don't see any netdata directory in /usr/share/ any ideas? thx Same problem here also. And here. Quote Link to comment
roland Posted September 30, 2016 Author Share Posted September 30, 2016 Yes, I got the same problem myself. It does not seem to be a 6.2 issue as I had it running on 6.2 before the recent update. I will raise this with the docker and netdata developers. Sorry, I am out of my dept here. Do you guys have any useful logs? Quote Link to comment
mswango Posted September 30, 2016 Share Posted September 30, 2016 Same problem after update Quote Link to comment
numbnu7s Posted October 1, 2016 Share Posted October 1, 2016 Yes, I got the same problem myself. It does not seem to be a 6.2 issue as I had it running on 6.2 before the recent update. I will raise this with the docker and netdata developers. Sorry, I am out of my dept here. Do you guys have any useful logs? Not sure if it's useful or not but here's my log file. Here's my start up: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Netdata" --net="host" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -v "/mnt/cache/appdata/netdata":"/etc/netdata":rw -v "/proc":"/host/proc":ro -v "/sys":"/host/sys":ro --cap-add SYS_PTRACE --log-opt max-size=50m --log-opt max-file=1 titpetric/netdata Quote Link to comment
roland Posted October 1, 2016 Author Share Posted October 1, 2016 OK, there is a workaround. go into the docker docker exec -it Netdata bash and run chown -R root:root /usr/share/netdata/web/ This is due to a change the docker dev made in the last build, deciding to run netdata as root in the docker. I am sure he will work it out somehow and resolve it soon. see: https://github.com/firehol/netdata/issues/1051 that refers to : https://github.com/titpetric/netdata/issues/18 Quote Link to comment
numbnu7s Posted October 1, 2016 Share Posted October 1, 2016 OK, there is a workaround. Awesome... it worked. Thank you Quote Link to comment
boxland Posted October 1, 2016 Share Posted October 1, 2016 Thanks for the workaround. Quote Link to comment
mswango Posted October 1, 2016 Share Posted October 1, 2016 That worked..... Thank You!!!!! Quote Link to comment
roland Posted October 4, 2016 Author Share Posted October 4, 2016 the newest version now has the chmod built in. Just update and it works again!! thanks to titpetric (https://github.com/titpetric) Quote Link to comment
xxredxpandaxx Posted October 21, 2016 Share Posted October 21, 2016 Netdata is now showing the cpu usage as much higher than both the unraid gui and cAdvisor. While cAdvisor and unraid gui show the cpu usage around 5-10% netdata shows it at 80-100% Quote Link to comment
roland Posted October 23, 2016 Author Share Posted October 23, 2016 Netdata is now showing the cpu usage as much higher than both the unraid gui and cAdvisor. While cAdvisor and unraid gui show the cpu usage around 5-10% netdata shows it at 80-100% Is that still the case for you? I have just checked mine and they are both on 29% and 31% respectively. Quote Link to comment
xxredxpandaxx Posted October 23, 2016 Share Posted October 23, 2016 It's now showing both at around 1% Sent from my iPhone using Tapatalk Quote Link to comment
mgworek Posted January 26, 2017 Share Posted January 26, 2017 anyone have problems starting it after last update? I updated it this morning and now it won't start. Logs show this /run.sh: line 27: conditional binary operator expected /run.sh: line 27: syntax error near `[[' /run.sh: line 27: `if [[ $SLACK_WEBHOOK_URL ]]; then' Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.