• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Question Wrong command and checks to do before restarting server

E42

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Obsidian
Hello,
There was a moment when I used the command "plesk bin cloning" and later realized that's not what I wanted.

Now, what I want is this: to be able to restart the server and be sure that everything works fine just like now. So, to "undo" the previous command, I used this one:
plesk bin cloning -u -prepare-public-image false -reset-license false -reset-init-conf false

Is this enough? How can I be sure that after a restart nothing will be erased? Thank you and kind regards
 
hello @E42 ,

first of all I'd recommend you to create full Plesk Backup (Tools & Settings > Backup Manager), just in case.


you can check that cloning was canceled by commands below:
:~# plesk bin cloning -s
0
:~# plesk bin cloning -i
prepare-public-image: false
reset-license: false
update-master-key: false
reset-init-conf: false
skip-update: true
maintenance: false

after that I was able to reboot my test Plesk server and everything fine.
 
Back
Top