New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More
This discussion has been closed.
Comments
Thanks for the detailed explanation. Might want to check into solusVM's reconfigure network script because it configured the wrong network interface for my migration (unless this was already fixed as per your most recent post).
@VirMach
My VM's FFME003/FFME005 from a days from migrations are still broken, any action from panel doesn't work start/stop, reinstall. Of course i choosed option without data migration. (Ticket #860081)
did you try "sudo systemctl restart networking" or a restart?
Yes, tried both. If eth0 is present in the interfaces file, restarting networking would result in error, ens3 restarts fine, but won't connect to the Internet. I'm guessing it could be something related to the gateway?
Also a FFME003 migrator. Migration was automated (I didn't initiate) - I've tried everything to get it to boot. I am holding off putting in a ticket, as I'm sure they are overloaded and trying to get this up and running
A very small amount of these are left over and part of the disk issues I mentioned in my last post. This is due to them being in a state of dropping off disks, it messed with some migrations, they're being corrected today.
When will migration to Miami servers be available?
That's an error in that text, it should have said that we're expanding to Miami. Anyway, Miami is just waiting on LOA. It can be up at any given time, we're just not doing it before fixing everything else, so tomorrow at the soonest and that's if we run into 0 problems with the public networking using those IP addresses.
What about LAXA031? Any idea what's wrong with that node?
Los Angeles Storage still keeps freezing up. I had to repair the filesystem for the root partition and one of our backup VMs there so it's possible there's some corruption on other VMs as well.
RAM was tested again, it's fine.
CPU not throwing any errors.
NIC is fine.
Kernel had some incompatibility but motherboard BIOS was updated to be compatible.
At this point it might actually just be the RAID controller even though it passes all tests and shows as healthy, and CacheVault shows as healthy as well. All disks healthy as well. We already have another RAID controller available in Los Angeles, I'm just trying to finish exhausting our options before I try a RAID controller swap while it may already have caused problems because I really want to avoid data loss.
What's weird is that it was stable until we had to do the VLAN change.
Q - I have quite some idlers here... How do I know if my service was migrated or ready for migration? Couple weeks ago I got 7-8 emails about impending migrations
thanks
Check to see if your IP or processor changed.
I got about 12 of those mails. 8 of my servers have been moved so far. 6 went without a hitch. Two wouldn't boot (PHXZ003 and LAXA031).
@FrankZ helped me resolve the issue with PHXZ003 and nobody has any idea what to do with LAXA031for now.
Thanks for the update! Hopefully my machines will start working correctly.
Not sure if you mean offline or network not working but there is a single VM on LAXA031 that's offline and we've been tracking and working on it today. Looks like the re-syncing of data just completed so I've booted it up (and reconfiguring now.)
Question about rdns, in the email notification it said:
I see the rDNS button on my service page and going through that opens a ticket that looks to be automatically processed with a "completed" message but reverse lookups still fail after several days.
But now I am re-reading it, it says the button has to show up AND function.
Any ETA on when rDNS requests will work?
thx
We have to set them up. We'll most likely switch over to getting it to work directly on SolusVM so once it's done you'll most likely know it's done if the rDNS button takes you to a pop-up that says to navigate to SolusVM.
@VirMach
LA10GKVM14 still not working?
I can't find any information at "https://billing.virmach.com/serverstatus.php?view=open"
No, servers on that node have no access to internet. network reconfigure doesn't help. They show as online but you can't reach them from outside. Essentially, they act as if they only have internal network with vnc connection.
@VirMach
I have a vps migrated to LAXA031, that once had a custom ISO mounted. The VPS however won't ON if any ISO mounted, and is unable to reach the default gateway no matter how I configure network interfaces while the gateway is reachable from the Internet. So, the VPS has no internet, and no way to reinstall OS using ISO.
Both my servers on LAX-A030 and LAX-A031 behave the same way, can VNC to it but can not access the internet, network configuration looks okay to me, but the server can not ping the gateway or any public IPs.
I've got a 7 years old light weight vps at LAKVM7 - it has never caught a issue like this before the "migration gathering" - it has offline 4 days, it is finally online, but it cannot boot and it is not running my image. So, another week? I did not expect this long, I will move everything temporary first next time.
The new order in this post is not started migration yet, but it's better to do something for reducing service downtime.
I know @VirMach is doing something, please keep it up.
I've got 5 VMs right now, looks like all but 1 have been migrated.
If the "Ryzen Migrate" button does not show up, does that mean it's expected to be migrated soon?
The last VM I can reinstall the OS so wondering if I can choose which location to migrate to.
Why do I get this email?
My FFME005 VPS has been stopped for a long time, it cannot be started, and reinstalling the system does not work.
Main IP pings: false
Node Online: false
Service online: offline
Operating System: linux-debian-11-x86_64-gen2-v1
Service Status:Active
Registration Date:2018-11-26
Mine were all migrated to Ryzen without using that button (didn't even show up for half of them).
Would Frankfurt be stable enough now to give a paid, $5 migration a shot?
@VirMach Tokyo Storage 2TB after 3/14 , any latest news?
@VirMach
Node Name SJCZ008
my ip is unavailable 194.33.39.19
productdetails id:637647
always offline
VNC doesn't work either / can't ping
Please help to solve it. Thanks
MJJ is invincible
I'm thinking that I spend a lot of time every day looking for comments on the forum to see if you have fixed it. Your ticket system is directly paralyzed
Is there an estimate of time to fix the problem on LAXA031?
--------LAXA031---------
Two days ago, I found I lost my connection to my VPS.
On the control panel, I found the IP was changed to 149.57.#.# on node LAXA031.
I tried to follow the instructions to fix the connection and all operations failed.
I reinstalled OS and got no luck.
I tried to access my VPS with VNC, but only see "login incorrect". There is nowhere to get the VNC login credentials.
I used "Fix Internet/ Reconfigure Network" and "Troubleshoot".
The "Troubleshoot" returns messages like:
Main IP pings: false
Node Online: false
Service online: online
Operating System: linux-ubuntu-20.04-x86_64-minimal-latest-v2
Service Status:Active
Registration Date:2016
What does the suspension reason say ?
overdue payment.