| Virtual Servers won't start [message #39955] |
Wed, 30 June 2010 20:30  |
mperkel
Messages: 253
Registered: December 2006
|
Senior Member |
|
|
Not sure what is going on but just upgraded using yum and when I restart the vz service it fails to start and VEs. I don't dare shut down what is currently running because I'd be out of business.
Bringing down interface venet0: [ OK ]
Stopping OpenVZ: [ OK ]
Starting OpenVZ: [ OK ]
Bringing up interface venet0: [ OK ]
Starting CT 115: [FAILED]
Starting CT 135: [FAILED]
vzctl says:
2010-06-30T13:19:45-0700 vzctl : Setting CPU units: 1000
2010-06-30T13:19:45-0700 vzctl : WARNING: Settings were not saved and will be reset to original values at the next start (use --save flag)
2010-06-30T13:20:01-0700 venetclean : CT 115 : CT died, clear IPs:
Not sure what to do but starting to freak out.
Junk Email Filter
http://www.junkemailfilter.com
|
|
|
|
|
|
|
|
|
|
| Re: Virtual Servers won't start [message #39982 is a reply to message #39971] |
Fri, 02 July 2010 13:31  |
maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
|
Senior Member |
|
|
Dear Marc,
I've been trying to find out the reason but unfortunately I couldn't. Here some details that might be useful:
-
| Quote: |
vzctl says:
2010-06-30T13:19:45-0700 vzctl : Setting CPU units: 1000
2010-06-30T13:19:45-0700 vzctl : WARNING: Settings were not saved and will be reset to original values at the next start (use --save flag)
2010-06-30T13:20:01-0700 venetclean : CT 115 : CT died, clear IPs:
|
Did the last message appear at the same moment as "service vz restart" was issued? May it appear earlier?
-
| Quote: |
venetclean : CT 115 : CT died, clear IPs:
|
This message may appear when "vpsnetclean" script is running. This script is scheduled in /etc/cron.d/vz but I don't know what can break the starting process. Here are information about changes in this script:
http:// git.openvz.org/?p=vzctl;a=history;f=scripts/vpsnetclean.in;h b=d50cdb66e59945a46b57e94642ac2c3b72080448
-
I was able to reproduce "CT died" message but wasn't able to reproduce your problem.
Nevertheless, we know that the problem appears when /etc/init.d/vz was invoked. So I'd recommend you to verbose
"vzctl start ..." output (/etc/init.t/vz - 415 line)
fi
msg=`$VZCTL start ${veid} 2>&1`
print_result "$msg"
Please, set VERBOSE and LOG_LEVEL to 10 in /etc/vz/vz.conf.
If it doesn't help it may be useful to get the previous "msg" value.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
