-
Notifications
You must be signed in to change notification settings - Fork 918
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.
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
API reports a problem with master but gives no reason #821
Comments
@utdrmac please update to latest release where this is resolved. |
@shlomi-noach I'm on the latest release 3.0.14 as reported by |
This is a different issue from #756. |
Can you please clarify what problem is reported by the API? I can't see it in the original comment. |
Hey Shlomi. There is no problem. That's the issue. If you look in the GUI, there is no error/problem. If you query the |
Let me rephrase that. if there is in fact an error, you cannot tell via the API. But I configured this simple M/SS setup, and I know there's no errors. There are no errors in GUI. Yet, the API keeps returning back 1 server (the master) has having some problem, but you cannot tell what that problem is. |
GUI shows no issues. But API does. There's no reasoning in the API on what the problem is.
mysql1
in this context is current master.The text was updated successfully, but these errors were encountered: