Closed DefenceLogic closed 4 years ago
unfortunately the config source is hardcoded to server today,. You can follow the code to see how to set up a config server: https://github.com/google/seesaw/blob/67eba17cffd346e0d616e7972307c64d15662693/engine/config/notifier.go#L299
Other alternatives: https://github.com/google/seesaw/blob/67eba17cffd346e0d616e7972307c64d15662693/cli/core.go#L75
seesaw_cli has a command to set config source. I didn't try it but you can try it out to change it: $ config source disk
This works only after you have started the seesaw_watchdog service, the command needed is
/usr/bin/seesaw -c " config source disk"
I moved my compiled seesaw_cli to /usr/bin/seesaw as part of my build.
W0730 15:52:31.028663 11624 fetcher.go:186] Fetch failed: fetch failed from https://lb2.<domain fqdn>:10255/config/defencelogic-lb (172.16.4.164): dial tcp 172.16.4.164:10255: connect: connection refused
E0730 15:52:31.028674 11624 notifier.go:159] Failed to pull configuration: all config server requests failed
I0730 15:53:12.054469 11624 notifier.go:141] Checking for config changes...
I0730 15:53:12.054685 11624 notifier.go:173] No config changes found
I0730 15:53:31.027717 11624 notifier.go:141] Checking for config changes...
I0730 15:53:31.028043 11624 notifier.go:173] No config changes found
I0730 15:54:31.027741 11624 notifier.go:141] Checking for config changes...
Thank You
Dear Sirs,
In the seeswaw.cfg you enable the following
In the /var/log/seesaw/seesaw_engine.INFO log you get
Is there a way to disable this functionality as it does not seem to affect seesaw's operation? Alternatively, can someone point in the direction of some documentation on how to set this feature up?
Any help appreciated.