Occurred the upgrade error

Hi, all.

I checked the error during the upgrade.
Upgrade the engine to 7.5.10 from 7.5.7. and also Upgrade the toolbox to 1.12.2.
Below is the details of the upgrade work.

===================================================================

  1. Ran the Upgrade command and Error occurred
    $ sdb-deploy upgrade --file-path /home/minkyung/1_singlestore/sdb_cluster/memsql-server-7.5.10-d6401ae628.x86_64.tar.gz --online


the upgrade cannot be started. No operations performed. The last error was: failed to activate version 7.5.10-d6401ae628 on host(s) 192.168.1.200: the memsqlctl binary is not linked to the target version.
You must reset memsqlctlPath in the Toolbox stateFile by either removing it or pointing it to the newly installed version.
Also check that the target version is marked as current in the tarInstallState file.

  1. Run the [sdb-admin list-nodes] command
    All node’s versions are printed 7.5.7.

  2. Check the describe-host.
    $ sdb-toolbox-config describe-host --host=192.168.1.200
    ±----------------------±-----------------------------------------------------------------------------------+
    | Host | 192.168.1.200 |
    | Local Host | Yes |
    | SSH Address | |
    | Identity File | |
    | Memsqlctl Path | /home/minkyung/1_singlestore/sdb_cluster/memsql-server-7.5.10-d6401ae628/memsqlctl |
    | Memsqlctl Config Path | /home/minkyung/1_singlestore/sdb_cluster/memsqlctl.hcl |
    | Tar Install Directory | /home/minkyung/1_singlestore/sdb_cluster |
    | Tar Install State | /home/minkyung/1_singlestore/sdb_cluster/packages.hcl |
    ±----------------------±-----------------------------------------------------------------------------------+

  3. Check the packages.hcl File
    version = 1

package {
path = “memsql-server-7.5.4-dc2ed6d229”
}

package {
path = “memsql-server-7.5.7-b31088a4e0”
}

package {
path = “memsql-server-7.5.10-d6401ae628”
current = true
}

  1. Reran the Upgrade Command with other option and same error occurred.
    $ sdb-deploy upgrade --file-path /home/minkyung/1_singlestore/sdb_cluster/memsql-server-7.5.10-d6401ae628.x86_64.tar.gz --force-package-format tar

  2. Restart all nodes.
    $ sdb-admin stop-node --all
    $ sdb-admin start-node --all

  3. Check the nodes list.
    $ sdb-admin list-nodes
    ±-----------±-------±--------------±------±--------------±-------------±--------±---------------±-------------------±-------------+
    | MemSQL ID | Role | Host | Port | Process State | Connectable? | Version | Recovery State | Availability Group | Bind Address |
    ±-----------±-------±--------------±------±--------------±-------------±--------±---------------±-------------------±-------------+
    | E49731C0F0 | Master | 192.168.1.200 | 30155 | Stopped | False | 7.5.10 | Unknown | | 0.0.0.0 |
    | 7BD822ECAB | Leaf | 192.168.1.200 | 30156 | Stopped | False | 7.5.10 | Unknown | | 0.0.0.0 |
    | B0E8FF2E8D | Leaf | 192.168.1.200 | 30157 | Stopped | False | 7.5.10 | Unknown | | 0.0.0.0 |
    ±-----------±-------±--------------±------±--------------±-------------±--------±---------------±-------------------±-------------+

  4. Start the SingleStore.
    $ singlestore -P30155
    ERROR 2003 (HY000): Can’t connect to MySQL server on ‘127.0.0.1’ (111)

  5. Check the hosts list and host details.
    $ sdb-toolbox-config list-hosts
    ±--------------±-----------±------------±--------------+
    | Host | Local Host | SSH address | Identity File |
    ±--------------±-----------±------------±--------------+
    | 192.168.1.200 | Yes | | |
    ±--------------±-----------±------------±--------------+
    $ sdb-toolbox-config describe-host --host=192.168.1.200
    ±----------------------±-----------------------------------------------------------------------------------+
    | Host | 192.168.1.200 |
    | Local Host | Yes |
    | SSH Address | |
    | Identity File | |
    | Memsqlctl Path | /home/minkyung/1_singlestore/sdb_cluster/memsql-server-7.5.10-d6401ae628/memsqlctl |
    | Memsqlctl Config Path | /home/minkyung/1_singlestore/sdb_cluster/memsqlctl.hcl |
    | Tar Install Directory | /home/minkyung/1_singlestore/sdb_cluster |
    | Tar Install State | /home/minkyung/1_singlestore/sdb_cluster/packages.hcl |
    ±----------------------±-----------------------------------------------------------------------------------+
    ===================================================================
    Please tell me how to take measures for DB to operate normally.

When I tried to upgrade using the toolbox v.1.11.10, the SingleStore upgraded well.
I think it is necessary to check if the toolbox v.1.12.2 has bug.

Hello, @minkyung.kang!
Thank you for reaching out!

Could you please share the state file content?
Consider running the sdb-admin env command and look at the stateFile section of the output. It might be the case, that memsqlctlPath is hardcoded there, and deleting that entry might help to proceed with upgrade.