I use the command: sdb-deploy setup-cluster --cluster-file /tmp/memsql.yaml
This appears to be successful. No errors and when I login I can see the cluster. When I connect using memsql -u root -p I can see the configuration and it appears to be fine.
Where I seem to be having issues is with trying to enable encryption using the following commands from the linux prompt:
When I try any of these commands I get the following:
Failed to check if 'ssl_cert' is a sync var. Will attempt to update-config assuming that it is not. Error is no master aggregator found in this cluster
Toolbox is about to run 'memsqlctl update-config --key ssl_cert --value /usr/local/bluetriangletech.pem' on the following nodes:
Would you like to continue? [Y/n]:
Automatically selected yes, non-interactive mode enabled
Operation completed successfully
When I try to run sdb-admin list-nodes
I get: No nodes found
I’ve had a really hard time trying to find how to do this.
Is there somewhere in the documentation that just runs through the basic setup to get sdb-admin aware of the cluster generated from the yaml file? Everything I’ve seen so far just ends up being for kubernetes or some other method of installing.
That makes total sense in this case. We are using ansible to deploy memsql and ansible uses a user/key specific to the memsql install process. When we go in to do maintenance or just check the status of the instance we use our individual user/keys. Is there any way to get around this? It seems strange that we have to use the specific user in order to be able to use the sdb-admin.
I apologize for my ignorance on this. I am not that familiar with memsql/singlestore. I see that using memsqlctl instead of sdb-admin works!
Ok, we may be getting to the edge of what we can help with via the forum, but:
The approach is for all users to have toolbox.hcl (path findable via sdb-admin env) files pointing to the same statefile/etc and the users would need to be in the same group with all toolbox and memsqlctl related files having group write/read/exec privs
Just want to double check and verify that you’re entering the correct path to the cert and key. I’m pretty sure it’s a relative path. (I’m assuming you’re ‘sanitizing’ your output above)
Also, permission denied? Does the user you’re running as have access permission to the cert file?
Verify those and then we can look at other options.