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
LAXA024 isn't actually down, it's just bugged on the panel. I keep not having time to look over it but I do temporary fix in bursts which isn't the solution, sorry for it taking so long.
LAXA014 actually requires maintenance. I think it's the power supply slowly dying or loose cable somewhere. Of course it could also be the motherboard as it's exhibiting some weird behaviors related to memory errors (not actual memory errors, just the same behavior.) We already did a RAM swap on it and it was stable afterward, I'll probably do another RAM swap since it's easy and check for loose cables and swap out the PSU. Was supposed to send a maintenance email earlier today, at this point unless it goes down again I'm going to wait until I have a more specific time available to assign for it so it's not just some vague and unhelpful email.
@VirMach is that ok to use vm's in Lax now? Nodes 30 and 31 yet have problems, cannot reach default gateway, and unable to boot using iso.
Phoenix has its own weird networking issue. It's the only location that has the ebtables working and in fact if ebtables is taken off it reacts the same way all others do when it's turned on. And it's unable to use the optimized network configuration.
Haven't had a chance to look into it but probably points to an older kernel and/or older SolusVM version.
@VirMach
Gonna appeal but yea, not expecting it coming back up since it has been down for past couple of days
Come to think of it, I remember encountering such a issue. I forgot about it because it was quickly resolved by @FrankZ's tutorial or something. However, I did not encounter any major issues, so I lost the opportunity to write a tutorial for it
Update on FFME004 ?
Try reconfiguring again, for some reason reconfigurations on this node probably failed when they were being done, I see only a very few number of them as working but they're definitely working and they all have the same configuration.
What kind of update?
@VirMach
The node RYZE.DAL-Z008.VMS default gateway cannot ping through,so the vps.
3/4 of my vps is online now, all 3 vps give a new ip,but one of then in blacklisted...my I have a chance for a free change?
What is a blacklist?
I just checked Node 31(LAXA031). reconfiguration didn't help. Still have access to the server on VNC, but no link to outside world and no response to ping.
Can you please check on that again? they appear to be online but no access from the outside.
It's alive! LAXA031 is back online, just got notification from NetData! Thanks VirMach.
@tototo
A new IP assigned to my vps after migration and a ticket opened for me(I guess it was gen by the system)
Please visit the link above for more information on how to remove your IP from the blacklist.
Offline for half a month.....Offline for half a month.....Offline for half a month.....#233805
My VMs in FFME005 & FFME006 are still getting the "no bootable device" error
Can you try restart your vps with an iso mounted? mine wont turn on this way.
That mean either the ISO haven't synced yet, or there's other issues with ISO.
You might have luck using the netboot.xyz system for now.
Status Update, it's still down.
My VPS at LAXA031 has restored connectivity but reinstalling does not currently work. Seems like they also removed a bunch of the non-Ryzen compatible images from the SolusVM control pnel.
Yeah, it didn't boot. Only TinyCore ISO is available there in Solus. It came right back online once I unmounted the ISO.
Here's YABS for the VM:
Ticket #380625
Oh so this is where those 5950X ended.
Huh? Only? Is this running in some eco mode or something?
I notice that the announcement about LAKVM9 was deleted. But my server at LAKVM9 can't still be connected by ssh or vnc. And the service page of my server shows
Operation Timed Out After 90001 Milliseconds With 0 Bytes Received. Should I open a ticket?Its up for me for past 2 days. Try unmounting ISO and see if u get anything on VNC as you might have network fucked up.
thanks @VirMach all good now. vps assigned 2 ip address, the old one no internet, new one does.
really ? are you sure it's ffme004 ? I can't even access the service from clientarea
ffme004 same here: Operation timed out
FFME02 is up and running after almost 2 weeks downtime
Still won't trust this with my data but it's online at least
Ffme003 same
involucrated after reboot.
@VirMach my VPS on NYCB019 just keeps alternating between an unbootable disk and the whole server info page timing out on an hourly basis (ever since the migration started).
Do you have any info on this? How long is it gonna take to sort out?