Closed Dieterbe closed 8 years ago
The first error, is an error event sent from the collector-controller. Essentially it is that the websocket message sent was malformed.
The second error is the reverse, were raintank-collector received an invalid message.
The third message looks to be a race condition, but is only triggered when a ping response is received at the same time that the ping is considered to have timed out. This timeout is 10seconds.
All 3 of these issues indicate that your server has some significant networking problem.
As the problem for the first two issues is due to data corruption while in transit, the crash that happened is expected.
The third issue is in github.com/raintank/go-pinger and ill open an issue there.
interesting. for the record, this was on devstack (raintank-docker) on my laptop. first time i notice this though. i did do a system upgrade the other day, i wonder if it's related. here's some potentially related packages:
[2015-11-30 18:32] [ALPM] upgraded docker (1:1.9.0-1 -> 1:1.9.1-1)
[2015-11-30 18:32] [ALPM] upgraded systemd (227-1 -> 228-3)
...
[2015-11-30 18:32] [ALPM] upgraded network-manager-applet (1.0.6-1 -> 1.0.8-1)
[2015-11-30 18:32] [ALPM] upgraded networkmanager (1.0.7-1 -> 1.0.8-1)
https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/docker&id=cee29e8c13318442d94b4f09c1720b73e51a14fd https://github.com/docker/docker/blob/master/CHANGELOG.md docker udate looks fairly harmless but maybe it's related.
no idea what these are about. i'm just running devstack, with 1 endpoint set to hostname
grafana
, all default settings.it was running fine until i saw gaps in the graph and noticed a bunch of different errors in the collector log:
the first one looked like it may be related to the collector controller, so i also checked the grafana log: