P

11 Messages

 • 

192 Points

Mon, Oct 25, 2021 7:02 PM

how do I retrieve my SCI serial # from the CLI....?

As the subject mentions, how do I retrieve my SCI serial # from the CLI....?
I no longer have access to the webui after attempting to perform an offline upgrade from 5.4.2 to 5.5.3

Employee

 • 

22 Messages

 • 

420 Points

3 m ago

Hello use the Following commmand in SCI CLI


sudo docker exec consul ./vendor/consul/consul-linux kv get clusters/default/serial_number

FABIAN GARZON

11 Messages

 • 

192 Points

3 m ago

Thanks @fabian_garzon_baquero but looks like I am out of diskspace so it does not work.

root@demo-20578186 ~ # sudo docker exec consul ./vendor/consul/consul-linux kv get clusters/default/serial                                        _number
OCI runtime exec failed: open /tmp/runc-process254483419: no space left on device: unknown
root@demo-20578186 ~ #

Employee

 • 

22 Messages

 • 

420 Points

3 m ago

You can Try Delete the Old versions from previous Upgrades or Delete parquet files to free some space.

Rectification is to manually remove old images. Please run the below commands on the master as well as all the data nodes.

Inspect space on the storage engine.
docker info | grep Space
List available versions of images.
docker images | awk '{print $2}' | sort | uniq
Remove images by version number.  Note: be very sure you are not removing a version currently in use.
sudo docker rmi -f `docker images | grep {version} | awk '{print $3}'`
For e.g., to delete all v 2.2.0 images, the command would be
sudo docker rmi -f `docker images | grep {v2.2.0} | awk '{print $3}’`
In some cases, we have noted that the above command does not work with the curly braces so if the above does not work for you, please try with the below:
sudo docker rmi -f `docker images | grep v2.2.0 | awk '{print $3}’`

FABIAN GARZON

11 Messages

 • 

192 Points

3 m ago

for whatever reason those escape characters don't seem to work. I have tried a few different ones....' " etc...

Employee

 • 

22 Messages

 • 

420 Points

3 m ago

Have you tried like this?

sudo docker rmi -f  'docker images | grep {version} | awk '{print $3}''

11 Messages

 • 

192 Points

3 m ago

yes that works

root@demo-20578186 / # docker images | awk '{print $2}' | sort | uniq
TAG
v5.4.0
v5.4.2

But sudo docker rmi -f `docker images | grep {v2.2.0} | awk '{print $3}’`

does not because of the ` ` escape characters. 

root@demo-20578186 / # sudo docker rmi -f `docker images | grep {v5.4.0} | awk '{print $3}’`
-bash: command substitution: line 1: unexpected EOF while looking for matching `''
-bash: command substitution: line 2: syntax error: unexpected end of file
-bash: sudo docker: command not found

Trying with ' same deal...

root@demo-20578186 / # sudo docker rmi -f 'docker images | grep {v5.4.0} | awk '{print $3}''
Error response from daemon: invalid reference format
Error response from daemon: invalid reference format
root@demo-20578186 / #

Employee

 • 

22 Messages

 • 

420 Points

3 m ago

Sometimes doesnt work with version inside curly braces, can you try without them?

sudo docker rmi -f `docker images | grep v5.4.0 | awk '{print $3}’`

Employee

 • 

22 Messages

 • 

420 Points

3 m ago

Also try

docker rmi $(docker images  "*/*:{version}"  -q)

FABIAN

11 Messages

 • 

192 Points

3 m ago

I have tried without the {}, same deal. Tried the new command you provided with/without the {}.

root@demo-20578186 / # docker rmi $(docker images  "*/*:{v5.4.0}"  -q)
"docker rmi" requires at least 1 argument.
See 'docker rmi --help'.

Usage:  docker rmi [OPTIONS] IMAGE [IMAGE...]

Remove one or more images
root@demo-20578186 / # docker rmi $(docker images  "*/*:v5.4.0"  -q)
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json232626725: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json236763968: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json488126367: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json411681394: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json752644393: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json080593524: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json775417667: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json217644486: no space left on device
Error response from daemon: conflict: unable to delete d7ae947dd46b (must be forced) - image is being used by stopped container 55493f0156bb
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json174514285: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json089548008: no space left on device
Error response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json114947879: no space left on device
root@demo-20578186 / #

I do have a case open currently. 01271497

Official Rep

 • 

1.4K Messages

 • 

18.6K Points

3 m ago

Is this failed during an upgrade?

If yes, you may have to increase the storage directory space from 22 to 75GB.

Support can help you since you already have a case.

11 Messages

 • 

192 Points

3 m ago

Hi Omer,

Yes it was a failed upgrade. 

Yes waiting on support to come back to me with a meeting request to work on this. 

Official Rep

 • 

1.4K Messages

 • 

18.6K Points

@Papa_WiFI seems like that is me :)

I will contact you soon over the support case.

Regards,

Syamantak Omer

Official Rep | Staff TSE | CWNA | CCNA | RASZA | RICXI

Follow me on Linkedin

Important Announcement