I have received several congratulations about Chisinau VPSes which are working great. However, there also have been several reports of VPSes which are offline, which I confirm. Additionally, there are multiple VPSes running very high CPU. . . .
@Not_Oles said:
I have received several congratulations about Chisinau VPSes which are working great. However, there also have been several reports of VPSes which are offline, which I confirm. Additionally, there are multiple VPSes running very high CPU. . . .
They are just mining LES coin and creating AI generated content for posting here
I missed one space in a yaml configuration file when testing the first of the Chisinau node's newly assigned IP addresses!
root@alexhost:~/vm-seed/vmXX# yamllint network-config
network-config
1:1 warning missing document start "---" (document-start)
11:8 error wrong indentation: expected 8 but found 7 (indentation)
12:14 error syntax error: mapping values are not allowed here (syntax)
root@alexhost:~/vm-seed/vmXX#
--------
After adding one space on line 11:
root@alexhost:~/vm-seed/vmXX# yamllint network-config
network-config
1:1 warning missing document start "---" (document-start)
root@alexhost:~/vm-seed/vmXX#
Looks like the newly assigned IP addresses do work just fine with the previous and now again reverted netplan when the yaml configuration is correct.
Now I have to figure out why some (but definitely not all!) of the previously made VPSes stopped WAN network access and picked up high %CPU after the netplan change and reversion, which turned out not to have been necessary.
My fault! Sorry!
Thanks again to Alexhost Support for trying to help! Thanks again to Alexhost for your kind donation!
Here's a Yabs from inside the new Chisinau VPS that I just made. Its IPv4 is one from the newly assigned group. The results seem pretty good, especially considering that several of the existing VMs currently are running 100% CPU. The results are -- if memory serves -- consistent with earlier Yabs when the node was not stressed.
This one is for @AuroraZero if he wants it. Note the terms from FOSSVPS.org: "Ephemeral. Could disappear at any moment!" So, not "stable."
@Not_Oles said:
This one is for @AuroraZero if he wants it. Note the terms from FOSSVPS.org: "Ephemeral. Could disappear at any moment!" So, not "stable."
Sounds perfect for the Yeti, who is also Ephemeral and people has spent decades searching for him
Given the lack of good ideas about the high %CPU VPSes, and in the absence of objection, I propose to shut them down, perhaps as soon as tomorrow.
One thing we might try is reverting one of the high CPU VPSes to its fresh snapshot. Maybe they all will work again if reverted. Otherwise I guess they could be reinstalled.
In the future, we could make snapshots after users finish their basic installs. With "basic-install" snapshots we could revert to an installed state.
I made a second new Ubuntu 24.04 VPS with another of the newly assigned IPv4s. It works great and will be assigned to someone, along with more, soon. You can see a list of the requests at https://fossvps.org/list.html.
@Not_Oles said:
I made a second new Ubuntu 24.04 VPS with another of the newly assigned IPv4s. It works great and will be assigned to someone, along with more, soon. You can see a list of the requests at https://fossvps.org/list.html.
At the moment there are 27 VPSes configured on the Chisinau server.
I don't know why, but 8 VPSes seemed to be running continuously at high %CPU following recent update and revert of the netplan. As far as I am aware, the remaining 19 VPSes are working fine.
All 8 of the overperforming VPSes have been shutdown. From here at LES, @jmaxwell is down.
@jmaxwell Do you want me to attempt restoring your VPS from your "fresh" snapshot? Attempting the restore will destroy whatever happened subsequent to the snapshot. Alternatively, we could rebuild your VPS from scratch. Please let me know.
By the way, if you restore or reinstall, we could make a another snapshot after your basic install is completed. That way, if a revert happens again, we could revert to your basic installed state.
Or, maybe, someone has a better idea about how to adjust the overperforming VPSes?
Comments
Two client reports confirmed the issues I was seeing. Netplan reverted. Chisinau node rebooted.
I hope everyone gets the servers they want!
Great news! Chisinau node came back up without needing a power bump! Also, I can ssh into the node and into my test VPS via IPv4 and via IPv6.
Hopefully we are back to where we left off before the netplan adjustment!
I need to sleep now. Anybody still having problems please post, and I will try to fix.
Thanks to Alexhost!
Best wishes!
I hope everyone gets the servers they want!
I have received several congratulations about Chisinau VPSes which are working great. However, there also have been several reports of VPSes which are offline, which I confirm. Additionally, there are multiple VPSes running very high CPU. . . .
I hope everyone gets the servers they want!
They are just mining LES coin and creating AI generated content for posting here
Never make the same mistake twice. There are so many new ones to make.
It’s OK if you disagree with me. I can’t force you to be right.
Mystery partially solved!
I missed one space in a yaml configuration file when testing the first of the Chisinau node's newly assigned IP addresses!
Looks like the newly assigned IP addresses do work just fine with the previous and now again reverted netplan when the yaml configuration is correct.
Now I have to figure out why some (but definitely not all!) of the previously made VPSes stopped WAN network access and picked up high %CPU after the netplan change and reversion, which turned out not to have been necessary.
My fault!
Sorry! 
Thanks again to Alexhost Support for trying to help! Thanks again to Alexhost for your kind donation!
I hope everyone gets the servers they want!
Here's a Yabs from inside the new Chisinau VPS that I just made. Its IPv4 is one from the newly assigned group. The results seem pretty good, especially considering that several of the existing VMs currently are running 100% CPU. The results are -- if memory serves -- consistent with earlier Yabs when the node was not stressed.
This one is for @AuroraZero if he wants it. Note the terms from FOSSVPS.org: "Ephemeral. Could disappear at any moment!" So, not "stable."
I hope everyone gets the servers they want!
Sounds perfect for the Yeti, who is also Ephemeral and people has spent decades searching for him
Never make the same mistake twice. There are so many new ones to make.
It’s OK if you disagree with me. I can’t force you to be right.
Given the lack of good ideas about the high %CPU VPSes, and in the absence of objection, I propose to shut them down, perhaps as soon as tomorrow.
One thing we might try is reverting one of the high CPU VPSes to its fresh snapshot. Maybe they all will work again if reverted. Otherwise I guess they could be reinstalled.
In the future, we could make snapshots after users finish their basic installs. With "basic-install" snapshots we could revert to an installed state.
I made a second new Ubuntu 24.04 VPS with another of the newly assigned IPv4s. It works great and will be assigned to someone, along with more, soon. You can see a list of the requests at https://fossvps.org/list.html.
Thanks everyone!
Thanks Alexhost! 
I hope everyone gets the servers they want!
2 of 4 assigned? So 2 more to go?
Grab them while they're hot!
Never make the same mistake twice. There are so many new ones to make.
It’s OK if you disagree with me. I can’t force you to be right.
2 of 5 assigned? So 3 more to go?
I have to update the numbers on fossvps.org.
I hope everyone gets the servers they want!
Sorry man busy trying to fix my truck and doc appointments. Should be able to get to this this weekend.
Free Hosting at YetiNode | MicroNode| Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Best of luck with both doc and truck!
I hope everyone gets the servers they want!
Hello!
At the moment there are 27 VPSes configured on the Chisinau server.
I don't know why, but 8 VPSes seemed to be running continuously at high %CPU following recent update and revert of the netplan. As far as I am aware, the remaining 19 VPSes are working fine.
All 8 of the overperforming VPSes have been shutdown. From here at LES, @jmaxwell is down.
@jmaxwell Do you want me to attempt restoring your VPS from your "fresh" snapshot? Attempting the restore will destroy whatever happened subsequent to the snapshot. Alternatively, we could rebuild your VPS from scratch. Please let me know.
By the way, if you restore or reinstall, we could make a another snapshot after your basic install is completed. That way, if a revert happens again, we could revert to your basic installed state.
Or, maybe, someone has a better idea about how to adjust the overperforming VPSes?
Thanks! Sorry for the issue!
Thanks to Alexhost! 
Tom
I hope everyone gets the servers they want!