OpenVZ Forum: Support » reboot not start againts

Home » General » Support » reboot not start againts

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

reboot not start againts [message #21691]

Mon, 15 October 2007 00:20

ardantus
Messages: 2
Registered: October 2007
Location: indonesia

Junior Member

i have hostnude with this spesification
ip4 3gb hd 80gb ram 1gb os HN fedora core 6
i have create 4 vps
[root@vps ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
140 4 running 192.168.0.140 slackware.vps.dj-avu.us
141 4 running 192.168.0.141 slackware.vps.dj-avu.us
142 21 running 192.168.0.142 fedora.vps.dj-avu.us
144 12 running 192.168.0.144 fedora.vps.dj-avu.us
[root@vps ~]#

if i ssh to some vps example to 142 ip= 192.168.0.142 then type reboot -h now thats vps will rebooting but not run againts, thats problem also happens if i type
[root@vps ~]# vzctl exec 142 reboot
[root@vps ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
140 4 running 192.168.0.140 slackware.vps.dj-avu.us
141 4 running 192.168.0.141 slackware.vps.dj-avu.us
144 12 running 192.168.0.144 fedora.vps.dj-avu.us
[root@vps ~]#

if i type vzctl restart 142 / vzctl restart VEID its can run and thats vps will rebooting

[root@vps ~]# vzctl restart 142
Restarting VE
Starting VE ...
VE is unmounted
VE is mounted
Adding IP address(es): 192.168.0.142
Setting CPU units: 1000
Configure meminfo: 49152
Set hostname: fedora.vps.dj-avu.us
File resolv.conf was modified
VE start in progress...
[root@vps ~]#
[root@vps ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
140 4 running 192.168.0.140 slackware.vps.dj-avu.us
141 4 running 192.168.0.141 slackware.vps.dj-avu.us
142 21 running 192.168.0.142 fedora.vps.dj-avu.us
144 12 running 192.168.0.144 fedora.vps.dj-avu.us
[root@vps ~]#

so what can i do to solved thats problem, i can everytime in my HN if some user reboot their vps they will contact me for start their vps manualy. on my HN i has set --onboot yes btw thats problem stilll hapen.
anybody can solved this problem and how to configure it so if some user reboot their vps can start againts no need i am to start manuali in HN.

Report message to a moderator

Re: reboot not start againts [message #21694 is a reply to message #21691]

Mon, 15 October 2007 04:58

curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany

Senior Member

Hi,

every 5min, script /usr/share/vzctl/scripts/vpsreboot, should started via cron and started all reboot-marked VE's.

Please check if cron started this script and take a look in /var/log/vzctl.log if "vereboot" entries exist.

Report message to a moderator

Re: reboot not start againts [message #21926 is a reply to message #21694]

Thu, 18 October 2007 00:52

ardantus
Messages: 2
Registered: October 2007
Location: indonesia

Junior Member

in my HN i have add crontab
5 * * * * /usr/share/vzctl/scripts/vpsreboot

btw some vps os can`t reboot againt
my HN os is fedora core and i have 2 vps slackware 11 and 2vps fedora core 7

both of fedora core can start againts but slackware die.
[root@vps ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
140 4 running 192.168.0.140 slackware.vps.dj-avu.us
141 4 running 192.168.0.141 slackware.vps.dj-avu.us
142 21 running 192.168.0.142 fedora.vps.dj-avu.us
144 12 running 192.168.0.144 fedora.vps.dj-avu.us
[root@vps ~]#

this is tail of logs

2007-10-18T05:35:01+0700 vereboot : VE 142 : reboot
2007-10-18T05:35:01+0700 vzctl : VE 142 : Starting VE ...
2007-10-18T05:35:01+0700 vzctl : VE 142 : VE is unmounted
2007-10-18T05:35:01+0700 vzctl : VE 142 : VE is mounted
2007-10-18T05:35:01+0700 venetclean : VE 142 : VE died, clear IPs: 192.168.0.142
2007-10-18T05:35:01+0700 vzctl : VE 142 : Adding IP address(es): 192.168.0.142
2007-10-18T05:35:04+0700 vzctl : VE 142 : Setting CPU units: 1000
2007-10-18T05:35:04+0700 vzctl : VE 142 : Configure meminfo: 49152
2007-10-18T05:35:04+0700 vzctl : VE 142 : Set hostname: fedora.vps.dj-avu.us
2007-10-18T05:35:04+0700 vzctl : VE 142 : File resolv.conf was modified
2007-10-18T05:35:04+0700 vzctl : VE 142 : VE start in progress...

------------------------------------------------------------ ----
2007-10-18T07:20:01+0700 venetclean : VE 141 : VE died, clear IPs: 192.168.0.141
2007-10-18T07:28:43+0700 vzctl : VE 141 : Starting VE ...
2007-10-18T07:28:43+0700 vzctl : VE 141 : VE is unmounted
2007-10-18T07:28:43+0700 vzctl : VE 141 : VE is mounted
2007-10-18T07:28:43+0700 vzctl : VE 141 : Adding IP address(es): 192.168.0.141
2007-10-18T07:28:45+0700 vzctl : VE 141 : Setting CPU units: 1000
2007-10-18T07:28:45+0700 vzctl : VE 141 : Configure meminfo: 49152
2007-10-18T07:28:45+0700 vzctl : VE 141 : Set hostname: slackware.vps.dj-avu.us
2007-10-18T07:28:45+0700 vzctl : VE 141 : File resolv.conf was modified
2007-10-18T07:28:45+0700 vzctl : VE 141 : VE start in progress...
--------------------------------------------------------
141 is VEID of slackware when i type reboot thats vps die and need start manual with vzctl start 141

Report message to a moderator

Previous Topic:	Quota off syscall for id : Device or resource busy
Next Topic:	Bridging problems with el5 kernel

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Feb 14 15:46:55 GMT 2026

Total time taken to generate the page: 0.55713 seconds