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 my new no maintenance policy prohibits it as I’d like to have the option to leave the facility today.
@dudu said:
Hi, I see "LAX1Z013 - Complete" in February 26th's Network Status page, not metioned in February 27th's though. Does it mean the service is back to normal? Mine is not. It went back online at about 05:30 (UTC +8), then turned to unpingable at about 13:57 (UTC +8). It can be accessible via VNC, but can't connect to the internet.
I tried Troubleshooter, it shows :
Main IP pings: false
Node Online: true
Service online: online
Operating System:
Service Status:Active
Registration Date:2021-09-23
Then I tried "Reconfigure Networking", it shows:
An Error Occurred!
Networking could not be reconfigured. Unknown operating system
Second error means you have to do it manually. Open a ticket but use the troubleshooter option if it’s available aka don’t do priority, that’s being spammed right now. Don’t mention maintenance or LAX in the title. Actually just give me the ticket ID.
If it’s not internal to the VPS then I’m aware of a few secondary blocks that need fixing.
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.
@VirMach said: In other news LAXA031 has been upgraded from a 5950X to a 3900X.
FYI - I can access VPS on LAXA031 via VNC, VPS is running.
No network. can't ping the gateway .129, can't ping 1.1.1.1. "Destination Host unreachable".
Reconfigure network does not solve. Manual check of network inside VPS looks good. BGP has not changed since the 24th.
@VirMach said: In other news LAXA031 has been upgraded from a 5950X to a 3900X.
FYI - I can access VPS on LAXA031 via VNC, VPS is running.
No network. can't ping the gateway .129, can't ping 1.1.1.1. "Destination Host unreachable".
Reconfigure network does not solve. Manual check of network inside VPS looks good. BGP has not changed since the 24th.
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 making plenty of other mistakes.
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.
@VirMach said:
Okay everything should be good (enough to leave and deal with remotely)
Great!
It's time to start working on the offers for users affected by the outage: huge compensation, free configuration upgrades, free migrations, endless ipv6 and a coupon.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
@VirMach said:
Okay everything should be good (enough to leave and deal with remotely)
Great!
It's time to start working on the offers for users affected by the outage: huge compensation, free configuration upgrades, free migrations, endless ipv6 and a coupon.
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.
I have been trying to turn on one of my VPSes in LAX1Z014 but it only shows "Powered off" after pressing the "On" button. I already did the troubleshoot steps (there's no ISO attached to the VPS, changed the boot order, rescue mode does not work, connecting to the VNC only shows "authentication failed", even changing the VNC password and force power off and on again does not let me connect to the VNC). Should I submit a non-emergency ticket or I wait a little bit longer?
@ricANNArdo said:
I have been trying to turn on one of my VPSes in LAX1Z014 but it only shows "Powered off" after pressing the "On" button. I already did the troubleshoot steps (there's no ISO attached to the VPS, changed the boot order, rescue mode does not work, connecting to the VNC only shows "authentication failed", even changing the VNC password and force power off and on again does not let me connect to the VNC). Should I submit a non-emergency ticket or I wait a little bit longer?
...nevermind, I can't even make a ticket:
Oops!
Something went wrong and we couldn't process your request.
Please go back to the previous page and try again.
Error: Call to undefined function ping() in [slash][redacted][slash]customTicketsAddon[slash]hooks.php
@ricANNArdo said:
I have been trying to turn on one of my VPSes in LAX1Z014 but it only shows "Powered off" after pressing the "On" button. I already did the troubleshoot steps (there's no ISO attached to the VPS, changed the boot order, rescue mode does not work, connecting to the VNC only shows "authentication failed", even changing the VNC password and force power off and on again does not let me connect to the VNC). Should I submit a non-emergency ticket or I wait a little bit longer?
...nevermind, I can't even make a ticket:
Oops!
Something went wrong and we couldn't process your request.
Please go back to the previous page and try again.
Error: Call to undefined function ping() in [slash][redacted][slash]customTicketsAddon[slash]hooks.php
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
@sh97 said:
anyway to know what node my VM was on (its now down)
The IP is 141.11.92.xxx
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 ready yet. So to answer your question, no. Also not that it'd help you at this point anyway.
@VirMach said: Second error means you have to do it manually
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 is almost no reason to reconfigure networking within your VPS as a result of the migration.
I'm exhausted so muscle memory kicked in and I've been looking at tickets where a lot of people are doing this, and I even did it myself, definitely don't do it. Nothing good will come of it. I'm going to add that to the status page in a final update.
Reason being is if it worked before, it'll work after once we fix any remaining issues on our end, and if you manually change things around, it's not going to work once we fix it, because for it to work, it needs to be how it used to be when it worked a few days ago. In the rare case that something has to change, you'll get an email.
@VirMach said: Reason being is if it worked before, it'll work after once we fix any remaining issues on our end, and if you manually change things around, it's not going to work once we fix it, because for it to work, it needs to be how it used to be when it worked a few days ago. In the rare case that something has to change, you'll get an email
Comments
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 my new no maintenance policy prohibits it as I’d like to have the option to leave the facility today.
Second error means you have to do it manually. Open a ticket but use the troubleshooter option if it’s available aka don’t do priority, that’s being spammed right now. Don’t mention maintenance or LAX in the title. Actually just give me the ticket ID.
If it’s not internal to the VPS then I’m aware of a few secondary blocks that need fixing.
Downgraded you mean?
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
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.
Def an upgrade.
We used to live in a 3-story.
Nowadays we live in a studio apartment.
Cleaning is so much easier.
No hostname left!
FYI - I can access VPS on LAXA031 via VNC, VPS is running.
No network. can't ping the gateway .129, can't ping 1.1.1.1. "Destination Host unreachable".
Reconfigure network does not solve. Manual check of network inside VPS looks good. BGP has not changed since the 24th.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
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 making plenty of other mistakes.
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
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.
Okay everything should be good (enough to leave and deal with remotely)
Great!
It's time to start working on the offers for users affected by the outage: huge compensation, free configuration upgrades, free migrations, endless ipv6 and a coupon.
Have the honor of being the crybaby who pays $20 for a 128MB VPS at VirMach in 2023.
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.
Build some custom rack slots under your mattress and you can get rid of your electric blanket...
QuickPacket - Dedicated Servers in Ashburn, Los Angeles, Chicago
I have been trying to turn on one of my VPSes in LAX1Z014 but it only shows "Powered off" after pressing the "On" button. I already did the troubleshoot steps (there's no ISO attached to the VPS, changed the boot order, rescue mode does not work, connecting to the VNC only shows "authentication failed", even changing the VNC password and force power off and on again does not let me connect to the VNC). Should I submit a non-emergency ticket or I wait a little bit longer?
You probably saw me somewhere...
@FrankZ Thanks for fixing everything!!!1111 Best support evr.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
Also thanks @VirMach & @qps for helping boss man fix everything.
@virmach where is the 1200GB NVMe server?
You know what would be better? A server with a couple of 2TB NVMe drives. The nearest to Dallas, the better.
Debían, thx
Since when? @FrankZ
Virmach Deals
...nevermind, I can't even make a ticket:
You probably saw me somewhere...
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
anyway to know what node my VM was on (its now down)
The IP is 141.11.92.xxx
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
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 ready yet. So to answer your question, no. Also not that it'd help you at this point anyway.
I'm not a fan of the spam either, but just to point out, this isn't an offer thread.
I'm assuming it got moved here from the other thread.
For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add
You can directly go to the CP from service list
Virmach Deals
Got it, its on LAXA006
Thanks!
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
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 is almost no reason to reconfigure networking within your VPS as a result of the migration.
I'm exhausted so muscle memory kicked in and I've been looking at tickets where a lot of people are doing this, and I even did it myself, definitely don't do it. Nothing good will come of it. I'm going to add that to the status page in a final update.
Reason being is if it worked before, it'll work after once we fix any remaining issues on our end, and if you manually change things around, it's not going to work once we fix it, because for it to work, it needs to be how it used to be when it worked a few days ago. In the rare case that something has to change, you'll get an email.
Understood
Virmach Deals
My VM on LAXA006 came back up. Gotta say - PREM NETWORK.
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC