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
@VirMach SEA008 is
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
error message.
and network is down.
@VirMach the vps on FFME005 has been down for over 2 weeks, and there is no news about FFME, what is going on? do you forget it?
@VirMach when PHXZ002? Status is Offline many many days/
From all servers I got I can only see Ryzen Migrate in one of them... the alpha(beta) test in Phoenix :P
Still waiting for this button to show up moaaaaaar.
@VirMach Ticket #191061
Pending update for a paid migration for a box stuck. I made the migration ticket on 16th June
@VirMach Ticket #380625
FFME004 seems to be online, but after your migrate I have only old xeon IP and it's not work. No new IP at Solus. Can you please add new IP, so I can install working OS to my VPS and start using it?
Thank you.
SEAZ001 is actually still offline. Solus error: An error occurred processing your request. The host is currently unavailable. Please try again later.
Status: Unknown
@VirMach The server （149.57.194.18） cannot connect，Operation Timed Out After 90001 Milliseconds With 0 Bytes Received
error message.
This kind of pre-sale is bullshit, and people will ask for a refund? I really think that your stuff is fragrant, people bought your service and waited for 4 months, can't they ask? Junk service is always rubbish
You don't have to reinstall. Just wait for the fix.
Still bitter, eh?
Very macho of you! I remember your fragrant...so bitter.
Didn't VirMach offer you personally a refund few months back? No?
That has to be refunded, or I'll let him go? Look at buying his services, wait a few months and no one else can ask? I can't stand this kind of situation, the purpose of my visit today is to complain
That goes without saying. 72 comments and all but one are you lambasting Virmach.
A lot of the problematic nodes were marked as complete by the DC so if they're not back up yet then DC hands were not successful in the maintenance and it looks like it'll be further delayed.
Everything else I'm looking through now. As for networking, we still have not got a solid answer.
so, my vm apparently is always be turned off by itself,
everytime i boot (virmach once did this from his side) a couple of minutes later it goes down,
it always like that..
even he said nothing wrong with the node tyoc030
if he still offering refund i might gonna take that way, i don't have much energy to be wasted for complaining over n over, it's a win-win solution..
i use it as win RDP btw,
will try to enter rescue mode and see whether it will always goes ON or not
Can you migrate my tokyo node25 machine to node31?before the node25 broken,my connection is very smooth,after you fix it,now it's shit.I wonder if it will be better if i migrate to node31 @VirMach
I think there is really nothing wrong with 30. Except for one reboot for kernel update, mine has been up since the week it launched.
Ah, the lowendsupport forum.
DALZ005 seems to be back online.
my VM on node DAL-Z007 has the same behavior, boot up then a few minutes later it goes down.
SEAZ008 needed a RAM swap and it looks like DC hands did the RAM swap and then decided not to power it on? I don't know... but either way looks like this is awaiting another request as a result. Or it could just be that the network is so bad that nothing is working even to a minimal level in which case we're waiting on the network configuration changes we requested a week ago at this point.
SEAZ001 looks like maintenance was completed successfully but it's an issue with it booting into OS, I've corrected it now. This had it's kernel changed and the settings didn't stick, this happens once in a while but is relatively rare.
SEAZ004 has just have been having a bad time for a long time. At this point I'm going to spend those multiple hours I mentioned to jerry-rig a solution since we can't rely on DC partner to make the necessary changes in the switch.
DALZ005 was completed as well but left in a powered off state but at least the DC hands actually powered the node itself back on (chassis power.) I've booted it back up through IPMI. Some others look like maintenance was completed successfully and without error. I'm looking into the rest of these now: ATLZ007, SEAZ010
SEAZ010 looks like it's in the same boat as DALZ005, for now. Except it won't power on through IPMI. Putting in a request with DC hands.
SEAZ001 is back up per last message.
There is 1 single VM offline on TYOC030. The OS on it is Windows, so automatically I'm going to say it's probably the OS powering off and you need to search knowledgebase for this if you're using Windows and the single VM offline is yours:
That should probably work based on your description.
Here's 3 random VM ping.pe results on TYOC025.
(edit) Forgot to actually include them let me dig back through for the links.
https://i.imgur.com/3zRzFQ3.png
https://i.imgur.com/CwNkhoV.png
https://i.imgur.com/lLv5uaV.png
Yes I know it's not full results but the whole point is that it's not facing any extreme issues on our end.
@VirMach ticket #233805 Please handle, rescue mode doesn't work
It's not down for over two weeks. All you're doing is making it more difficult to deal with problems and harder to take into account any reports because the majority of them end up being false reports. Just because you may have clicked migrate button and it never created properly, doesn't mean the whole node is just down.
There's 9 VM's in an offline state.
All 9 powered on, without any error. So if you're on FFME005 and your service is actually "offline" that just means you were one of 9 people that did not even click boot.
Note - I remember most of these being either Ryzen migrates without data getting stuck or maybe a couple of them were transfers from Amsterdam that didn't properly process. If it's the latter it's still possible the data needs to be moved in and it's on a list of a couple dozen VMs that require this. That means if it's the former, you also still need an OS install.
If it's none of the above then specify what you mean by "down"
This one ran into memory errors, putting the request in. Got it back up for now, this ran into these errors after maintenance.
Down for 25 days, reinstall doesn't work, rescue mode doesn't work. . . day after day. . . . .
@VirMach DALZ008 is down or just my VM? I did't get any info in
network status pageabout DALZ008 ,It's offline about 2 weeks+Just your VM, but your VM should be up too now. All you needed to do was click on the boot button if it was one of the 2 that I booted, may need OS install.
If you used Ryzen migrate button and it didn't create properly then it'd be stuck. If it's in Tokyo, these are being handled in bulk as space frees up. If you want it handled sooner close your ticket and take Tokyo out the title and say you want to be recreated and name another location.
Otherwise keep that ticket open if you want it to be fixed in Tokyo, and you'll receive credit for the days it didn't work as long as you mentioned it in the ticket.
It took me 3 days to restore the backup, and thank goodness the boss didn't hold me accountable
But the trust in vir has been lost