Memsql deploy list versions

Off-Topic
1

Hi,

I have installed simple memsql cluster as shown below

[17.1.0:vagrant@featur:0 database]$ memsql-admin list-nodes
±-----------±-------±----------±------±--------------±-------------±--------±---------------±-------------------+
| MemSQL ID | Role | Host | Port | Process State | Connectable? | Version | Recovery State | Availability Group |
±-----------±-------±----------±------±--------------±-------------±--------±---------------±-------------------+
| DC3601E39D | Master | 127.0.0.1 | 43306 | Running | True | 6.7.18 | Online | |
| 198292BB75 | Leaf | 127.0.0.1 | 43307 | Running | True | 6.7.18 | Online | 1 |
±-----------±-------±----------±------±--------------±-------------±--------±---------------±-------------------+

But when I run memsql-deploy list-versions , I am getting result as

now versions found

why is it not showing the version

2

That’s strange! I’d also expect to see 6.7.18 listed in list-versions if you already have a cluster running with it. I have some questions to help us figure out what’s going on.

I see that the hostname used is 127.0.0.1, so I’m assuming this is all happening on the local host. How did you install the memsql-server package? Did you use memsql-deploy cluster-in-a-box, your system package manager, or something else?

memsql-deploy list-versions checks your system package manager for memsql-server packages. Run these commands to figure out where memsql-server is:

  • rpm -qa | grep memsql
  • dpkg -l | grep memsql
  • memsql-admin describe-node --memsql-id DC3601E39D --property memsqld

memsql-deploy list-versions should recognize your installed memsql-server packages if dpkg -l or rpm -qa shows them. The memsql-admin describe-node will tell us which memsqld binary is being used to run that node, in the case that it wasn’t installed with the system package manager.

Last, I’d like to get some diagnostic information. Please run these commands and include the output. If you hit the character limit for forum posts, use a service like Pastebin.

  • memsql-deploy version
  • memsql-deploy env
  • memsql-deploy list-versions -vvv
3

I followed the manual process of installation specified in the link below.
Memsqlctl command not found - Help - SingleStore Forums. As mentioned we either need to copy content over the default memsql data directory to new data directory or run the memsql-deploy. Not sure if running the memsql-deploy is the right way of doing but it worked for me.

4

After running the memsql-deploy install, I am getting the versions list.

$memsql-deploy list-versions
±----------±-------------------------------±--------±-------+
| Host | Package | Version | Active |
±----------±-------------------------------±--------±-------+
| 127.0.0.1 | memsql-server6.7.18-db1caffe94 | 6.7.18 | No |
±----------±-------------------------------±--------±-------+
$ rpm -qa | grep memsql
memsql-server6.7.18-db1caffe94-6.7.18-1.x86_64
memsql-client-1.0.0-1.x86_64
memsql-toolbox-1.1.1-1.x86_64
memsql-studio-1.6.3-1.x86_64
[17.1.0:vagrant@feature-114:1 database]$ dpkg -l | grep memsql
-bash: dpkg: command not found
$ memsql-admin describe-node --memsql-id 8F606B1136 --property memsqld
/database/software/memsql-server-6.7.18/memsqld

Here is the other report you asked for

$ memsql-deploy version
Version: 1.1.1
Commit: 29ca3d3748f324fa2e6d6d34e853afb776bce2c0
$ memsql-deploy env
±-----------±------------------------------------------------------------+
| configFile | /home/vagrant/.config/memsql-toolbox/toolbox.hcl |
| stateFile | /home/vagrant/.local/share/memsql-toolbox/toolbox-state.hcl |
| cacheFile | /home/vagrant/.local/share/memsql-toolbox/toolbox-cache.hcl |
| sessionDir | /tmp/memsql-toolbox147263242 |
| sshBinary | /usr/bin/ssh |
±-----------±------------------------------------------------------------+
$ memsql-deploy list-versions -vvv
Debug 2019/06/26 05:58:36 env.go:200 cannot resolve runtime dir: XDG_RUNTIME_DIR not set and no override specified
2019/06/26 05:58:36 main.go:39 Running command /usr/bin/id -u -n
2019/06/26 05:58:36 main.go:39 Command /usr/bin/id -u -n took 1.38556ms
2019/06/26 05:58:36 main.go:39 Running command /usr/bin/which rpm
2019/06/26 05:58:36 main.go:39 Command /usr/bin/which rpm took 855.26µs
2019/06/26 05:58:36 main.go:39 Running command /usr/bin/which dpkg
2019/06/26 05:58:36 main.go:39 Command /usr/bin/which dpkg failed with exit code 1 in 807.503µs
2019/06/26 05:58:36 main.go:39 Running command /bin/rpm --query --all --queryformat %{NAME} %{VERSION}\n
2019/06/26 05:58:37 main.go:39 Command /bin/rpm --query --all --queryformat %{NAME} %{VERSION}\n took 371.739011ms
2019/06/26 05:58:37 main.go:39 Running command /bin/readlink --canonicalize --no-newline /database/software/memsql-server-6.7.18/memsqlctl
2019/06/26 05:58:37 main.go:39 Command /bin/readlink --canonicalize --no-newline /database/software/memsql-server-6.7.18/memsqlctl took 1.071264ms
2019/06/26 05:58:37 main.go:39 Running command /bin/rpm --query --queryformat %{NAME} --file /database/software/memsql-server-6.7.18/memsqlctl
2019/06/26 05:58:37 main.go:39 Command /bin/rpm --query --queryformat %{NAME} --file /database/software/memsql-server-6.7.18/memsqlctl failed with exit code 1 in 11.004969ms
±----------±-------------------------------±--------±-------+
| Host | Package | Version | Active |
±----------±-------------------------------±--------±-------+
| 127.0.0.1 | memsql-server6.7.18-db1caffe94 | 6.7.18 | No |
±----------±-------------------------------±--------±-------+

5

Here is the report for without running the memsql-deploy install

$ rpm -qa | grep memsql
memsql-client-1.0.0-1.x86_64
memsql-toolbox-1.1.1-1.x86_64
memsql-studio-1.6.3-1.x86_64
$ dpkg -l | grep memsql
-bash: dpkg: command not found
$ memsql-deploy list-versions
No versions found
$ memsql-admin describe-node --memsql-id E22CEF02A0 --property memsqld
/database/software/memsql-server-6.7.18/memsqld
$ memsql-deploy version
Version: 1.1.1
Commit: 29ca3d3748f324fa2e6d6d34e853afb776bce2c0
[17.1.0:vagrant@feature-114:1 database]$ memsql-deploy env
±-----------±------------------------------------------------------------+
| configFile | /home/vagrant/.config/memsql-toolbox/toolbox.hcl |
| stateFile | /home/vagrant/.local/share/memsql-toolbox/toolbox-state.hcl |
| cacheFile | /home/vagrant/.local/share/memsql-toolbox/toolbox-cache.hcl |
| sessionDir | /tmp/memsql-toolbox880714193 |
| sshBinary | /usr/bin/ssh |
±-----------±------------------------------------------------------------+
$ memsql-deploy list-versions -vvv
Debug 2019/06/26 06:04:02 env.go:200 cannot resolve runtime dir: XDG_RUNTIME_DIR not set and no override specified
2019/06/26 06:04:02 main.go:39 Running command /usr/bin/id -u -n
2019/06/26 06:04:02 main.go:39 Command /usr/bin/id -u -n took 1.224898ms
2019/06/26 06:04:02 main.go:39 Running command /usr/bin/which rpm
2019/06/26 06:04:02 main.go:39 Command /usr/bin/which rpm took 693.68µs
2019/06/26 06:04:02 main.go:39 Running command /usr/bin/which dpkg
2019/06/26 06:04:02 main.go:39 Command /usr/bin/which dpkg failed with exit code 1 in 688.302µs
2019/06/26 06:04:02 main.go:39 Running command /bin/rpm --query --all --queryformat %{NAME} %{VERSION}\n
2019/06/26 06:04:03 main.go:39 Command /bin/rpm --query --all --queryformat %{NAME} %{VERSION}\n took 363.880409ms
No versions found

6

The instructions you followed install memsql-server in a way that is not managed by memsql-deploy. This is confirmed by the output of the diagnostics without running memsql-deploy install:

It looks like some of your recent questions are also referring to this same scenario. Rather than answer them all individually, I’d like to learn about your deployment goal so we can give better advice about the whole process. Can you start a new thread with more details about what your current setup looks like and what you’re trying to do?