[Vserver] Bug on 2.6.22
Hello
I was testing linux-2.6.22-vs2.2.0-rc5 and it crashes after 30 hours : here
is the kern.log
http://paste.linux-vserver.org/4555
srvweb:/var/log# vserver-info
Versions:
Kernel: 2.6.21.5-vs2.2.0-rc3
VS-API: 0x00020200
util-vserver: 0.30.213; Jun 16 2007, 14:53:27
Features:
CC: gcc, gcc (GCC) 4.1.2 20061115 (prerelease)
(Debian 4.1.1-21)
CXX: g++, g++ (GCC) 4.1.2 20061115 (prerelease)
(Debian 4.1.1-21)
CPPFLAGS: ''
CFLAGS:
'-g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time'
CXXFLAGS:
'-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time'
build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
Use dietlibc: yes
Build C++ programs: yes
Build C99 programs: yes
Available APIs: compat,v11,fscompat,v13,net,v21,oldproc,olduts
ext2fs Source: e2fsprogs
syscall(2) invocation: alternative
vserver(2) syscall#: 273/glibc
Paths:
prefix: /usr/local
sysconf-Directory: ${prefix}/etc
cfg-Directory: ${prefix}/etc/vservers
initrd-Directory: $(sysconfdir)/init.d
pkgstate-Directory: ${prefix}/var/run/vservers
vserver-Rootdir: /opt/vservers
It crashes when i just stop and restart a vserver.
pmenier
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] bug 2.6.20.2 ??
Hello all, Today big problem with linux-2.6.20.2 (from kernel.org) and patch-2.6.20.2-vs2.2.0-rc16.diff. (debian-sarge, Pentium4D, 2Go ram) I use vserver since two years, so i don't think it's a compil error. It runs fine two hours then hangs with this message in syslog : Mar 11 20:59:05 srvweb kernel: BUG: unable to handle kernel paging request at virtual address 0270 Mar 11 20:59:05 srvweb kernel: printing eip: Mar 11 20:59:05 srvweb kernel: c0225907 Mar 11 20:59:05 srvweb kernel: *pde = Mar 11 20:59:05 srvweb kernel: Oops: [#1] Mar 11 20:59:05 srvweb kernel: PREEMPT SMP Mar 11 20:59:05 srvweb kernel: Modules linked in: md_mod parport_pc parport ipt_iprange iptable_filter ip_tables x_tables w83627ehf hwmon i2c_isa i2c_core dummy ipv6 r8169 Mar 11 20:59:05 srvweb kernel: CPU:0 Mar 11 20:59:05 srvweb kernel: EIP:0060:[tty_devnum+3/18]Not tainted VLI Mar 11 20:59:05 srvweb kernel: EFLAGS: 00010086 (2.6.20.2-vs2.2.0-rc16 #1) Mar 11 20:59:05 srvweb kernel: EIP is at tty_devnum+0x3/0x12 Mar 11 20:59:05 srvweb kernel: eax: d795c000 ebx: d244e540 ecx: 0200 edx: 0202 Mar 11 20:59:05 srvweb kernel: esi: ed982ab0 edi: ed982ab0 ebp: f5ce1240 esp: d1ff9de0 Mar 11 20:59:05 srvweb kernel: ds: 007b es: 007b ss: 0068 Mar 11 20:59:05 srvweb kernel: Process ps (pid: 30354[#20], ti=d1ff8000 task=d53cd030 task.ti=d1ff8000) Mar 11 20:59:05 srvweb kernel: Stack: c018f33a d1ff9f00 c0164c95 c0226bde d94ddc26 d94f5fbb 0101 c716b00f Mar 11 20:59:05 srvweb kernel:d1af0f40 caac27c8 01c5a71f 0004 c716b00b d1ff9f30 d1af01c0 c0171901 Mar 11 20:59:05 srvweb kernel:d1ff9f30 c0165e28 dcc3f324 d1af01c0 22f6dd4a 45f41848 22f6dd4a Mar 11 20:59:05 srvweb kernel: Call Trace: Mar 11 20:59:05 srvweb kernel: [do_task_stat+465/2161] do_task_stat+0x1d1/0x871 Mar 11 20:59:05 srvweb kernel: [permission+405/426] permission+0x195/0x1aa Mar 11 20:59:05 srvweb kernel: [n_tty_receive_buf+2120/2216] n_tty_receive_buf+0x848/0x8a8 Mar 11 20:59:05 srvweb kernel: [mntput_no_expire+17/99] mntput_no_expire+0x11/0x63 Mar 11 20:59:05 srvweb kernel: [link_path_walk+154/164] link_path_walk+0x9a/0xa4 Mar 11 20:59:05 srvweb kernel: [in_group_p+33/34] in_group_p+0x21/0x22 Mar 11 20:59:05 srvweb kernel: [generic_permission+82/203] generic_permission+0x52/0xcb Mar 11 20:59:05 srvweb kernel: [permission+418/426] permission+0x1a2/0x1aa Mar 11 20:59:05 srvweb kernel: [do_path_lookup+375/402] do_path_lookup+0x177/0x192 Mar 11 20:59:05 srvweb kernel: [proc_info_read+206/273] proc_info_read+0xce/0x111 Mar 11 20:59:05 srvweb kernel: [vfs_read+138/303] vfs_read+0x8a/0x12f Mar 11 20:59:05 srvweb kernel: [sys_read+65/103] sys_read+0x41/0x67 Mar 11 20:59:05 srvweb kernel: [sysenter_past_esp+93/129] sysenter_past_esp+0x5d/0x81 Mar 11 20:59:05 srvweb kernel: [xfrm_policy_unregister_afinfo+34/133] xfrm_policy_unregister_afinfo+0x22/0x85 Mar 11 20:59:05 srvweb kernel: === Mar 11 20:59:05 srvweb kernel: Code: 00 00 c7 86 c0 00 00 00 00 00 00 00 c7 86 c8 00 00 00 00 00 00 00 e8 56 6a f3 ff 8d 46 04 e8 ce bb f3 ff 31 c0 5b 5e c3 8b 48 04 8b 51 70 c1 e2 14 0b 51 74 03 50 08 89 d0 c3 53 89 c3 8b 80 50 Mar 11 20:59:05 srvweb kernel: EIP: [tty_devnum+3/18] tty_devnum+0x3/0x12 SS:ESP 0068:d1ff9de0 Mar 11 20:59:05 srvweb kernel: 6note: ps[30354] exited with preempt_count 2 Mar 11 20:59:05 srvweb kernel: BUG: scheduling while atomic: ps/0x1002/30354 Mar 11 20:59:05 srvweb kernel: [schedule+87/1648] __sched_text_start+0x57/0x670 Mar 11 20:59:05 srvweb kernel: [unmap_page_range+178/256] unmap_page_range+0xb2/0x100 Mar 11 20:59:05 srvweb kernel: [__cond_resched+22/52] __cond_resched+0x16/0x34 Mar 11 20:59:05 srvweb kernel: [cond_resched+38/49] cond_resched+0x26/0x31 Mar 11 20:59:05 srvweb kernel: [unmap_vmas+401/523] unmap_vmas+0x191/0x20b Mar 11 20:59:05 srvweb kernel: [exit_mmap+133/392] exit_mmap+0x85/0x188 Mar 11 20:59:05 srvweb kernel: [mmput+32/120] mmput+0x20/0x78 Mar 11 20:59:05 srvweb kernel: [do_exit+424/931] do_exit+0x1a8/0x3a3 Mar 11 20:59:05 srvweb kernel: [die+466/474] die+0x1d2/0x1da Mar 11 20:59:05 srvweb kernel: [do_page_fault+1066/1307] do_page_fault+0x42a/0x51b Mar 11 20:59:05 srvweb kernel: [inotify_d_instantiate+65/110] inotify_d_instantiate+0x41/0x6e Mar 11 20:59:05 srvweb kernel: [get_pid_task+17/53] get_pid_task+0x11/0x35 Mar 11 20:59:05 srvweb kernel: [pid_revalidate+20/414] pid_revalidate+0x14/0x19e Mar 11 20:59:05 srvweb kernel: [pid_revalidate+263/414] pid_revalidate+0x107/0x19e Mar 11 20:59:05 srvweb kernel: [do_page_fault+0/1307] do_page_fault+0x0/0x51b Mar 11 20:59:05 srvweb kernel: [error_code+124/132] error_code+0x7c/0x84 Mar 11 20:59:05 srvweb kernel: [deactivate_super+27/70] deactivate_super+0x1b/0x46 Mar 11 20:59:05 srvweb kernel: [tty_devnum+3/18] tty_devnum+0x3/0x12 Mar 11 20:59:05 srvweb kernel: [do_task_stat+465/2161] do_task_stat+0x1d1/0x871 Mar 11 20:59:05 srvweb kernel: [permission+405/426] permission+0x195
Re: [Vserver] patch-vs-2.1.1.7.diff nok ?
Hello, Indeed, i RE-compil my kernel and all goes fine without any errors. Sorry for the convenience. Next time, i will retry several times before posting. Patrick - Original Message - From: Herbert Poetzl [EMAIL PROTECTED] To: Matt Anger (manger) [EMAIL PROTECTED] Cc: vserver@list.linux-vserver.org Sent: Thursday, December 14, 2006 7:20 PM Subject: Re: [Vserver] patch-vs-2.1.1.7.diff nok ? On Thu, Dec 14, 2006 at 09:17:29AM -0800, Matt Anger (manger) wrote: I'm pretty sure you have to disable legacy kernel api. how do you get to such a conclusion? I think its been broken for a while and removed completely in the new 2.2/2.3 releases. while it will be removed for 2.3.x, and is already removed to some extend for 2.2.x, it is still part of 2.1.x and it compiles and works perfectly fine, if you have any .configs where this is not true, please let us know, as it is considered a bug ... Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 14, 2006 2:27 AM To: vserver@list.linux-vserver.org Subject: [Vserver] patch-vs-2.1.1.7.diff nok ? Hello I try patch-vs-2.1.1.7.diff : error during compil but i don't know if it's due to patch CC kernel/power/process.o CC kernel/power/console.o CC kernel/power/pm.o kernel/power/pm.c:205: attention : `pm_register' is deprecated (declared at kernel/power/pm.c:64) kernel/power/pm.c:205: attention : `pm_register' is deprecated (declared at kernel/power/pm.c:64) kernel/power/pm.c:206: attention : `pm_send_all' is deprecated (declared at kernel/power/pm.c:180) kernel/power/pm.c:206: attention : `pm_send_all' is deprecated (declared at kernel/power/pm.c:180) that is normal, most of the power management has been deprecated in recent kernels, and the maintainers do not care much to fix it up ... you'll get the same warnings on mainline malloc: ../bash/make_cmd.c:89: assertion botched malloc: block on free list clobbered so, that looks like some tool wasn't able to allocate (or free) memory properly, which somewhat points to a broken toolchain ... Stopping myself...make[2]: *** [kernel/power/pm.o] Erreur 134 make[1]: *** [kernel/power] Erreur 2 make: *** [kernel] Erreur 2 I just activate the following options in VSERVER : [*] Enable Legacy Kernel API [*] Enable dynamic context IDs [*] Enable Legacy Networking Kernel API [*] Enable Proc Security that is, like all other configurations, a perfectly fine one ... HTC, Herbert Patrick ___ 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 ___ 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
[Vserver] patch-vs-2.1.1.7.diff nok ?
Hello I try patch-vs-2.1.1.7.diff : error during compil but i don't know if it's due to patch CC kernel/power/process.o CC kernel/power/console.o CC kernel/power/pm.o kernel/power/pm.c:205: attention : `pm_register' is deprecated (declared at kernel/power/pm.c:64) kernel/power/pm.c:205: attention : `pm_register' is deprecated (declared at kernel/power/pm.c:64) kernel/power/pm.c:206: attention : `pm_send_all' is deprecated (declared at kernel/power/pm.c:180) kernel/power/pm.c:206: attention : `pm_send_all' is deprecated (declared at kernel/power/pm.c:180) malloc: ../bash/make_cmd.c:89: assertion botched malloc: block on free list clobbered Stopping myself...make[2]: *** [kernel/power/pm.o] Erreur 134 make[1]: *** [kernel/power] Erreur 2 make: *** [kernel] Erreur 2 I just activate the following options in VSERVER : [*] Enable Legacy Kernel API [*] Enable dynamic context IDs [*] Enable Legacy Networking Kernel API [*] Enable Proc Security Patrick ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] compil error on 2.6.19.1
Hi all A compil problem on 2.6.19.1 with patch-2.6.19.1-vs2.1.1.6.diff I got this error : LD .tmp_vmlinux1 fs/built-in.o(.text+0x423f): In function `chrdev_open': : undefined reference to `vs_map_device' fs/built-in.o(.text+0x22446): In function `bd_acquire': : undefined reference to `vs_map_device' make: *** [.tmp_vmlinux1] Erreur 1 Patrick ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] compil error on 2.6.19.1
Hello, Error during compil, after applying patch delta-dmap-feat04.4.diff and activating CONFIG_VSERVER_DEVICE . CC kernel/vserver/legacynet.o CC kernel/vserver/device.o kernel/vserver/device.c:48: error: erreur de syntaxe before ';' token make[2]: *** [kernel/vserver/device.o] Erreur 1 make[1]: *** [kernel/vserver] Erreur 2 make: *** [kernel] Erreur 2 Regards, Pat - Original Message - From: Daniel Hokka Zakrisson [EMAIL PROTECTED] To: vserver@list.linux-vserver.org Sent: Wednesday, December 13, 2006 4:34 PM Subject: Re: [Vserver] compil error on 2.6.19.1 [EMAIL PROTECTED] wrote: Hi all A compil problem on 2.6.19.1 with patch-2.6.19.1-vs2.1.1.6.diff I got this error : LD .tmp_vmlinux1 fs/built-in.o(.text+0x423f): In function `chrdev_open': : undefined reference to `vs_map_device' fs/built-in.o(.text+0x22446): In function `bd_acquire': : undefined reference to `vs_map_device' make: *** [.tmp_vmlinux1] Erreur 1 I think the device mapping patches were included a bit prematurely (I don't think they're supposed to be there), but to get rid of the errors you could enable CONFIG_VSERVER_DEVICE (though I had problems booting without some further fixes, http://people.linux-vserver.org/~dhozac/p/k/delta-dmap-feat04.4.diff). -- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412 ___ 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 doesn't start automatically
Hello, When i type : apt-file search popd i got this answer : .. ksh: usr/share/ksh/functions/popd zsh: usr/share/zsh/help/popd . Perhaps it expects a zsh/ksh shell ? I got this error last week, and i just launch vserver from /usr/local/sbin as you did and it works too... Pat - Original Message - From: Alejandro Cabrera Obed [EMAIL PROTECTED] To: Vserver (list) vserver@list.linux-vserver.org Sent: Wednesday, December 13, 2006 5:58 PM Subject: [Vserver] Vserver doesn't start automatically Dear all, I have a vserver on a Debian Etch box with the corresponding packages versions to this distribution, which has the /etc/vservers/virtual1/apps/init/mark file with the 'default' value in order to start automatically on booting. In the past it starts automatically OK, but today it doesn't (yesterday there was a power shutdown and the Debian box was down). I get this messages on the boot process: starting vservers of type 'default'/usr/lib/util-vserver/vserver.functions: line 696: popd: /tmp/vserver-init.us3839: no such file or directory Failed to start vserver 'virtual1' make ** [.proxy.stamp] Error 1 make target 'all' not remake because of errors ERROR Can you help me to correct this problem ??? While I wait for a response, I start automatically my vserver from the /etc/rc.local script from Debian, when I put '/usr/sbin/vserver virtual1 start'...but I don't want this solution. Thanks a lot, Alejandro ___ 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
[Vserver] Bug again on 2.6.19
Hello all I try util-vservers-0.30.212-rc5 with patch-vs-2.1.1.4.diff on kernel 2.6.19 : And a few minutes later after starting vservers, i loose their context and got this message in syslog : Dec 9 11:15:34 srvweb kernel: BUG: warning at kernel/vserver/proc.c:398/proc_vx_info_read() Dec 9 11:15:34 srvweb kernel: [dump_trace+107/417] dump_trace+0x6b/0x1a1 Dec 9 11:15:34 srvweb kernel: [show_trace_log_lvl+23/43] show_trace_log_lvl+0x17/0x2b Dec 9 11:15:34 srvweb kernel: [__func__.0+3843/287512] 0xc0326c7b Dec 9 11:15:34 srvweb kernel: DWARF2 unwinder stuck at 0xc0326c7b Dec 9 11:15:34 srvweb kernel: Dec 9 11:15:34 srvweb kernel: Leftover inexact backtrace: Dec 9 11:15:34 srvweb kernel: Dec 9 11:15:34 srvweb kernel: [show_trace+15/17] show_trace+0xf/0x11 Dec 9 11:15:34 srvweb kernel: [dump_stack+19/21] dump_stack+0x13/0x15 Dec 9 11:15:34 srvweb kernel: [proc_vx_info_read+90/222] proc_vx_info_read+0x5a/0xde Dec 9 11:15:34 srvweb kernel: [vfs_read+138/308] vfs_read+0x8a/0x134 Dec 9 11:15:34 srvweb kernel: [sys_read+65/103] sys_read+0x41/0x67 Dec 9 11:15:34 srvweb kernel: [sysenter_past_esp+86/121] sysenter_past_esp+0x56/0x79 Dec 9 11:15:34 srvweb kernel: [__xfrm_state_bump_genids+83/339] __xfrm_state_bump_genids+0x53/0x153 Dec 9 11:15:34 srvweb kernel: === Dec 9 11:17:13 srvweb kernel: BUG: warning at kernel/vserver/proc.c:398/proc_vx_info_read() Dec 9 11:17:13 srvweb kernel: [dump_trace+107/417] dump_trace+0x6b/0x1a1 Dec 9 11:17:13 srvweb kernel: [show_trace_log_lvl+23/43] show_trace_log_lvl+0x17/0x2b Dec 9 11:17:13 srvweb kernel: [__func__.0+3843/287512] 0xc0326c7b Dec 9 11:17:13 srvweb kernel: DWARF2 unwinder stuck at 0xc0326c7b Dec 9 11:17:13 srvweb kernel: Dec 9 11:17:13 srvweb kernel: Leftover inexact backtrace: Dec 9 11:17:13 srvweb kernel: Dec 9 11:17:13 srvweb kernel: [show_trace+15/17] show_trace+0xf/0x11 Dec 9 11:17:13 srvweb kernel: [dump_stack+19/21] dump_stack+0x13/0x15 Dec 9 11:17:13 srvweb kernel: [proc_vx_info_read+90/222] proc_vx_info_read+0x5a/0xde Dec 9 11:17:13 srvweb kernel: [vfs_read+138/308] vfs_read+0x8a/0x134 Dec 9 11:17:13 srvweb kernel: [sys_read+65/103] sys_read+0x41/0x67 Dec 9 11:17:13 srvweb kernel: [sysenter_past_esp+86/121] sysenter_past_esp+0x56/0x79 Dec 9 11:17:13 srvweb kernel: [__xfrm_state_bump_genids+83/339] __xfrm_state_bump_genids+0x53/0x153 Dec 9 11:17:13 srvweb kernel: === Patrick ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Bug again on 2.6.19
Hello dan
By loosing context i want to say :
when it's ok :
srvweb:/var/log# vserver-stat
CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME
0 82 986.7M 220.4M 4m15s84 1m41s00 2h49m11 root server
20 18 424.1M 117.1M 0m10s24 0m01s12 2h48m00 vweb1
21 15 729.1M 107M 0m02s70 0m01s10 2h05m32 vweb2
22 10 63.6M 22.4M 0m00s50 0m00s50 2h05m14 vweb3
when it loose context :
srvweb:/var/log# vserver-stat
CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME
0 82 986.7M 220.4M 4m15s84 1m41s00 2h49m11 root server
20 18 424.1M 117.1M 0m10s24 0m01s12 2h48m00
21 15 729.1M 107M 0m02s70 0m01s10 2h05m32
22 10 63.6M 22.4M 0m00s50 0m00s50 2h05m14
And of course(?) i can't enter anymore in the vserver when it doesn't appear
in vserver-stat. But the processes attached to this vserver continue to run.
This morning Bertl told me to launch testme.sh : the result is ok.
srvweb:/usr/local# ./testme.sh
Linux-VServer Test [V0.16] Copyright (C) 2003-2006 H.Poetzl
chcontext is working.
chbind is working.
Linux 2.6.19-vs2.1.1.4 #2 SMP Sat Dec 9 11:42:13 CET 2006 i686
Ea 0.30.212 273/glibc (DSa) compat,v11,fscompat,v13,net,v21,oldproc,olduts
VCI: 0002:0102 273 03000416 (TbLgnP)
---
[000]# succeeded.
[001]# succeeded.
[011]# succeeded.
[031]# succeeded.
[101]# succeeded.
[102]# succeeded.
[201]# succeeded.
[202]# succeeded.
I've REcompiled util-vservers-0.30.212-rc5 with enable-apis=NOLEGACY. It
works for the moment In the previous compil i had left the default
available apis :
v13,net,v21.
srvweb:/usr/local# vserver-info
Versions:
Kernel: 2.6.19-vs2.1.1.4
VS-API: 0x00020102
util-vserver: 0.30.212-rc5; Dec 9 2006, 12:38:30
Features:
CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13)
CPPFLAGS: ''
CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W'
CXXFLAGS:
'-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0'
build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
Use dietlibc: yes
Build C++ programs: yes
Build C99 programs: yes
Available APIs: compat,v11,fscompat,v13,net,v21,oldproc,olduts
ext2fs Source: e2fsprogs
syscall(2) invocation: alternative
vserver(2) syscall#: 273/glibc
Paths:
prefix: /usr/local
sysconf-Directory: ${prefix}/etc
cfg-Directory: ${prefix}/etc/vservers
initrd-Directory: $(sysconfdir)/init.d
pkgstate-Directory: ${prefix}/var/run/vservers
vserver-Rootdir: /vservers
Patrick
- Original Message -
From: Daniel Hokka Zakrisson [EMAIL PROTECTED]
To: vserver@list.linux-vserver.org
Sent: Saturday, December 09, 2006 1:52 PM
Subject: Re: [Vserver] Bug again on 2.6.19
[EMAIL PROTECTED] wrote:
Hello all
I try util-vservers-0.30.212-rc5 with patch-vs-2.1.1.4.diff on kernel
2.6.19
:
And a few minutes later after starting vservers, i loose their context
and
got this message in syslog :
Lose their context? What does that mean exactly?
Dec 9 11:15:34 srvweb kernel: BUG: warning at
kernel/vserver/proc.c:398/proc_vx_info_read()
Dec 9 11:15:34 srvweb kernel: [dump_trace+107/417]
dump_trace+0x6b/0x1a1
Dec 9 11:15:34 srvweb kernel: [show_trace_log_lvl+23/43]
show_trace_log_lvl+0x17/0x2b
Dec 9 11:15:34 srvweb kernel: [__func__.0+3843/287512] 0xc0326c7b
Dec 9 11:15:34 srvweb kernel: DWARF2 unwinder stuck at 0xc0326c7b
Dec 9 11:15:34 srvweb kernel:
Dec 9 11:15:34 srvweb kernel: Leftover inexact backtrace:
Dec 9 11:15:34 srvweb kernel:
Dec 9 11:15:34 srvweb kernel: [show_trace+15/17] show_trace+0xf/0x11
Dec 9 11:15:34 srvweb kernel: [dump_stack+19/21] dump_stack+0x13/0x15
Dec 9 11:15:34 srvweb kernel: [proc_vx_info_read+90/222]
proc_vx_info_read+0x5a/0xde
Dec 9 11:15:34 srvweb kernel: [vfs_read+138/308] vfs_read+0x8a/0x134
Dec 9 11:15:34 srvweb kernel: [sys_read+65/103] sys_read+0x41/0x67
Dec 9 11:15:34 srvweb kernel: [sysenter_past_esp+86/121]
sysenter_past_esp+0x56/0x79
Dec 9 11:15:34 srvweb kernel: [__xfrm_state_bump_genids+83/339]
__xfrm_state_bump_genids+0x53/0x153
Dec 9 11:15:34 srvweb kernel: ===
This is probably a race in the proc-code that we haven't been able to
track down yet, but if you have a sure-fire way to reproduce it, that
would help a lot.
--
Daniel Hokka Zakrisson
GPG id: 06723412
GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412
___
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] Just for info about 2.6.19
Hello,
I've tried util-vserver-0.30.212 with kernel-2.6.19: compil ok, starting
vservers ok . Just a little bug :
trying vserver vweb1 enter : ok but the prompt indicates always vweb3 as i'm
in vweb1's context :
srvweb:/usr/local/util-vserver-0.30.212-rc2# vserver vweb1 enter
WARNING: can not find configuration, assuming legacy method
ipv4root is now 192.168.0.230
New security context is 49152
vweb3:/# ip addr
2: eth0: BROADCAST,MULTICAST,UP,1 mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:16:17:1a:69:87 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.230/24 brd 192.168.0.255 scope global secondary
eth0:vweb1
vweb3:/# exit
logout
srvweb:/usr/local/util-vserver-0.30.212-rc2# vserver vweb3 enter
WARNING: can not find configuration, assuming legacy method
ipv4root is now 192.168.0.232
New security context is 49154
vweb3:/# ip addr
2: eth0: BROADCAST,MULTICAST,UP,1 mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:16:17:1a:69:87 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.232/24 brd 192.168.0.255 scope global secondary
eth0:vweb3
vweb3:/#
Patrick
- Original Message -
From: Herbert Poetzl [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: vserver@list.linux-vserver.org
Sent: Friday, December 01, 2006 8:20 PM
Subject: Re: [Vserver] Just for info about 2.6.19
On Fri, Dec 01, 2006 at 06:48:33PM +0100, [EMAIL PROTECTED] wrote:
Hello,
I'm using util-vserver 0.30.211
which does not support 2.6.19 kernels, because
mainline changed in regard of virtualization
in back then 'unexpected' ways ...
please update to 0.30.212+
best,
Herbert
srvweb:/etc/bind# vserver-info
Versions:
Kernel: 2.6.18.3-vs2.1.1.2
VS-API: 0x00020102
util-vserver: 0.30.211; Oct 18 2006, 14:38:29
Features:
CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13)
CPPFLAGS: ''
CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W'
CXXFLAGS:
'-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0'
build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
Use dietlibc: yes
Build C++ programs: yes
Build C99 programs: yes
Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts
ext2fs Source: e2fsprogs
syscall(2) invocation: alternative
vserver(2) syscall#: 273/glibc
Paths:
prefix: /usr/local
sysconf-Directory: ${prefix}/etc
cfg-Directory: ${prefix}/etc/vservers
initrd-Directory: $(sysconfdir)/init.d
pkgstate-Directory: ${prefix}/var/run/vservers
vserver-Rootdir: /opt/vservers
Assumed 'SYSINFO' as no other option given; try '--help' for more
information.
===
srvweb:/etc/bind# vserver-stat
CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME
0 84 985.7M 219.2M 4m17s11 1m51s38 6h50m05 root server
49152 18 421M 119.7M 0m07s54 0m01s11 6h49m08
49153 16 838.4M 85.8M 0m03s14 0m03s62 6h48m54
49154 1166M 23.4M 0m00s33 0m00s40 6h48m41
Patrick
- Original Message -
From: Daniel Hokka Zakrisson [EMAIL PROTECTED]
To: vserver@list.linux-vserver.org
Sent: Friday, December 01, 2006 6:02 PM
Subject: Re: [Vserver] Just for info about 2.6.19
[EMAIL PROTECTED] wrote:
Hello
I try new release today (patch-2.6.19-vs2.1.x-t1.diff) but it
doesn't
work
properly : boot ok, starting vserver ok but it doesn't switch
context i
think.
I try to explain :
my master is : srvweb
So i try :
srvweb:/#vserver vweb1 start
srvweb:/#vserver vweb2 start
srvweb:/#vserver vweb3 start
All seems to work fine but suddenly the prompt is changing :
vweb3:/#
whereas i didn't enter into vserver !!! The context-ID are OK in
/usr/local/var/run/vservers/vwebX.ctx
but i can't never get out from vweb3 !!! i've seen on the tty1 a
message :
get_ctx_id() and the prompt was changing alone whereas i wasn't
loggued
on
this tty.
Then i enter into vserver vweb3 and i try to leave it with CTRL-D :
it
stays
in vweb3 in the home directory of user with which i connect to the
master !
I can never come back to the master
I think it's a very little bug for you :-)
Thanks again for your great job.
Patrick
You _are_ using at least util-vserver 0.30.212-rc1, right? That's when
the initial 2.6.19 support was added, and (from what I hear) it works
for most things, but some are broken (e.g. chcontext not creating a
new
UTS namespace).
--
Daniel Hokka Zakrisson
GPG id: 06723412
GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412
___
Vserver mailing list
Re: [Vserver] Just for info about 2.6.19
Hello I try new release today (patch-2.6.19-vs2.1.x-t1.diff) but it doesn't work properly : boot ok, starting vserver ok but it doesn't switch context i think. I try to explain : my master is : srvweb So i try : srvweb:/#vserver vweb1 start srvweb:/#vserver vweb2 start srvweb:/#vserver vweb3 start All seems to work fine but suddenly the prompt is changing : vweb3:/# whereas i didn't enter into vserver !!! The context-ID are OK in /usr/local/var/run/vservers/vwebX.ctx but i can't never get out from vweb3 !!! i've seen on the tty1 a message : get_ctx_id() and the prompt was changing alone whereas i wasn't loggued on this tty. Then i enter into vserver vweb3 and i try to leave it with CTRL-D : it stays in vweb3 in the home directory of user with which i connect to the master ! I can never come back to the master I think it's a very little bug for you :-) Thanks again for your great job. Patrick - Original Message - From: Herbert Poetzl [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: vserver@list.linux-vserver.org Sent: Thursday, November 30, 2006 7:52 PM Subject: Re: [Vserver] Just for info about 2.6.19 On Thu, Nov 30, 2006 at 04:35:31PM +0100, [EMAIL PROTECTED] wrote: Hello, I've tested patch-2.6.19-rc6-vs2.1.1-t3.diff on linux-2.6.19 but it doesn't seem to apply properly : srvweb:/usr/src/linux-2.6.19# patch -p1 ../patch-2.6.19-rc6-vs2.1.1-t3.diff patching file Documentation/vserver/debug.txt patching file Makefile Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej patching file arch/arm/Kconfig Hunk #1 succeeded at 935 (offset 2 lines). . patching file arch/i386/kernel/process.c Hunk #1 succeeded at 300 (offset 2 lines). Hunk #2 succeeded at 354 (offset 2 lines). patching file arch/i386/kernel/traps.c Hunk #2 succeeded at 373 (offset 4 lines). Hunk #3 succeeded at 463 (offset 4 lines). Hunk #4 succeeded at 501 (offset 4 lines). ... patching file arch/x86_64/kernel/process.c Hunk #2 succeeded at 302 (offset 2 lines). ... patching file arch/x86_64/kernel/traps.c Hunk #1 succeeded at 487 (offset 14 lines). Hunk #2 succeeded at 658 (offset 14 lines). Hunk #3 succeeded at 759 (offset 14 lines). patching file fs/proc/base.c Hunk #2 succeeded at 974 (offset 1 line). Hunk #3 succeeded at 1028 (offset 1 line). Hunk #4 succeeded at 1047 (offset 1 line). Hunk #5 succeeded at 1417 (offset 1 line). Hunk #6 succeeded at 1628 (offset 1 line). Hunk #7 succeeded at 1769 (offset 1 line). Hunk #8 succeeded at 1809 (offset 1 line). Hunk #9 succeeded at 1952 (offset 1 line). Hunk #10 succeeded at 2156 (offset 1 line). Hunk #11 succeeded at 2198 (offset 1 line). Hunk #12 succeeded at 2295 (offset 1 line). patching file fs/reiserfs/file.c Hunk #1 succeeded at 1575 (offset 1 line). Hunk #2 succeeded at 1590 (offset 1 line). patching file include/linux/nsproxy.h Hunk #1 succeeded at 51 with fuzz 1 (offset 2 lines). patching file kernel/fork.c Hunk #15 succeeded at 1404 (offset -1 lines). patching file net/ipv4/udp.c Hunk #5 succeeded at 1472 (offset 9 lines). Hunk #6 succeeded at 1492 (offset 9 lines). Hope that helps. there will be a 2.6.19 release shortly ... please if you 'test' it, let me know how it goes TIA, Herbert Regards, Patrick ___ 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] Just for info about 2.6.19
Hello,
I'm using util-vserver 0.30.211
srvweb:/etc/bind# vserver-info
Versions:
Kernel: 2.6.18.3-vs2.1.1.2
VS-API: 0x00020102
util-vserver: 0.30.211; Oct 18 2006, 14:38:29
Features:
CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13)
CPPFLAGS: ''
CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W'
CXXFLAGS:
'-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0'
build/host: i686-pc-linux-gnu/i686-pc-linux-gnu
Use dietlibc: yes
Build C++ programs: yes
Build C99 programs: yes
Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts
ext2fs Source: e2fsprogs
syscall(2) invocation: alternative
vserver(2) syscall#: 273/glibc
Paths:
prefix: /usr/local
sysconf-Directory: ${prefix}/etc
cfg-Directory: ${prefix}/etc/vservers
initrd-Directory: $(sysconfdir)/init.d
pkgstate-Directory: ${prefix}/var/run/vservers
vserver-Rootdir: /opt/vservers
Assumed 'SYSINFO' as no other option given; try '--help' for more
information.
===
srvweb:/etc/bind# vserver-stat
CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME
0 84 985.7M 219.2M 4m17s11 1m51s38 6h50m05 root server
49152 18 421M 119.7M 0m07s54 0m01s11 6h49m08
49153 16 838.4M 85.8M 0m03s14 0m03s62 6h48m54
49154 1166M 23.4M 0m00s33 0m00s40 6h48m41
Patrick
- Original Message -
From: Daniel Hokka Zakrisson [EMAIL PROTECTED]
To: vserver@list.linux-vserver.org
Sent: Friday, December 01, 2006 6:02 PM
Subject: Re: [Vserver] Just for info about 2.6.19
[EMAIL PROTECTED] wrote:
Hello
I try new release today (patch-2.6.19-vs2.1.x-t1.diff) but it doesn't
work
properly : boot ok, starting vserver ok but it doesn't switch context i
think.
I try to explain :
my master is : srvweb
So i try :
srvweb:/#vserver vweb1 start
srvweb:/#vserver vweb2 start
srvweb:/#vserver vweb3 start
All seems to work fine but suddenly the prompt is changing : vweb3:/#
whereas i didn't enter into vserver !!! The context-ID are OK in
/usr/local/var/run/vservers/vwebX.ctx
but i can't never get out from vweb3 !!! i've seen on the tty1 a
message :
get_ctx_id() and the prompt was changing alone whereas i wasn't loggued
on
this tty.
Then i enter into vserver vweb3 and i try to leave it with CTRL-D : it
stays
in vweb3 in the home directory of user with which i connect to the
master !
I can never come back to the master
I think it's a very little bug for you :-)
Thanks again for your great job.
Patrick
You _are_ using at least util-vserver 0.30.212-rc1, right? That's when
the initial 2.6.19 support was added, and (from what I hear) it works
for most things, but some are broken (e.g. chcontext not creating a new
UTS namespace).
--
Daniel Hokka Zakrisson
GPG id: 06723412
GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412
___
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
[Vserver] Just for info about 2.6.19
Hello, I've tested patch-2.6.19-rc6-vs2.1.1-t3.diff on linux-2.6.19 but it doesn't seem to apply properly : srvweb:/usr/src/linux-2.6.19# patch -p1 ../patch-2.6.19-rc6-vs2.1.1-t3.diff patching file Documentation/vserver/debug.txt patching file Makefile Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej patching file arch/arm/Kconfig Hunk #1 succeeded at 935 (offset 2 lines). . patching file arch/i386/kernel/process.c Hunk #1 succeeded at 300 (offset 2 lines). Hunk #2 succeeded at 354 (offset 2 lines). patching file arch/i386/kernel/traps.c Hunk #2 succeeded at 373 (offset 4 lines). Hunk #3 succeeded at 463 (offset 4 lines). Hunk #4 succeeded at 501 (offset 4 lines). ... patching file arch/x86_64/kernel/process.c Hunk #2 succeeded at 302 (offset 2 lines). ... patching file arch/x86_64/kernel/traps.c Hunk #1 succeeded at 487 (offset 14 lines). Hunk #2 succeeded at 658 (offset 14 lines). Hunk #3 succeeded at 759 (offset 14 lines). patching file fs/proc/base.c Hunk #2 succeeded at 974 (offset 1 line). Hunk #3 succeeded at 1028 (offset 1 line). Hunk #4 succeeded at 1047 (offset 1 line). Hunk #5 succeeded at 1417 (offset 1 line). Hunk #6 succeeded at 1628 (offset 1 line). Hunk #7 succeeded at 1769 (offset 1 line). Hunk #8 succeeded at 1809 (offset 1 line). Hunk #9 succeeded at 1952 (offset 1 line). Hunk #10 succeeded at 2156 (offset 1 line). Hunk #11 succeeded at 2198 (offset 1 line). Hunk #12 succeeded at 2295 (offset 1 line). patching file fs/reiserfs/file.c Hunk #1 succeeded at 1575 (offset 1 line). Hunk #2 succeeded at 1590 (offset 1 line). patching file include/linux/nsproxy.h Hunk #1 succeeded at 51 with fuzz 1 (offset 2 lines). patching file kernel/fork.c Hunk #15 succeeded at 1404 (offset -1 lines). patching file net/ipv4/udp.c Hunk #5 succeeded at 1472 (offset 9 lines). Hunk #6 succeeded at 1492 (offset 9 lines). Hope that helps. Regards, Patrick ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] postgres 8.1
I am running debian etch vserver with postgres 8.1 installed. I have Enable options stats_start_collector and stats_row_level. However when postgres starts i get thefollowing in the log. LOG: could not resolve localhost: Name or service not known LOG: disabling statistics collector for lack of working socket LOG: database system was shut down at 2006-10-09 08:05:02 CDT LOG: checkpoint record is at 0/10AA55C LOG: redo record is at 0/10AA55C; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 63483; next OID: 20444 LOG: next MultiXactId: 1; next MultiXactOffset: 0 WARNING: autovacuum not started because of misconfiguration HINT: Enable options stats_start_collector and stats_row_level. LOG: database system is ready LOG: transaction ID wrap limit is 2147484146, limited by database postgres LOG: incomplete startup packet Thanks in advance for any hepl! henryg ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] postgres 8.1
On Mon, 9 Oct 2006 16:01:49 +0200 Guenther Fuchs [EMAIL PROTECTED] wrote: Hi there, on Monday, October 9, 2006 at 3:29:55 PM there was posted: vhn LOG: could not resolve localhost: Name or service not vhn known put localhost 127.0.0.1 (or better: your guest main IP) into the file /etc/hosts in your guest - this should solve your problem. I have adeded localhost pup.ip.x.x to /etc/host. it now resolves localhost but autovacuum still does not start. I have multiple vserver guest, I have all traffic that is not explicitedly allowed blocked on the loopback interface. I am using fwbuilder to manage the firewall. I am not sure which ports to allow for udp socket for stat collector. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] postgres 8.1
On Mon, 09 Oct 2006 10:10:38 -0500 [EMAIL PROTECTED] wrote: On Mon, 9 Oct 2006 16:01:49 +0200 Guenther Fuchs [EMAIL PROTECTED] wrote: Hi there, on Monday, October 9, 2006 at 3:29:55 PM there was posted: vhn LOG: could not resolve localhost: Name or service not vhn known put localhost 127.0.0.1 (or better: your guest main IP) into the file /etc/hosts in your guest - this should solve your problem. I have adeded localhost pup.ip.x.x to /etc/host. it now resolves localhost but autovacuum still does not start. I have multiple vserver guest, I have all traffic that is not explicitedly allowed blocked on the loopback interface. I am using fwbuilder to manage the firewall. I am not sure which ports to allow for udp socket for stat collector. This is the log now! LOG: could not send test message on socket for statistics collector: Operation not permitted LOG: disabling statistics collector for lack of working socket LOG: database system was shut down at 2006-10-09 10:13:59 CDT LOG: checkpoint record is at 0/10AA648 LOG: redo record is at 0/10AA648; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 66579; next OID: 20444 LOG: next MultiXactId: 1; next MultiXactOffset: 0 WARNING: autovacuum not started because of misconfiguration HINT: Enable options stats_start_collector and stats_row_level. LOG: database system is ready LOG: transaction ID wrap limit is 2147484146, limited by database postgres LOG: incomplete startup packet ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] util-vserver 0.30.211 released
Hello Daniel I've tried to compile the new util-vserver 0.30.211) in a vmware debian-sarge 3.1 . Linux version 2.6.18-vs2.1.1-rc35-t1 ([EMAIL PROTECTED]) (version gcc 3.3.5 (Debian 1:3.3.5-13)) #3 PREEMPT Fri Oct 6 13:15:24 CEST 2006 I ran ./configure --enable-apis=ALL --with-vrootdir=/opt/vservers but when i launch make, i got this error : rm -f src/vdlimit src/vdlimit /bin/sed -e '...' pathconfig.h.pathsubst pathconfig.h make all-recursive make[1]: entrant dans le répertoire « /usr/local/util-vserver-0.30.211 » Making all in . make[2]: entrant dans le répertoire « /usr/local/util-vserver-0.30.211 » if diet -Os gcc -DHAVE_CONFIG_H -I. -I. -I. -I ./lib -I ./ensc_wrappers -D_GNU_SOURCE -D_REENTRANT -DNDEBUG -g -O2 -std=c99 -Wall -pedantic -W -MT lib/lib_libvserver_a-syscall.o -MD -MP -MF lib/.deps/lib_libvserver_a-syscall.Tpo -c -o lib/lib_libvserver_a-syscall.o `test -f 'lib/syscall.c' || echo './'`lib/syscall.c; \ then mv -f lib/.deps/lib_libvserver_a-syscall.Tpo lib/.deps/lib_libvserver_a-syscall.Po; else rm -f lib/.deps/lib_libvserver_a-syscall.Tpo; exit 1; fi In file included from lib/syscall.c:40: lib/syscall-legacy.hc: Dans la fonction « set_ipv4root_rev0 »: lib/syscall-legacy.hc:84: attention : asm operand 1 probably doesn't match constraints lib/syscall-legacy.hc: Dans la fonction « set_ipv4root_rev1 »: lib/syscall-legacy.hc:85: attention : asm operand 1 probably doesn't match constraints lib/syscall-legacy.hc: Dans la fonction « set_ipv4root_rev2 »: lib/syscall-legacy.hc:86: attention : asm operand 1 probably doesn't match constraints lib/syscall-legacy.hc: Dans la fonction « set_ipv4root_rev3 »: lib/syscall-legacy.hc:87: attention : asm operand 1 probably doesn't match constraints lib/syscall-legacy.hc: Dans la fonction « new_s_context_rev0 »: lib/syscall-legacy.hc:103: attention : asm operand 1 probably doesn't match constraints lib/syscall-legacy.hc: Dans la fonction « set_ipv4root_rev0 »: lib/syscall-legacy.hc:84: error: impossible constraint in `asm' lib/syscall-legacy.hc:84: attention : `__res' might be used uninitialized in this function make[2]: *** [lib/lib_libvserver_a-syscall.o] Erreur 1 make[2]: quittant le répertoire « /usr/local/util-vserver-0.30.211 » make[1]: *** [all-recursive] Erreur 1 make[1]: quittant le répertoire « /usr/local/util-vserver-0.30.211 » make: *** [all] Erreur 2 If you need more infos tell me. Thanks, Patrick - Original Message - From: Daniel Hokka Zakrisson [EMAIL PROTECTED] To: vserver@list.linux-vserver.org Sent: Saturday, October 07, 2006 9:23 PM Subject: [Vserver] util-vserver 0.30.211 released Hello everyone! This new release comes with a few new features, a lot of fixes, and a new (co-)maintainer. Among the new features are: - the build method template, which builds guests from tarball(s), cpio(s) and/or dump(s). - the build method fai, which builds guests using Debian's Fully Automatic Installation[1], original patch and testing by Sam Vilain. - support for CPUSETs in the configuration, to limit guests to certain CPUs, patch by Jan Rekorajski. - a namespace cleanup in userspace implementation, by Bastian Blank. - a delete method to remove guests, patch by Thomas Champagne. - vlogin, a terminal proxy which creates a psuedo-tty on the inside of the guest when you use vserver guest enter, patch by Benedikt Böhm. - support for an initialize script, to (for instance) create device nodes required for the guest's root mount, patch by Herbert Pötzl. - FC5 and FC6 (in theory) support. Among the fixes, we find things like: - vattribute doesn't reset all bcaps when setting ccaps/one bcap. - chcontext lets you grant more caps than --secure allows. - start-vservers --all actually means all guests, not just the unmarked ones. - make namespaces work on s390/sparc. - an update to Herbert's shiny10 alternative syscall implementation. - make vrpm/vapt-get/vyum run inside the network context. - vserver guest suexec lets you specify usernames on 2.6 kernels. - RPM-based builds on CentOS/RHEL 4.4 should work. - centos42 was changed to centos4, which should point at the latest 4.x release at all times. - vshelper works correctly with legacy support turned off in the kernel. - Gentoo is now as supported as any other distribution. - having the guest's / mount in the fstab file should work again (previously stop/enter would fail). - the save_ctxinfo: execv(): No such file or directory on RH-based systems should be resolved. To see the complete list of changes, see the ChangeLog inside the tarball. Get it while it's hot, in either a gzip- or bzip2-compressed tarball, from http://ftp.linux-vserver.org/pub/utils/util-vserver/, which is the new official location. I have signed the tarballs, so if you're verifying them you'll have to import my key (available from pgp.mit.edu). [1] http://www.informatik.uni-koeln.de/fai/ -- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F
[Vserver] Bug linux-2.6.17.13 ?
Hello all I'm new member on this mailing-list but i use linux-vserver since 2 years. I've a problem today with kernel-2.6.17.13 patch-2.6.17.13-vs2.1.1-rc34.diff but I am not sure that is in connection with the patch : My config : - debian-3.1 stable + sources backports. - preceding core : linux-2.6.17.11 patch-2.6.17.11-vs2.1.1-rc29.diff : works fine with 3 virtual servers. - hardware : Pentium 805D - 2Go DDRII - MotherBoard : MSI 945P Neo2 - util-vserver-0.30.210 - Compilation without problem BUT just before i can login these messages appears and are repeated : Sep 15 09:50:02 srvweb kernel: CPU:1 Sep 15 09:50:02 srvweb kernel: EIP:0060:[]Not tainted VLI Sep 15 09:50:02 srvweb kernel: EFLAGS: 00010286 (2.6.17.13-vs2.1.1-rc34 #1) Sep 15 09:50:02 srvweb kernel: EIP is at rest_init+0x3feffd68/0x2f Sep 15 09:50:02 srvweb kernel: eax: f7636d00 ebx: f73cdf64 ecx: 0003 edx: f7636ed8 Sep 15 09:50:02 srvweb kernel: esi: edi: f7636d00 ebp: c210d4c0 esp: f73cdedc Sep 15 09:50:02 srvweb kernel: ds: 007b es: 007b ss: 0068 Sep 15 09:50:02 srvweb kernel: Process ps (pid: 1982[#1], threadinfo=f73cc000 task=c2146580) Sep 15 09:50:02 srvweb kernel: Stack: c015b5b4 f74f4738 f73cdf64 c015b615 f73cdf64 f73cdf04 Sep 15 09:50:02 srvweb kernel:f73cc000 c015b68d f74f0090 c210d4c0 f73cdf24 0004 f7be1880 0001 Sep 15 09:50:02 srvweb kernel:0001 c0332600 f7be1880 0041 c0332600 c01858cb f6ff4000 Sep 15 09:50:02 srvweb kernel: Call Trace: Sep 15 09:50:02 srvweb kernel: c015b5b4 generic_fillattr+0xd4/0x10e c015b615 vfs_getattr+0x27/0x75 Sep 15 09:50:02 srvweb kernel: c015b68d vfs_stat_fd+0x2a/0x3c c01858cb show_tty_driver+0x146/0x14f Sep 15 09:50:02 srvweb kernel: c01c52b7 copy_to_user+0x33/0x3b c018144d proc_delete_inode+0x0/0x84 Sep 15 09:50:02 srvweb kernel: c015bc30 sys_stat64+0xf/0x23 c010269f sysenter_past_esp+0x54/0x75 Sep 15 09:50:02 srvweb kernel: Code: Bad EIP value. Sep 15 09:50:02 srvweb kernel: EIP: [] rest_init+0x3feffd68/0x2f SS:ESP 0068:f73cdedc Sep 15 09:50:04 srvweb kernel: 1BUG: unable to handle kernel NULL pointer dereference at virtual address Sep 15 09:50:04 srvweb kernel: printing eip: Sep 15 09:50:04 srvweb kernel: Sep 15 09:50:04 srvweb kernel: *pde = Sep 15 09:50:04 srvweb kernel: Oops: [#2] Sep 15 09:50:04 srvweb kernel: PREEMPT SMP Sep 15 09:50:04 srvweb kernel: Modules linked in: ipt_iprange iptable_filter ip_tables x_tables dm_mod w83627ehf i2c_isa dummy ipv6 r8169 rtc Can anybody helps ? Thanks by advance and excuse me but i'm not very fluent in english :-) Patrick ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Guest IP address is not accessible from outside
Hello. When I try to connect to guest virtual machine IP address from outside, connection goes to host machine, and I cannot connect to guest at all. Details are attached below. I installed linux-vserver over CentOS 4 x86_64 according strictly to instructions here: http://linux-vserver.org/CentOS_HowTo I used the following create command: # vserver hosting build -m yum --hostname hosting --interface hosting=eth0:213.248.62.106/24 --initstyle sysv --context 500 --force -- -d centos4 So, guest OS (hosting) has assigned IP 213.248.62.106 Host machine (delta) has IP address 213.248.62.107 on eth0. Something goes wrong with networking. [EMAIL PROTECTED] 00]# vserver hosting start Starting system logger:[ OK ] Starting kernel logger:[ OK ] [EMAIL PROTECTED] 00]# ifconfig eth0 Link encap:Ethernet HWaddr 00:30:48:75:13:D2 inet addr:213.248.62.107 Bcast:213.248.62.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe75:13d2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:322664 errors:0 dropped:0 overruns:0 frame:0 TX packets:2134 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:20858801 (19.8 MiB) TX bytes:233103 (227.6 KiB) Base address:0x3000 Memory:dd30-dd32 eth0:host Link encap:Ethernet HWaddr 00:30:48:75:13:D2 inet addr:213.248.62.106 Bcast:213.248.62.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Base address:0x3000 Memory:dd30-dd32 You see, 213.248.62.106 was added as alias to eth0. Maybe it is OK, let's go forward: [EMAIL PROTECTED] 00]# vserver hosting enter [EMAIL PROTECTED] /]# ifconfig eth0 Link encap:Ethernet HWaddr 00:30:48:75:13:D2 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:323267 errors:0 dropped:0 overruns:0 frame:0 TX packets:2175 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:20898570 (19.9 MiB) TX bytes:238393 (232.8 KiB) Base address:0x3000 Memory:dd30-dd32 eth0:host Link encap:Ethernet HWaddr 00:30:48:75:13:D2 inet addr:213.248.62.106 Bcast:213.248.62.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Base address:0x3000 Memory:dd30-dd32 You see, IP address in guest OS is OK - 213.248.62.106. And - Internet from virtual machine is fully accessible, I can use yum, for example. But, when I try to connect to guest IP (213.248.62.106) from outside (from other machines in Internet), I really connect to HOST machine, NOT to virtual! It is very, very strange! Moreover, [EMAIL PROTECTED] /]# telnet 127.0.0.1 22 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. SSH-1.99-OpenSSH_3.9p1 You see, I connected from virtual machine to 127.0.0.1, SSH port, and answer was - OK. So, I connected to HOST machine AGAIN, because virtual machine does not have SSH server at all. 127.0.0.1 in GUEST OS connects us to HOST machine? Strange, very strange! What do I do incorrectly? P.S. I also tried to remove /etc/vservers/hosting/interfaces/00/name (it contains hosting, guest name). After that there is NO alias 213.248.62.106 in host machine ifconfig, but - also there is NO ifconfig output in GUEST OS. I tried service network start in GUEST machine, creating /etc/sysconfig/network-scripts/ifcfg-eth0 file before, but - when I run service network start in guest, I have error message about already used interface 213.248.62.106. At last, I tried to remove /etc/vservers/hosting/interfaces/00/ totally and operate /etc/sysconfig/network-scripts/ifcfg-eth0 in guest only, but - it does not work too (service network start finished OK, but following ifconfig shows nothing). Please tell how to configure networking in linux-vserver, to be able to connect to virtual machine from outside. -- B.r, Dmitry Koteroff Chief programmer, http://host-ing.ru ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Problem running 2.4.23-vs1.22 - 2.4.24-vs1.22 - 2.4.24-vs1.23
Hello again: This email is in reference to a problem I reported back in December 18, 2003. Well, due to shortage of time as my real job kept me very busy, I never got an opportunity to try vs1.21 on my kernel 2.4.23 as suggested by Herbert. Just yesterday I decided to upgrade my kernel to 2.4.24 which I patched with vs1.22 in hopes of making it work, but it didn't. Now that I'm running 2.4.24-vs1.22, I'm still having the same problem I was experiencing back in December: -- Jan 10 10:14:14 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: cannot bind: Address already in use Jan 10 10:14:14 moses sm-mta[3237]: daemon MTA-RX: problem creating SMTP socket Jan 10 10:14:19 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: cannot bind: Address already in use Jan 10 10:14:19 moses sm-mta[3237]: daemon MTA-RX: problem creating SMTP socket Jan 10 10:14:19 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: server SMTP socket wedged: exiting -- Here is the output of lsof -i (grep sendmail) where both the HOST and CLIENT should show the same output. - HOST --- sendmail 3165 root4u IPv4 56533 TCP *:25 (LISTEN) sendmail 3165 root5u IPv4 56534 TCP *:587 (LISTEN) sendmail 3167 root4u IPv4 56531 TCP localhost:10025 (LISTEN) - CLIENT --- sendmail 3240 root4u IPv4 58614 TCP christngraphics.com:10025 (LISTEN) The new question is, how do I back out the vs1.22 patch in order to try vs1.21? Thanks in advance, RV On Thu, Dec 18, 2003 at 12:01:34AM -0500, VServer wrote: Hello list: What a great project this is. Hats off guys. I recently found the vserver project and quickly decided to setup my box to take some abuse... This was the logical solution since there are too many computers in this room already. sounds great! I have been running linux-vserver version 2.4.23-vs1.20 on a athlon 1.2 MHz with 1.5 GB Ram with Slackware 9.1 as the OS. hmm, don't know about slackware, but the rest sounds good to me ... I configured 3 vserver guests (2 running Slackware Live and 1 running Sentry Linux) to handle email for 3 domains. Sendmail and the virus/spam scanning system have been running beautifully on this setup. okay, so it works with vs1.20 ... I attempted to run 2.4.23-vs1.22 as soon as it came out but after the reboot, sendmail started to error out on me. I wrote a rc.vservers script that executes on boot to bring up the vserver clients. there is a runlevel script included in the userspace tools (/etc/init.d/vservers) this might be working for you too ... Once Sendmail starts up on the clients, I get the following error repeated every five minutes: Dec 17 21:41:40 salvation sm-mta[1867]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: cannot bind: Address already in use Dec 17 21:41:40 salvation sm-mta[1867]: daemon MTA-RX: problem creating SMTP socket okay, looks like the 'address/port' (whatever it might be) is already used by some other task ... I would ask you to try vs1.21, and see if this works for you, and to locate the address/port the daemon tries to bind to ... maybe you could provide the following on a web site: * output of lsof -i * your vserver configurations * your host service configuration TIA, Herbert I hope somebody can help, Ronald Vazquez ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Problem running 2.4.23-vs1.22 - 2.4.24-vs1.22 - 2.4.24-vs1.23
Hello again: This email is in reference to a problem I reported back in December 18, 2003. Well, due to shortage of time as my real job kept me very busy, I never got an opportunity to try vs1.21 on my kernel 2.4.23 as suggested by Herbert. Just yesterday I decided to upgrade my kernel to 2.4.24 which I patched with vs1.22 in hopes of making it work, but it didn't. Now that I'm running 2.4.24-vs1.22, I'm still having the same problem I was experiencing back in December: -- Jan 10 10:14:14 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: cannot bind: Address already in use Jan 10 10:14:14 moses sm-mta[3237]: daemon MTA-RX: problem creating SMTP socket Jan 10 10:14:19 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: cannot bind: Address already in use Jan 10 10:14:19 moses sm-mta[3237]: daemon MTA-RX: problem creating SMTP socket Jan 10 10:14:19 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: server SMTP socket wedged: exiting -- Here is the output of lsof -i (grep sendmail) where both the HOST and CLIENT should show the same output. - HOST --- sendmail 3165 root4u IPv4 56533 TCP *:25 (LISTEN) sendmail 3165 root5u IPv4 56534 TCP *:587 (LISTEN) sendmail 3167 root4u IPv4 56531 TCP localhost:10025 (LISTEN) - CLIENT --- sendmail 3240 root4u IPv4 58614 TCP christngraphics.com:10025 (LISTEN) The new question is, how do I back out the vs1.22 patch in order to try vs1.21? Thanks in advance, RV On Thu, Dec 18, 2003 at 12:01:34AM -0500, VServer wrote: Hello list: What a great project this is. Hats off guys. I recently found the vserver project and quickly decided to setup my box to take some abuse... This was the logical solution since there are too many computers in this room already. sounds great! I have been running linux-vserver version 2.4.23-vs1.20 on a athlon 1.2 MHz with 1.5 GB Ram with Slackware 9.1 as the OS. hmm, don't know about slackware, but the rest sounds good to me ... I configured 3 vserver guests (2 running Slackware Live and 1 running Sentry Linux) to handle email for 3 domains. Sendmail and the virus/spam scanning system have been running beautifully on this setup. okay, so it works with vs1.20 ... I attempted to run 2.4.23-vs1.22 as soon as it came out but after the reboot, sendmail started to error out on me. I wrote a rc.vservers script that executes on boot to bring up the vserver clients. there is a runlevel script included in the userspace tools (/etc/init.d/vservers) this might be working for you too ... Once Sendmail starts up on the clients, I get the following error repeated every five minutes: Dec 17 21:41:40 salvation sm-mta[1867]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA-RX: cannot bind: Address already in use Dec 17 21:41:40 salvation sm-mta[1867]: daemon MTA-RX: problem creating SMTP socket okay, looks like the 'address/port' (whatever it might be) is already used by some other task ... I would ask you to try vs1.21, and see if this works for you, and to locate the address/port the daemon tries to bind to ... maybe you could provide the following on a web site: * output of lsof -i * your vserver configurations * your host service configuration TIA, Herbert I hope somebody can help, Ronald Vazquez ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Problem running 2.4.23-vs1.22
Thank you Herbert for the reply. I will try 1.21 soon and let you know the outcome. RV On Thursday 18 December 2003 10:15, you wrote: [EMAIL PROTECTED] ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
