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
Hello use the Following commmand in SCI CLI
sudo docker exec consul ./vendor/consul/consul-linux kv get clusters/default/serial_number
FABIAN GARZON
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 _numberOCI runtime exec failed: open /tmp/runc-process254483419: no space left on device: unknownroot@demo-20578186 ~ #
You can Try Delete the Old versions from previous Upgrades or Delete parquet files to free some space.
for whatever reason those escape characters don't seem to work. I have tried a few different ones....' " etc...
Have you tried like this?
sudo docker rmi -f 'docker images | grep {version} | awk '{print $3}''
yes that works
root@demo-20578186 / # docker images | awk '{print $2}' | sort | uniqTAGv5.4.0v5.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 formatError response from daemon: invalid reference formatroot@demo-20578186 / #
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}’`
Also try
docker rmi $(docker images
"*/*:{version}"
-q)
FABIAN
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 imagesroot@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 deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json236763968: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json488126367: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json411681394: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json752644393: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json080593524: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json775417667: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json217644486: no space left on deviceError response from daemon: conflict: unable to delete d7ae947dd46b (must be forced) - image is being used by stopped container 55493f0156bbError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json174514285: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json089548008: no space left on deviceError response from daemon: open /var/lib/docker/image/overlay2/.tmp-repositories.json114947879: no space left on deviceroot@demo-20578186 / #
I do have a case open currently. 01271497
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.
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.
@Papa_WiFI seems like that is me 🙂
I will contact you soon over the support case.