YardVPS down?

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > YardVPS down?

Posted by Daniel15, 11-30-2011, 05:36 AM
My VPS on node "shaggy" is down (and has been for a day now). Anyone else encountering the same issue? I've contacted support but haven't heard back yet.
Posted by Profuse-Jimmy, 11-30-2011, 05:44 AM
No reported outages here.
Posted by Daniel15, 11-30-2011, 06:16 AM
Interesting... I opened a ticket about it (#NOF-950021). I can see the VPS in SolusVM but clicking the boot button doesn't do anything.
Posted by lovelycesar, 12-04-2011, 12:37 PM
@Daniel15: the same for me
Posted by lovelycesar, 12-05-2011, 06:34 AM
As they said, my VPS was crashed. How was it crashed? I could not boot/reboot, even reload OS. If my system was crashed, I could reload new OS smoothly. I don't think they see the issue, just advise me to rebuild OS -but I have no mean to do that.
Posted by FinerTech, 12-05-2011, 05:26 PM

Quote:

Originally Posted by lovelycesar

As they said, my VPS was crashed. How was it crashed? I could not boot/reboot, even reload OS. If my system was crashed, I could reload new OS smoothly. I don't think they see the issue, just advise me to rebuild OS -but I have no mean to do that.

If a VM crashes a few things could happen depending on the setup of the NODE, what type of Virtual Machine (VZ, Xen, KVM, Cloud) whatever, they have ways of crashing that would prevent any use of the virtual machine until the node is smacked around a bit, and the container is refreshed and spun backup, it could be locked down, or corrupted to where the system locks and won't allow you to activate any functions.

They could of also meant the node crashed and if that is the case every option for the virtual server would not be working, as if the node is down everything is down, including all virtual machines on it.

But I do understand what your saying, but saying the Virtual Machine crashed (if this is really what happen) 99% of the time it would not corrupt your disk/hdd causing you to have to rebuild/reload your operating system from scratch. It seems there was a issue on their side that they are hiding some how, or some reason. (I could be wrong, as I don't know the exact reasons), but from over looking yardvps from previous years and learning a few things from reading reviews and topics about them here and their affiliate sites and such, it seems they have a road of bad luck sometimes and their excuses they use don't always make sense with what happen during that period.

Good luck,
How is the overall performance and reliability of the server besides for this issue/outage? Do this occur more then once or on a daily basis? I was reading some feed back from lowendtalk (or box) and a client was talking about his virtual machine crashing, and having periods of 1-5 hr downtime for almost 1 week straight and they blamed it on the client, when the client showed proof that he had just ordered the virtual machine two weeks prior and did not one thing with it besides ran some tests as he's the Admin of a VPSReviews Blog, sorta like lowendbox but he purchases the services or gets them donated to have a free review and advertisement placed on his blog/community and well the only other thing the guy ever did on his virtual machine was reload the os by their request to fix the issue and then after he did that it caused it go up & down even more, with them blaming it on him for his "use", and terminated him for "abuse", when all he did was a few bench marks, stress tests, ping/wget on testfiles and so on for his review. I still have that review booked marked from his website!

But, even with that... I believe they later resolved the issue and credited them, but that is the only bad information I have about them otherwise, they've looked like they updated alot of things and overall upgraded the service they provide and are doing much better.

I personally, don't have no personal experience. But crashing and having to reload the OS seems strange to me unless the crash of the node corrupted the container ID's allocated disk.3

-D