From: Guillaume Bourque (bougui_at_logisoftech.com)
Date: Fri 25 Jan 2002 - 06:01:04 GMT
Just to let you know,
It seem that if you change the name of a vserver and is ROOT name in the /vservers directory your
better reboot before trying to restart this vserver. with other vserver still running !
Now everything seem's to be back on track and all my vserver boot correctly.
Guillaume Bourque a écrit :
> Hello all,
>
> I have kernel 2.4.18-ctx-5 and almost everything is fine, well after
> starting all my vserver I'm loosing one of them :(
>
> If I do [root_at_sonloup root]# vserver-stat
> CTX# PROC QTY VSZ RSS utime stime NAME
> 0 41 53140 5834 00m08.90 00m16.86 root server
> 2 13 24532 2492 00m01.39 00m00.70
> 3 6 13552 1708 00m00.44 00m00.24 v2
> 4 4 7348 793 00m00.16 00m00.03 v3
> 5 18 32764 2457 00m04.52 00m00.65 v4
>
> You can see that context #2 (v1) is not showing up ok. everything was
> working until I decide to start them all automaticly at boot time.
>
> Now if I enter that v server I get in a new context !!???
>
> [root_at_sonloup root]# vserver v1 enter
> Server v1 is not running
> ipv4root is now 204.19.190.2
> Host name is now ns1.logisoftech.com
> New security context is 7
> [root_at_ns1 /]#
>
> If I do ssh to the Ip of the vserver everything is still up in the
> context #2 !
>
> [root_at_ns1 service]# ps -ef
> UID PID PPID C STIME TTY TIME CMD
> root 1 0 0 21:29 ? 00:00:06 init [3]
> root 1159 1 0 21:41 ? 00:00:00 syslogd -m 0
> root 1167 1 0 21:41 ? 00:00:00 klogd -2
> root 1191 1 0 21:41 ? 00:00:00 sshd
> root 1220 1 0 21:41 ? 00:00:00 crond
> root 1239 1 0 21:41 pts/0 00:00:00 /bin/sh
> /command/svscanboot
> root 1260 1239 0 21:41 pts/0 00:00:00 svscan /service
> root 1261 1239 0 21:41 pts/0 00:00:00 readproctitle service
> errors: .........................
> root 1265 1260 0 21:41 pts/0 00:00:00 supervise lstdns
> root 1266 1260 0 21:41 pts/0 00:00:00 supervise log
> tinydns 1267 1265 0 21:41 pts/0 00:00:00 /usr/local/bin/tinydns
> dnslog 1268 1266 0 21:41 pts/0 00:00:00 multilog t ./main
> root 1913 1191 0 21:42 ? 00:00:00 sshd
> root 1920 1913 0 21:42 pts/1 00:00:00 -bash
> root 2909 1920 0 21:56 pts/1 00:00:00 ps -ef
>
> Now if I trie to stop the v1 server in context 2 I get this
>
> [root_at_sonloup root]# vserver v1 stop
> Stopping the virtual server v1
> Server v1 is not running
>
> And naturally the vserver keep's running ;-0 and the proc filesystem for vserver v1 is still mount
>
> [root_at_sonloup root]# mount
> /dev/md4 on / type ext3 (rw)
> none on /proc type proc (rw)
> /dev/md0 on /boot type ext3 (rw)
> none on /dev/pts type devpts (rw,mode=0620)
> none on /dev/shm type tmpfs (rw)
> /dev/md5 on /home type ext3 (rw)
> /dev/md1 on /var type ext3 (rw)
> /dev/md6 on /var/ftp type ext3 (rw)
> /dev/md2 on /var/sql type ext3 (rw)
> /dev/md3 on /var/www type ext3 (rw)
> none on /vservers/v1/proc type proc (rw)
> none on /vservers/v1/dev/pts type devpts (rw)
> /var on /vservers/v2/var type none (rw,bind)
> none on /vservers/v2/proc type proc (rw)
> none on /vservers/v2/dev/pts type devpts (rw)
> none on /vservers/v3/proc type proc (rw)
> none on /vservers/v3/dev/pts type devpts (rw)
> none on /vservers/v4/proc type proc (rw)
> none on /vservers/v4/dev/pts type devpts (rw)
>
> Any help would be of great value !
>
> --
> --------------------- La qualité avant tout ! ----------------------
> Guillaume Bourque Conseiller technologique
> LogiSoft Technologies inc.
> Tél. (514) 576-7638 Fax: (450) 649-6134
> -------------------- http://www.logisoftech.com --------------------
--
--------------------- La qualité avant tout ! ----------------------
Guillaume Bourque Conseiller technologique
LogiSoft Technologies inc.
Tél. (514) 576-7638 Fax: (450) 649-6134
-------------------- http://www.logisoftech.com --------------------