No display (rpm installation on CentOS 7)

Hi,

I’ve just installed netdata on a CentOS 7 system using the rpm method :
curl -s https://packagecloud.io/install/repositories/netdata/netdata/script.rpm.sh | sudo bash
yum install netdata.x86_64

Netdata seems to be running : systemctl status netdata shows
oct. 27 15:00:54 systemd[1]: Starting Real time performance monitoring…
oct. 27 15:00:54 systemd[1]: Started Real time performance monitoring.

Netstat show that netdata is listening :
# netstat -pantu | fgrep LISTEN | fgrep 1999
tcp 0 0 127.0.0.1:19999 0.0.0.0:* LISTEN 17997/netdata
tcp6 0 0 ::1:19999 :::* LISTEN 17997/netdata

The firewall is off :
# iptables -t filter -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

But the browser shows nothing …

Any hint ?
Thank you,
Michal

Hello @mbulik ,

Sorry for the delay, but I had to create a VM where I could install from scratch Netdata using the same method you used.

I observed that when Netdata finishes the installation, it is using the following /etc/netdata/netdata.conf:

[global]
    run as user = netdata

    # the default database size - 1 hour
    history = 3600

    # some defaults to run netdata with least priority
    process scheduling policy = idle
    OOM score = 1000

[web]
    web files owner = root
    web files group = netdata

    # by default do not expose the netdata port
    bind to = localhost

And as you can see, it is listening only localhost addresses. To access your Netdata from other host, you can set:

[web]
    bind to = *

this will force Netdata to be accessed from any host on your network. On the other hand, this will also give full access to Netdata for any person accessing the computer, if this is not wished, you can verify our documentation to give specific access for ports. Or you can run Netdata behind nginx to have authentication.

Best regards!

Hey mbulik, no worries. I edited your post and added the console output in a code block to make it more readable.

We are looking into it!

Oups, sorry. I forgot to escape the ‘#’ characters …

Hi,
Thanks a lot for your quick answers.

  1. When I run curl on the host I get the index.html file :
# curl -o index.html http://localhost:19999
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 89305  100 89305    0     0  12.5M      0 --:--:-- --:--:-- --:--:-- 14.1M

2. The log file shows only my two curl connections this morning :
2020-10-28 09:51:00: 1: 18132 '[localhost]:54440' 'CONNECTED'
2020-10-28 09:51:00: 1: 18132 '[localhost]:54440' 'DISCONNECTED'
2020-10-28 09:51:00: 1: 18132 '[localhost]:54440' 'FILECOPY' (sent/all = 89305/89305 bytes -0%, prep/sent/total = 1.09/0.74/1.82 ms) 200 '/'
2020-10-28 10:41:22: 2: 18119 '[localhost]:56226' 'CONNECTED'
2020-10-28 10:41:22: 2: 18119 '[localhost]:56226' 'DISCONNECTED'
2020-10-28 10:41:22: 2: 18119 '[localhost]:56226' 'FILECOPY' (sent/all = 89305/89305 bytes -0%, prep/sent/total = 0.04/0.95/0.99 ms) 200 '/'

3. On the host running netdata the firewall is off :
# firewall-cmd --state
not running

and the iptables have no rules :
# iptables -t filter -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination

I’ve also scanned the host with zenmap and I see no service listening at the port 19999 …

Thank you,
Michal

Thanks Thiago for jumping in this thread!

@mbulik, no worries! We have the expert here, so we will get to the bottom of this :slight_smile:

Hello @mbulik ,

When Netdata is installed, by default it listens all ports, and considering what you showed us, it is not expected to have this kind of problems, so I will ask you additional information for we understand what is happening.

1 - When you run curl -o index.html http://localhost:19999 on the host with Netdata, do you have return?
2 - Netdata has a log file that registers access, its name is /var/log/netdata/access.log, can you see data on it when you try to access from another host?
3 - On the host you are trying to access Netdata, do you have any firewall or proxy configured?

Best regards!