roland Posted March 8, 2020 Author Share Posted March 8, 2020 7 hours ago, bastl said: Why is TRACKING enabled by default? This is the default behaviour in the vanilla netdata installation. I don't believe it is my place to disable it for everyone by default, but this makes it easy and in my opinion obvious to everyone that uses this template to at least think about it. https://docs.netdata.cloud/docs/anonymous-statistics/#opt-out 2 Quote Link to comment
mattgob86 Posted March 9, 2020 Share Posted March 9, 2020 Is there something that needs to happen to get nvidia SMI data to work in this new docker? I had it working in the old one but now the steps to create it before are not working. Quote Steps to reproduce: Grab the docker from Community Apps. During the initial container install switch to advanced view, and add --runtime=nvidia to the end of the list. Add a new variable "NVIDIA_VISIBLE_DEVICES" with the value set to "all" Click done, and let the docker install. Open a console for the docker. echo "nvidia_smi: yes" >> /etc/netdata/python.d.conf Restart the docker. Enjoy. 1 Quote Link to comment
scubieman Posted March 9, 2020 Share Posted March 9, 2020 Hope to set up a ENV variable, but clueless where this is at or what I put ETC. I want to setup pushbullet. Do I add a variable to my docker ? If so what goes in the name,key, and value? Quote -e PUSHBULLET_ACCESS_TOKEN=o.l8VuizWhXgbERf2Q78ghtzb1LDCYvbSD -e [email protected] Quote Link to comment
Squid Posted March 9, 2020 Share Posted March 9, 2020 key: PUSHBULLET_ACCESS_TOKEN value: o.l8VuizWhXgbERf2Q78ghtzb1LDCYvbSD Name is the "human" description 1 Quote Link to comment
scubieman Posted March 9, 2020 Share Posted March 9, 2020 1 minute ago, Squid said: key: PUSHBULLET_ACCESS_TOKEN value: o.l8VuizWhXgbERf2Q78ghtzb1LDCYvbSD Name is the "human" description Thank you Quote Link to comment
IGOBYD Posted March 30, 2020 Share Posted March 30, 2020 what is up with the constant updates to Netdata, becoming annoying! Quote Link to comment
Arbadacarba Posted April 1, 2020 Share Posted April 1, 2020 On 3/6/2020 at 8:10 PM, roland said: Thank you all! @L0rdRaiden @Squid @Dazog I have - updated the template to point to the official docker - added the PGID as well as the DO_NOT_TRACK variable - updated the logo again. the template is on github: https://raw.githubusercontent.com/Data-Monkey/docker-templates/master/Data-Monkey/netdata.xml thanks for all your help. I had the old version reporting on my UPS - but when I replaced it with the new version I can't get it to work. Was Sudo removed? Thanks Quote Link to comment
Crewger Posted April 3, 2020 Share Posted April 3, 2020 On 3/9/2020 at 2:37 AM, mattgob86 said: Is there something that needs to happen to get nvidia SMI data to work in this new docker? I had it working in the old one but now the steps to create it before are not working. Any update on this? Looks like the same guide from before doesn't work for adding the nvidia SMI plugin :( 1 Quote Link to comment
ThaFacialHair Posted April 3, 2020 Share Posted April 3, 2020 Im trying to add this docker to my nodes list for netdata cloud and it cant seem to access the site. Any advice? Quote Link to comment
AlexB108 Posted April 3, 2020 Share Posted April 3, 2020 Hey guys, Loving the netdata container and having fun playing with it. Currently trying to get the back end configuration for getting data into influxdb, so I can talk myself into out of buying a new CPU by having data to back up my hypothesis I am smashing my CPU. I have got the netdata.conf file from http://{localhost}:19999/netdata.conf and edited it to contain the following: [backend] # host tags = enabled = yes data source = average type = graphite destination = udp:10.0.0.2:8086 prefix = netdata hostname = Tower # update every = 10 # buffer on failures = 10 # timeout ms = 20000 # send names instead of ids = yes # send charts matching = * # send hosts matching = localhost * I then saved this to /mnt/cache/appdata/netdata/netdata.conf (which is what I have mapped to /etc/netdata/override), and restarted the container. However it doesn't seem to be picked up, and when I then do http://{localhost}:19999/netdata.conf again, it is set to the defaults. I have a feeling that I am missing something stupid, but for the life of me I can't work it out. I have tried remapping /etc/netdata/override to a different location, as well as using vim to create the file rather than saving it locally and then dropping it into /mnt/cache/appdata/netdata/ location. Any help would be greatly appreciated! Thanks, Alex Quote Link to comment
Markland Posted April 7, 2020 Share Posted April 7, 2020 (edited) On 3/8/2020 at 10:37 PM, mattgob86 said: Is there something that needs to happen to get nvidia SMI data to work in this new docker? I had it working in the old one but now the steps to create it before are not working. On 4/3/2020 at 8:27 AM, Crewger said: Any update on this? Looks like the same guide from before doesn't work for adding the nvidia SMI plugin I have tired to get it to work as well and I cant figure it out. Anyone know of a way to install an earlier release of the container? Maybe that would work? 58 minutes ago, Markland said: I even went as far as installing random dockers and putting in the above variable and parameters and nvidia-smi worked in them.... Edited April 7, 2020 by Markland more data Quote Link to comment
Markland Posted April 8, 2020 Share Posted April 8, 2020 22 hours ago, Markland said: I have tired to get it to work as well and I cant figure it out. Anyone know of a way to install an earlier release of the container? Maybe that would work? Guys I posted this on Reddit and got it to work by using a different docker. Linked is the Reddit thread. And what I did: "I took D34DC3N73R's docker and shoved it in Data-monkey aka roland's template from the CA Hub and tada it works. All of my gpus that support nvidia-smi showed up! Now onto custom configs and things. Muahahaha!" I dont know if everything works but it seems to be! D34DC3N73R's docker: https://hub.docker.com/r/d34dc3n73r/netdata-glibc Quote Link to comment
szymon Posted April 14, 2020 Share Posted April 14, 2020 On 4/1/2020 at 7:48 AM, Arbadacarba said: I had the old version reporting on my UPS - but when I replaced it with the new version I can't get it to work. Was Sudo removed? Thanks I can confirm that the UPS reporting is now also gone for me. Any chances of bringing it back? Quote Link to comment
primeval_god Posted April 16, 2020 Share Posted April 16, 2020 (edited) On 4/3/2020 at 5:53 PM, AlexB108 said: I then saved this to /mnt/cache/appdata/netdata/netdata.conf (which is what I have mapped to /etc/netdata/override), and restarted the container. A while back this template switched to using the official Netdata Docker Image netdata/netdata. The official image does not have the /etc/netdata/override feature that was present in the old titpetric/netdata image. Try mapping your config folder to /etc/netdata directly (/mnt/cache/appdata/netdata -> /etc/netdata). I believe that is the proper way to do it now, but if it doesnt work or causes other problems try mapping the file into the container instead -v /mnt/cache/appdata/netdata/netdata.conf:/etc/netdata/netdata.conf @szymon @Arbadacarba Did you have a config file mapped in to get UPS support? If so see my answer to @AlexB108 above. Edited April 16, 2020 by primeval_god Quote Link to comment
cinereus Posted April 18, 2020 Share Posted April 18, 2020 Any idea why my fanspeeds have suddenly disappeared from netdata this morning (or how to get them back?) Quote Link to comment
SudoPacman Posted April 21, 2020 Share Posted April 21, 2020 (edited) Hmm, this appears to store it's databases in the docker image?! There are in /var/cache/netdata/dbengine Isn't that just going to grow and grow? I'm going to try mapping it to appdata somewhere. Edit: Hmm no, doesn't work: 2020-04-21 17:20:33: netdata INFO : MAIN : Data files not found, creating in path "/var/cache/netdata/dbengine". 2020-04-21 17:20:33: netdata INFO : MAIN : Creating new data and journal files in path /var/cache/netdata/dbengine 2020-04-21 17:20:33: netdata ERROR : MAIN : uv_fs_write: bad address in system call argument (errno 14, Bad address) 2020-04-21 17:20:33: netdata ERROR : MAIN : Failed to create data and journal files in path "/var/cache/netdata/dbengine". Edited April 21, 2020 by SudoPacman Quote Link to comment
Markland Posted April 30, 2020 Share Posted April 30, 2020 Ok so I found a weird bug I think. When I install the netdata-glibc stock their is no config file in the override folder. I noticed that when I told it to not mnt the override folder all of a sudden the config files appeared in the /etc/netdata. Has anyone run into something similar and or a fix for this? Quote Link to comment
primeval_god Posted April 30, 2020 Share Posted April 30, 2020 13 hours ago, Markland said: Ok so I found a weird bug I think. When I install the netdata-glibc stock their is no config file in the override folder. I noticed that when I told it to not mnt the override folder all of a sudden the config files appeared in the /etc/netdata. Has anyone run into something similar and or a fix for this? Are you perhaps looking for this support thread ? I dont believe that the netdata container supported by this thread has an override folder at this point. Quote Link to comment
Markland Posted May 1, 2020 Share Posted May 1, 2020 On 4/30/2020 at 12:41 PM, primeval_god said: I dont believe that the netdata container supported by this thread has an override folder at this point. Nope this docker for one still comes with the override directory when you pull it. Its still in the template. Two that override dir does nothing as netdata no longer uses it and so when you modify the template before installing to be etc/netdata it doesn't work their are no configs but there were configs when the the template was pointing to the override folder. Also I checked it on the other one you mentioned and both have the same behavior. The etc/netdata folder the should contain configs is empty except for .opt-out-form.... and the claim.d Quote Link to comment
roland Posted May 2, 2020 Author Share Posted May 2, 2020 OK, I missed it. The official docker does not support the override folder that the previous version had. So if we need config files, we need to mount them one-by-one. To start with the master config file, get the template from your netdata docker: wget [your_netdata_ip]:19999/netdata.conf then edit that file and mount it into the docker: -v '/mnt/cache/appdata/netdata/netadata.conf':'/etc/netdata/netadata.conf':'rw' 'ro' might be good enough you can repeat that with all other files that you need. Sorry, this seems to be the only solution they support currently. I will remove the override mount from the template now. 1 Quote Link to comment
L0rdRaiden Posted May 12, 2020 Share Posted May 12, 2020 I have this configuration and it was working until now I get this errors now Access to file is not permitted: /usr/share/netdata/web//index.html The logs repeats itself with other dockers I have. 2020-05-12 14:20:55: cgroup-name.sh: INFO: Running API command: curl --unix-socket /var/run/docker.sock http://localhost/containers/1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62/json 2020-05-12 14:20:55: cgroup-name.sh: INFO: docker container '1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62' is named 'Tautulli' 2020-05-12 14:20:55: cgroup-name.sh: INFO: cgroup 'docker_1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62' is called 'Tautulli' 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network INFO : MAIN : Using host prefix directory '/host' 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network INFO : MAIN : running: exec /usr/libexec/netdata/plugins.d/cgroup-network-helper.sh --cgroup '/host/sys/fs/cgroup/cpuacct/docker/1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62' 2020-05-12 14:20:55: cgroup-network-helper.sh: INFO: searching for network interfaces of cgroup '/host/sys/fs/cgroup/cpuacct/docker/1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62' 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network ERROR : MAIN : child pid 974 exited with code 1. 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network ERROR : MAIN : Cannot find a cgroup PID from cgroup '/host/sys/fs/cgroup/cpuacct/docker/1659bb1d4973cd61bfb530260cf031019d70fdf973d8e2d0b06d4b82ea058e62' 2020-05-12 14:20:55: cgroup-name.sh: INFO: Running API command: curl --unix-socket /var/run/docker.sock http://localhost/containers/7c9948d84533e2f51d1fec6fba3fa98a03cae05fd949ea5caf03cd67a47be39d/json 2020-05-12 14:20:55: cgroup-name.sh: INFO: docker container '7c9948d84533e2f51d1fec6fba3fa98a03cae05fd949ea5caf03cd67a47be39d' is named 'Pi-Hole' 2020-05-12 14:20:55: cgroup-name.sh: INFO: cgroup 'docker_7c9948d84533e2f51d1fec6fba3fa98a03cae05fd949ea5caf03cd67a47be39d' is called 'Pi-Hole' 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network INFO : MAIN : Using host prefix directory '/host' 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network INFO : MAIN : running: exec /usr/libexec/netdata/plugins.d/cgroup-network-helper.sh --cgroup '/host/sys/fs/cgroup/cpuacct/docker/7c9948d84533e2f51d1fec6fba3fa98a03cae05fd949ea5caf03cd67a47be39d' 2020-05-12 14:20:55: cgroup-network-helper.sh: INFO: searching for network interfaces of cgroup '/host/sys/fs/cgroup/cpuacct/docker/7c9948d84533e2f51d1fec6fba3fa98a03cae05fd949ea5caf03cd67a47be39d' 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network ERROR : MAIN : child pid 1004 exited with code 1. 2020-05-12 14:20:55: /usr/libexec/netdata/plugins.d/cgroup-network ERROR : MAIN : Cannot find a cgroup PID from cgroup '/host/sys/fs/cgroup/cpuacct/docker/7c9948d84533e2f51d1fec6fba3fa98a03cae05fd949ea5caf03cd67a47be39d' Quote Link to comment
L0rdRaiden Posted May 12, 2020 Share Posted May 12, 2020 I have downgrade to netdata/netdata:v1.21.0 and then I have come back to netdata/netdata and now it works. Maybe something was corrupt. Quote Link to comment
mint Posted May 12, 2020 Share Posted May 12, 2020 2 hours ago, L0rdRaiden said: I have downgrade to netdata/netdata:v1.21.0 and then I have come back to netdata/netdata and now it works. Maybe something was corrupt. How did you go about doing this? Quote Link to comment
L0rdRaiden Posted May 12, 2020 Share Posted May 12, 2020 5 hours ago, mint said: How did you go about doing this? what do you mean? Quote Link to comment
stefan marton Posted May 13, 2020 Share Posted May 13, 2020 (edited) after update to new version i dont see docker name only the id then before update i see the container name Edited May 13, 2020 by stefan marton 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.