It is not too hard to rebuild all the VPSes numbered beginning with 2. There is a directory with scripts for each VPS, so I have to go through that directory, rerun the scripts, and double check.
Everything should be the same as before, except that there will be new host ssh keys and, unfortunately, you will have to reinstall. I apologize for the inconvenience!
When you have time, could you please check and let us know if you can get in and if everything seems okay.
I have successfully received the VPS and connected via SSH. Everything is working perfectly. 🙏
Thank you so much for your kind support and for providing this great opportunity. I really appreciate the generosity of you and the providers! ❤️
virsh seems to think that some of the VPSes whose qcow2 files were deleted are still running.
I logged in to one VPS where the client apparently had not deleted my ssh key. I did nothing except log out immediately, but it seems people still could log in to their VPSes even though the .qcow2 files are gone.
I dont know what use it would be to log in, but maybe I ought not to rebuild VPSes until clients have had a chance to log in if they want to do so.
Clients who are affected are those with Alexhost VPSes numbered vm2*. If you are in the vm2* group, please let me know if I should go ahead and rebuild your VPS.
@Not-Oles#217@Not-Oles#342
I have successfully regained access and logged into the VPS without any issues. I have now transitioned to the next phase of deploying the system for project use, and I am currently conducting thorough project testing to ensure all functionalities are operating as expected.
Thank you sincerely for your support and assistance — it is greatly appreciated, especially for a public-interest initiative like ours.
Unfortunately, your new VPS was among the group whose .qcow2 and .iso files I accidentally delete:
root@alexhost:~/vm-seed/vmXX-@千狐# ls /var/lib/libvirt/images/ | grep vmXX
root@alexhost:~/vm-seed/vmXX-@千狐#
We now know from @cmeerwon LES that the deleted files remain in /proc. Also, I logged into a VPS for which the .qcow2 file had been deleted.
Do you want to check out your deleted VPS and see if you still can log in? Do you want me to remove what remains and recreate your VPS? Or maybe you want something else?
It is easy to recreate your VPS. Just a few commands, most of which are scripted.
@Not-Oles just make a spectacular noob mistake!
During the process of rebuilding vm2 I went to remove the qcow2 image and the vm-seed.iso for vm2.
Here is what went wrong:
It is not too hard to rebuild all the VPSes numbered beginning with 2. There is a directory with scripts for each VPS, so I have to go through that directory, rerun the scripts, and double check.
I will post more as events progress.
But it will take a while.
Sorry!
Wow!
Tom
@horrah
Hello!
It looks like your VPS is rebuilt.
Everything should be the same as before, except that there will be new host ssh keys and, unfortunately, you will have to reinstall. I apologize for the inconvenience!
When you have time, could you please check and let us know if you can get in and if everything seems okay.
Best wishes!
Tom
@Not-Oles #335
Hello Tom,
I have successfully received the VPS and connected via SSH. Everything is working perfectly. 🙏
Thank you so much for your kind support and for providing this great opportunity. I really appreciate the generosity of you and the providers! ❤️
Best wishes,
千狐
Unexpected discovery!
virsh seems to think that some of the VPSes whose qcow2 files were deleted are still running.
I logged in to one VPS where the client apparently had not deleted my ssh key. I did nothing except log out immediately, but it seems people still could log in to their VPSes even though the .qcow2 files are gone.
I dont know what use it would be to log in, but maybe I ought not to rebuild VPSes until clients have had a chance to log in if they want to do so.
Clients who are affected are those with Alexhost VPSes numbered vm2*. If you are in the vm2* group, please let me know if I should go ahead and rebuild your VPS.
Sorry for the inconvenience!
Tom
免费VPS，伦敦基希讷乌！
@Not-Oles #340
got it ,thanks!
@Not-Oles #217 @Not-Oles #342
I have successfully regained access and logged into the VPS without any issues. I have now transitioned to the next phase of deploying the system for project use, and I am currently conducting thorough project testing to ensure all functionalities are operating as expected.
Thank you sincerely for your support and assistance — it is greatly appreciated, especially for a public-interest initiative like ours.
Best regards.
There is an interesting comment by @cmeerw on LES at
https://lowendspirit.com/discussion/comment/219651/#Comment_219651
@cmeerw discusses how deleted files cab still be present inside /proc
这个帖子怎么上来了
@千狐 #343
Hi!
Thanks for your kind comment!
Unfortunately, your new VPS was among the group whose .qcow2 and .iso files I accidentally delete:
We now know from @cmeerw on LES that the deleted files remain in /proc. Also, I logged into a VPS for which the .qcow2 file had been deleted.
Do you want to check out your deleted VPS and see if you still can log in? Do you want me to remove what remains and recreate your VPS? Or maybe you want something else?
It is easy to recreate your VPS. Just a few commands, most of which are scripted.
Thanks again! Always best wishes!
Tom