Bandwidth graph is gone

[moses]

After reinstalling to a CentOS server, everything is working fine, except the bandwidth graph is gone, appears to be something awry with jQuery:

It errors out every update interval.

http://fogserverIP/status/bandwidth.php returns the following:

{"dev":"unknown","rx":0,"tx":0}

[Wayne Workman]

A temporary fix would be to increase the bandwidth chart’s update cycle to something pretty high:
Web Interface -> FOG Configuration -> FOG Settings -> General Settings -> FOG_BANDWIDTH_TIME

Also, alerting @Tom-Elliott about this.

[Wayne Workman]

Also - we’ve seen this sort of thing happen when the interface for a storage node is wrong, or the IP for the storage node is wrong.

[moses]

@Wayne-Workman The errors don’t really cause much problem for me because I don’t spend much time on the homepage.

If there are any other logs I can post that would be helpful, let me know.

Edit: that was the first thing I checked, both are correct.

[Wayne Workman]

@moses So what was different about the reinstall ?

[moses]

@Wayne-Workman I reinstalled due to a Linux kernel issue, but nothing changed as far as configuration. The one thing I did do was restore from a backup of the database.

[Tom Elliott]

Maybe firewall?

[moses]

@Tom-Elliott I used CentOS Minimal, which doesn’t have firewalld installed.

[Tom Elliott]

@moses What about selinux/iptables?

[Sebastian Roth]

@moses What is your main network interface on that machine?

[moses]

@Tom-Elliott SELinux is set to permissive (just confirmed that). Not sure how to properly check iptables or what to look for there, could you elaborate?

[Tom Elliott]

@moses iptables -L -n

[moses]

@Tom-Elliott Here’s the output:

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

[moses]

@Sebastian-Roth Interface name is ‘eno1’

[Tom Elliott]

@moses You sure it’s eno1 and not eno1777728 or somethign like that?

[Tom Elliott]

@moses How did you confirm selinux was set to permissive? sestatus?

[moses]

@Tom-Elliott

[admin@localhost bin]$ ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.66  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::9eb6:54ff:fef0:3e0d  prefixlen 64  scopeid 0x20<link>
        ether 9c:b6:54:f0:3e:0d  txqueuelen 1000  (Ethernet)
        RX packets 71305  bytes 55866671 (53.2 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 64775  bytes 60474259 (57.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 11135  bytes 37843099 (36.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 11135  bytes 37843099 (36.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[admin@localhost bin]$ sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   permissive
Mode from config file:          permissive
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      28

[Tom Elliott]

@moses and what does the node look like? Understand I’m just trying to see/get all the details

[moses]

@Tom-Elliott

[Tom Elliott]

@moses can you try updTing?