yanic/contrib/respondd-crashed
Martin/Geno d6875c5a39
[TASK] add respondd-crashed
a tool to find wrong offline detected nodes.
by pinging the nodes which does not answer by respondd
2019-02-27 02:57:40 +01:00
..
README.md [TASK] add respondd-crashed 2019-02-27 02:57:40 +01:00
helper.go [TASK] add respondd-crashed 2019-02-27 02:57:40 +01:00
helper_test.go [TASK] add respondd-crashed 2019-02-27 02:57:40 +01:00
hook.go [TASK] add respondd-crashed 2019-02-27 02:57:40 +01:00
main.go [TASK] add respondd-crashed 2019-02-27 02:57:40 +01:00
run.go [TASK] add respondd-crashed 2019-02-27 02:57:40 +01:00
status.go [TASK] add respondd-crashed 2019-02-27 02:57:40 +01:00

README.md

respondd-crashed

This tool ping every "offline" node at every ip address of a meshviewer.json to detect, if a respondd deamon is not running anymore.

give access to run ping

 sudo setcap cap_net_raw=+ep %GOPATH/bin/respondd-crashed

Usage

Usage of respondd-crashed: -ll-iface string interface to ping linklocal-address -loglevel uint Show log message starting at level (default 40) -meshviewer-path string path to meshviewer.json from yanic (default "meshviewer.json") -ping-count int count of pings (default 3) -ping-timeout duration timeout to wait for response (default 5s) -run-every duration repeat check every (default 1m0s) -status-path string path to store status (default "respondd-crashed.json") -timestamps Enables timestamps for log output