All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Network issue I've never seen before
Hello LET,
I have an OVZ VPS with CentOS 6 32bit at a unnamed provider that has been reliable and without issue to date. Yesterday the VPS went offline and was not accessible, even by VNC through SolusVM. This evening it is contactable through SolusVM VNC and the VPS looks completely intact. Including all network configuration. Problem is I have no networking at all.
IP route shows nothing ""
ifconfig shows nothing ""
restarting the VPS does not change things.
and a network restart shows this
/etc/init.d/network restart
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: RTNETLINK answers: Operation not supported
Failed to bring up lo. [FAILED]
Bringing up interface venet0: RTNETLINK answers: Operation not supported
Failed to bring up venet0. [FAILED]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Nothing has been changed on the VPS in about a month, and it was restarted afterwards. I submitted a ticket yesterday, but have not received a response from the provider yet and have other things to do, so any guidance would be appreciated.
Comments
You need to do venet0:0 but i suppose this is updated to centos 6.5 and you hit the bug.
ok you have auto update on and your vps was updated to centos 6.5
this is knowen issue which was explained here with solution
http://www.webhostingtalk.com/showthread.php?t=1327600
thank the wht thread poster for his effort
Thanks
@Maounique - Is it the CentOS 6.5 container on CentOS 5 Node bug that you are speaking of?
Or something I can correct from the container?
We have a similar thread by rds100 here. I couldnt find it, but here it is another one:
http://lowendtalk.com/discussion/17646/centos-6-5-released
@Hani - looks like it. Thanks.... Looks like I have 15 containers to update before they crash.
EDIT: Should be interesting to fix with no networking on the down container
It does not crash if you do not update it, it means you had some autoupdate of sorts.
@Maounique - "it means you had some autoupdate of sorts" - I did
Rule of thumb:
Do not put anything on autoupdate if in production/critical. If it is that important will probably be worth some supervision during this delicate process.
Besides, the eye of the owner makes the cow give more milk. It does not hurt to visit it from time to time, you might notice things that otherwise would escape, such as problems with backups or signs of intrusion.
Mao - Good advice
Solved, thread can be closed. Thanks everyone.
mistake
What?
It's a saying here.
Ochiul stapanului ingrasa vita.
It means literally: The eye of the owner fattens the cow. If you keep an eye on things, they go better.