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
Have you tried "Reconfigure Network" on Billing? (Not the fix/change IP button on top, the one below it).
Another way to check if it's your issue (unable to connect to server), IP announcement issue (VNC, SolusVM connected, unable to connect to server via SSH), or total network failure (nothing works) is check SolusVM, VNC and SSH.
@VirMach downtime really hurts my business
FFME001 down again..
It was fine first 1-2 days ... and now it restarts every 2~3 minutes
Thanks, yeah I tried reconfigure network to no avail. I used solus html ssh login and there are no ip addresses in Ubuntu. But I have two ipv4 listed in solus (should be one)
Hmm. So SolusVM and web based VNC works right?
If you try to SSH into the system, does it work?
If not, try this on your VNC:
curl https://ifconfig.co(DO NOT POST THE OUTPUT HERE). Let me know if it returns any IP address, or the error message ( you might see unknown host, or something like that).If the curl command does not work, How about rebooting the service and see if you get an IP? You might also try to request DHCP again (since you are using VNC from host, it shouldn't affect your access)
still spinning...
Anyone else detected outage on node "LA10GKVM26"? I have two VM on them, and both went offline, I'm not able to reach them about a day ago. I not see any information from this node on the 'network status' page. Thx!
Or this is THE sign, to time to migrate them to a Ryzen node?
the node 025 becomes very slow after fixed,will it be improved later?@virmach
It looks like a bad disk or raid controller to me.
I'm seeing disk corruption. I suggest you take backups quickly if you are on FFME001and are still online.
As a suggestion...
If you are stuck at grub and your VPS will not boot, or if you have already taken your backups, you should shutdown your VPS until this is resolved. Allowing the VPS to run at grub, disk not found, or other boot errors, causes high server load and will cause the issue to take longer to resolve.
how much network do you think you should be getting for 1-3$/month prices on yearly deals?
Manually add the IP to your nic. If you can't ping the gateway, then ticket as they need to fix that.
If it does ping, just configure those IP's and be done with it.
Automatic network config is a feature, not a requirement.
Both of my VM get back online about 2 hours ago
2 days ago, Migrated, inserted ISO, started install and then disconnected, seems LAXA024 has been offline since then. Wonder is VirMach is dealing with a bad batch of hardware
Yo, the problem is not bandwidth threshold but packet loss
Under high packet loss, TCP CC will greatly reduce window size and frequently trigger resend, result in significantly less throughput and high latency on the application layer.
FFME002 still offline? I have been migrated but troubleshooter says the host node looks down
anyone in LAXA014? still offline since the migration
Jeps my VM is still offline on node FFME002
FFME002 has an issue with one disk, and FFM001 has issue with memory similar to TYOC025 but worse, where the disks are there but the volume isn't.
A lot of Los Angeles went offline due to a widespread outage and has trouble coming back. This happened around the same time as everything else. Since FFME002 is only affecting a very small number of people on only one disk, it's not the current priority. I understand this may be frustrating but we have a lot of fires to put out right now so we have to do it in the proper order to minimize downtime. With what happened at Los Angeles (non-Ryzen) we also have a flood of tickets as well, and in the middle of this I'm also preparing large shipments of Ryzen servers and scheduled migrations.
The plan for FFME001 is currently to try to boot it back up long enough to move the few people here off onto another node and then run memory tests. Otherwise, we'll have to bring it offline and run memory tests while everyone's still on it so we can figure out which DIMM is having issues as we're low on replacement RAM at this specific location and it's a nightmare right now to ship anything to Frankfurt. UPS took over a month to deliver our 1-3 day shipped packages and two of them ended up not being delivered and essentially thrown away by UPS into their warehouse as they continued to ignore us.
I've paused all new customer purchases for the time being, as in all of our products are marked sold out, so we can focus over the next few days to a week on everything.
Fixing this now, it's related to the SolusVM bug regarding libvirtd version requiring a downgrade. I forgot to apply this reverted version for the node, I just set it up a few hours ago.
This may not be related to hardware, although we definitely got screwed over on hardware on many levels, even buying it brand new and in multiple batches. Our RAM supplier is willing to work with us to see what happened but I need to get back the bad DIMMs and send it over to their lab so engineering can take a look and trace it. As for the motherboards, I think ASRock is just bad and they're the only ones making a Ryzen server board really so we're stuck. I have something like 5-10% of all motherboards we built in a pile that are only semi-functional and those are just the ones we caught at the office and didn't send out.
Anyway, I think your case is just the VM never having created properly. You need a priority ticket but as I mentioned we got a boatload of them due to LA outage.
I'll have a look at this sometime today or have someone else in the team take a look.
This was part of the LA outage.
Uptime 355 days, I'll look at this one next and see if anything else is going on but it's also not overloading.
Will take a look at this as well. Data shouldn't be lost, the LVMs were properly recovered but its possible corruption occurred within.
I'll also try to go through all nodes and test networking again and see which ones are facing problems. I'll specifically look at this node too.
Looks like this faced an issue recently, there's been so many that my memory on it isn't very good. I'll have to check to get back an answer for you, I believe I delegated this one to someone else.
reporting AMSKVM4 being offline for a couple of days, tried 'Fix/reconfigure network' already. the vm itself is up and running, but the network appears to be unreachable.
The same problem occurs with LA10GKVM14.
Dear VirMach Customers,
We are currently investigating several outages in Los Angeles. We will update this post when we have more news regarding the situation.
Update 7:42PM 06/23/2022 - LA10GKVM24 has been booted and is now online
Update 7:55PM 06/23/2022 - LA10GKVM15, LA10GKVM18, LA10GKVM19 have also been booted and are now online
Update 9:28PM 06/23/2022 - LA10GKVM26 has been booted and is now online.
Update 12:56AM 06/24/2022 - After further troubleshooting, we have determined that both LAKVM36 and LA10GKVM14 have failed power supplies. We will ship 2 replacement PSUs next day air to get these replaced as soon as possible.
@VirMach I just migrated one of my servers to Frankfurt and I got put on FFME002...
Finally decided to click the Ryzen fix IP button because packet loss got worse, here's the result:
1) the button worked, and IP got changed to another Class-A, packet loss didn't improve.
2) the process may require clicking the fix network button.
3) the IP assigned is blocked by GFW already, so there's a risk that you may end up with an unusable service (like in my case).
There's no Saturday delivery in Canada from the big couriers, but the US does for major cities. There's probably even two tiers for Saturday delivery for guaranteed times.
The last time I paid a premium for Saturday delivery for a production thing, it was delivered to the local city sorting center at 3am Saturday morning and then delivered Monday. Fucking pissed me off that it travelled thousands of km's in just a few hours to sit for 50 hours 5 kilometres away from destination.
still spinning...
Hi, I click Ryzen Migrate to Frankurt. It works smoothly but I noticed 4 ipv4 has been assigned on my VM.
NY10GKVM61 is not even connected to any, that's why it kept spinning, nothing happens, @VirMach would you care to take a look at this?
TYOC025 seems to be limited to a very low cpu frequency and narrow bandwidth,hope you can undo the limit.
@VirMach
Can you arrange the migration??? Once again request to you
Ticket # 571560
The last time I replied to my message was 20 days ago, and now the product has not successfully completed the migration (paid migration >30 days), and now it seems that the VPS is offline, which is really terrible @VirMach