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
Not the news I was anticipating, and also not the way I know a number of Datacenters around Amsterdam work. But these are strange times, and I have heared a number of occasions where idiotic price raises have been asked.
For my ordered Amsterdam VPS it's not an option to move to Frankfurt; the target users are dutch, and the lower the latency the better. But I'll wait until things settle down a bit and the way forward is more clear.
You know what they say, the longer you wait before you unwrap a present, the greater the surprise and joy! :-)
It works!
Thanks.
Sory typo : Node Name SJCZ004
Works with almalinux template
I probably should actually go in today and make sure Psychz isn't using the servers as drink coasters.
Should've opted for the extraordinary VPS.
We definitely will try to do Amsterdam still, just probably not with Psychz and even if we did I have no idea of the ETA so it's best we try to send the servers to the closest location with a reputable partner that can get them up quickly and right now that looks like Frankfurt. I'd say we're looking at... maybe another two weeks on top of any current estimates? Disclaimer: I am not saying that Amsterdam will be ready in two weeks, just that maybe at least another two weeks. And hopefully Frankfurt much sooner than that. I'm not providing this disclaimer for you as I'm sure you understand, just in case anyone decides to copy a portion of this two weeks from now to call me a liar.
And it's honestly not the price increase that's concerning. Whatever, let's say we did agree to the price hike, they apparently never even provisioned our cabinet while charging us for it and pretending they did.
I have to remind you that there are still some people in TYOC038, the status of our server is always offline, and we can't solve this problem through migration, because the migration option has been closed, when will this problem be solved?
I was actually looking at that right now.
TYOC038 Update - All the people left with a broken service are not directly involved in the disk issue it had, but most likely affected by it in that the system stuttered while they were creating and didn't create as efficiently, it looks like a provisioning issue similar to the other node earlier, I forgot the name. They never created properly. These date back from 04/11/2021 until now. We're going to set them back to pending, adjust the due date again to make up for the lost time, and add them to the pending queue. These should still be created first on the script again but I want to be very clear that it's not a guarantee. I don't see any reason why they shouldn't since it's the same script that would select these first if they were already selected first.
So if yours never provisioned correctly, today, you will see it go back to pending and due date changed to later.
Tokyo Update
Then, we're going to schedule maintenance with Tokyo to add in a new disk to TYOC038, as well as TYOC035. These nodes are both missing 2TB and have <65% CPU usage currently, so after the maintenance, creations will run again.
There will be total 3.5TB space for services, so about 10GB for 384MB plan and 50GB for 2.5GB plan for a rough average of 30GB, or 116 services. There are currently 72 services we know that did not provision correctly so those will fit, plus about 44 others.
TYOC033 has about 1.5TB of space, so up to another 50 here.
TYOC036 already received another disk, for another 1.75TB or 58 more services.
Total room for up to 152 services after TYOC038 is taken care of. Probably closer to 100 due to CPU constraints and since larger plans are left at the end due to previously discussed issue with the script.
Other nodes, they still need to cool off or may already be at capacity. That means 50-100 services at the end without an immediate home. Going to go through another round of requested refunds and see if we can make it all work.
TYOC037 has 1.5TB of space but it needs to calm down, we did just recently create a good amount on this one.
TYOC034 has about 1.2TB of space, but same, needs to calm.
TYOC039 has 660GB of space and it's pretty calm but I don't want to put anyone else here.
TYOC040 has 690GB of space that can maybe be used but I'll have to monitor it.
(edit) Actually a lot of this space issue can be resolved quickly, I'm going to go through anyone who has a ticket open about TYOC038 which has an active network status and start cancelling/refunding people since we request tickets not be opened in these cases. Email was sent as well already.
Did’t xTom have Amsterdam data center?
And I’m sure they own data center in CA as well.
Finally! I've really had enough with buffalo. Thank you,virmarch!Best provider ever!
They do have Amsterdam but we didn't sign up for a service there already so ETA would be longer. It's best we get the servers out of Psychz DC immediately and into another datacenter that's more immediately available.
We'll start talking to them with Amsterdam afterward too.
is TYOC040 fully working? no more work gonna be done on it?
Not much else that can be done.
On my end I see recent full port usage, as well as semi-stable ping. Actually the graph looks a little wavy, I think there is some work that can be done but at the same time this also has high packets per second so probably some abuse, I'll look into it further. Later down today's queue.
This situation is the main reason I say: I'll see how things evolve. Moneywise it's a lowcost VPS, and if I have to wait, I have to wait - I'm not "missing" the money in my wallet, and the purpose of the VPS was just to extend the number of DC's I'm in for some services to be even more redundant.
So for me it's no big deal, and I really feel with @VirMach about what's happening, because nobody is waiting for this kind of drawbacks.
what i meant was more of teething issues like bad drives, bugs etc. so i can start using it instead of YABS
i mean i love YABS but
TYOC039 had a drive fail, most likely XPG. Adding it to investigate and send out emails/network status page.
Also per this information, a lot more people would have been on it. I'm hoping we can get this one to return to migrate people off. Going to finish dealing with SEAZ001 first since that's been waiting all day, DC hands finally did the switcharoo we requested.
I think we're almost down to the last XPG drive soon, one way or another. I've still locked off these partial XPG nodes from filling any further and planning a swap per my previous messages, before they get worse.
Yikes, this has two XPG drives. Good news is this is our oldest node in Tokyo so... wait, or is that bad news? I mean I guess it means they aren't just immediate duds. But yeah, probably bad news.
I might send out a pre-emptive notification for this location. server.
I'm going to see if we can squeeze in an extra drive or two on all these or if we can strategically move people off XPG to another node that's non-XPG and then provision others afterward.
ok good to know, YABS to continue
@VirMach How many are left in Tokyo that haven't been created?
I'm also going to set up backups for all XPG nodes or ensure the backups we already set up work, it's a race against the clock. I really do not want people to lose important data (although anyone who has important data should always have backups, even if we do backups.) For this location though luckily it seems most people are just messing around with it since it's so new or just using it as a VPN.
Good-ish news is we did buy all those drives in Japan that we didn't end up using so they're all more or less immediately available as replacements.
200~ plus 72~ facing issues on TYOC038, plus more now with TYOC039, if I had to guess, another 40 to 100. I do have other nodes ready to ship to Tokyo, I'm going to repack those today 100% -- we meant to send them sooner with the last two we sent but everything started falling apart and I ran out of time.
We do have enough disks to fit everyone though after maintenance window, and they're good disks. All Samsung, WD, and other reputable brands.
Storage nodes will be shipped?
How long is the ETA for Tokyo storage?
Trying to send out Tokyo on Monday. Los Angeles is ready, just waiting for a reply from Psychz about everything. Amsterdam is delayed per Amsterdam issue. NYC needs to be tested, I dropped the motherboard like an idiot (well I knocked it off a shelf, technically it had padding on it so there's hope.) May most likely need a replacement board that doesn't exist for sale anywhere, we still do have backup dual E5 though.
It seems that Tokyo will not continue to create new servers for a while. sad
Wtf? They are working on it... Just wait for drive swap
@VirMach - Just a FYI. I expect Node 39 is getting ready to cause you more problems.
I am getting the following error message repeatedly.
Really? I saw the following words on their official website "We are not currently running the stagger creation script." I'm not quite sure what "stagger" means.
Please READ carefully (only a few posts up, but well... ppl dont read)
Thanks for the heads up, powering all these down to avoid it from crashing (already done as of this message, that's why I wasn't replying) and going to try to copy off the whole disk. If no reads/writes happening to it, it should have a higher chance of survival as well.
"All these" as in on the affected disk.
Looking forward to getting good news!