Differences between vzctl stop/start and restart? [message #30285] |
Tue, 20 May 2008 07:06 |
imknight
Messages: 15 Registered: January 2008
|
Junior Member |
|
|
Just wondering what the significant differences were between doing
vzctl stop
vzctl start
and
vzctl restart
On a server when i do the initial two it has no issues:
[root@node0 ~]# service vz stop
Shutting down VE 101
Bringing down interface venet0: [ OK ]
Stopping OpenVZ: [ OK ]
[root@node0 ~]# service vz start
Starting OpenVZ: [ OK ]
Bringing up interface venet0: [ OK ]
Configuring interface venet0: [ OK ]
Starting VE 101: [ OK ]
[root@node0 ~]#
But when doing a vzctl restart:
[root@node0 ~]# service vz restart
Shutting down VE 101
Bringing down interface venet0: [ OK ]
Stopping OpenVZ: [ OK ]
/etc/init.d/vz: line 200: echo: write error: Broken pipe
/etc/init.d/vz: line 200: echo: write error: Broken pipe
Starting OpenVZ: [ OK ]
Bringing up interface venet0: [ OK ]
Configuring interface venet0: [ OK ]
Starting VE 101: [ OK ]
[root@node0 ~]#
Are these 'Broken pipe' errors anything to worry about?
197 conf="`zcat /proc/config.gz 2>/dev/null | grep -E -v '^#|^$'`"
198
199 for opt in $opt_must; do
200 if ! echo "$conf" | grep -q "$opt="; then
201 echo "ERROR: Missing kernel config option: CONFIG_$opt"
202 err=1
203 fi
204 done
As it doesnt actually echo any missing kernel config options so bit unsure as if restart is having an issue or not.
|
|
|
|
|
Re: Differences between vzctl stop/start and restart? [message #53407 is a reply to message #32584] |
Sun, 15 July 2018 04:27 |
vinesh
Messages: 2 Registered: May 2018
|
Junior Member |
|
|
Hello,
My openvz slave node rebooting every 10 minutes.
~~~~~~
[root@lax10 ~]# /etc/init.d/vz status
OpenVZ is stopped.
[root@lax10 ~]# /etc/init.d/vz restart
OpenVZ is locked [FAILED]
OpenVZ is locked [FAILED]
~~~~~~~
I have checked with above commands.
Note:
[root@lax10 ~]# cat /etc/issue
CentOS release 6.10 (Final)
Kernel \r on an \m
[root@lax10 ~]# uname -a
Linux lax10.jinserver.com 2.6.32-042stab131.1 #1 SMP Wed Jun 20 16:32:07 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux
Please help me to resolve this issue.....
Thanks,
Vinesh
|
|
|