[Vserver] stop vserver cause error/oops - with new debian 4.0 vserver kernel version
: 0001 R14: 81000f741188 R15: 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: 82180f74119e CR3: 077fc000 CR4: 06e0 Jan 8 10:55:37 hal9000 kernel: Process apache2 (pid: 28327[#51], threadinfo 810011514000, task 8100130ed140) Jan 8 10:55:37 hal9000 kernel: Stack: 0001 81000f741188 0001 Jan 8 10:55:37 hal9000 kernel: 0292 0001 810011515d38 8022d038 Jan 8 10:55:37 hal9000 kernel: 0020 810011515d58 0020 8100010f4780 Jan 8 10:55:37 hal9000 kernel: Call Trace: Jan 8 10:55:37 hal9000 kernel: [8022d038] __wake_up+0x38/0x4f Jan 8 10:55:37 hal9000 kernel: [80214181] do_exit+0x901/0x948 Jan 8 10:55:37 hal9000 kernel: [80246e14] cpuset_exit+0x0/0x6c Jan 8 10:55:37 hal9000 kernel: [8022a295] get_signal_to_deliver+0x4b0/0x4df Jan 8 10:55:37 hal9000 kernel: [80228cb6] do_signal+0x55/0x751 Jan 8 10:55:37 hal9000 kernel: [80232404] lock_sock+0xa2/0xad Jan 8 10:55:37 hal9000 kernel: [8023f839] d_rehash+0x6a/0x80 Jan 8 10:55:37 hal9000 kernel: [802610ba] _spin_lock_bh+0x9/0x14 Jan 8 10:55:37 hal9000 kernel: [8022fb95] release_sock+0x13/0xaa Jan 8 10:55:37 hal9000 kernel: [803d18bb] inet_accept+0xab/0xb7 Jan 8 10:55:37 hal9000 kernel: [8039837d] sys_accept+0x1b8/0x1ea Jan 8 10:55:37 hal9000 kernel: [80220b9b] __up_read+0x13/0x8a Jan 8 10:55:37 hal9000 kernel: [8025ab97] sysret_signal+0x1c/0x27 Jan 8 10:55:37 hal9000 kernel: [8025ae1b] ptregscall_common+0x67/0xac Jan 8 10:55:37 hal9000 kernel: Jan 8 10:55:37 hal9000 kernel: Jan 8 10:55:37 hal9000 kernel: Code: 49 8b 18 eb 2a 49 8d 78 e8 45 8b 68 e8 4c 89 f9 8b 55 d0 8b Jan 8 10:55:37 hal9000 kernel: RSP 810011515cc8 Jan 8 10:55:37 hal9000 kernel: 1Fixing recursive fault but reboot is needed! --- additional notes: 1. other vserver instances can be stopped successfully. 2. with the kernel 2.6.17.13-vs2.0.2.1 this failure does not appear. Regards -- Oliver Paulus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer reboot - timeout opening/writing control channel /dev/initctl
reboot alone won't work without an init, and by default guests don't have one (see below). reboot -f just calls into the kernel and tells it to reboot. This is caught by the patch and the kernel runs vshelper, which does the rebooting/halting. Thank you for your explanation. Only if you're using the plain initstyle, the default (sysv) just runs the initscripts without going through init. Ok, I have found this page: http://oldwiki.linux-vserver.org/InitStyles. I have to set /etc/vservers/id/apps/init/style to plain, right? I will test this. Are there any reasons why using sysv instead? ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] VServer reboot - timeout opening/writing control channel /dev/initctl
Hello, I am runnung VServer 2.0.2.1 with 2.6.17.13 kernel on a Debian Etch machine. util-vserver in version 0.30.211. The guest (vserver) is running Etch too. I have set CAP_SYS_BOOT in /etc/vservers/vservername/bcapabilities. Every time I want to reboot from within the guest (vserver) I get the following error: shutdown: timeout opening/writing control channel /dev/initctl init: timeout opening/writing control channel /dev/initctl What is with vshelper? Is this needed for rebooting in VServer 2.x too? Regards Oliver Paulus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer reboot - timeout opening/writing control channel /dev/initctl
As expected if you're not running an init (i.e. using the plain initstyle). You'll have to use reboot -f to invoke vshelper which would reboot the guest. Can you explain that a little bit more in detail for me? How is it possible to use a simple reboot within vserver? As expected if you're not running an init (i.e. using the plain initstyle). I think vserver is running init on startup. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
