Re: [vserver] kernel ctx-12 and vserver 0.18

About this list Date view Thread view Subject view Author view Attachment view

From: Jukka Laaksola (jukka.laaksola_at_netland.fi)
Date: Thu Jul 11 2002 - 03:37:01 EDT

Jacques Gelinas wrote:
>
> The other is NIS. The NIS server and client (ypbind) works correctly inside vservers,
> but ypwhich fails to talk to ypbind.

I have vserver 0.17 and ctx-10.

I have in /etc/hosts on 10.10.10.41
-----
10.10.10.41 vserver2 localhost
10.10.10.40 vserver1 

---
[root_at_vserver2 /]ypwhich
ypwhich: Can't communicate with ypbind
[root_at_vserver2 /]ypwhich localhost
vserver1
[root_at_vserver2 /]

So I have for a work around changed /etc/init.d/ypbind startup script to 
use "ypwhich localhost" and it will found the NIS server.

> 
> Anyone knows of other package needing special handling on the loopback ?

I'm not sure if this is a real loopback problem or what.
Portmap only in vservers works fine for me. But I need to run portmap 
also in the main server for NFS-server. This is need special tricking. 
If I start portmap normally in the main server then portmap in a vserver 
  can't bind the udp address. Now I use in main server "chbind --ip 
127.0.0.1 /etc/init.d/portmap start". Then I need to use rinetd for 
forwarding nfs-servers IP's (192.168.0.3) tcp port 111 to localhost port 
111. I haven't found a solution for forwarding udp port also.

rinetd.conf:
-----
193.168.0.3 111 127.0.0.1 111
-----

But despite of that Vserver is a very good solution for our ha-cluster. 
At the failover we can swap the vservers to the second machine of the 
cluster with the drbd and the Heartbeat.
So thanks for all of you.

-- 
Jukka Laaksola
Netland Oy
About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.4 : Mon Aug 19 2002 - 12:01:01 EDT