Portal Home > Knowledgebase > Articles Database > Spartan host or SolusVM won't fix IP's down for 6 hours


Spartan host or SolusVM won't fix IP's down for 6 hours




Posted by hostcadet, 11-30-2016, 09:40 AM
Ok I have several thousand IP's on SolusVM on one container it quit working after months of working. These are announced IP's that I leased from LeasWeb. Now what I did wrong because I assumed when they put the IP's on there were purchased in 500 blocks. I didn't know about the shared gateway for both. But worked anyway before but on one range I can get certain IP's to work that won't create a container with the ips no ip listed for it. 355 18 running - test.test.test When adding one of the ip of one not working but others in that range working it only has the loopback ip in ifconfig in console. Even with the updated settings not working. Both blame the other SolusVM said its nothing to do with it. Any help would be awesome thanks

Posted by hostcadet, 11-30-2016, 03:04 PM
Well datacenter went over everything and its maybe a SolusVM because its just keep ips assinged to old containers but with vzlist -a doesn't show them any more. The IP's assign to the wrong container. I have been down like 8 hours and can't even get the SolusVM to help with more than a few words of advise. Asked him to escalate it he refuses

Posted by Afterburst-Jack, 11-30-2016, 03:27 PM
I don't think you'll get any useful replies without more details -- e.g. IPv4 or IPv6? Perhaps post your network configuration (even change your IPs to placeholders if you want; as long as its consistent so people can understand your config)

Posted by hostcadet, 11-30-2016, 03:35 PM
Ok here is what I do. I sell proxies and have thousands of IP's each container get's lots of IP's on it. What I noticed first was that when deleting containers in SolusVM control panel it kept not removing it and I would manually remove. Now because it keeps doing this like IP's that clearly show in the control panel assigned to one vps with 220 IP's but I ssh to some of the IP's on there I get to a machine that shows like 950 IP's now that machine was scaled back to 600 IP's but it shows 950 like before. I verified it in control panel and its 600 there too. On one of the containers when restarting normally it will show the IP's being assigned it won't show any at all. Thanks so much

Posted by Afterburst-Jack, 11-30-2016, 03:37 PM
OpenVZ? KVM? IPv4 or V6? Did you check in the container configuration file to see if the right number of IPs are listed? Edit: If its the bug with solusvm where a OpenVZ VPS doesn't get deleted when you delete from solusvm; you'll need to recreate the network configuration on the new VPS (that tried to use the IPs previously used by a "ghost" VPS ) after deleting/disabling the ghost VPS , and then reboot the new VPS.

Posted by hostcadet, 11-30-2016, 03:42 PM
Thanks it's OPenVZ and IPv4. Not sure how to check that I did get this just tried it grep -irl '196.52.xx.xx' /etc/vz/conf/ /etc/vz/conf/301.conf /etc/vz/conf/255.conf.destroyed /etc/vz/conf/ve-301.conf-sample /etc/vz/conf/345.conf /etc/vz/conf/248.conf.destroyed

Posted by Afterburst-Jack, 11-30-2016, 03:43 PM
If both CTID 301 and 345 are online at the same time you'll have problems. Check in solus to see if both are meant to exist or not

Posted by hostcadet, 11-30-2016, 04:09 PM
Ok awesome I removed it now so there is just one but can't ssh into it or was it listed when it listed the ips when I restart 345 # grep -irl '196.52.36.23' /etc/vz/conf/ /etc/vz/conf/255.conf.destroyed /etc/vz/conf/ve-301.conf-sample /etc/vz/conf/301.conf.destroyed /etc/vz/conf/345.conf /etc/vz/conf/248.conf.destroyed [root@tx ~]#

Posted by Afterburst-Jack, 11-30-2016, 04:13 PM
Do you get any warnings when running vzctl start on the problematic container (from offline)?

Posted by hostcadet, 11-30-2016, 04:19 PM
No it starts without errors but like one issue is that in that .36.0 range most of it won't work on containers it was assigned to and working before. But like the last 25 are assigned and working ok ssh into correct one. Thanks

Posted by Afterburst-Jack, 11-30-2016, 04:20 PM
Did you check the IPs that got warnings in the config directory to see if they are assigned to any other VPS?

Posted by hostcadet, 11-30-2016, 04:23 PM
Awesome I think I got it after your help for sure I just removed them in the control panel and added it back and now it works!!! OMG you have made my whole day!!

Posted by Afterburst-Jack, 11-30-2016, 04:25 PM
Glad its sorted



Was this answer helpful?

Add to Favourites Add to Favourites    Print this Article Print this Article

Also Read
latency issues @ NAC? (Views: 637)
.htaccess url rewrite (Views: 580)