[Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
Hello,
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:
---
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: Oops: 0002 [5] SMP
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: CR2: 82180f7411a6
/usr/lib/util-vserver/vserver.functions: line 895: 16787 Getötet
$_VWAIT --timeout $VSHELPER_SYNC_TIMEOUT --status-fd 3 $2 $_is_tmpdir/out
2$_is_tmpdir/err 3$_is_tmpdir/fifo
/usr/lib/util-vserver/vserver.stop: line 85: 16794 Getötet
[EMAIL PROTECTED] ${USE_VNAMESPACE:+$_VNAMESPACE --enter $S_CONTEXT -- }
$_VCONTEXT $SILENT_OPT --migrate --chroot --xid $S_CONTEXT --
[EMAIL PROTECTED]
internal error: 'vwait' exited with an unexpected status ''; I will
try to continue but be prepared for unexpected events.
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: Oops: [6] SMP
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: CR2: 82180f74119e
---
here is the content of /var/log/messages:
Jan 8 10:55:37 hal9000 kernel: PGD 0
Jan 8 10:55:37 hal9000 kernel: CPU 0
Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot dm_mirror
dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3 jbd
mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata scsi_mod
via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
Jan 8 10:55:37 hal9000 kernel: Pid: 16787, comm: vwait Not tainted
2.6.18-3-vserver-amd64 #1
Jan 8 10:55:37 hal9000 kernel: RIP: 0010:[802474d2]
[802474d2] add_wait_queue+0x29/0x43
Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810016c71ee8 EFLAGS: 00010002
Jan 8 10:55:37 hal9000 kernel: RAX: 810016c71f20 RBX: 810016c71f08 RCX:
81000f741190
Jan 8 10:55:37 hal9000 kernel: RDX: 82180f74119e RSI: 0246 RDI:
81000f741188
Jan 8 10:55:37 hal9000 kernel: RBP: fffd R08: R09:
Jan 8 10:55:37 hal9000 kernel: R10: 0040189a R11: 0202 R12:
81000f741188
Jan 8 10:55:37 hal9000 kernel: R13: 0033 R14: 001e R15:
0003
Jan 8 10:55:37 hal9000 kernel: FS: 2b6e32afc6d0()
GS:8052f000() knlGS:
Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: ES: CR0:
8005003b
Jan 8 10:55:37 hal9000 kernel: CR2: 82180f7411a6 CR3: 1376d000 CR4:
06e0
Jan 8 10:55:37 hal9000 kernel: Process vwait (pid: 16787[#0], threadinfo
810016c7, task 81001169c880)
Jan 8 10:55:37 hal9000 kernel: Stack: 810016c71f58 81000f74
7fffee1029e0 802996d4
Jan 8 10:55:37 hal9000 kernel: 81001169c880
8027fc81
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel: Call Trace:
Jan 8 10:55:37 hal9000 kernel: [802996d4] vc_wait_exit+0x5d/0x106
Jan 8 10:55:37 hal9000 kernel: [8027fc81]
default_wake_function+0x0/0xe
Jan 8 10:55:37 hal9000 kernel: [80295f87] sys_vserver+0x4ab/0x59e
Jan 8 10:55:37 hal9000 kernel: [8025ab0e] system_call+0x7e/0x83
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel: Code: 48 89 42 08 48 89 53 18 48 89 48 08 49 89
44 24 08 5b 5b 41
Jan 8 10:55:37 hal9000 kernel: RSP 810016c71ee8
Jan 8 10:55:37 hal9000 kernel: 1Unable to handle kernel paging request at
82180f74119e RIP:
Jan 8 10:55:37 hal9000 kernel: PGD 0
Jan 8 10:55:37 hal9000 kernel: CPU 0
Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot dm_mirror
dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3 jbd
mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata scsi_mod
via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
Jan 8 10:55:37 hal9000 kernel: Pid: 28327, comm: apache2 Not tainted
2.6.18-3-vserver-amd64 #1
Jan 8 10:55:37 hal9000 kernel: RIP: 0010:[8027e45e]
[8027e45e] __wake_up_common+0x24/0x68
Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810011515cc8 EFLAGS: 00010092
Jan 8 10:55:37 hal9000 kernel: RAX: 0292 RBX: 81000f741188 RCX:
Jan 8 10:55:37 hal9000 kernel: RDX: 0001 RSI: 0001 RDI:
81000f741188
Jan 8 10:55:37 hal9000 kernel: RBP: 810011515cf8 R08: 82180f74119e R09:
Jan 8 10:55:37 hal9000 kernel: R10: R11: 8100130ed268 R12:
0001
Jan 8 10:55:37 hal9000 kernel: R13:
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
Hi, okay, as it seems, I cannot recreate this here please could you make the following changes to get_task_state() There is nothing new in kernel log after changes, oops in attachement. Jarek Dylag Jan 3 13:02:33 v2140 [10966.004095] BUG: unable to handle kernel NULL pointer dereference Jan 3 13:02:33 v2140 at virtual address Jan 3 13:02:33 v2140 [10966.004192] printing eip: Jan 3 13:02:33 v2140 [10966.004227] c01b2498 Jan 3 13:02:33 v2140 [10966.004260] *pde = Jan 3 13:02:33 v2140 [10966.004300] Oops: [#1] Jan 3 13:02:33 v2140 [10966.004341] Jan 3 13:02:33 v2140 SMP Jan 3 13:02:33 v2140 DEBUG_PAGEALLOC Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.004428] Modules linked in: Jan 3 13:02:33 v2140 ipt_LOG Jan 3 13:02:33 v2140 ipt_owner Jan 3 13:02:33 v2140 xt_state Jan 3 13:02:33 v2140 xt_tcpudp Jan 3 13:02:33 v2140 iptable_filter Jan 3 13:02:33 v2140 ipt_MASQUERADE Jan 3 13:02:33 v2140 iptable_nat Jan 3 13:02:33 v2140 ip_nat Jan 3 13:02:33 v2140 ip_tables Jan 3 13:02:33 v2140 x_tables Jan 3 13:02:33 v2140 ecb Jan 3 13:02:33 v2140 af_key Jan 3 13:02:33 v2140 tun Jan 3 13:02:33 v2140 netconsole Jan 3 13:02:33 v2140 e100 Jan 3 13:02:33 v2140 r8169 Jan 3 13:02:33 v2140 crc32 Jan 3 13:02:33 v2140 ip_conntrack_ftp Jan 3 13:02:33 v2140 ip_conntrack Jan 3 13:02:33 v2140 nfnetlink Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005037] CPU:2 Jan 3 13:02:33 v2140 [10966.005040] EIP:0060:[c01b2498]Not tainted VLI Jan 3 13:02:33 v2140 [10966.005044] EFLAGS: 00010286 (2.6.19.1-vs2.2.0-rc5.p4smp.53 #1) Jan 3 13:02:33 v2140 [10966.005201] EIP is at do_task_stat+0xa5/0x766 Jan 3 13:02:33 v2140 [10966.005253] eax: ebx: d91ef000 ecx: c06ecbb4 edx: 0040 Jan 3 13:02:33 v2140 [10966.005311] esi: dbdf45a0 edi: dbdf45a0 ebp: cc0e9f14 esp: cc0e9dc0 Jan 3 13:02:33 v2140 [10966.005368] ds: 007b es: 007b ss: 0068 Jan 3 13:02:33 v2140 [10966.005418] Process pidof (pid: 23423[#2149], ti=cc0e8000 task=da4e45a0 task.ti=cc0e8000) Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005473] Stack: Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 cc0e9de8 Jan 3 13:02:33 v2140 c0141f03 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005788] Jan 3 13:02:33 v2140 cc0e9e00 Jan 3 13:02:33 v2140 c0140dd6 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006090] Jan 3 13:02:33 v2140 cc0e9e1c Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 c151a4c0 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 cc0e9e3c Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006427] Call Trace: Jan 3 13:02:33 v2140 [10966.006510] [c0103dbd] Jan 3 13:02:33 v2140 show_trace_log_lvl+0x2f/0x45 Jan 3 13:02:33 v2140 [10966.006593] [c0103e9b] Jan 3 13:02:33 v2140 show_stack_log_lvl+0x9f/0xa7 Jan 3 13:02:33 v2140 [10966.006678] [c01040b2] Jan 3 13:02:33 v2140 show_registers+0x1b1/0x242 Jan 3 13:02:33 v2140 [10966.006755] [c0104345] Jan 3 13:02:33 v2140 die+0x151/0x246 Jan 3 13:02:33 v2140 [10966.006829] [c058a68e] Jan 3 13:02:33 v2140 do_page_fault+0x498/0x58a Jan 3 13:02:33 v2140 [10966.006919] [c0588c09] Jan 3 13:02:33 v2140 error_code+0x39/0x40 Jan 3 13:02:33 v2140 [10966.006998] [c01b2b9b] Jan 3 13:02:33 v2140 proc_tgid_stat+0x20/0x22 Jan 3 13:02:33 v2140 [10966.007080] [c01ad6dd] Jan 3 13:02:33 v2140 proc_info_read+0x12f/0x17e Jan 3 13:02:33 v2140 [10966.007166] [c01761f0] Jan 3 13:02:33 v2140 vfs_read+0xa3/0x177 Jan 3 13:02:33 v2140 [10966.007244] [c017658e] Jan 3 13:02:33 v2140 sys_read+0x47/0x6b Jan 3 13:02:33 v2140 [10966.040593] [c0102feb] Jan 3 13:02:33 v2140 syscall_call+0x7/0xb Jan 3 13:02:33 v2140 [10966.040650] === Jan 3 13:02:33 v2140 [10966.040685] Code: Jan 3 13:02:33 v2140 07 Jan 3 13:02:33 v2140 8b Jan 3 13:02:33 v2140 97 Jan 3 13:02:33 v2140 8c Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 b9 Jan 3 13:02:33 v2140 98 Jan 3 13:02:33 v2140 cb Jan 3 13:02:33 v2140 6e Jan 3 13:02:33 v2140 c0 Jan 3 13:02:33 v2140 83 Jan 3 13:02:33 v2140 e0 Jan 3 13:02:33 v2140 1f Jan 3 13:02:33 v2140 83 Jan 3 13:02:33 v2140 e2 Jan 3 13:02:33 v2140 60 Jan 3 13:02:33 v2140 09 Jan 3 13:02:33 v2140 d0 Jan 3 13:02:33 v2140 74 Jan 3 13:02:33 v2140 13 Jan 3 13:02:33 v2140 83 Jan 3 13:02:33 v2140 c1 Jan 3 13:02:33 v2140 04 Jan 3 13:02:33 v2140 d1 Jan 3 13:02:33 v2140 e8 Jan
[Vserver] Re: firewall between 2 vservers
hello bruno, thanks for the explanation, it helped in finding the right configuration for shorewall. in short: i had to apply the filters to the $FW (local) interface instead of dummy0 (eth0 or whatever interface your vserver is using) and do the filtering for the ip addresses. i haven't tested it with firehol. Bruno wrote: On Sunday 07 January 2007 18:13, oliver oli wrote: i'm trying to restrict access from one vserver to another vserver running on the same machine. one is running on dummy0, the other one on dummy1. i tried firehol and shorewall, but it just doesn't work. it seems that all firewall rules are just ignored. what's so special with the vserver networking? has anyone examples how to setup working iptables rules that prevents access from one vserver to another? VServer just does IP-level isolation. To filter with iptables, either specify lo as interface or no interface at all, but just the addresses of both guests. The reason for this is that kernel sees local traffic as going over lo, no matter on what interface the IP addresses are assigned (would be the same if IP addresses were on eth0 and eth1 or even on the same interface) If I remember well, firehol by default allows ALL lo traffic... so getting the filtering with firehol might be some more work (you need to disable default allow policy on lo and setup your own rules) Bruno ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] FC5 Linux-Vserver ( gotcha ).
Daniel Hokka Zakrisson wrote:
Roderick A. Anderson wrote:
I found another slight gotcha in the install process.
I think the following is the fix.
After:
A. Installing the vserver utilities system from rpm
Need to run the command:
service vprocunhide start
And in the future (util-vserver 0.30.213+),
service util-vserver start
Daniel is there a discussion for util-vserver going on? IRC or another
mailing list? The ease of set-up and use of Linux-Vservers is my main
interest so I would like to follow along and know what is planned and
happening.
I think I saw a thread that indicated you were actually or kind-of
taking on development of util-vserver.
would be a good idea. The easier, non-version specific way would be to
just reboot again after installing the utils, but that's not at all as
pretty.
This idea did cross my mind but since I had just rebooted to get the new
kernel running it went against the grain for me.
Could the command
yum install util-vserver{,-core,-lib,-sysv,-build}
be run before rebooting the system? Then the new kernel would be
started along with the rest of the utilities with a single reboot.
Not sure if the util-vserver{,-core,-lib,-sysv,-build} need to have a
running vserver kernel to do the right stuff.
Rod
--
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] OSCON 2007?
Anyone planning on attending OSCON in 2007? Anyone planning a presentation on Linux-Vserver? Where do we go and who do we talk to about this? My assumption is it would cost too much for an individual or their company to pay on their own for most of the active developers. Rod -- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] kernel panic patch-2.6.19.1-vs2.1.1.7.diff
On Mon, Jan 08, 2007 at 11:29:46AM +0100, Jarek Dylag wrote: Hi, okay, as it seems, I cannot recreate this here please could you make the following changes to get_task_state() There is nothing new in kernel log after changes, oops in attachement. very strange ... you constantly omit the kernel lines from the oops traces, could you verify that you actually booted the modified kernel? could you also upload the vmlinux (not vmlinuz) file somewhere where I could access it? TIA, Herbert Jarek Dylag Jan 3 13:02:33 v2140 [10966.004095] BUG: unable to handle kernel NULL pointer dereference Jan 3 13:02:33 v2140 at virtual address Jan 3 13:02:33 v2140 [10966.004192] printing eip: Jan 3 13:02:33 v2140 [10966.004227] c01b2498 Jan 3 13:02:33 v2140 [10966.004260] *pde = Jan 3 13:02:33 v2140 [10966.004300] Oops: [#1] Jan 3 13:02:33 v2140 [10966.004341] Jan 3 13:02:33 v2140 SMP Jan 3 13:02:33 v2140 DEBUG_PAGEALLOC Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.004428] Modules linked in: Jan 3 13:02:33 v2140 ipt_LOG Jan 3 13:02:33 v2140 ipt_owner Jan 3 13:02:33 v2140 xt_state Jan 3 13:02:33 v2140 xt_tcpudp Jan 3 13:02:33 v2140 iptable_filter Jan 3 13:02:33 v2140 ipt_MASQUERADE Jan 3 13:02:33 v2140 iptable_nat Jan 3 13:02:33 v2140 ip_nat Jan 3 13:02:33 v2140 ip_tables Jan 3 13:02:33 v2140 x_tables Jan 3 13:02:33 v2140 ecb Jan 3 13:02:33 v2140 af_key Jan 3 13:02:33 v2140 tun Jan 3 13:02:33 v2140 netconsole Jan 3 13:02:33 v2140 e100 Jan 3 13:02:33 v2140 r8169 Jan 3 13:02:33 v2140 crc32 Jan 3 13:02:33 v2140 ip_conntrack_ftp Jan 3 13:02:33 v2140 ip_conntrack Jan 3 13:02:33 v2140 nfnetlink Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005037] CPU:2 Jan 3 13:02:33 v2140 [10966.005040] EIP:0060:[c01b2498]Not tainted VLI Jan 3 13:02:33 v2140 [10966.005044] EFLAGS: 00010286 (2.6.19.1-vs2.2.0-rc5.p4smp.53 #1) Jan 3 13:02:33 v2140 [10966.005201] EIP is at do_task_stat+0xa5/0x766 Jan 3 13:02:33 v2140 [10966.005253] eax: ebx: d91ef000 ecx: c06ecbb4 edx: 0040 Jan 3 13:02:33 v2140 [10966.005311] esi: dbdf45a0 edi: dbdf45a0 ebp: cc0e9f14 esp: cc0e9dc0 Jan 3 13:02:33 v2140 [10966.005368] ds: 007b es: 007b ss: 0068 Jan 3 13:02:33 v2140 [10966.005418] Process pidof (pid: 23423[#2149], ti=cc0e8000 task=da4e45a0 task.ti=cc0e8000) Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005473] Stack: Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 cc0e9de8 Jan 3 13:02:33 v2140 c0141f03 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.005788] Jan 3 13:02:33 v2140 cc0e9e00 Jan 3 13:02:33 v2140 c0140dd6 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 c0588874 Jan 3 13:02:33 v2140 da4e45a0 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006090] Jan 3 13:02:33 v2140 cc0e9e1c Jan 3 13:02:33 v2140 0296 Jan 3 13:02:33 v2140 c06e4a44 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 c01142ed Jan 3 13:02:33 v2140 c151a4c0 Jan 3 13:02:33 v2140 0001 Jan 3 13:02:33 v2140 cc0e9e3c Jan 3 13:02:33 v2140 Jan 3 13:02:33 v2140 [10966.006427] Call Trace: Jan 3 13:02:33 v2140 [10966.006510] [c0103dbd] Jan 3 13:02:33 v2140 show_trace_log_lvl+0x2f/0x45 Jan 3 13:02:33 v2140 [10966.006593] [c0103e9b] Jan 3 13:02:33 v2140 show_stack_log_lvl+0x9f/0xa7 Jan 3 13:02:33 v2140 [10966.006678] [c01040b2] Jan 3 13:02:33 v2140 show_registers+0x1b1/0x242 Jan 3 13:02:33 v2140 [10966.006755] [c0104345] Jan 3 13:02:33 v2140 die+0x151/0x246 Jan 3 13:02:33 v2140 [10966.006829] [c058a68e] Jan 3 13:02:33 v2140 do_page_fault+0x498/0x58a Jan 3 13:02:33 v2140 [10966.006919] [c0588c09] Jan 3 13:02:33 v2140 error_code+0x39/0x40 Jan 3 13:02:33 v2140 [10966.006998] [c01b2b9b] Jan 3 13:02:33 v2140 proc_tgid_stat+0x20/0x22 Jan 3 13:02:33 v2140 [10966.007080] [c01ad6dd] Jan 3 13:02:33 v2140 proc_info_read+0x12f/0x17e Jan 3 13:02:33 v2140 [10966.007166] [c01761f0] Jan 3 13:02:33 v2140 vfs_read+0xa3/0x177 Jan 3 13:02:33 v2140 [10966.007244] [c017658e] Jan 3 13:02:33 v2140 sys_read+0x47/0x6b Jan 3 13:02:33 v2140 [10966.040593] [c0102feb] Jan 3 13:02:33 v2140 syscall_call+0x7/0xb Jan 3 13:02:33 v2140 [10966.040650] === Jan 3 13:02:33 v2140 [10966.040685] Code: Jan 3 13:02:33 v2140 07 Jan 3 13:02:33 v2140 8b Jan 3 13:02:33 v2140 97 Jan 3 13:02:33 v2140 8c Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 00 Jan 3 13:02:33 v2140 b9 Jan 3 13:02:33 v2140 98 Jan 3 13:02:33 v2140 cb Jan 3 13:02:33 v2140 6e
Re: [Vserver] FC5 Linux-Vserver ( gotcha ).
On Mon, Jan 08, 2007 at 07:57:00AM -0800, Roderick A. Anderson wrote:
Daniel Hokka Zakrisson wrote:
Roderick A. Anderson wrote:
I found another slight gotcha in the install process.
I think the following is the fix.
After:
A. Installing the vserver utilities system from rpm
Need to run the command:
service vprocunhide start
And in the future (util-vserver 0.30.213+),
service util-vserver start
Daniel is there a discussion for util-vserver going on? IRC or another
mailing list? The ease of set-up and use of Linux-Vservers is my main
interest so I would like to follow along and know what is planned and
happening.
I think I saw a thread that indicated you were actually or kind-of
taking on development of util-vserver.
correct, IMHO a good place is the IRC channel
#vserver @ irc.oftc.net, YMMV
best,
Herbert
would be a good idea. The easier, non-version specific way would be
to just reboot again after installing the utils, but that's not at
all as pretty.
This idea did cross my mind but since I had just rebooted to get the
new kernel running it went against the grain for me.
Could the command
yum install util-vserver{,-core,-lib,-sysv,-build}
be run before rebooting the system? Then the new kernel would be
started along with the rest of the utilities with a single reboot.
Not sure if the util-vserver{,-core,-lib,-sysv,-build} need to have a
running vserver kernel to do the right stuff.
Rod
--
___
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] firewall between 2 vservers
On Sun, Jan 07, 2007 at 09:46:32PM +0100, Oliver Welter wrote: Hi Bruno, All traffic does go through iptables, even local one! Local traffic will leave through the OUTPUT chain and come in through the INPUT chain, using lo interface. In most cases though iptables is configured to accept all traffic that goes through lo... Hmm , guess I was wrong - through lo it should work - I mixxed up my tries to do some nat between guests which is surely not working through loopback. sorry to correct you once again, NAT on lo is working perfectly fine too, just requires the proper kernel support and the correct rules ... note: naturally local traffic does not pass the forward chains at all, only output, and input HTH, Herbert Sorry for the miss Oliver ___ 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] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
On Mon, Jan 08, 2007 at 11:05:50AM +0100, Oliver Paulus wrote:
Hello,
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
---
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: Oops: 0002 [5] SMP
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: CR2: 82180f7411a6
/usr/lib/util-vserver/vserver.functions: line 895: 16787 Getötet
$_VWAIT --timeout $VSHELPER_SYNC_TIMEOUT --status-fd 3 $2
$_is_tmpdir/out
2$_is_tmpdir/err 3$_is_tmpdir/fifo
/usr/lib/util-vserver/vserver.stop: line 85: 16794 Getötet
[EMAIL PROTECTED] ${USE_VNAMESPACE:+$_VNAMESPACE --enter $S_CONTEXT -- }
$_VCONTEXT $SILENT_OPT --migrate --chroot --xid $S_CONTEXT --
[EMAIL PROTECTED]
internal error: 'vwait' exited with an unexpected status ''; I will
try to continue but be prepared for unexpected events.
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: Oops: [6] SMP
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: CR2: 82180f74119e
---
here is the content of /var/log/messages:
Jan 8 10:55:37 hal9000 kernel: PGD 0
Jan 8 10:55:37 hal9000 kernel: CPU 0
Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot dm_mirror
dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3 jbd
mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata scsi_mod
via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
Jan 8 10:55:37 hal9000 kernel: Pid: 16787, comm: vwait Not tainted
2.6.18-3-vserver-amd64 #1
Jan 8 10:55:37 hal9000 kernel: RIP: 0010:[802474d2]
[802474d2] add_wait_queue+0x29/0x43
Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810016c71ee8 EFLAGS: 00010002
Jan 8 10:55:37 hal9000 kernel: RAX: 810016c71f20 RBX: 810016c71f08
RCX:
81000f741190
Jan 8 10:55:37 hal9000 kernel: RDX: 82180f74119e RSI: 0246
RDI:
81000f741188
Jan 8 10:55:37 hal9000 kernel: RBP: fffd R08:
R09:
Jan 8 10:55:37 hal9000 kernel: R10: 0040189a R11: 0202
R12:
81000f741188
Jan 8 10:55:37 hal9000 kernel: R13: 0033 R14: 001e
R15:
0003
Jan 8 10:55:37 hal9000 kernel: FS: 2b6e32afc6d0()
GS:8052f000() knlGS:
Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: ES: CR0:
8005003b
Jan 8 10:55:37 hal9000 kernel: CR2: 82180f7411a6 CR3: 1376d000
CR4:
06e0
Jan 8 10:55:37 hal9000 kernel: Process vwait (pid: 16787[#0], threadinfo
810016c7, task 81001169c880)
Jan 8 10:55:37 hal9000 kernel: Stack: 810016c71f58 81000f74
7fffee1029e0 802996d4
Jan 8 10:55:37 hal9000 kernel: 81001169c880
8027fc81
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel: Call Trace:
Jan 8 10:55:37 hal9000 kernel: [802996d4] vc_wait_exit+0x5d/0x106
Jan 8 10:55:37 hal9000 kernel: [8027fc81]
default_wake_function+0x0/0xe
Jan 8 10:55:37 hal9000 kernel: [80295f87] sys_vserver+0x4ab/0x59e
Jan 8 10:55:37 hal9000 kernel: [8025ab0e] system_call+0x7e/0x83
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel: Code: 48 89 42 08 48 89 53 18 48 89 48 08 49
89
44 24 08 5b 5b 41
Jan 8 10:55:37 hal9000 kernel: RSP 810016c71ee8
Jan 8 10:55:37 hal9000 kernel: 1Unable to handle kernel paging request at
82180f74119e RIP:
Jan 8 10:55:37 hal9000 kernel: PGD 0
Jan 8 10:55:37 hal9000 kernel: CPU 0
Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot dm_mirror
dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3 jbd
mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata scsi_mod
via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
Jan 8 10:55:37 hal9000 kernel: Pid: 28327, comm: apache2 Not tainted
2.6.18-3-vserver-amd64 #1
Jan 8 10:55:37 hal9000 kernel: RIP: 0010:[8027e45e]
[8027e45e] __wake_up_common+0x24/0x68
Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810011515cc8 EFLAGS: 00010092
Jan 8 10:55:37
Re: [Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
On Mon, Jan 08, 2007 at 11:05:50AM +0100, Oliver Paulus wrote:
Hello,
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.
---
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: Oops: 0002 [5] SMP
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: CR2: 82180f7411a6
/usr/lib/util-vserver/vserver.functions: line 895: 16787 Getötet
$_VWAIT --timeout $VSHELPER_SYNC_TIMEOUT --status-fd 3 $2
$_is_tmpdir/out
2$_is_tmpdir/err 3$_is_tmpdir/fifo
/usr/lib/util-vserver/vserver.stop: line 85: 16794 Getötet
[EMAIL PROTECTED] ${USE_VNAMESPACE:+$_VNAMESPACE --enter $S_CONTEXT --
}
$_VCONTEXT $SILENT_OPT --migrate --chroot --xid $S_CONTEXT --
[EMAIL PROTECTED]
internal error: 'vwait' exited with an unexpected status ''; I will
try to continue but be prepared for unexpected events.
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: Oops: [6] SMP
Message from [EMAIL PROTECTED] at Mon Jan 8 10:55:37 2007 ...
hal9000 kernel: CR2: 82180f74119e
---
here is the content of /var/log/messages:
Jan 8 10:55:37 hal9000 kernel: PGD 0
Jan 8 10:55:37 hal9000 kernel: CPU 0
Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot
dm_mirror
dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3
jbd
mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata
scsi_mod
via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
Jan 8 10:55:37 hal9000 kernel: Pid: 16787, comm: vwait Not tainted
2.6.18-3-vserver-amd64 #1
Jan 8 10:55:37 hal9000 kernel: RIP: 0010:[802474d2]
[802474d2] add_wait_queue+0x29/0x43
Jan 8 10:55:37 hal9000 kernel: RSP: 0018:810016c71ee8 EFLAGS:
00010002
Jan 8 10:55:37 hal9000 kernel: RAX: 810016c71f20 RBX:
810016c71f08 RCX:
81000f741190
Jan 8 10:55:37 hal9000 kernel: RDX: 82180f74119e RSI:
0246 RDI:
81000f741188
Jan 8 10:55:37 hal9000 kernel: RBP: fffd R08:
R09:
Jan 8 10:55:37 hal9000 kernel: R10: 0040189a R11:
0202 R12:
81000f741188
Jan 8 10:55:37 hal9000 kernel: R13: 0033 R14:
001e R15:
0003
Jan 8 10:55:37 hal9000 kernel: FS: 2b6e32afc6d0()
GS:8052f000() knlGS:
Jan 8 10:55:37 hal9000 kernel: CS: 0010 DS: ES: CR0:
8005003b
Jan 8 10:55:37 hal9000 kernel: CR2: 82180f7411a6 CR3:
1376d000 CR4:
06e0
Jan 8 10:55:37 hal9000 kernel: Process vwait (pid: 16787[#0],
threadinfo
810016c7, task 81001169c880)
Jan 8 10:55:37 hal9000 kernel: Stack: 810016c71f58
81000f74
7fffee1029e0 802996d4
Jan 8 10:55:37 hal9000 kernel: 81001169c880
8027fc81
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel: Call Trace:
Jan 8 10:55:37 hal9000 kernel: [802996d4]
vc_wait_exit+0x5d/0x106
Jan 8 10:55:37 hal9000 kernel: [8027fc81]
default_wake_function+0x0/0xe
Jan 8 10:55:37 hal9000 kernel: [80295f87]
sys_vserver+0x4ab/0x59e
Jan 8 10:55:37 hal9000 kernel: [8025ab0e]
system_call+0x7e/0x83
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel:
Jan 8 10:55:37 hal9000 kernel: Code: 48 89 42 08 48 89 53 18 48 89 48
08 49 89
44 24 08 5b 5b 41
Jan 8 10:55:37 hal9000 kernel: RSP 810016c71ee8
Jan 8 10:55:37 hal9000 kernel: 1Unable to handle kernel paging
request at
82180f74119e RIP:
Jan 8 10:55:37 hal9000 kernel: PGD 0
Jan 8 10:55:37 hal9000 kernel: CPU 0
Jan 8 10:55:37 hal9000 kernel: Modules linked in: ipv6 dm_snapshot
dm_mirror
dm_mod loop snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore
snd_page_alloc pcspkr serio_raw psmouse shpchp pci_hotplug evdev ext3
jbd
mbcache raid1 md_mod ide_generic sd_mod ide_cd cdrom sata_sil libata
scsi_mod
via_rhine mii ehci_hcd uhci_hcd via82cxxx generic ide_core processor
Jan 8 10:55:37 hal9000 kernel: Pid: 28327, comm: apache2 Not tainted
Re: [Vserver] FC5 Linux-Vserver ( gotcha ).
Roderick A. Anderson wrote:
Daniel Hokka Zakrisson wrote:
Roderick A. Anderson wrote:
I found another slight gotcha in the install process.
I think the following is the fix.
After:
A. Installing the vserver utilities system from rpm
Need to run the command:
service vprocunhide start
And in the future (util-vserver 0.30.213+),
service util-vserver start
Daniel is there a discussion for util-vserver going on? IRC or another
mailing list? The ease of set-up and use of Linux-Vservers is my main
interest so I would like to follow along and know what is planned and
happening.
As Herbert said, IRC is always a good place to reach me, and where most of
the discussions happen.
I think I saw a thread that indicated you were actually or kind-of
taking on development of util-vserver.
Yeah, I've been doing most of the work recently, with help from Enrico and
Benedikt.
would be a good idea. The easier, non-version specific way would be to
just reboot again after installing the utils, but that's not at all as
pretty.
This idea did cross my mind but since I had just rebooted to get the new
kernel running it went against the grain for me.
Yeah, that's what I meant by the pretty comment.
Could the command
yum install util-vserver{,-core,-lib,-sysv,-build}
be run before rebooting the system? Then the new kernel would be
started along with the rest of the utilities with a single reboot.
Not sure if the util-vserver{,-core,-lib,-sysv,-build} need to have a
running vserver kernel to do the right stuff.
The only thing I can think of/remember is that you'd have to set the
barrier manually post-reboot with something like setattr --barrier
/vservers /vservers/.pkg. This is what I normally do, since I really hate
rebooting (my systems take way too long to reboot).
Rod
--
Daniel Hokka Zakrisson
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
