Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

What does this error mean? Manager failed to determine haConfig #36

Open
johntwei opened this issue Oct 17, 2017 · 0 comments
Open

What does this error mean? Manager failed to determine haConfig #36

johntwei opened this issue Oct 17, 2017 · 0 comments

Comments

@johntwei
Copy link

When starting seesaw, I saw following error in the seesaw_engine.ERROR file

E1016 17:16:02.756551 6427 core.go:366] Manager failed to determine haConfig: node 10.145.207.151 not configured

What does this mean? I do have seesaw.cfg and cluster.pb files and all the seesaw processes (watchdog, ncc, engine, ha, ecu, healthcheck) seem to be running.

10.145.207.151 is the current node, the peer is 10.145.207.153.
vip is configured on the lb NIC on both seesaw nodes. dummy0 is present too.

John
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johntwei