Host system is 2005.1 vserver running sys-kernel/vserver-sources-2.0.1 sys-cluster/util-vserver-0.30.209-r1 do a 'reboot' inside a vserver (not the host system!), ps aux shows 'reboot -d', seconds later your console gets killed and you're kicked out, like the virtual machine really is getting down. vserver-stat resets the uptime counters to 0 for this vserver making you think the vserver really got rebooted. enter the vserver again, do a ps aux, the 'reboot -d' command is still running, seconds later you're console gets killed again but this time vserver-stat doesn't show the vserver running anymore. So reboot behaves like halt in the vservers...
# emerge info (of the host system) Portage 2.0.53 (default-linux/x86/2005.1/vserver, gcc-3.3.6, glibc-2.3.5-r2, 2.6.14-vs2.0.1-gentoo i686) ================================================================= System uname: 2.6.14-vs2.0.1-gentoo i686 Intel(R) Xeon(TM) CPU 3.00GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.4, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo-mirror/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://gentoo-mirror/gentoo-portage" USE="x86 alsa apache2 bash-completion bzip2 bzlib crypt devfs26 eds emboss expat ftp gd gif gstreamer imagemagick imap innodb ipv6 jpeg md5sum mhash mime mmx mmx2 mp3 ncurses nls nocd nocstrike nodod ogg pam perl php png posix readline rtc sse sse2 ssl tcpd tiff truetype-fonts type1-fonts udev uudeview vorbis xml2 zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS # emerge info (from the vserver running on the host) Portage 2.0.53 (default-linux/x86/2005.1/vserver, gcc-3.3.6, glibc-2.3.5-r2, 2.6.14-vs2.0.1-gentoo i686) ================================================================= System uname: 2.6.14-vs2.0.1-gentoo i686 Intel(R) Xeon(TM) CPU 3.00GHz Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://gentoo-mirror/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo" LANG="de_DE@euro" LINGUAS="de" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://gentoo-mirror/gentoo-portage" USE="x86 alsa apache2 apm arts avi bash-completion bitmap-fonts bzip2 cups eds emboss encode expat foomaticdb gif gstreamer libg++ libwww mad mikmod motif mp3 mpeg mpm-prefork nls no-htdocs nocd ogg oggvorbis opengl oss pam pdflib quicktime readline sdl ssl tcpd truetype-fonts type1-fonts vorbis xmms xv zlib linguas_de userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
(In reply to comment #1) > # emerge info (from the vserver running on the host) > Portage 2.0.53 (default-linux/x86/2005.1/vserver, gcc-3.3.6, glibc-2.3.5-r2, > 2.6.14-vs2.0.1-gentoo i686) > ================================================================= > System uname: 2.6.14-vs2.0.1-gentoo i686 Intel(R) Xeon(TM) CPU 3.00GHz > Gentoo Base System version 1.6.13 Could you try if fails with baselayout-vserver-1.11.14 too? (would be base system 1.6.14)
Ok, here is ps aux right after starting the vserver: (vserver)# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 1428 476 ? S 13:00 0:00 init [3] root 9329 0.0 0.0 1468 560 ? Ss 13:00 0:00 /usr/sbin/syslogd -m 0 root 9427 0.0 0.0 3316 896 ? Ss 13:00 0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.pid root 9495 0.0 0.0 1680 640 ? Ss 13:00 0:00 /usr/sbin/cron root 9510 6.5 0.1 2976 1896 pts/0 S 13:00 0:00 /bin/bash -login root 9534 0.0 0.0 2624 880 pts/0 R+ 13:00 0:00 ps aux (vserver)# . /etc/profile (vserver)# reboot (vserver)# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 1428 480 ? S 13:00 0:00 init [6] root 9329 0.0 0.0 1468 560 ? Ss 13:00 0:00 /usr/sbin/syslogd -m 0 root 9510 2.3 0.2 3892 2772 pts/0 S 13:00 0:00 /bin/bash -login root 9549 5.0 0.1 2396 1348 ? Ss 13:00 0:00 /bin/bash /sbin/rc reboot root 10002 0.0 0.1 2532 1100 ? S 13:00 0:00 /bin/bash /sbin/rc reboot root 10028 0.0 0.0 1960 500 ? S 13:00 0:00 sleep 1 root 10029 0.0 0.0 2624 880 pts/0 R+ 13:00 0:00 ps aux (vserver)# logout (host)# vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 0 53 85.2M 59.5M 4h06m29 1h10m48 6d02h11 root server 1234 1 1.2M 268K 0m00s00 0m00s00 0m05s98 gentoo-template (host)# vserver gentoo-template enter (vserver)# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 10165 0.0 0.0 1280 268 ? D 13:00 0:00 /sbin/reboot -d root 10226 6.0 0.1 2972 1892 pts/0 S 13:00 0:00 /bin/bash -login root 10250 0.0 0.0 2624 876 pts/0 R+ 13:00 0:00 ps aux (vserver)#Killed (host)# vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 0 47 77.5M 55.8M 4h06m29 1h10m48 6d02h14 root server
> Could you try if fails with baselayout-vserver-1.11.14 too? emerged baselayout-vserver-1.11.14 inside the vserver, stopped & started the vserver, did a reboot inside the vserver, logged out of the vserver, watched vserver-stat and after around 30 seconds the vserver stopped running.
Even a 'reboot -f' inside the vserver doesn't help - the console gets destroyed immediately and 30 seconds later the vserver isn't running anymore.
(In reply to comment #0) > Host system is 2005.1 vserver running > > sys-kernel/vserver-sources-2.0.1 > sys-cluster/util-vserver-0.30.209-r1 > Could you please try >=sys-apps/baselayout-vserver-1.12.0_pre16 and see if that fixes it ? At least it works for me now ..
Nope, sys-apps/baselayout-vserver-1.12.0_pre16 breaks everything here. Emerged it along with the masked bash package and had problems halting the vserver after that: /bin/bash /sbin/runscript.sh /etc/init.d/clock stop was in processlist twice with did nothing than block the shutdown process. Alter killing these 2 processes by hand and starting the vserver again, the vserver hangs at starting sshd: (vserver) # ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 1452 500 ? S 12:50 0:00 init [3] root 27303 0.0 0.0 2880 1604 ? Ss 12:50 0:00 /bin/bash /sbin/rc default root 27891 0.0 0.0 3004 1712 ? S 12:50 0:00 /bin/bash /sbin/runscript.sh /etc/init.d/sshd start root 27925 0.0 0.0 3004 924 ? S 12:50 0:00 /bin/bash /sbin/runscript.sh /etc/init.d/sshd start root 27926 0.0 0.0 1444 360 ? S 12:50 0:00 cat /var/lib/init.d/exclusive/net.lo root 27951 0.0 0.1 3584 2276 pts/0 S 12:50 0:00 /bin/bash -login root 28011 0.0 0.0 2644 892 pts/0 R+ 12:53 0:00 ps aux sys-apps/baselayout-vserver-1.12.0_pre16 is not an option for me.
Maybe this is of interest: When using stable baselayout-vserver-1.11.14-r3 and issueing a 'reboot' inside the vserver, on the host system i see this in the processlist: root 14 -5 0.0 0.0 00:00:00 24-03:14:54 ? [khelper] root 4989 -5 0.0 0.0 00:00:00 00:00 ? \_ [khelper] root 4990 -5 0.0 0.0 00:00:00 00:00 ? \_ /bin/bash /usr/sbin/vserver --defaulttty /etc/vservers/MYVSERVERNAME restart root 5007 -5 0.0 0.0 00:00:00 00:00 ? \_ /bin/bash /usr/sbin/vserver --defaulttty --sync /etc/vservers/MYVSERVERNAME stop root 5015 -5 0.0 0.0 00:00:00 00:00 ? \_ /usr/lib/util-vserver/lockfile /var/lock/vserver.etcvserversMYVSERVERNAME.startup /tmp/vserver-lock.NRZC2B root 5042 -5 0.0 0.0 00:00:00 00:00 ? \_ /bin/bash /usr/sbin/vserver --defaulttty --sync /etc/vservers/MYVSERVERNAME stop root 5043 -5 0.0 0.0 00:00:00 00:00 ? \_ /usr/sbin/vwait --timeout 30 --status-fd 3 56
(In reply to comment #0) > Host system is 2005.1 vserver running > > sys-kernel/vserver-sources-2.0.1 > sys-cluster/util-vserver-0.30.209-r1 Marcel, could you please try it again with >=vserver-sources-2.0.2 and >=util-vserver-0.30.210-r15 and >=baselayout-vserver-1.12.1 within the VPS ? Reopen the bug once you get around to test it.
(In reply to comment #9) > Marcel, could you please try it again with >=vserver-sources-2.0.2 and > >=util-vserver-0.30.210-r15 and >=baselayout-vserver-1.12.1 within the VPS ? Hi Christian, i finally got the time to test this. scenario I ========== host: sys-kernel/vserver-sources-2.0.2.1 sys-cluster/util-vserver-0.30.211 vps: sys-apps/baselayout-vserver-1.12.1 result: the vps is hanging at the boot-process like described by me in comment 7 scenario II =========== host: sys-kernel/vserver-sources-2.0.2.1 sys-cluster/util-vserver-0.30.211 vps: sys-apps/baselayout-vserver-1.12.3 (*) result: rebooting the vps works. The only drawback is bug #152768 (sysklogd initscript doesn't work anymore).
closed
chked
again
