@Neoon said:
Any update on DALZ009? Still on Private IP range.
Not sure what you mean by that, on my end the /24 is functional and previous issue(s) corrected. I actually fully forgot what happened with this one, my brain can only store so much when it comes to literally everything breaking at some point but I did just check and verify every VM in DALZ009 has a correct IP assigned and random ones ping.
@Ny100k said:
Any update on NYCB013? Networking still not working.
Same thing here.
@atomi said:
Last night my Seattle VPS got migrate to Ryzen and it seems that finally everything went smoothly. Except its now in Frankfurt, Germany. I hope that there will be somekind of "relocate Ryzen"-button in near future since on my map Frankfurt is not very near of Seattle
Yeah that one I was like yikes I can't believe I'm moving Seattle to Frankfurt but I had to do it. Node had to be moved and there was no other place left for it because the shape was weird, by shape I mean the disk usage compared with IP usage. We'll definitely keep this one as a main focus for migrations once everything settles and make sure you can get back to the other end of the globe.
@tototo said:
For my VPS that can't login to SolusVM (always getting "Invalid vserverid or username" error when clicking "VPS Controll Panel" button), cn I open the ticket? But it's from the BF-SPECIAL-2020 offer and has been migrated to Ryzen.
(Edit) It's probably working perfectly except for logging in to SolusVM panel. I think the error has occurred before the move to Ryzen and I didn't receive any email when the VPS was activated.
Yeah error must have occurred in the past. You'd need a ticket for it and it's going to take a long time for us to get to it unfortunately at this stage. Open it in priority department as an emergency if you actually can't access it but it sounds like you can so otherwise you'll have to try to go without controls for a week or two. Again if it's important though, use priority, we won't bill you.
Yet my vm in NYCB013 is not working. Priority ticket created 2 weeks ago.
@VirMach
Just in case you weren't aware an Atlanta node appears to have gone down today. I don't have the node name as Solus is borked there but IP is in subnet 23.147.227.0
No problem for me as this is marked for cancellation and was only used when my other ATL node was down.
(DALZ007 Solus ISO only has TinyCore on it, so looks as though those replications are still stalling. Also, Rescue mode is inoperable - doesn't boot. Again, no rush, for me.)
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
@AlwaysSkint said: @VirMach
Just in case you weren't aware an Atlanta node appears to have gone down today. I don't have the node name as Solus is borked there but IP is in subnet 23.147.227.0
There was a notice on the status page about reconfiguring atlanta nodes a short time before your message, perhaps that? It's either that or you are on the same node as one of mine that disappeared this afternoon it shows according to monitoring
@Daevien said: It's either that or you are on the same node as one of mine that disappeared this afternoon..
Likely this.
Noticed at: 2022-07-19 19:09:37 (UTC+00:00)
As said, not an issue for me, as I just switched back to my original nameserver, which was idling.
Just took a look at the Virmach notice - ta. Looks as though my other ATL is at risk too. It's ns4, out of 6 though.
..currently re-configuring the network..
That should sort the steal out for everyone - so all good. We hope.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
@tototo said:
For my VPS that can't login to SolusVM (always getting "Invalid vserverid or username" error when clicking "VPS Controll Panel" button), cn I open the ticket? But it's from the BF-SPECIAL-2020 offer and has been migrated to Ryzen.
(Edit) It's probably working perfectly except for logging in to SolusVM panel. I think the error has occurred before the move to Ryzen and I didn't receive any email when the VPS was activated.
Yeah error must have occurred in the past. You'd need a ticket for it and it's going to take a long time for us to get to it unfortunately at this stage. Open it in priority department as an emergency if you actually can't access it but it sounds like you can so otherwise you'll have to try to go without controls for a week or two. Again if it's important though, use priority, we won't bill you.
Literally two weeks ago, I realized I couldn't log in, but I didn't have any problems. From another point of view, I may never have been in trouble since last October. So I would like to open a ticket at a later date with normal priority.
@VirMach said: I'd scream at CC but I've given up on that. They placed a permanent nullroute on the main IP. This is probably the 30th time they've done this, from a single website being malicious. I'm trying to get a server up and just move it at this point.
Ah I see, well I have about a zillion idle VPS so I'll just move the site to one of them. Thanks for the explanation. I'm losing millions!!!! Well not really, heh.
@Neoon said:
Any update on DALZ009? Still on Private IP range.
Not sure what you mean by that, on my end the /24 is functional and previous issue(s) corrected. I actually fully forgot what happened with this one, my brain can only store so much when it comes to literally everything breaking at some point but I did just check and verify every VM in DALZ009 has a correct IP assigned and random ones ping.
Forgive me.
The first time I checked it, the Subnet had no route, likely was not announced + the IP started with 172. and someone mentioned some private IP addresses prior.
But the Subnet was just not announced, which it is now, and actually its not in the Private Range.
SEAZ008 finally back up, god that took a long time. DC hands plugged in IPMI to LAN and LAN to IPMI, finally corrected. A lot of others have been fixed as well, all of Atlanta (DC hands gave the port numbers in reverse order) and all of NYC by now except NYCB036., SJCZ004 as well, and looking at the rest now.
@netrix said:
LAXA014 need Ryzen to Ryzen migrate button so we could move our VPS to different nodes.
LAXA014 still having recurring reboot if VPS in use.
We completed PSU swap here, so we have to see what's wrong at this point. It's just shutting off and not throwing out kernel errors so what's left that could be possible I can think of is CPU suddenly overheating or loose cables elsewhere.
Thank you for SEAZ008 I appreciate that one.
Just a FYI. There may still be an issue with NYCM101. Billing panel times out, and there have been a couple of reports of no access (ssh ping). My VM on this node has been down since 07-18 14:02 although I am redundant in NYC so no big deal for me .
@gogogo said:
Hi. @VirMach, The VM at DALZ007 has been offline for more than 3 weeks.when will it be repaired. Or help me migrate it to different nodes?
Thank you for SEAZ008 I appreciate that one.
Just a FYI. There may still be an issue with NYCM101. Billing panel times out, and there have been a couple of reports of no access (ssh ping). My VM on this node has been down since 07-18 14:02 although I am redundant in NYC so no big deal for me .
It's been renamed to NYCB036 and I've been painfully aware of it being down. I have no access to IPMI and no one seems to care. I've mentioned it at least 4 times and it hasn't even been marked as request put in to the DC yet. Also marked on a problem sheet and specifically marked as having customers on it and therefore higher priority.
It could very well be another case of DC hands doesn't know the difference between IPMI and LAN ports but we'll eventually see.
Out of curiosity only, what does it say when you press Troubleshoot?
If you contact support, provide debug data:
Main IP pings: true
Node Online: false
Service online: online
Operating System: linux-debian-11-x86_64-legacy-gen2-v1
Service Status:Active
Registration Date:2020-12-08
@gogogo said:
Hi. @VirMach, The VM at DALZ007 has been offline for more than 3 weeks.when will it be repaired. Or help me migrate it to different nodes?
@gogogo
That's the same tiny VPS that I have. What's with Ubuntu? Don't even think about it!
At best, you're looking at debian 8, with that limited RAM - perhaps if lucky, a later version. I gave Alamalinux 8 a shot just to check for template issues, but didn't really expect that to boot.
The "complete" suite of ISO is unavailable to this node, so netboot.xyz isn't an option for now and the only one, TinyCore isn't booting either.
I've created a debian 8 img file to try out but can't due to Rescue not booting, which is strange.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
@gogogo said: I tried everything, reboot, shutdown, reinstall, rescue. But always offline. then can you tell me what should i do?
@AlwaysSkint is probably correct about the lack of memory and Ubuntu 20.04 being an issue. I am working with someone on the OGF with the same problem on DALZ007, also with an Ubuntu 20.04 ISO install, on a larger VPS. Originally purchased as Ryzen, never migrated, worked fine from April to July 5th when it went down and has never booted since. The node is confirmed up as other people have confirmed working VMs on DALZ007, and VirMach has confirmed it here. Same symptoms as you, reboot, shutdown, no ISO mounted, etc, stays offline. If we figure anything out I'll let you know.
My Dallas 512mb VPS didn't work with Debian either (every time I did an upgrade, it lost the boot drive and wouldn't reboot). Centos 8 Stream install didn't work for me so I installed Centos 8 and manually upgraded it to Centos 8 Stream and it's been up for 7 days now.
@AlwaysSkint said: @gogogo
That's the same tiny VPS that I have. What's with Ubuntu? Don't even think about it!
At best, you're looking at debian 8, with that limited RAM - perhaps if lucky, a later version. I gave Alamalinux 8 a shot just to check for template issues, but didn't really expect that to boot.
The "complete" suite of ISO is unavailable to this node, so netboot.xyz isn't an option for now and the only one, TinyCore isn't booting either.
I've created a debian 8 img file to try out but can't due to Rescue not booting, which is strange.
so，The only thing left to do was to wait for @VirMach 's help
@gogogo said: I tried everything, reboot, shutdown, reinstall, rescue. But always offline. then can you tell me what should i do?
@AlwaysSkint is probably correct about the lack of memory and Ubuntu 20.04 being an issue. I am working with someone on the OGF with the same problem on DALZ007, also with an Ubuntu 20.04 ISO install, on a larger VPS. Originally purchased as Ryzen, never migrated, worked fine from April to July 5th when it went down and has never booted since. The node is confirmed up as other people have confirmed working VMs on DALZ007, and VirMach has confirmed it here. Same symptoms as you, reboot, shutdown, no ISO mounted, etc, stays offline. If we figure anything out I'll let you know.
@gogogo - I made a mistake on the node ID it was DALZ004 not DALZ007, but we ended up in the same place as you, not booting no matter what we tried. Guess we are just going to have to wait on VirMach to fix these. Like he said above it is in the queue. Hope you get going soon™
Comments
Yet my vm in NYCB013 is not working. Priority ticket created 2 weeks ago.
@VirMach
Just in case you weren't aware an Atlanta node appears to have gone down today. I don't have the node name as Solus is borked there but IP is in subnet 23.147.227.0
No problem for me as this is marked for cancellation and was only used when my other ATL node was down.
(DALZ007 Solus ISO only has TinyCore on it, so looks as though those replications are still stalling. Also, Rescue mode is inoperable - doesn't boot. Again, no rush, for me.)
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
There was a notice on the status page about reconfiguring atlanta nodes a short time before your message, perhaps that? It's either that or you are on the same node as one of mine that disappeared this afternoon it shows according to monitoring
Likely this.
As said, not an issue for me, as I just switched back to my original nameserver, which was idling.
Just took a look at the Virmach notice - ta. Looks as though my other ATL is at risk too. It's ns4, out of 6 though.
That should sort the steal out for everyone - so all good. We hope.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Literally two weeks ago, I realized I couldn't log in, but I didn't have any problems. From another point of view, I may never have been in trouble since last October. So I would like to open a ticket at a later date with normal priority.
Ah I see, well I have about a zillion idle VPS so I'll just move the site to one of them. Thanks for the explanation. I'm losing millions!!!! Well not really, heh.
Forgive me.
The first time I checked it, the Subnet had no route, likely was not announced + the IP started with 172. and someone mentioned some private IP addresses prior.
But the Subnet was just not announced, which it is now, and actually its not in the Private Range.
Free NAT KVM | Free NAT LXC
SEAZ008 finally back up, god that took a long time. DC hands plugged in IPMI to LAN and LAN to IPMI, finally corrected. A lot of others have been fixed as well, all of Atlanta (DC hands gave the port numbers in reverse order) and all of NYC by now except NYCB036., SJCZ004 as well, and looking at the rest now.
LAXA014 need Ryzen to Ryzen migrate button so we could move our VPS to different nodes.
LAXA014 still having recurring reboot if VPS in use.
dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/
Anyone else having intermittent packet loss on LAXA031 node?
We completed PSU swap here, so we have to see what's wrong at this point. It's just shutting off and not throwing out kernel errors so what's left that could be possible I can think of is CPU suddenly overheating or loose cables elsewhere.
Thank you for SEAZ008 I appreciate that one.
Just a FYI. There may still be an issue with NYCM101. Billing panel times out, and there have been a couple of reports of no access (ssh ping). My VM on this node has been down since 07-18 14:02 although I am redundant in NYC so no big deal for me .
LES • About • Donate • Rules • Support
Hi. @VirMach, The VM at DALZ007 has been offline for more than 3 weeks.when will it be repaired. Or help me migrate it to different nodes?
04:40:12 up 6 days, 4:12, 1 user, load average: 8.04, 8.25, 7.43
It's been renamed to NYCB036 and I've been painfully aware of it being down. I have no access to IPMI and no one seems to care. I've mentioned it at least 4 times and it hasn't even been marked as request put in to the DC yet. Also marked on a problem sheet and specifically marked as having customers on it and therefore higher priority.
It could very well be another case of DC hands doesn't know the difference between IPMI and LAN ports but we'll eventually see.
.
Understandable, from both sides, though I concur that DALZ007 has been inoperable for weeks now.
Won't even respond to a Rescue boot up. :-/
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Weird. My VPS is Dallas is on DALZ007 ... working fine.
Out of curiosity only, what does it say when you press Troubleshoot?
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
If you contact support, provide debug data:
Main IP pings: true
Node Online: false
Service online: online
Operating System: linux-debian-11-x86_64-legacy-gen2-v1
Service Status:Active
Registration Date:2020-12-08
Just an FYI this does not seem to work correctly on Ryzen nodes. I get the same "Node Online: false" on perfectly good, working VMs.
LES • About • Donate • Rules • Support
Thought as much.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
I tried everything, reboot, shutdown, reinstall, rescue. But always offline. then can you tell me what should i do?
@gogogo
That's the same tiny VPS that I have. What's with Ubuntu? Don't even think about it!
At best, you're looking at debian 8, with that limited RAM - perhaps if lucky, a later version. I gave Alamalinux 8 a shot just to check for template issues, but didn't really expect that to boot.
The "complete" suite of ISO is unavailable to this node, so netboot.xyz isn't an option for now and the only one, TinyCore isn't booting either.
I've created a debian 8 img file to try out but can't due to Rescue not booting, which is strange.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
There's about 3-5% of the VMs offline, but the node as a whole isn't. Those are on our queue.
@AlwaysSkint is probably correct about the lack of memory and Ubuntu 20.04 being an issue. I am working with someone on the OGF with the same problem on DALZ007, also with an Ubuntu 20.04 ISO install, on a larger VPS. Originally purchased as Ryzen, never migrated, worked fine from April to July 5th when it went down and has never booted since. The node is confirmed up as other people have confirmed working VMs on DALZ007, and VirMach has confirmed it here. Same symptoms as you, reboot, shutdown, no ISO mounted, etc, stays offline. If we figure anything out I'll let you know.
Node: DALZ007 id: 659218
LES • About • Donate • Rules • Support
My Dallas 512mb VPS didn't work with Debian either (every time I did an upgrade, it lost the boot drive and wouldn't reboot). Centos 8 Stream install didn't work for me so I installed Centos 8 and manually upgraded it to Centos 8 Stream and it's been up for 7 days now.
so，The only thing left to do was to wait for @VirMach 's help
thanks.
@gogogo - I made a mistake on the node ID it was DALZ004 not DALZ007, but we ended up in the same place as you, not booting no matter what we tried. Guess we are just going to have to wait on VirMach to fix these. Like he said above it is in the queue. Hope you get going soon™
LES • About • Donate • Rules • Support