Gateway latency graph empty after upgrade to C169

Getting Started with IPFire Updates Trouble
1

hi
i have several errors after the update 169
in report system

Requests with error response codes
    401 Unauthorized
       /cgi-bin/index.cgi: 3 Time(s)
       /graphs/vnstat-5-green0.png: 1 Time(s)
       /graphs/vnstat-d-green0.png: 1 Time(s)
       /graphs/vnstat-h-green0.png: 1 Time(s)
       /graphs/vnstat-m-green0.png: 1 Time(s)
       /graphs/vnstat-s-green0.png: 1 Time(s)
       /graphs/vnstat-t-green0.png: 1 Time(s)

in kernel


WARNING:  Segmentation Faults in these executables
    libxml2.so.2.9. :  1

in graph gateway

Graphique de la qualité réseau (autres)
Graphique de la qualité réseau (autres)960×418 8.38 KB

no graph
ty

2

Hi,

thank you for reporting back.

However, aside from the empty gateway latency graph, these errors can all be safely ignored. During the update, major parts of the web interface are being changed, so it is normal to see some glitches being logged, since things like the speed display snippet will continue to generate HTTP requests during the upgrade.

libxml2 has been updated as well, as mentioned in the changelog. If any process still running against the old version tries to conduct some XML parsing by chance, that will fail - with the log message you noted.

After a reboot, such log messages should not happen anymore. If they do, please let us know.

Does the empty gateway graph persist after a reboot as well?

Thanks, and best regards,
Peter MĂĽller

3

ty
I have done a reboot with a system file check for errors I have to wait for the logs to be updated
for the graph nothing it did not appear

4

Hi,

just for the records, an ordinary reboot is completely sufficient after an upgrade. There is no need for a forced file system check. :slight_smile:

I assume the graph worked before. If so, please answer the following questions:

  • From which Core Update were you upgrading?
  • Are there any correspondent log messages in the firewall logs (they include DROP_OUTPUT)?
  • What is the gateway to your IPFire? An upstream router, your ISP, … ?
  • What is the output of ping -c 5 gateway on your IPFire machine?

Thanks, and best regards,
Peter MĂĽller

2 Likes
5

hi

From which Core Update were you upgrading?

168

Are there any correspondent log messages in the firewall logs (they include DROP_OUTPUT)?

no

What is the gateway to your IPFire? An upstream router, your ISP, … ?

ISP router bridge mode

What is the output of ping -c 5 gateway on your IPFire machine?

ping -c 5 gateway
# ping -c 5 gateway
PING gateway (x.x.x.x) 56(84) bytes of data.

--- gateway ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4100ms

ty

6

Hi,

well, for some reason, your gateway does not respond to pings (anymore). Therefore, the graph cannot show anything since there is no data to display.

Thanks, and best regards,
Peter MĂĽller

2 Likes
7

hi
ok I’m going to restart the bridge
ty

8

hi
i have restart the bridge and ipfire
same result gateway does not respond to pings
ty

9

hi

for the logs is ok no error
ty

10

In my one case, the ISP gateway is also not responding to pings.
Below I provide a link to some workaround:

Regards

1 Like
11

hi
I tried your solution but it doesn’t work, only the gateway graph is displayed, not the other 2
ty

12

Don’t give up :grinning:

I did a test on the VM.
I entered the following lines into the /etc/collectd.custom file and rebooted the VM.

obraz

The result, after entering into the /etc/collectd.custom file, rebooting and waiting a few minutes

obraz
obraz613Ă—822 84.1 KB

Note that the interval is 30 seconds.

edit:

Next test.
I edited the /etc/collectd.custom file as follows and restarted the VM.

obraz

Below is the effect after rebooting and waiting a few minutes.

obraz
obraz568Ă—881 93.2 KB

edit2:
Next test just to be sure.

obraz

obraz
obraz579Ă—863 102 KB

Tested on Core Update 169 Development Build

Regards.

1 Like
13

hi
I tested it again and it works
thank you for your solution
ty

1 Like