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.
IPXCore
This discussion has been closed.
Comments
Still going strong for me.
19:32:12 up 12:03, 1 user, load average: 0.07, 0.02, 0.00
By the way, Sapphire is back up.
198.144.190.2 wasn't working... Which is sapphire.
May as well consider solus to be down at the moment. @Damian is getting a few hours of much deserved rest... Should be back later on and will undoubtedly get to some of these issues identified
Make sense, thanks a lot!
Yea, I've got a few things for @Damian too
He deserves a rest though - let him have it!
Exactly, that's why I do not want to bug him now. Thanks a lot for the input
It looks as if it works, but the I.P and Solus do not sync yet.
If you press anything, like reboot, boot, reinstall, etc, it will turn vps off.
It seems to be back up, attempt to connect again.
Sapphire keeps going up and down and I keep getting memory resource allocation errors so I dunno what's going on.
I'm sure @Damian will have an explanation when he wakes up.
There's periodic, short network timeouts. The node itself has been up for ~12 hours.
Someone DDOSing 50 cents VPS? LOL
I'm alive!
1: Reinstalling OS is completely broken at this point, because /vz/template/cache on every node is a symlink to /carbon/ostemplate/, of which /carbon is still in Phoenix. Fixing this is high on my list of things to do today.
2: I'm not showing that Sapphire is truly going down:
..and i've been connected to it via SSH this whole time. On the other hand, I'm seeing plenty of notification from Pingdom that it's unreachable for about 3 minutes every hour or so, so I'll look into it.
3: There may be some issues with containers starting. There's about 15 tickets in WHMCS about this so far, so i'm going to tackle those. If your container isn't starting properly, please submit a support ticket; otherwise I may miss your posting here.
4: Individual containers connection's will be limited to 100mbit, as that was part of our agreement with Chris. Plus that's what we've always advertised, so not a big change there. IRC will still be available though.
5: Chris provisioned our next /24 block of IPs, so I'll be adding those last 85 soon (if you were unlucky enough to be in that group)
Yep, it's just network issues. Still having trouble with memory allocation though, I wonder if everyone is apt-getting at the same time.
@Victor I have no problems with transfer in San Diego... who was your provider
@Damian -- Thanks for the reply! Please send an e-mail once you've resolved the reinstallation.
+1
Network has been stable (for me at least) for the last 2 hours. Well done
Anyone else concur on this?
Things are up, but not working 100% correctly yet. For example, you can buy a VPS, but OS install would fail. Still working on that one...
Seems stable atm...
It is stable, but I.P does not sync with Solus yet.
For me, everything looks fine in SolusVM. IP, memory usage, swap, disk usage all correlate with what I see inside the VM.
507 comments so far. I wonder if this is the longest thread on LET yet?
+1
@sleddog: Excellent. In typical fashion, VPS containers are either working 100% properly, or are 100% completely broken. Fortunately, there's not very many that are completely broken...
Nope the WHMCS hacked thread has 700+
And is mineeee Muahahaha! Ok, just trolling.
Yes, stable here n_n
@Jack Hit reboot, see if it reboots or destroy you vps.
Your ordering system is broken, it says No stock.
You need to fix that
i don't think he's accepting orders yet