VirMach
VirMach
About
- Username
- VirMach
- Joined
- Visits
- 3,198
- Last Active
- Roles
- Member
- Thanked
- 9664
Comments
-
(Quote) This should've been fixed but there's so much going on right now it's possible I missed it. This should have been fixed with NYCB044 though which people said works above your comment so I'm leaning toward I made some error in fixing it. (Qu…
-
(Quote) I've been babysitting this all day and it's not going well, a lot to clean up. The node had some new weird situations the system did not account for properly and it got delayed into missing the IP change window, except some smart recovery sy…
-
(Quote) In your case it's not done yet, being worked on now. (As in I'm aware.) Some delay. Luckily not many affected.
-
(Quote) This particular batch was a last minute change, mostly as a precaution due to previous node issues. I decided to use it as an opportunity to cluster everyone across more stable and emptier nodes. This did cause an additional delay on an alre…
-
(Quote) Bug fixed.
-
I'm sure all of this has already been thoroughly discussed. I'm here to chime in to the original post, I haven't read any of the replies yet, so please just ignore most of what I'm saying if it's already been repeated. Hopefully there's maybe a few …
-
I've been able to confirm something, after going through the data. Let's say there are 20 different test points, and let's say that each block can reach 10 test points, but not the other 10 test points. We have 10x new /24 subnets (we actually hav…
-
(Quote) Yeah, it's strange. I'm still investigating on our end but I've spent a lot of time on it without anything fruitful coming from my investigation. I'm just trying to make sure it's nothing that could theoretically be on our end, I still don'…
-
(Quote) If it is 100% unreachable from everywhere, that's a different issue. On NYCB045, I see some virtual servers that are definitely receiving connectivity (with the routing issue) but I also see at least one that got an early change and it's no…
-
(Quote) This appears to be the same issue that's being discussed on this page by others. Yours is pinging, but not on all routes. So it's possible the route to you specifically is one of the ones not working. See my message above for more informati…
-
(Quote) When it doesn't work, if anyone sees my message here, please specify between you cannot ping it and if you checked it globally. If you cannot reach it, ticket with MTR (both directions preferred or one way to a public test server we can test…
-
(Quote) It could potentially be an upstream routing issue on specific routes. They're supposed to be live. It could also be human error. I should've done more extensive testing globally, I'm looking into it now and contacting the provider. At least…
-
(Quote) Which server?
-
(Quote) I'll try to remember to work in a fix for this, our new system has the capability to technically correct these glitched states when they happen in the future. Sorry you had to wait so long.
-
(Quote) This is something that's currently being worked on, alongside IP renumbering planning, and San Jose. Some progress has been made but it likely will not be until at least the next few days for a solution to be found. (Quote) Alpha/beta monit…
-
(Quote) I've definitely made some time for other things, most of it happening/starting around the time everyone thought I disappeared. I tried cutting back hours to what would be considered "normal" after the first San Jose incident occurr…
-
(Quote) I can confirm you are 1 of 5 virtual servers affected on LAXA017. That's good, it means nothing weird going on that isn't already accounted/detected. I went ahead and corrected yours using the conflict scanner tool instead of "official…
-
(Quote) There's up to 2 services on LAXA026, 2 on LAXA025, 1 on LAXA023, 3 on LAXA021, 5 on LAXA017, 1 on LAXA016, 1 on LAXA014, 1 on LAXA012, 12 on LAXA011, 2 on LAXA010, 2 on LAX1Z020, and 2 on LAXA006 that still need a change. Most of these just…
-
(Quote) I decided to postpone Chicago changes, but forgot that I coordinated the date with the datacenter. Quickly caught and asked them to re-announce but likely (Quote) This is due to a SVM bug. There's a few things that they never fixed even aft…
-
(Quote) The automatic network issue are not perfect right now when it comes to things flying around. I haven't focused on fixing that right now. In your case though, it being "resolved" is correct. Just your specific VM is not, which would…
-
(Quote) A lot of stuff is going on with some of the LAX renumbering, it's not how I wanted, but the good news is that the system has them all tracked. I've had to work on improving the system to deal with really specific scenarios and the code didn'…
-
(Quote) I'm conflicted on whether I want to add an invoice for better reference. I just see all the ways it could end up making the process run into issues. It's definitely "intended" right now for it to be credits, except I don't like how…
-
(Quote) Hello! Just to keep you updated, we now have a fancy new system for IP changes, but we're still VirMach so it means that didn't prevent it from being a total headache/mess. (Quote) There was a network revamp in the works, the LAX region ha…
-
(Quote) I saw your request in the system. It's due to human error, not the tool in this case. I put TYOC027 out of maintenance mode to test/get it ready for something I'm working on, and I forgot to put it back in maintenance mode. The system should…
-
(Quote) Aware, being worked on.
-
(Quote) Services extended by a year as long as we can all pretend it's still 2025. Except for @Kris, I don't know how I feel about extending it into near the end of 2028, feels weird. We'll figure something out. (Quote) I apologize it's dragging o…
-
(Quote) This did not go well.
-
(Quote) Working on it, sorry for the wait. Another bug is reconfigures aren't going through when early button is used, related to the staggering feature I mentioned. Only affects some servers that are also switching VLANs for the bridge issue. The …
-
IP changes are going to go out kind of last minute. Announcements were delayed in NYC, and some bugs had to be worked out with the new system (it worked in testing, the bugs were in specific batch operations when multiple subnets and VLAN changes we…
-
(Quote) Try now, it was a bug. Seems to have affected a few VMs. If it keeps happening let me kno.
-
TYO started having more issues around the same time migrations from SJC to Tokyo were supposed to take place, and some of the issues were actually exasperated by the migrations happening. Therefore, some of the migrations might end up being redirec…
-
IP renumbering is about to happen again. These will be with a provider I trust who has mentioned they have no intention of pulling them any time soon, therefore it's good for long-term stability (as with IPXO, even though we've avoided major problem…
-
(Quote) Generally bad advice for what's trying to be achieved. Reported as lost/stolen or whatever doesn't prevent the card from being auto updated with the merchant, so previous charges/subscriptions can still go through. It only prevents the old n…
-
(Quote) The servers just need some generic cialis. (Quote) We're cicada farmers. Demand is low. (Quote) Make sure you create a ticket for your case if you haven't. It'll probably take a while for it to be processed but you'll likely get another ex…
-
Sorry I won't be able to reply to everyone but I'll try to focus on a few important things. (Quote) The IPv4 was cancelled on purpose since it's not being used. Unfortunately San Jose relocation has taken way longer than anticipated as other issues…
-
San Jose Update * SJCZ001, SJCZ009, SJCZ010 -- These are in Los Angeles and waiting for an IP change. All others will be migrated as previously discussed. I had a tire blowout on the drive back which added some time to the trip, and while I didn't…
-
Some updates on specific nodes that have been facing an extended outage. ATLZ030 - Data loss on 7x VMs. Service extended by 160 days. Not yet back online, requires some more work. ATLZ031 - In the process of being migrated/partially migrated. Exte…
-
Service extensions processed for San Jose, by 75 days (exceeds outage, to give time for communication, migration, padding for renewals.) Three servers went in LAX to replace broken nodes and some maintenance took place for LAX as well. (Quote) Thi…
-
Physical servers have been collected from San Jose.
-
(Quote) I’ll have a look. Based on the information you provided it doesn’t make sense (Quote) Your payout request 3 years ago (10/03/22) was rejected with reason provided in the communication. It’s not an issue that would prevent you from getting a…