After upgrade to Ubuntu 20.04 LTS Netdata will not load in my browser
Netdata was running perfectly on my home system prior to my upgrade to Ubuntu 20.04 Wednesday. Now when I enter http://192.168.0.220:19999 into my browser it just will not load. I’ve checked and it’s running:
netdata 429047 0.2 0.0 175120 12996 ? Ssl 17:21 0:00 /usr/sbin/netdata -D netdata 429107 0.0 0.0 5076 4132 ? S 17:21 0:00 bash /usr/lib/netdata/plugins.d/alarm-notify.sh sysadmin localhost 1596318081 1596316947 80 1601489172 10min_cpu_iowait system.cpu cpu WARNING CLEAR 41 37 17@/etc/netdata/health.d/cpu.conf 3780 0 % average CPU wait I/O for the last 10 minutes 41% 37% NOSOURCE NOERRMSG 0 0 netdata 429110 0.5 0.1 46932 26188 ? Sl 17:21 0:00 /usr/bin/python3 /usr/lib/netdata/plugins.d/python.d.plugin 1 netdata 429111 0.0 0.0 4332 3504 ? S 17:21 0:00 bash /usr/lib/netdata/plugins.d/tc-qos-helper.sh 1 netdata 429118 0.0 0.0 55228 5520 ? S 17:21 0:00 /usr/lib/netdata/plugins.d/apps.plugin 1 netdata 429120 0.0 0.0 4608 696 ? S 17:21 0:00 /usr/lib/netdata/plugins.d/nfacct.plugin 1 netdata 429190 0.0 0.0 38124 5988 ? S 17:21 0:00 /usr/sbin/sendmail -t netdata 429191 0.0 0.0 38116 5876 ? S 17:21 0:00 /usr/sbin/postdrop -r
These are the ports it’s connected to:
tcp 0 0 127.0.0.1:8125 0.0.0.0:* LISTEN 418542/netdata tcp 0 0 192.168.0.220:19999 0.0.0.0:* LISTEN 418542/netdata udp 0 0 127.0.0.1:8125 0.0.0.0:* 418542/netdata
Firefox keeps reporting
Firefox can’t establish a connection to the server at 192.168.0.220:19999
This is just on my home system but I’m a glutton for stats and really like the information I was getting from Netdata. Any advice or troubleshooting info would be appreciated.
Can you please send us the logs, as shown in the documentation? Also, did you try to restart netdata service or try a different browser?
Don’t worry, we will get to the bottom of this
@OdysLam Oddly enough after again stopping and restarting Netdata it’s now working correctly. I did notice one error in my ‘error’ log a minute ago.
netdata ERROR : WEB_SERVER[static1] : PROCFILE: Cannot open file '/etc/netdata/.environment' (errno 2, No such file or directory)
I just now got an iowait warning vie email from last Wed, 30 Sep which is the day I started the 20.04 upgrade. I’ll keep an eye on it however I think that like the network connectivity problem I had for 3 days after the upgrade which fixed itself somehow the same has happened with Netdata. I guess there really is magic in the air. Appreciate you getting back ot me so quickly.
Thanks for that log file. How did you install netdata?
(P.S Magic and love* is in the air. )
I installed via Ubuntu repos under 18.04 and it was updated with the 20.04 upgrade:
apt-cache policy netdata netdata: Installed: 1.19.0-3ubuntu1 Candidate: 1.19.0-3ubuntu1 Version table: *** 1.19.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/universe i386 Packages
And here is our culprit!
I would ask you to uninstall netdata and install it using the method we suggest in our documentation: https://learn.netdata.cloud/docs/get
The reason is that those packages are not controlled by us but by the package maintainers. Thus we can’t ensure quality or feature-completeness. (Some distributions omit certain features of netdata).
@OdysLam What a pain in the rear removing the Ubuntu version was! Apt remove --purge (with sudo of course) did absolutely nothing. Ran it three times and all the files remained. I had to resort to manually listing all the files in a terminal then going 1 by 1 and moving them to trash. Think it’s time for my first bug report in 20.04. Anyway, after all that I ran your install script and the first 2 times I kept getting:
bash <(curl -Ss https://my-netdata.io/kickstart.sh) curl: (6) Could not resolve host: my-netdata.io
Pinged ‘my-netdata.io’ and got a good return then the script ran. The 2 minutes according to the install page actually took me about 45 with the manual removal but it’s done and I’m happy with the results.
Thanks again for your reply and assistance
Hello @chris-pollock ,
We are not the maintainers of Ubuntu repo, but we have our official repo https://packagecloud.io/netdata/netdata.
About the error you are having, I ran now on my local machine a
nslookupand I can resolve the addresses:
bash-5.0$ nslookup my-netdata.io Server: 18.104.22.168 Address: 22.214.171.124#53 Non-authoritative answer: Name: my-netdata.io Address: 126.96.36.199 Name: my-netdata.io Address: 188.8.131.52 Name: my-netdata.io Address: 184.108.40.206 Name: my-netdata.io Address: 2606:4700:3033::681c:3f8 Name: my-netdata.io Address: 2606:4700:3036::ac43:9cc0 Name: my-netdata.io Address: 2606:4700:3035::681c:2f8
Are you not having DNS problem?
@Thiago-Marques-0 Thank you for your reply. Yes, I was advised earlier to remove the Ubuntu version and install the official one which I have done. I run Bind9 here on my desktop as a caching nameserver. I really never thought to run nslookup yesterday as this upgrade to 20.04 is the worst I’ve seen as far as glitches, missing software and so on. So far it’s taken me five days to get my system back to somewhat normal again. Luckily I do nightly backups and have everything from my 18.04 system. As far as resolving the address I ran nslookup this morning:
time nslookup my-netdata.io Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: my-netdata.io Address: 220.127.116.11 Name: my-netdata.io Address: 18.104.22.168 Name: my-netdata.io Address: 22.214.171.124 Name: my-netdata.io Address: 2606:4700:3035::681c:2f8 Name: my-netdata.io Address: 2606:4700:3033::681c:3f8 Name: my-netdata.io Address: 2606:4700:3036::ac43:9cc0 real 0m10.563s user 0m0.016s sys 0m0.000s time nslookup my-netdata.io Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: my-netdata.io Address: 126.96.36.199 Name: my-netdata.io Address: 188.8.131.52 Name: my-netdata.io Address: 184.108.40.206 Name: my-netdata.io Address: 2606:4700:3035::681c:2f8 Name: my-netdata.io Address: 2606:4700:3036::ac43:9cc0 Name: my-netdata.io Address: 2606:4700:3033::681c:3f8 real 0m0.013s user 0m0.006s sys 0m0.005s
So it all seems to be fine now. I sometimes think also that my DSL provider has issues.
@chris-pollock we can never discard problems with DSL providers, last week I had to set manually the nameserver to
220.127.116.11, because my ISP had DNS problems, this was the motive I asked you about
I am glad that everything is fine, please, let us know if you have any problem.