Re: [Vserver] vserver enter eating cpu and vkill problem
On Sat, Jan 13, 2007 at 12:31:52AM +0100, Philippe Teuwen wrote: This is on a remote server in a datacenter so I'm not that fan to try a vanilla home-patched remotely :-/ i know ... i had same problem ;-) Nevertheless I tried some upgrade: the last kernel and the last util-vserver tools of etch and sid: Linux version 2.6.18-3-vserver-amd64 (Debian 2.6.18-7) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 17:19:24 CET 2006 vserver patch: 2.0.2.2-rc8 util-vserver: 0.30.212-1 I have the same problems with this single difference: now killing a process of a guest with a single kill in context 0 does not work anymore (as expected), so the only way is # vserver exec kill as vkill still does not work. yes 2.6.18-3-vserver-amd64 was bad too ... -- 5o Peter.Mann at tuke.sk ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vserver enter eating cpu and vkill problem
yes 2.6.18-3-vserver-amd64 was bad too ... Are the kernels here better? http://linux-vserver.derjohn.de/debian-etch-sid/debian/dists/sid/main/binary-amd64/ as seen in the faq http://linux-vserver.org/Frequently_Asked_Questions#Were_can_I_get_newer_versions_of_VServer_as_ready_made_packages_for_Debian.3F Phil ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vserver enter eating cpu and vkill problem
On Sat, Jan 13, 2007 at 12:44:05PM +0100, Philippe Teuwen wrote: yes 2.6.18-3-vserver-amd64 was bad too ... Are the kernels here better? http://linux-vserver.derjohn.de/debian-etch-sid/debian/dists/sid/main/binary-amd64/ as seen in the faq http://linux-vserver.org/Frequently_Asked_Questions#Were_can_I_get_newer_versions_of_VServer_as_ready_made_packages_for_Debian.3F i don't know ... you can make own kernel with vanilla source + vserver patch by using your kernel config and make-kpkg ... IMHO it's easy and safe ... i sent to this list mail about Etch vserver kernels a few days ago: Subject: Re: [Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version Date: Tue, 9 Jan 2007 09:47:36 +0100 On Tue, Jan 09, 2007 at 06:11:10AM +0100, [EMAIL PROTECTED] wrote: On Mon, Jan 08, 2007 at 11:05:50AM +0100, Oliver Paulus wrote: I have used Linux kernel 2.6.17.13 with VServer 2.0.2.1 before - everything worked correctly. Now I have installed the Debian 4.0 (Etch) vserver kernel 2.6.18-3-vserver-amd64. If I stop a specific vserver instance with vserver name stop I get the following error: please try with a mainstream kernel, preferable one of the 2.2.0-rc* kernels, and mainstream util-vserver (0.30.212) if the issue remains, please let us know, otherwise please contact the debian maintainers about those issues ... TIA, Herbert The Debian maintainers are aware, and it's the bug fixed in 2.0.2.2-rc9 (off by one cacct). From what I gathered, the most recent Debian snapshot kernel should work fine, but I didn't quite understand how or where to get it. Debian Etch is now frozen, so every package update into Etch is processed through debian-release team ... some new linux-2.6 (kernel) is scheduled: http://lists.debian.org/debian-release/2007/01/msg00085.html -- 5o Peter.Mann at tuke.sk ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Compiling 2.6.19.1 with vs+grsec
Hi I just tried compiling kernel 2.6.19.1 patched with vs2.2.0-rc6-grsec2.1.9 (latest upcoming stable). I doesn't seem to work very well however, I get this error message: saturn linux-2.6.19.1 # make all make modules_install CHK include/linux/version.h CHK include/linux/utsrelease.h CHK include/linux/compile.h CC fs/proc/array.o fs/proc/array.c: In function ‘proc_pid_status’: fs/proc/array.c:329: error: ‘nx_info’ undeclared (first use in this function) fs/proc/array.c:329: error: (Each undeclared identifier is reported only once fs/proc/array.c:329: error: for each function it appears in.) fs/proc/array.c:329: error: ‘nxi’ undeclared (first use in this function) fs/proc/array.c:331: warning: ISO C90 forbids mixed declarations and code make[2]: *** [fs/proc/array.o] Error 1 make[1]: *** [fs/proc] Error 2 make: *** [fs] Error 2 I get this error both with GCC 4.1.1 and GCC 3.4.6 Anyone else having the same problem? / Johan Marcusson ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Compiling 2.6.19.1 with vs+grsec
On Sat, Jan 13, 2007 at 03:05:20PM +0100, Johan Marcusson wrote: Hi I just tried compiling kernel 2.6.19.1 patched with vs2.2.0-rc6-grsec2.1.9 (latest upcoming stable). I doesn't seem to work very well however, I get this error message: saturn linux-2.6.19.1 # make all make modules_install CHK include/linux/version.h CHK include/linux/utsrelease.h CHK include/linux/compile.h CC fs/proc/array.o fs/proc/array.c: In function ???proc_pid_status???: fs/proc/array.c:329: error: ???nx_info??? undeclared (first use in this function) fs/proc/array.c:329: error: (Each undeclared identifier is reported only once fs/proc/array.c:329: error: for each function it appears in.) fs/proc/array.c:329: error: ???nxi??? undeclared (first use in this function) fs/proc/array.c:331: warning: ISO C90 forbids mixed declarations and code make[2]: *** [fs/proc/array.o] Error 1 make[1]: *** [fs/proc] Error 2 make: *** [fs] Error 2 I get this error both with GCC 4.1.1 and GCC 3.4.6 Anyone else having the same problem? I guess so, I would suggest to leave grsec out for now, until newer/fixed patches are available 2.6.19.2 + 2.2.0-rc7 is supposed to work fine (except for a mainline bug which is worked on) HTH, Herbert / Johan Marcusson ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vserver enter eating cpu and vkill problem
Philippe Teuwen wrote: Hello, Here are some problems I have with vserver. My environment: Kernel: Debian vserver_pre-patched kernel for AMD64: Linux version 2.6.17-2-vserver-amd64 (Debian 2.6.17-9) ([EMAIL PROTECTED]) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Wed Sep 13 18:02:36 CEST 2006 According to changelog.Debian, this version is using vserver patch v2.0.2 util-vserver: 0.30.211-6 First problem: In some situations my CPU was burning like hell for days before I noticed it. This was the vcontext/login process, the one running when using the command vserver XX enter. If it happens that the process is disconnected from its terminal it eats all the CPU :-( Apparently it happens when the session is not ended properly (disconnections, etc) I could reproduce the problem as follow: * ssh to the server as normal user * sudo su - * vserver XX enter * now from another term, kill -9 on either of the two su processes (su - or -su) At that point the session in the vserver ends but vcontext is still hooked to the current terminal so cpu is fine. * now quit the current terminal At that point vcontext is not hooked to any terminal (vps ax = ? on the tty column) and using top you see it's running 100% cpu, ~ 80% system and 20% user. I'll look in to it. Second problem (cosmetic): Depending on the tool, the process I was talking about in the previous problem appears as vcontext (top, pgrep,... cat /proc/NNN/status) or as login (ps ax, pgrep -f,... cat /proc/NNN/cmdline) or should I say login\0\0\0\0\0\0\0\0\0\0\0... This is quite disturbing using processes mgmt tools like when I wrote a cron to detect cpu hangry vcontext processes to be killed :-) Lots of programs overwrite the process name to get nicer ps/top/etc. output. Third problem I discovered when writing that watchdog: Processes from guests are not displayed using ps/top/etc in context 0 (ps ax from host) but well in context 1 (e.g. vps ax). Fine. But if I want to kill one of them: host:~# vserver devel enter devel:~# top --- in another host term --- host:~# ps -C top PID TTY TIME CMD host:~# vps -C top PID CONTEXT TTY TIME CMD 17111 31022 devel pts/13 00:00:00 top host:~# vkill 17111 vkill: vc_ctx_kill(): No such process vkill needs the context too, i.e. vkill --xid devel 17111. host:~# chcontext --ctx 1 ps -C top PID TTY TIME CMD 17111 pts/13 00:00:00 top host:~# chcontext --ctx 1 kill 17111 no error but nothing happens neither: host:~# vps -C top PID CONTEXT TTY TIME CMD 17111 31022 devel pts/13 00:00:00 top host:~# kill 17111 host:~# vps -C top PID CONTEXT TTY TIME CMD worked!! This is not the behaviour I expected. Apart from that I'm happy running vserver for almost a year with now 6 guests. Phil PS: nothing particular here when I ran testme.sh Linux-VServer Test [V0.17] Copyright (C) 2003-2006 H.Poetzl chcontext is working. chbind is working. Linux 2.6.17-2-vserver-amd64 #1 SMP Wed Sep 13 18:02:36 CEST 2006 x86_64 Ea 0.30.211 236/glibc (DSa) compat,v11,fscompat,v13,net,v21,oldproc,olduts VCI: 0002:0002 236 0316 (TbLgnP) --- [000]# succeeded. [001]# succeeded. [011]# succeeded. [031]# succeeded. [101]# succeeded. [102]# succeeded. [201]# succeeded. [202]# succeeded. -- Daniel Hokka Zakrisson ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
