Re: [Vserver] gentoo update breaks shutdowns?
On Sun, Mar 11, 2007 at 02:33:44AM -0500, Chuck wrote: there is something in my system that updated recently that has since broken vserver's ability to report shutting down guests. I get this kind of report on every type of guest. it also appears to be a random thing. other times i shut guests down and i get no errors. this variable behavior was only noticed yesterday because we are moving physical drives around so we have had to stop/start the server otherwise we may not stop any for months. it also waits the 'timeout' time before reporting. as in example below, after this message i try a vps ax|grep 3910 and i find no processes with that context running! an immediate restart is error free. valkyrie boinc # vserver cacti stop A timeout occured while waiting for the vserver to finish and it will be killed by sending a SIGKILL signal. The following process list might be useful for finding out the reason of this behavior: -- 14685 3910 cacti ?Ss 0:00 init [3] 15181 3910 cacti ?Ss 0:00 \_ /usr/sbin/syslog-ng 15245 3910 cacti ?Ssl0:00 \_ /usr/sbin/named -u named -n 4 -t /var/bind 15265 3910 cacti ?Ss 0:00 \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15266 3910 cacti ?S 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15312 3910 cacti ?Sl 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15313 3910 cacti ?Sl 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15310 3910 cacti ?Ss 0:01 \_ /usr/sbin/clamd 15327 3910 cacti ?Ss 0:00 \_ /usr/bin/freshclam -d 15468 3910 cacti ?Ss 0:00 \_ /usr/sbin/cron 15539 3910 cacti ?Ds 0:00 \_ /sbin/shutdown -r 0 w -- Vserver '/etc/vservers/cacti' still running unexpectedly; please investigate it manually... maybe it takes quite long (timeout +/- something) and thus, the timeout strikes sometimes ... I observed similar with qmail, which is quite strange in shutdown behaviour, especially when combined with other services ... (read: it can take between 1 and 10 minutes to do a proper shutdown) just and idea, Herbert essentially when it behaves like this, every shutdown says it is still running does anyone in gentoo-vserver land have any clue what may be causing this apparently false report? my util-vserver version is 0.30.212-r2 kernel version 2.6.19-vs2.2.0-rc2 -- Chuck ___ 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] vserver nfs
Hi, i haven't found a complete vserver nfs how-to unfortunately... Here is my situation: -host is named vakhos -guest, where nfs is running is called nfs I had a working vserver system/network, with nfs-user-server running, but i re-installed (because of damage) the host-system (vakhos). That means, that neither the clients of my network nor the vserver guest (nfs) are causing problems, probably. The main thing i cannot remember is how is it possible to create NAPT entries if mountd is constantly changing port... Here is some output: vakhos:~# rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper nfs:/# rpcinfo -p nfs program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 132 udp 2049 nfs 132 tcp 2049 nfs 151 udp923 mountd 152 udp923 mountd 151 tcp926 mountd 152 tcp926 mountd vakhos:~# cat /var/lib/iptables/active :PREROUTING ACCEPT [3:536] :POSTROUTING ACCEPT [3:220] :OUTPUT ACCEPT [3:220] ... -A POSTROUTING -d 192.168.1.0/24 -j SNAT --to-source 192.168.1.5 -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp --dport 111 -j DNAT --to-destination 192.168.1.12:111 -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp --dport 111 -j DNAT --to-destination 192.168.1.12:111 -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp --dport 745 -j DNAT --to-destination 192.168.1.12:745 -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp --dport 745 -j DNAT --to-destination 192.168.1.12:745 -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp --dport 747 -j DNAT --to-destination 192.168.1.12:747 -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp --dport 747 -j DNAT --to-destination 192.168.1.12:747 -A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp --dport 2049 -j DNAT --to-destination 192.168.1.12:2049 -A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp --dport 2049 -j DNAT --to-destination 192.168.1.12:2049 #-A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp --dport 981 -j DNAT --to-destination 192.168.1.12:981 #-A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp --dport 981 -j DNAT --to-destination 192.168.1.12:981 #-A PREROUTING -d 192.168.1.5 -i eth0 -p tcp -m tcp --dport 984 -j DNAT --to-destination 192.168.1.12:984 #-A PREROUTING -d 192.168.1.5 -i eth0 -p udp -m udp --dport 984 -j DNAT --to-destination 192.168.1.12:984 ... COMMIT Even another vserver-guest (not a PC outside the vserver-network) cannot mount nfs dirs: home:/home/kostas# showmount -e mount clntudp_create: RPC: Program not registered home:/home/kostas# mount -a mount: pimp:/shared failed, reason given by server: Permission denied Can somebody help please? If more info is needed i will post them... ___ All New Yahoo! Mail Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] gentoo update breaks shutdowns?
On Sunday 11 March 2007 12:46, Herbert Poetzl wrote: On Sun, Mar 11, 2007 at 02:33:44AM -0500, Chuck wrote: there is something in my system that updated recently that has since broken vserver's ability to report shutting down guests. I get this kind of report on every type of guest. it also appears to be a random thing. other times i shut guests down and i get no errors. this variable behavior was only noticed yesterday because we are moving physical drives around so we have had to stop/start the server otherwise we may not stop any for months. it also waits the 'timeout' time before reporting. as in example below, after this message i try a vps ax|grep 3910 and i find no processes with that context running! an immediate restart is error free. valkyrie boinc # vserver cacti stop A timeout occured while waiting for the vserver to finish and it will be killed by sending a SIGKILL signal. The following process list might be useful for finding out the reason of this behavior: -- 14685 3910 cacti ?Ss 0:00 init [3] 15181 3910 cacti ?Ss 0:00 \_ /usr/sbin/syslog-ng 15245 3910 cacti ?Ssl0:00 \_ /usr/sbin/named -u named -n 4 -t /var/bind 15265 3910 cacti ?Ss 0:00 \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15266 3910 cacti ?S 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15312 3910 cacti ?Sl 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15313 3910 cacti ?Sl 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15310 3910 cacti ?Ss 0:01 \_ /usr/sbin/clamd 15327 3910 cacti ?Ss 0:00 \_ /usr/bin/freshclam -d 15468 3910 cacti ?Ss 0:00 \_ /usr/sbin/cron 15539 3910 cacti ?Ds 0:00 \_ /sbin/shutdown -r 0 w -- Vserver '/etc/vservers/cacti' still running unexpectedly; please investigate it manually... maybe it takes quite long (timeout +/- something) and thus, the timeout strikes sometimes ... its an idea... however even nameserver guests that do nothing but run named which normally shut down very fast take a reasonably long time and many times error out. I observed similar with qmail, which is quite strange in shutdown behaviour, especially when combined with other services ... qmail is odd... unless you want to wait for it to finish whatever it is doing, the only way is an explicit kill. (read: it can take between 1 and 10 minutes to do a proper shutdown) just and idea, thanks! will look for the timeout config and try extending it a bit Herbert essentially when it behaves like this, every shutdown says it is still running does anyone in gentoo-vserver land have any clue what may be causing this apparently false report? my util-vserver version is 0.30.212-r2 kernel version 2.6.19-vs2.2.0-rc2 -- Chuck ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] gentoo update breaks shutdowns?
On Sunday 11 March 2007 12:46, Herbert Poetzl wrote: On Sun, Mar 11, 2007 at 02:33:44AM -0500, Chuck wrote: there is something in my system that updated recently that has since broken vserver's ability to report shutting down guests. I get this kind of report on every type of guest. it also appears to be a random thing. other times i shut guests down and i get no errors. this variable behavior was only noticed yesterday because we are moving physical drives around so we have had to stop/start the server otherwise we may not stop any for months. it also waits the 'timeout' time before reporting. as in example below, after this message i try a vps ax|grep 3910 and i find no in the system console log i noticed something i don't remember seeing before.. an option given that says nonamespace or something like that... is this somethjing new? need I convert anything? these servers were created between oct 06 and feb 07 so if there is anything new that came up that needs a config change i guess i need to do it. processes with that context running! an immediate restart is error free. valkyrie boinc # vserver cacti stop A timeout occured while waiting for the vserver to finish and it will be killed by sending a SIGKILL signal. The following process list might be useful for finding out the reason of this behavior: -- 14685 3910 cacti ?Ss 0:00 init [3] 15181 3910 cacti ?Ss 0:00 \_ /usr/sbin/syslog-ng 15245 3910 cacti ?Ssl0:00 \_ /usr/sbin/named -u named -n 4 -t /var/bind 15265 3910 cacti ?Ss 0:00 \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15266 3910 cacti ?S 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15312 3910 cacti ?Sl 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15313 3910 cacti ?Sl 0:00 | \_ /usr/sbin/apache2 -D DEFAULT_VHOST -D PHP5 -d /usr/lib64/apache2 -f /etc/apache2/httpd.conf -k start 15310 3910 cacti ?Ss 0:01 \_ /usr/sbin/clamd 15327 3910 cacti ?Ss 0:00 \_ /usr/bin/freshclam -d 15468 3910 cacti ?Ss 0:00 \_ /usr/sbin/cron 15539 3910 cacti ?Ds 0:00 \_ /sbin/shutdown -r 0 w -- Vserver '/etc/vservers/cacti' still running unexpectedly; please investigate it manually... maybe it takes quite long (timeout +/- something) and thus, the timeout strikes sometimes ... I observed similar with qmail, which is quite strange in shutdown behaviour, especially when combined with other services ... (read: it can take between 1 and 10 minutes to do a proper shutdown) just and idea, Herbert essentially when it behaves like this, every shutdown says it is still running does anyone in gentoo-vserver land have any clue what may be causing this apparently false report? my util-vserver version is 0.30.212-r2 kernel version 2.6.19-vs2.2.0-rc2 -- Chuck ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vserver nfs
El Domingo, 11 de Marzo de 2007 19:24, Konstantinos Pachopoulos escribió: i haven't found a complete vserver nfs how-to unfortunately... Here is my situation: -host is named vakhos -guest, where nfs is running is called nfs I had a working vserver system/network, with nfs-user-server running, but i re-installed (because of damage) the host-system (vakhos). That means, that neither the clients of my network nor the vserver guest (nfs) are causing problems, probably. The main thing i cannot remember is how is it possible to create NAPT entries if mountd is constantly changing port... I've a running nfs server using unfs3. It's no so fast that kernel NFS but works very well. The main pro is that with unfs3 you don't need portmap so it's allways running at port 2049... but your nfs client must allow to specify the ports and some windows clients don't If you need help I can post the steps here. -- Asier. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] gentoo update breaks shutdowns?
Chuck wrote: ... my util-vserver version is 0.30.212-r2 kernel version 2.6.19-vs2.2.0-rc2 You sure you were running that kernel before? IIRC that one has a broken vc_ctx_kill, so you might want to upgrade... -- Daniel Hokka Zakrisson ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] gentoo update breaks shutdowns?
On Sunday 11 March 2007 15:42, Daniel Hokka Zakrisson wrote:
2.6.19? or the vserver patch?
i also found something interesting just now. on a whim i looked at the
shutdown.sh in init.d and it has changed since older ones. the newer one
which fails every time is
opts=-d
[[ ${INIT_HALT} != HALT ]] opts=${opts}p
[[ ${RC_DOWN_INTERFACE} == yes ]] opts=${opts}i
[[ ${RC_DOWN_HARDDISK} == yes ]] opts=${opts}h
/sbin/halt ${opts}
# hmm, if the above failed, that's kind of odd ...
# so let's force a halt
/sbin/halt -f
but if i change it to match the older one which works every time, it becomes
/sbin/halt -dp
# hmm, if the above failed, that's kind of odd ...
# so let's force a halt
/sbin/halt -f
in changing only a few of our vservers to this older method, every one now
shuts down properly.
Chuck wrote:
...
my util-vserver version is 0.30.212-r2
kernel version
2.6.19-vs2.2.0-rc2
You sure you were running that kernel before? IIRC that one has a broken
vc_ctx_kill, so you might want to upgrade...
--
Daniel Hokka Zakrisson
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
--
Chuck
...and the hordes of M$*ft users descended upon me in their anger,
and asked 'Why do you not get the viruses or the BlueScreensOfDeath
or insecure system troubles and slowness or pay through the nose
for an OS as *we* do?!!', and I answered...'I use Linux'.
The Book of John, chapter 1, page 1, and end of book
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] gentoo update breaks shutdowns?
On Sunday 11 March 2007 15:42, Daniel Hokka Zakrisson wrote: oh to answer your other question, yes we switched to this kernel back in december when we found out the hard way that 2.6.18 had issues with reiserfs and lvm Chuck wrote: ... my util-vserver version is 0.30.212-r2 kernel version 2.6.19-vs2.2.0-rc2 You sure you were running that kernel before? IIRC that one has a broken vc_ctx_kill, so you might want to upgrade... -- Daniel Hokka Zakrisson ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ 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]
[Vserver] java socket connections between guests seem to have the host as a source
Hi, before reinstalling the host system (the guests have remained exactly the same) there was no problem. Now, if i create a java socket connection from one guest to another, the guests believe that the source of the connection is the host! Do i need to change something in /etc/vservers/guest-name dir? While creating each guest i had used the hostname parameter however... Ideas? ___ All New Yahoo! Mail Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
