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 Oh shit, you put my VPS on node 40. It is a mjj node. Why put me and those mjjs together? Now it's like a piece of shit.
Bill #1412760, has been inactive, o
Network issue,TYO40 node
mtr -c 30 193.111.31.1
NiftyBrown-VM (45.66.128.24x) 2022-04-08T01:21:32-0400
Keys: Help Display mode Restart statistics Order of fields
quit Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 45.66.128.1.stati 0.0% 10 65.6 69.7 47.0 98.6 15.3
2. 45.149.159.1 0.0% 10 621.0 565.9 396.6 690.5 93.3
3. 193.111.31.1 11.1% 9 498.0 518.5 375.6 702.9 95.2
GreenCloud.x(193.111.31.x)
Keys: Help Display mode Restart statistics Order of fie
lds quit Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 45.142.166.1 0.0% 26 0.5 1.3 0.5 18.9 3.6
2. 91.200.240.20 0.0% 26 19.5 16.8 11.6 22.1 3.8
3. 45.149.159.2 0.0% 25 0.8 3.5 0.7 12.9 2.9
4. 45.66.128.24x. 0.0% 25 1.9 2.1 0.3 17.4 3.4
download from same IIJ network only 200KB/s. unusable.
I just wanna ask about my vps in node 40. I ping gateway in my vps, it showed up to 300ms delays. I want to know that is that normal or not? Will it be improved later?
Try now.
That's not even the "MJJ" node. That ended up being scrapped because I realized we need it to complete fast deployments. I won't say which one that is since it will just cause people to make myths about it.
Anyway, try network now. Around 8 VMs were going into kernel panic due to bad OS and causing high system CPU usage, now it's cleared.
This wasn't normal, it should improve now. Let me know.
39 nodes have a similar problem
Taking a look. They might all have some degree of the same problem as people install an OS if it gets frozen. The ones showing issues right now are CentOS 5.8 and Ubuntu 18 or Ubuntu 20 ISO.
I've paused further creation until these settle down a little bit, to give people a chance to mass install their OS, do their benchmarking, etc.
@VirMach Hi! When will all the VPS in Tokyo be deployed?
Tokyo is about 36% deployed right now.
We'll probably reach 60% within the next 12 hours if there's not further issues. I still have two of these nodes I need to configure, all the rest are being used.
I thought you said CentOS 5.8 is removed some time ago because lots of people use that (or as default) and it's long into EOL?
Correct, that's why TYOC040 was most affected, these people booted it back on and just left it there in kernel panic.
I'm starting to send tickets when I shut down so people know.
Keep in mind though, if 2,000+ people are being deployed, no matter the number of servers, if they're all setting up their OS at the same time and testing network, it will obviously be only so much that can be done in this scenario. It will of course normalize when everyone stops benchmarking and setting up the OS and begins just using it normally.
We can't have it both ways, but I'm trying to balance it versus quick deployment and staggering it enough to give it some breathing room. This always happens initially with bulk special offers being sold. Otherwise when customers normally buy it X amount per day over a longer period of course it's more stable deployment.
I'm unable to use the SolusVM due to the aggressive protection. It banned me temporarily after trying to just reset the password. Logging in with the new password doesn't work because I have hit the limits.
Now the network of node 40 is a little better than a few hours ago, but it is still very different from the previous network, I will try it later. Thank you for your reply!
I understand this issue but we're already at capacity. Let me see if I can enable Cloudflare waiting room and lower the ratelimits. But again, hundreds of closer to a thousand people are trying to use 10 year old PHP software at the same time, I can't do much about that...
Good to hear. Don't worry, it will only get better over the next day or two, this is just because everyone is setting it up at once. Remember these are shared ports, even if we barely put anyone on each node, if let's say 20 people are doing speed testing at once or setting up their OS then that's 1Gbps port divided by 20 and 50Mbps max speed per person. It's not normal for that many people to try to max out 1Gps at once, so it will settle down and be normal and "average" out better.
You can completely prohibit Chinese users from buying your services. There is no need to treat them differently. This is too bad
Tokyo has continuously 60KB/s abnormal traffic. 60KB/s * 60 60 24* 30, 150G traffic loss per month.
I Confirmed 37 and 39 nodes have this problem.
Has nothing to do with race, nationality, or region.
These were just 40~ people activated earlier as a joke because they were spamming tickets and order IDs trying to get ahead in line. I thought it would be interesting to put them on a node together where they are neighbors. It's not limited in any way, the only difference was that they would be on a node together with all others that were impatient.
Edit -- And just so we're clear, not all of these people were from China. I remember activating people in Indonesia, Thailand, and other regions.
Tokyo node is a shitty network!
Which server, so I can take a look and make improvements? I'm repeating myself now but when everyone is activated and testing at once it will be temporarily overloaded. We're also waiting on datacenter to switch to 40Gbps uplink, it's scheduled very soon.
We can also temporarily move you to San Jose if you wish, until it cools off.
I also found the abnormal traffic of 60kb/s. My system is almalinux 8.
By the way, have you finished change the next due date of all the service? My date is still 03 / 12 / 2023.
I do not care when my server is booted now,but I checked my account and found that my server is missing.Order #553264
I remember before you said about anti-abuse script or something similar. After my node activated later I will start doing an initial set up sync. That involves rsyncing gigabytes of thousands of small files from my other server (or extracting similar contents from a big fat tar) and may takes a while.
How do I make sure its not going to falsely trigger this anti-abuse script?
We'll run some more queries to catch the rest of these. Probably 99% of them done though.
This bugged out, I'm fixing it now.
@VirMach Are there some VMes repessing the CPU (kernel problem or so) on 039 node?
It may falsely trigger at the beginning if you participate in setting it up today or tomorrow but after that we'll be sure to be very lenient. This is just so node isn't overloaded from any installations that freeze due to OS incompatibility.
What you describe though should be fine and if you get false flagged don't worry, it will not count against you in any way.