SolusVM is notoriously bad at reconfigurations, and a good number of VMs need to be reconfigured because the initial reconfiguration failed, luckily this is a button available on your end as well.
SolusVM new version appears to preserve states, meaning if your VM was powered down to migrate it may remain powered down, luckily again this is a button on your end that can be pressed to solve most of these.
Old IP addresses were not removed properly, we're going through and removing these every day. This is not a huge issue but it also means if it's not done, WHMCS doesn't grab the new IP and may display your old IP instead. The correct IP displays on SolusVM.
SolusVM doesn't update the VNC port for migrated VMs, at least not in this case, so if your VM doesn't power on, outside of an old ISO being mounted, it means it's most likely this issue. You can disable VNC on your end and boot, otherwise we have to manually change these port numbers. We already have someone else hired to process these and they're actively working on it as migrations occur.
None of these solutions worked on both my nodes FFME003/004, one is powered down no matter what, the other couldn't find it`s disk.
Hope not, as I have one near there already (Vint Hill): Seattle/Denver/Dallas in order of preference, though not ideal due to likely more Asian traffic. :-(
I guess, what's more concerning is my Buffalo with the two additional IPs. Time will tell. (I've been rebuilding it using Almalinux 8.6 in some forlorn hope.)
@AlwaysSkint - My Chicago was moved to Secaucus, NJ as I expected. Seattle/Denver/Dallas 🤷🏻♂️.
By the way the Amsterdam migration special was moved to Frankfurt and the disk is now read only. I expect it will be fixed in time, but you did not miss anything there. I hope your recovery is going well, we are pulling for you.
My tiny Buffalo VPS surreptitiously (had to spell check!) moved to NYC. Dunno exactly when. It's currently running Debian 10 and miraculously started up absolutely perfectly. Mein Gott!
Had to change its' hostname to reflect the new location though.
My vps7 previously in Atlanta went offline several minutes ago.
It's visible in WHMCS as being on ATLKVM12 host node, but the main IP suddenly became 149.57.204.*.
I thought Miami beach club would be opening?
@yoursunny said:
My vps7 previously in Atlanta went offline several minutes ago.
It's visible in WHMCS as being on ATLKVM12 host node, but the main IP suddenly became 149.57.204.*.
I thought Miami beach club would be opening?
If you didn't select a different location, and if the present location still exists in their new plan, you're not going to be migrated somewhere else. Same happens with my Atlanta one on ATLKVM13. New main IP, original IP now secondary (still accessible).
vps7 is now showing as in ATLZ010 host node and "Offline".
Two months ago I pressed the button for New York, but it assigned IP but did nothing else.
I pressed "Power On" and the machine came online.
Then I had to adjust Netplan config, Route48.org tunnel, and DNS records for it to work again.
Docker containers must be re-created.
Otherwise, they would enter a restart loop because the previous public IPv4 no longer exists.
This is why it's good to keep virtual servers "Offline" after a migration and let the customer start it.
Still waiting for Miami beach club because Zayo network is said to be crap.
@yoursunny said:
Still waiting for Miami beach club because Zayo network is said to be crap.
Also waiting, hoping to join you on the Miami beach! I did end up moving one of my VPS to Atlanta and the network was somewhat passable, a lot of interesting routing decisions though. the INAP locations are performing a lot better
Your service has been migrated if it is on a new "node" using the name LAXA000, NYCB000, TYOC000, AMSD000, FFME000, PHXZ000, SEAZ000, DENZ000, ATLZ000, SJCZ000, or MIAZ000.
Your service has been migrated if it is on a new "node" using the name LAXA000, NYCB000, TYOC000, AMSD000, FFME000, PHXZ000, SEAZ000, DENZ000, ATLZ000, SJCZ000, or MIAZ000.
Bulk of migrations are complete to some level, with a lot of problems. FFM is still facing disk configuration issue, I couldn't get to it, but luckily only a small number of people are affected outside of FFME04 which rebooted into no disks, and potentially FFME05 which is displaying services as online but large disk issue.
FFM has ECC RAM onsite and this will repair FFME001 which is actually correcting the errors just fine for now, but to avoid any comorbidities.
Migrations had issue with reconfigurations, SolusVM can't handle that many and keeps crashing. We'll be going through today and also fixing incorrect IPv4 showing up on WHMCS but for the most part you should be able to reconfigure and get it to work. A small percentage of these will still have problems booting back up, and we're actively still going through those right now.
@yoursunny said: vps7 is now showing as in ATLZ010 host node and "Offline".
Two months ago I pressed the button for New York, but it assigned IP but did nothing else.
I pressed "Power On" and the machine came online.
Then I had to adjust Netplan config, Route48.org tunnel, and DNS records for it to work again.
Docker containers must be re-created.
Otherwise, they would enter a restart loop because the previous public IPv4 no longer exists.
This is why it's good to keep virtual servers "Offline" after a migration and let the customer start it.
Still waiting for Miami beach club because Zayo network is said to be crap.
Miami will be the next thing to be worked on, sometime this week. I do believe our schedule will open back up and we'll also be focusing on returning support response times to normal.
My LA one finally migrated to LAXA031, but it seems that there are only a few EOL installation templates on that node. Newer ones show up in solusvm but won't work.
@fan said:
My LA one finally migrated to LAXA031, but it seems that there are only a few EOL installation templates on that node. Newer ones show up in solusvm but won't work.
OS templates may have ran into issue for LAX since they were interrupted by the network issue we faced, and then interrupted again with mass migrations. I'll put in another sync soon.
@Virmach is it possible to move CHI to a closer venue, such as Denver, rather than NYC?
Are all AMS earmarked for FFM?
Also, please refrain from migrating multi-IP VPS until you're closer to fixing that issue.
Patiently (kinda) waiting for rDNS to be working again, so that my server notifications get delivered.
@VirMach said:
Bulk of migrations are complete to some level, with a lot of problems. FFM is still facing disk configuration issue, I couldn't get to it, but luckily only a small number of people are affected outside of FFME04 which rebooted into no disks, and potentially FFME05 which is displaying services as online but large disk issue.
May need to check FFME002 as well I'm afraid, my migrated one to it has been down for quite a while. Every day or two I poke it with a stick but it seems pretty dead.
@VirMach said:
Bulk of migrations are complete to some level, with a lot of problems. FFM is still facing disk configuration issue, I couldn't get to it, but luckily only a small number of people are affected outside of FFME04 which rebooted into no disks, and potentially FFME05 which is displaying services as online but large disk issue.
May need to check FFME002 as well I'm afraid, my migrated one to it has been down for quite a while. Every day or two I poke it with a stick but it seems pretty dead.
I only see the "Migrate" button instead of "Ryzen migrate" even though I got the email (and I only have one service active). Is this normal? I also want to migrate to MIA.
Comments
Atlanta 7 finally back up. Thanks @Virmach
lowendinfo.com had no interest.
With your experience, you should write a book called "How not to perform mass server migration".
None of these solutions worked on both my nodes FFME003/004, one is powered down no matter what, the other couldn't find it`s disk.
Was still hoping that one of my Buffalo VMs would be
But there is still no migrate option for Miami :d
Certainement qui est en droit de vous rendre absurde, est en droit de vous rendre injuste - Voltaire
I'm a little concerned as to where my Chicago nameserver may end up automatically migrating to.
lowendinfo.com had no interest.
NYC?
Certainement qui est en droit de vous rendre absurde, est en droit de vous rendre injuste - Voltaire
Hope not, as I have one near there already (Vint Hill): Seattle/Denver/Dallas in order of preference, though not ideal due to likely more Asian traffic. :-(
Time will tell. (I've been rebuilding it using Almalinux 8.6 in some forlorn hope.)
I guess, what's more concerning is my Buffalo with the two additional IPs.
lowendinfo.com had no interest.
@AlwaysSkint - My Chicago was moved to Secaucus, NJ as I expected. Seattle/Denver/Dallas 🤷🏻♂️.
By the way the Amsterdam migration special was moved to Frankfurt and the disk is now read only. I expect it will be fixed in time, but you did not miss anything there. I hope your recovery is going well, we are pulling for you.
Certainement qui est en droit de vous rendre absurde, est en droit de vous rendre injuste - Voltaire
LAX Quadranet is offline now. hope the network reconfig works.
I bench YABS 24/7/365 unless it's a leap year.
One of my VM moved from CHI to NYC and the other seems to be hiding on a node still in CHI heh.
LAX Quadranet is online now. hope the network reconfig worked.
I bench YABS 24/7/365 unless it's a leap year.
My tiny Buffalo VPS surreptitiously (had to spell check!) moved to NYC. Dunno exactly when. It's currently running Debian 10 and miraculously started up absolutely perfectly. Mein Gott!
Had to change its' hostname to reflect the new location though.
lowendinfo.com had no interest.
My interfaces file was stuffed up and had to be altered using LXC, but packet loss has gone.
My vps7 previously in Atlanta went offline several minutes ago.
It's visible in WHMCS as being on ATLKVM12 host node, but the main IP suddenly became 149.57.204.*.
I thought Miami beach club would be opening?
If you didn't select a different location, and if the present location still exists in their new plan, you're not going to be migrated somewhere else. Same happens with my Atlanta one on ATLKVM13. New main IP, original IP now secondary (still accessible).
vps7 is now showing as in ATLZ010 host node and "Offline".
Two months ago I pressed the button for New York, but it assigned IP but did nothing else.
I pressed "Power On" and the machine came online.
Then I had to adjust Netplan config, Route48.org tunnel, and DNS records for it to work again.
Docker containers must be re-created.
Otherwise, they would enter a restart loop because the previous public IPv4 no longer exists.
This is why it's good to keep virtual servers "Offline" after a migration and let the customer start it.
Still waiting for Miami beach club because Zayo network is said to be crap.
Also waiting, hoping to join you on the Miami beach! I did end up moving one of my VPS to Atlanta and the network was somewhat passable, a lot of interesting routing decisions though. the INAP locations are performing a lot better
MIAMI!!
Bulk of migrations are complete to some level, with a lot of problems. FFM is still facing disk configuration issue, I couldn't get to it, but luckily only a small number of people are affected outside of FFME04 which rebooted into no disks, and potentially FFME05 which is displaying services as online but large disk issue.
FFM has ECC RAM onsite and this will repair FFME001 which is actually correcting the errors just fine for now, but to avoid any comorbidities.
Migrations had issue with reconfigurations, SolusVM can't handle that many and keeps crashing. We'll be going through today and also fixing incorrect IPv4 showing up on WHMCS but for the most part you should be able to reconfigure and get it to work. A small percentage of these will still have problems booting back up, and we're actively still going through those right now.
Miami will be the next thing to be worked on, sometime this week. I do believe our schedule will open back up and we'll also be focusing on returning support response times to normal.
Ryzen migrate button will be converted to Ryzen to Ryzen location change button by around the end of this week.
My LA one finally migrated to LAXA031, but it seems that there are only a few EOL installation templates on that node. Newer ones show up in solusvm but won't work.
OS templates may have ran into issue for LAX since they were interrupted by the network issue we faced, and then interrupted again with mass migrations. I'll put in another sync soon.
In the meantime all Ryzen nodes are getting a final sync of netboot.xyz to make sure that at least works as an option.
@Virmach is it possible to move CHI to a closer venue, such as Denver, rather than NYC?
Are all AMS earmarked for FFM?
Also, please refrain from migrating multi-IP VPS until you're closer to fixing that issue.
Patiently (kinda) waiting for rDNS to be working again, so that my server notifications get delivered.
lowendinfo.com had no interest.
May need to check FFME002 as well I'm afraid, my migrated one to it has been down for quite a while. Every day or two I poke it with a stick but it seems pretty dead.
windowz 2022 image not working
Same with me on node FFME003.
I only see the "Migrate" button instead of "Ryzen migrate" even though I got the email (and I only have one service active). Is this normal? I also want to migrate to MIA.