★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

VirMach · April 2022

I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

Such · April 2022

@VirMach said:

@ceplavia said:

@opshk said:

@Such said:
Quote：Biennial pre-orders in Tokyo will also receive a guaranteed spot on Gen4/Ryzen 5000 Series processor server and will be activated in the first pre-order batch for that location.
Shouldn't the Biennial pre-order be activated first？just ask, maybe it's a problem with my translation software

I am having the same question in my mind, though the servers are not stable in the current stage, it still kind of a promise Virmach made in the first post. Or am I missing anything?

my biennial 768 still pending lol

I want to clarify something regarding the biennial plans.

Some people seem to have a misunderstand that these would 100% be created before everyone else. These were listed as being created on the first "batch" which was the batch of Gen4/5900X servers. Then there were other "batches" of servers, with Gen3 being set up next, and then there's a final batch planned which was the 10Gbit, and any others.

I could have worded this better. Initially this did mean that these would be created first because we were going to try to save some space on 5900X nodes and create everyone else balanced throughout 5000 AND 3000 series.

However, we decided to put everyone on 5000 series. So the other "batch" was delayed, since we didn't need to send that out with great urgency.

This resulted in them being mixed more in the same batch.

In addition to this, even if we did mean that they would all be created first, unfortunately in that situation that's something that would only delay the creation of ALL the services even more. If they're created together this way with the script, I can assure you that you will receive your service sooner than if we had activated biennial plans manually first because of the WHMCS and SolusVM webserver slowdowns. Loading certain pages on our end are still very slow so it would take 5 to 10 times longer than our script.

Ok,thanks for the explanation, i think i got it all, wish you all the best.

Sure · April 2022

When is the Tokyo node expected to be fully online.

xmd5 · April 2022

Ryzen Special 2560 None of them are active?

umzak · April 2022

@VirMach said:

@tototo said:
I wish I could move my Tokyo node to TYOC033 or TYOC035...

I'm going to speak to our developer today and see if we can implement our migration without data script to allow people on TYOC040 or TYOC039 to recreate on another random node. That might help everyone, including us, and calm things down.

I'm setting up two more nodes right now as well.

Why? Is node 35 better and more stable than 40?

VirMach · April 2022

@umzak said:

@VirMach said:

@tototo said:
I wish I could move my Tokyo node to TYOC033 or TYOC035...

I'm going to speak to our developer today and see if we can implement our migration without data script to allow people on TYOC040 or TYOC039 to recreate on another random node. That might help everyone, including us, and calm things down.

I'm setting up two more nodes right now as well.

Why? Is node 35 better and more stable than 40?

Node 40 and 39 are the first two nodes. They have the most number of people with older operating systems, before I disabled them, and therefore they have more virtualization incompatibility causing high interrupts, and thus causing networking not to be able to perform to full capacity.

Basically, libvirt/qemu is constantly preventing the network controller from doing its job immediately from (some) VMs crashing and restarting or almost crashing.

(edit) Here's one way I can present it to you.

On TYOC040, the libvirt logs, aka, text files with what's going on, are 3.7GB right now.

On TYOC035, they are 11MB.

There are less logs when everything works as expected with virtualization.

(edit) and they are 17MB for TYOC039. So a really really really oversimplified to the extreme way of saying this can be that TYOC039 potentially runs 0-50% worse than TYOC035, and TYOC040 runs 0-33,600% worse. Please no one make fun of me for simplifying it to this degree, I understand it doesn't actually mean that, it's just how I would explain it to where every person in the world could understand and based on limited information without reading logs for the next 2 years.

Sure · April 2022

\

VirMach · April 2022

TYOC040 - here's how I've decided to proceed for now.

Everyone who is potentially causing issues will be suspended and re-created on another node using a stable OS. If you have important data, you can request your data from the suspended node which will remain there for at least a few days, so please immediately contact us with a priority ticket if you need your data in this situation. I'll also adjust your due date.

I'll send an email now.

tototo · April 2022

@VirMach said:

@tototo said:
It might be better to have something like "Instant", which is a higher rank than "Available".
It's all in the notes, but even so, I can't expect people opening nonsense tickets to read it...

I want to avoid using the word "instant" for now. I already removed it a while ago from the location selections and tried to avoid using it moving forward. I don't know how well of a job I've done but I don't want people to think that anything will be within 1 second.

So unfortunately that means it'll be "available" no matter what state of "available" it is in right now. I could add a word beneath that but then all of them would still go into that as they're all available with some minor caveats.

Yes, you are right. I should think deeply about it...

@VirMach said:

@tototo said:
I wish I could move my Tokyo node to TYOC033 or TYOC035...

I'm going to speak to our developer today and see if we can implement our migration without data script to allow people on TYOC040 or TYOC039 to recreate on another random node. That might help everyone, including us, and calm things down.

I'm setting up two more nodes right now as well.

That is so interesting! I will definitely use it.
In fact, TYOC039 seems to be more stable than before, so I'm looking forward to moving to a more unstable node and taking part in the test.
(Other people who said "I want to take the test!" may agree with this)

However, you may need to warn us that "tickets requesting a return to previous node are not acceptable", "we do not guarantee that another random node is stable", "recreate is not unlimited", etc....

VirMach · April 2022

@tototo said: In fact, TYOC039 seems to be more stable than before, so I'm looking forward to moving to a more unstable node and taking part in the test.

TYOC039 should be as good as it's going to get for a while so if anyone still has problems let me know very specifically what it is here so I can take a look. So in my comparison, it's only 17MB logs versus 11MB logs so it was only a few VMs (as in 1, 2, 3, 4, etc) that had problems.

VirMach · April 2022

@cgs3238 said:

@VirMach said:
TYOC040 Update - just adding a small note/update here, to rule out this being caused by the switch or network cable or the way it is seated, we requested some time ago that the datacenter replace the cable. This has been completed.

We've had some very rare cases where something similar was alleviated to some degree when the cable was changed. We didn't expect this to actually work or be the solution, but it was just done as a precaution.

Don’t forget 039 node which is not as stable as yesterday, maybe the similar situation with 040

Can you provide more details?

umzak · April 2022

@VirMach said:
TYOC040 - here's how I've decided to proceed for now.

Everyone who is potentially causing issues will be suspended and re-created on another node using a stable OS. If you have important data, you can request your data from the suspended node which will remain there for at least a few days, so please immediately contact us with a priority ticket if you need your data in this situation. I'll also adjust your due date.

I'll send an email now.

hopefully, after all the vps causing the problem are moved, node 40 gets a lot better than 35

leendon · April 2022

@VirMach said:

@cgs3238 said:

@VirMach said:
TYOC040 Update - just adding a small note/update here, to rule out this being caused by the switch or network cable or the way it is seated, we requested some time ago that the datacenter replace the cable. This has been completed.

We've had some very rare cases where something similar was alleviated to some degree when the cable was changed. We didn't expect this to actually work or be the solution, but it was just done as a precaution.

Don’t forget 039 node which is not as stable as yesterday, maybe the similar situation with 040

Can you provide more details?

Unfortunately, I ordered two servers, one with 40 nodes has been delayed for a month and it has not improved, and the other storage does not know when it will be resolved. My guess may be the same time as 40 nodes, but this is my assumption

cgs3238 · April 2022

@VirMach said:

@cgs3238 said:

@VirMach said:
TYOC040 Update - just adding a small note/update here, to rule out this being caused by the switch or network cable or the way it is seated, we requested some time ago that the datacenter replace the cable. This has been completed.

We've had some very rare cases where something similar was alleviated to some degree when the cable was changed. We didn't expect this to actually work or be the solution, but it was just done as a precaution.

Don’t forget 039 node which is not as stable as yesterday, maybe the similar situation with 040

Can you provide more details?

It has been recovered about 40 minutes ago.
Here is the monitor : https://tz.115.al/Detail/BEEEE74D

Maybe it’s a risk to click links, but in short :
About 12 hours ago the load became very high, and the networking max throughout became less than 30mb/s. 40 minutes ago it recovered as smoothly.

qwerttaa · April 2022

@VirMach said:
I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

my 039 has been more than 1 dday and 19h without automatic shutdown, i can continue to observe and give you feedback

let me know if you need to do any other tests on 039

btw, 384 plan

VirMach · April 2022

@cgs3238 said: About 12 hours ago the load became very high, and the networking max throughout became less than 30mb/s. 40 minutes ago it recovered as smoothly.

I'm checking to see what happened, thanks for the info. I can confirm on my end the same thing happened at a glance.

VirMach · April 2022

@qwerttaa said:

@VirMach said:
I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

my 039 has been more than 1 dday and 19h without automatic shutdown, i can continue to observe and give you feedback

let me know if you need to do any other tests on 039

btw, 384 plan

I'll let you know after I look at the logs, thanks.

leendon · April 2022

@VirMach said:

@qwerttaa said:

@VirMach said:
I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

my 039 has been more than 1 dday and 19h without automatic shutdown, i can continue to observe and give you feedback

let me know if you need to do any other tests on 039

btw, 384 plan

I'll let you know after I look at the logs, thanks.

Sorry, my English is not very good, I want to say that the 40 node is ready to migrate to other places? I received the email, but I don't understand it very well after the translation, I need to confirm it to you

VirMach · April 2022

@leendon said:

@VirMach said:

@qwerttaa said:

@VirMach said:
I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

my 039 has been more than 1 dday and 19h without automatic shutdown, i can continue to observe and give you feedback

let me know if you need to do any other tests on 039

btw, 384 plan

I'll let you know after I look at the logs, thanks.

Sorry, my English is not very good, I want to say that the 40 node is ready to migrate to other places? I received the email, but I don't understand it very well after the translation, I need to confirm it to you

If your service is suspended by me, it will recreate. If you need your data and it gets suspended, let me know. That's what the email means mostly.

leendon · April 2022

@VirMach said:

@leendon said:

@VirMach said:

@qwerttaa said:

@VirMach said:
I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

my 039 has been more than 1 dday and 19h without automatic shutdown, i can continue to observe and give you feedback

let me know if you need to do any other tests on 039

btw, 384 plan

I'll let you know after I look at the logs, thanks.

Sorry, my English is not very good, I want to say that the 40 node is ready to migrate to other places? I received the email, but I don't understand it very well after the translation, I need to confirm it to you

If your service is suspended by me, it will recreate. If you need your data and it gets suspended, let me know. That's what the email means mostly.

Rebuild on another node server? Will it be migrated back in the future?

vhhjkgl · April 2022

@leendon said:

@VirMach said:

@leendon said:

@VirMach said:

@qwerttaa said:

@VirMach said:
I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

my 039 has been more than 1 dday and 19h without automatic shutdown, i can continue to observe and give you feedback

let me know if you need to do any other tests on 039

btw, 384 plan

I'll let you know after I look at the logs, thanks.

Sorry, my English is not very good, I want to say that the 40 node is ready to migrate to other places? I received the email, but I don't understand it very well after the translation, I need to confirm it to you

If your service is suspended by me, it will recreate. If you need your data and it gets suspended, let me know. That's what the email means mostly.

Rebuild on another node server? Will it be migrated back in the future?

No

spjhpo · April 2022

Do you have a schedule to active the rest vps？

qwerttaa · April 2022

@VirMach said:

@qwerttaa said:

@VirMach said:
I'll also try to think out a good email to send to everyone once we make a decision on how to proceed for those nodes, but it will most likely be an email to everyone on those two nodes telling them to "power down" and re-install. I want to test some templates today finally and try to break it and see which ones are fully stable and disable all other templates for now.

The fix doesn't necessarily have to be ALL of EVERYTHING re-done, just enough people moving around and re-installing should alleviate it.

my 039 has been more than 1 dday and 19h without automatic shutdown, i can continue to observe and give you feedback

let me know if you need to do any other tests on 039

btw, 384 plan

I'll let you know after I look at the logs, thanks.

the last automatic shutdown i did not provide the log to you, because i was checked and there was nothing unusual

after that i have tried to dd a pure debian11 from official sources,,,,i just fxxked up...

so i reinstall debian10 from panel and update to debian11

now, running for almost 2 days

leendon · April 2022

@spjhpo said:
Do you have a schedule to active the rest vps？

It may be a long time before the storage server, as far as I understand it is at least 15 days or more

qwerttaa · April 2022

also i see a person who had the same problem as i had before, the two-step verification email problem...

there may be another victim of this problem, so hopefully the bug can be fixed once and for all

vhhjkgl · April 2022

Go to bed, after wake up hope everything will become better!Good night!

AlwaysSkint · April 2022

@vhhjkgl said: Go to bed, after wake up hope everything will become better!Good night!

That's the spirit!
Take a week's holiday and it'll only get better.

reb0rn · April 2022

Denver node looks fine
https://browser.geekbench.com/v4/cpu/16529970

Phoenix node PHXZ001 did not manage to get it online
Ticket #787759

bedr8m · April 2022

i need this server

384MB RAM -- Limit 800 Quantity
10GB NVMe
1 vCore Ryzen* CPU
1TB @ 1Gbps Bandwidth
1x IPv4 Address
japan

can i buy?

emperor · April 2022

@bedr8m said: can i buy?

Yes, after you read all 128 pages.

Howdy, Stranger!

Categories

In this Discussion

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

★ VirMach ★ RYZEN ★ NVMe ★★ $8.88/YR- 384MB ★★ $21.85/YR- 2.5GB ★ Instant ★ Japan Pre-order ★ & More

Comments