#26 2017-05-16 22:55:45

rcomputer
Trusted Member
Registered: 2015-04-21
Posts: 7

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Thank you Thank you Anthony for this (ridiculously cheap) service. I have nothing novel on my 'machine' and just value its remote cycles - so a clean slate is fine for me (anyone who does not have a backup - just get two machines and mirror them?). IRC was so '90s and like X25 (and FTP) from that time - now well past its time.

Again THANK YOU

Julian Robinson

Offline

#27 2017-05-17 05:02:29

manjana
Trusted Member
Registered: 2015-11-23
Posts: 105

Re: Phoenix (used to be Dallas) issues [RESOLVED]

rcomputer wrote:

IRC was so '90s

Hope you are aware that you just opened Pandora's box.

@WSS Your turn.

Offline

#28 2017-05-17 07:27:55

PeterL
Trusted Member
Registered: 2014-06-03
Posts: 30

Re: Phoenix (used to be Dallas) issues [RESOLVED]

I'm really sorry to hear solus completely crapped the server. I personally appreciate everything you do for such a ridiculously cheap service.

I'm with @WSS on this, build up the core service and fire off an email to everyone to say they have to rebuild their own VPSs.

It only takes one muppet to mess it up for everyone else sad. Hopefully it won't take too long to get it back online as you shouldn't have to do this in the first place.

Offline

#29 2017-05-17 10:11:36

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

I have access to some of the data but as I suspected it is a waste of time, its low-level recovery, they are badly out of order and I will not be sifting through 5 million+ files to sort them into their correct containers, so I wasted a day attempting recovery rather than going directly to rebuild.

I will try and have it up and running by the end of the day fresh.


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#30 2017-05-17 12:12:10

jinks
Member
Registered: 2017-05-17
Posts: 1

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Just to clarify, will IRC definitely be disabled when the VPSs come back up?

I got my LES box specifically for an IRC bouncer, even clarified that that was an acceptable use before purchase.

Znc is literally the only non-OS service running.

Offline

#31 2017-05-17 14:34:03

LivingSouL
Trusted Member
Registered: 2014-01-21
Posts: 39

Re: Phoenix (used to be Dallas) issues [RESOLVED]

jinks wrote:

Just to clarify, will IRC definitely be disabled when the VPSs come back up?

I got my LES box specifically for an IRC bouncer, even clarified that that was an acceptable use before purchase.

Znc is literally the only non-OS service running.

me too... maybe let's just wait and see

Offline

#32 2017-05-17 15:03:42

WSS
Trusted Member
Registered: 2016-12-22
Posts: 255

Re: Phoenix (used to be Dallas) issues [RESOLVED]

rcomputer wrote:

IRC was so '90s

Julian Robinson

Well, I know someone who is not getting a Christmas card this year.

jinks wrote:

Just to clarify, will IRC definitely be disabled when the VPSs come back up?

I got my LES box specifically for an IRC bouncer, even clarified that that was an acceptable use before purchase.

Znc is literally the only non-OS service running.

I hope you feel you got your few dollars worth of service.   Just tunnel it to another LES, and you won't need to move things.

Anthony went out of his way to get HE to allow IRC through on the IPv6; I doubt he's going to ask them to remove that-but I also doubt he's going to request any new space have those ports opened.


RbyeR4Nm.png

Offline

#33 2017-05-17 18:09:42

Bochi
Trusted Member
Registered: 2016-09-05
Posts: 48

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Backtogeek wrote:

I will try and have it up and running by the end of the day fresh.

Oh my...you're a beast! big_smile
So no possible hardware defect that could have contributed to the creeping filesystem error?

Offline

#34 2017-05-17 21:02:28

geppetto
Trusted Member
Registered: 2017-01-20
Posts: 8

Re: Phoenix (used to be Dallas) issues [RESOLVED]

We need a miracle here.. Understand.. hmm

Offline

#35 2017-05-17 21:28:44

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Well sadly things did not go to plan today, 101 other things happened that required immediate attention, 2 separate servers in 2 locations spat a disk out, the Netherlands OpenVZ (not LES) node got hit with a huge DDOS attack, and the ssd cache on the KVM LHC server started showing signs of failure so I had to get that swapped too.

It is always when you have something big to do that all these things happen, I must have been a terrible person in a past life.

I will try to have this done now by tomorrow afternoon.


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#36 2017-05-18 00:38:39

WSS
Trusted Member
Registered: 2016-12-22
Posts: 255

Re: Phoenix (used to be Dallas) issues [RESOLVED]

That's impressive.  Do you teleport to the datacenters?


RbyeR4Nm.png

Offline

#37 2017-05-18 01:12:40

AuroraZero
Slacker
From: Slacker Labs
Registered: 2017-04-01
Posts: 60
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

V31 wrote:
Backtogeek wrote:

You can be sure IRC will be blocked when it comes back up either way.

I've been using a vps on this node for over a year just for an IRC session (precisely, a personal quassel core).
How does IRC cause problems? Is it the spammers or irc hosts?
If you can, please consider at least whitelisting freenode. Thank you very much for all the effort put into this node.

The problem is not really irc itself it is the jackholes that are dick on irc and get a DDOS for their efforts. Once that happens it screws us all and therefor for the good of the rest of us it needs to be dealt with. Freenode or efnet makes no difference you will still get the jackholes and then the DDOS.


I have not had time to even set mine up yet so I am all good Ant. Take what ever time you need with mine and do what you have to brother. smile


The world is full of nuts.....Come join us. smile

Offline

#38 2017-05-18 06:43:04

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

WSS wrote:

That's impressive.  Do you teleport to the datacenters?

private jet mate.


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#39 2017-05-18 08:06:54

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

With any luck, things should be back up in around an hour, got an early start.


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#40 2017-05-18 09:25:31

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

90% of the way there just trying to find a way to trigger a regeneration of the config files


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#41 2017-05-18 09:44:17

manjana
Trusted Member
Registered: 2015-11-23
Posts: 105

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Backtogeek wrote:

90% of the way there just trying to find a way to trigger a regeneration of the config files

SolusVM has a (somewhat useable) API for users. Isn't there the same for admins? So you can iterate through the containers and recreate them?

Offline

#42 2017-05-18 10:15:10

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

manjana wrote:
Backtogeek wrote:

90% of the way there just trying to find a way to trigger a regeneration of the config files

SolusVM has a (somewhat useable) API for users. Isn't there the same for admins? So you can iterate through the containers and recreate them?

The problem with that is that they already exist in the solusvm database so I dont want to recreate them as such because then it would issue new vserverid's which in turn would mess up the whmcs side of things, with the API function it is an all or nothing thing.

Anyhoo solusvm kindly provided a 1 liner for just regenerating the config CTID.conf files on the host node which is running now so everyone should be ready to roll in about 2 minutes smile

Just login to solusvm as always and click reinstall and you should be good to go!

I will be double checking the iptables rules as I think I missed some forwarding and IPv6 will be enabled again later today.


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#43 2017-05-18 10:28:02

AlesioRFM
Trusted Member
Registered: 2017-01-21
Posts: 11

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Everything is working fine for me now

EDIT: apt-get update fails to connect

Last edited by AlesioRFM (2017-05-18 10:32:53)

Offline

#44 2017-05-18 10:34:34

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

AlesioRFM wrote:

Everything is working fine for me now

EDIT: apt-get update fails to connect

is it trying to use ipv6?


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#45 2017-05-18 10:43:03

manjana
Trusted Member
Registered: 2015-11-23
Posts: 105

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Great news, thanks Anthony! smile

Reinstall worked flawlessly using the Centos 6 image. /etc/resolv.conf was empty afterwards, so I had to add nameservers manually.

Offline

#46 2017-05-18 10:43:08

AlesioRFM
Trusted Member
Registered: 2017-01-21
Posts: 11

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Looks like it couldn't find a default dns server. I set the google one.

Offline

#47 2017-05-18 10:46:23

manjana
Trusted Member
Registered: 2015-11-23
Posts: 105

Re: Phoenix (used to be Dallas) issues [RESOLVED]

You might want to have a look at this, Anthony...

[[email protected] ~]# free -m
             total       used       free     shared    buffers     cached
Mem:       4194303          0    4194303          2          0          8
-/+ buffers/cache:    4194295          8
Swap:            0          0          0

Offline

#48 2017-05-18 11:05:47

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

Thanks, I have globally applied google dns to all containers now.

Will have a look at that ram reporting issue next and report back.


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#49 2017-05-18 11:17:02

Backtogeek
Low End Boss
From: ~/
Registered: 2013-02-13
Posts: 3,498
Website

Re: Phoenix (used to be Dallas) issues [RESOLVED]

I have set everyone's ram to 128mb for now, waiting for a response from solusvm as the wrong ram values were pulled from the solusvm database for some reason, I can use vzctl set in a loop but this will not persist a reinstall.

I am aware some people had 256MB and even 280MB in same cases, this is only temporary it will be fixed.


http://LittleHappyCloud.net KVM VPS with 1TB Bandwidth for €3.00

Offline

#50 2017-05-18 11:21:19

Bochi
Trusted Member
Registered: 2016-09-05
Posts: 48

Re: Phoenix (used to be Dallas) issues [RESOLVED]

I guess a later fix to the RAM issue won't trigger another full reset of the container? So, are we save to reinstall the machines? smile

Offline

Board footer