Graphs occasionally freeze even though new data is arriving

[telsin]

usually seems to occur after a data source has been offline for a while (1h + ?) but then comes back online naturally, due to a network interruption for example.

While avoid the issue would be preferable, a good "repair" might be a way to signal a graph to reset (which would also restore the time scale to default) via a right click menu option.

Current work around is to restart vodka.

[vegu]

How often does this happen ? Pretty much anytime there is a longer gap, or have there been longer gaps where this issue did not appear?

[telsin]

unclear, usually spotted in the morning, and checking history reveals a network outage between vaping and vodka/graphserv of an hour+. Never seen it without being able to identify an outage though.

[vegu]

This was observed while running graphsrv 1.0.6, correct ? No luck so far trying to reproduce it with the latest github checkout.

[telsin]

Looks like a custom install by grizz, ask him what the NCHC noc is running, version wise. And how to convert to a normal pip install ;)

[vegu]

Might be caused by this issue: 20c/vodka#8

[telsin]

It still happens in 1.1.3. appears to be a case of graphsrv/vodka not noticing a session has closed when the client side goes away:

[root@spire openvpn]# netstat -an | grep 7461
tcp 0 0 0.0.0.0:7461 0.0.0.0:* LISTEN
[root@spire openvpn]# ps ax | grep vaping
8362 pts/0 Sl 0:02 /bin/python2.7 /usr/bin/vaping --debug start
32242 pts/0 S+ 0:00 grep --color=auto vaping

[root@netflowx vodka]# netstat -an | grep 7461
tcp 0 0 10.34.0.10:60134 10.34.3.2:7461 ESTABLISHED

[root@spire openvpn]# kill 8362
[root@spire openvpn]# ps ax | grep vaping
32634 pts/0 S+ 0:00 grep --color=auto vaping
[root@spire openvpn]# netstat -an | grep 7461
[root@spire openvpn]#

[root@netflowx vodka]# netstat -an | grep 7461
tcp 0 0 10.34.0.10:60134 10.34.3.2:7461 ESTABLISHED

This last item is like 5 minutes later too, session is not Established or coming back. Guessing it may return in whatever the long term socket timeout is?

[telsin]

still happens with 1.2.0, btw.

[vegu]

guess me wishing it away didn't work ;)