VirMach
VirMach
About
- Username
- VirMach
- Joined
- Visits
- 3,207
- Last Active
- Roles
- Member
- Karma
- 9,672
Comments
-
OKC Update I don't know if I let you guys know, but my car was having some issues that just got resolved (hopefully permanently-ish) as of about 10 minutes ago. Going to head to the DC in about 30 minutes to an hour. It's the weekend and …
-
(Quote) The buzzer for 308 still goes to my phone for some reason. Any time you want to put in an emergency ticket you know what to do.
-
Every time I come back here I have to clear out a preloaded essay I was writing. Okay, so an update on Oklahoma: ready tomorrow (for us.) A few other things pushing into eachother but I'm pretty determined to at least plant the router there as…
-
(Quote) Depends. As for routing to Dallas first, I assume you mean if it has to get to the west coast. I know of a transit provider that has a 60G direct route to San Jose, it's just way too expensive. If we expand the location out, or other p…
-
(Quote) Lumen connected. Cabinet will be fully set up mid-week with the router, switch, and a few servers. So we're still on schedule, only thing that changed is Cogent is delayed and Lumen is early.
-
(Quote) I can confirm. I haven't had time to figure it out, I know some people talked about it earlier and I had a ticket about it with useful information from several months ago that I have to review as I think people already figured it out. …
-
A little more clarification on how it would work for the "VirMach" portion of OKC. It'd be exactly the same. We'd used leased IPv4, likely with however frequent renumberings that occur and any limitations. Same control panel, pl…
-
(Quote) Oregon, Utah, and Colorado were all being considered. However, the location we'll be launching is Oklahoma City. OKC Launch We're going to be doing this location a little bit differently. I wanted to confirm with you guys that th…
-
First batch of migrations are about to happen for Chicago. A few were done yesterday, this will be the bulk. I'll likely keep doing them in 24 hour batches for the first few days as it was taking too long finding suitable servers per ticket. Al…
-
Okay guys instead of confirming with everyone again whether or not they intend on migrating or not per ticket (after it returned online) since not everyone is going to want one or the other, I'm about to send out email communication. And I'…
-
(Quote) The service network is back up, we can just move the existing data from the server directly. No longer loaded from backups, we'll just straight up migrate it normally. I don't actually know about your service specifically our moni…
-
Strategy change, we're going to focus on making sure backups run immediately so we have fresh copies. (I'll still migrate people who requested afterward.)
-
(Quote) That's because the servers are back online. Yes I'm confused too.
-
Okay so I'm going to select other buttons other than "Network Status" and hit continue, I also approved VNC screenshots, and this is on a service that's offline. It does look like the code update I put on here is also working as…
-
(Quote) We probably need a better name for them than buttons or departments. I'm going to do a quick check logged in as a customer just to communicate what I'm specifically verifying right now. * Service page takes a while to load, but do…
-
(Quote) Everything was already assessed and this was the best way to do it. We can go over it later in a long post if anyone wants, just not now. (Quote) I've been meaning to post about this, if I can just have 3 hours of breathing room this w…
-
QN said to move by end of April. I'm not going to pretend like I wasn't expecting this as a possibility, that's why we already had weekly backups off-site, but it would have been nice if we at least made it to the end of March. Most …
-
(Quote) Don't be afraid to make a ticket. We usually say to please not make one but this time around I went out of my way to insist on tickets being made and it was with good reason -- this was a huge mess to complete. I've already locate…
-
Knowledgebase articles on ticket submit removed as it was just annoying, buggy, and it's already basically replied with AI. Long overdue. If we integrate it back it'll be at the AI phase most likely. Priority department removed (technical…
-
(Quote) Sounds like your payment wasn't accepted. How did you open your ticket by the way? Whichever way you did it means it gets delayed in the queue, I want to make sure we patch that so others don't do it. I've located your paymen…
-
(Quote) Aware. They'll be moved off at this point or to another disk. There's also still abuse, I need to wrap up LAXA004S first.
-
(Quote) Should be OK now. Monitoring further.
-
(Quote) That one started being weird a day or two ago. None of this is a coincidence though, I just haven't had time to play detective while dealing with LAXA004S. Such a PITA, I had to basically piece together the host operating system because…
-
(Quote) Tokyo-exclusive issue. We can't move people to nearby location as we normally would (we'd get 95% complaints) and can't move everyone to another Tokyo node either because it'll likely cause problems on the other node afte…
-
(Quote) Sorry, I guess I should just go for it. I'm really dreading this situation because if I take action in this particular case, there is a small chance it could go terribly wrong. But you're right, it's been too long and I haven&…
-
(Quote) Might just be your VPS only, I don't see a problem with the node.
-
(Quote) Create a ticket to be moved away. I've been working on this and trying to get it more stable, it does appear temporarily more stable after every fix for a few days to a week and then this happens again as you've described. By the …
-
(Quote) Wow I used to have a lot of hair back then. (Quote) Persian/Iranian.
-
(Quote) Sadly had to get rid of this part for now as it was causing some other problems with controls: and it also it loads everything before waiting for a timeout from SolusVM. But I fixed anomoly .. maybe. Okay I need to stop staring at this pag…
-
(Quote) This has been fixed. I also improved the process to where in cases of the troubleshooter timing out, instead of telling you to go back and clicking network status, it tries to let you proceed with creating a ticket instead. If it breaks in a…
-
LAX1Z017 is going to get decommissioned with a hammer right after I move customers off.
-
(Quote) If it was closed like that it means there was high confidence it was already resolved. It'd be helpful if you show which generic response you received as they're not meant to be very generic and there's a good set of different…
-
LAX2Z021 being worked on, likely due to human error (me, I'm the human.) I'm going to be reviewing more recent tickets first, so if you guys put an important one in and the ticket is unanswered, close it and re-open in this case. Then au…
-
(Quote) Control issue on this one, fixing. As in everything's up, controls are down. You could have some secondary issue which you'll be able to see after I fix the controls.
-
(Quote) Hi, I'm aware. I listed it as webhosting specifically instead of mentioning the specific name, it still requires some additional work. I'm about 12 hours behind schedule right now with everything. Two servers still have major probl…
-
(Quote) Adjusting some configurations on the switch to address it. Nothing to do with BGP or the servers or anything else in this case, I just fixed the remaining network issues too quickly and it cascaded into this.
-
(Quote) I just want to add a huge disclaimer on what I said here, I was just saying that in cases where the network reconfigure tool fails, you have to do it manually. I shouldn't have focused on that at all, and should have instead said there …
-
(Quote) I'm assuming it got moved here from the other thread.
-
(Quote) Fixing all these control and ticket issues. I've also partially coded something out for what you're requesting, it's basically a replacement page for the current single message "something might be wrong" page. Not re…
-
(Quote) Someone was supposed to fix that ticket error when it got reported earlier, hmm. Okay I know what’s wrong based on that though no need for a ticket. Working on it now
-
(Quote) Best I can do is offer a free migration to an E5 in my bedroom. I get to power it down if it gets too loud, that’s the AUP.
-
Okay everything should be good (enough to leave and deal with remotely)
-
Okay LAXA014 has been fixed for a while but it’s back to being a network issue, I’ll hang a bit longer after bringing that one back up (hopefully for the last time) to see if anything else drops off then we should be good.
-
Almost everything being rebooted a final time due to motherboard bug, in case anyone’s wondering. This one’s my favorite bug it breaks IPMI and looks no different than it being set correctly
-
(Quote) Yeah that sounds like the “some secondary subnets” scenario since you can access VNC. I’ll fix those remotely. It’s possible a /24 or /23 left over also got missed and not noticed as I’m focusing on getting remote access to everything and ma…
-
LAXA014 going down isn't part of the maintenance, it's an actual outage. Let's see how quick I can resolve it in this rare scenario where I'm right there as it happens.
-
Okay I’m not doing any further maintenance outside of maybe reseating PCIe, I had to end up doing a board swap for LAXA031 because of a BIOS update. In other news LAXA031 has been upgraded from a 5950X to a 3900X. I could put the 5950X back in but m…
-
(Quote) There’s a bullet point somewhere mentioning IPv6 and Los Angeles. (Quote) This one needed to be physically unplugged and plugged back in, no idea why. Probably related to BMC/IPMI on these boards and particular scenarios where everything ra…
-
(Quote) Let me know if you want me to continue addressing your concerns here or if you want it shifted back over to the ticket. I haven't closed the ticket as I usually would have if we addressed you here instead when you reference the ticket, …
-
(Quote) From memory so could be wrong -- it took around 9AM to 12PM to remove everything, another 30 minutes around 2PM for the storage server. Around 12PM to 4PM for first cabinet. Around 4PM to 7:30PM to find out the switch had bad flash and compl…