Difference between revisions of "Frequently Asked Questions scratch"

Error: /proc must be mounted

It expects this because it was compiled this way on Linux and to increase its ulimit. 

It looks like you only can run bind as root once you compile bind with this option, but this should be fine inside a vserver.

Syncing hardware clock to system time hwclock is unable to get I/O port access:  the iopl(3) call failed FAILED]
Turning off swap:  Not superuser.    [FAILED]
Turning off quotas:  quotaoff: Can't stat() mounted device /dev/hdv1: No such file or directory
Unmounting file systems:  umount2: No such file or directory umount: /vservers: not found

Then look for S* links in /etc/rc6.d/ and remove the one responsible for the errors. In RH9 it is called S01reboot

[root@VServerGuest /]# ping 123.123.123.123
connect: Invalid argument

[root@VServerGuest /]# host www.yahoo.ca
socket.c: internal_send: 222.222.222.222#53: Invalid argument
;; connection timed out; no servers could be reached

[root@VServerGuest /]# vyum VServerGuest -- check-update
Cannot find a valid baseurl for repo: core
Error: Cannot find a valid baseurl for repo: core
Make sure that you have either a Public IP setup on the VServer Guest, or that you have a proper SNAT/DNAT rules setup on your VServer Host. After that, restart the vserver guest with the verbose option to see what your ipv4root is set to:
[root@VServerGuest  /]# vserver -v VServerGuest start
ipv4root is now 127.0.0.10 111.111.111.111
New security context is 49156


[root@ge root]# vserver zoe enter

zoe:/# screen
Cannot open your terminal '/dev/pts/5' - please check.

zoe:/# strace screen 
...
stat64("/dev/pts/5", {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
open("/dev/pts/5", O_RDWR|O_NONBLOCK)   = -1 EACCES (Permission denied)


+++ oplock.c.orig       2005-02-14 14:27:51.000000000 +0200

--- oplock.c    2005-02-02 12:27:50.000000000 +0200
@@ -181,14 +181,12 @@
                return False;
        }

+#if 0
     /* Validate message from address (must be localhost). */
        if(from.sin_addr.s_addr != htonl(INADDR_LOOPBACK)) {
                DEBUG(0,("receive_local_message: invalid 'from' address \
 (was %lx should be 127.0.0.1)\n", (long)from.sin_addr.s_addr));
                return False;
        }
+#endif

        /* Setup the message header */
        SIVAL(buffer,OPBRK_CMD_LEN_OFFSET,msg_len);

kernel oplocks = no
oplocks = no

# cat /etc/sysconfig/network
NETWORKING=yes

# cat /etc/smb.conf
...
  # YOUR VSERVER IP/MASK HERE
  interfaces = xxx.xxx.xxx.xxx/mask
...

# cat /etc/smb.conf
...
  use client driver = no
...

# cat /etc/samba/smb.conf | awk '!/^$/ && !/^\s*(#|;)/ {print $0}'
[global]
   workgroup = MYDOMAIN
   netbios name = MYHOSTNAME
   server string = MYCOMMENT (Samba %v)
   printcap name = cups
   load printers = yes
   printing = cups
   printer admin = @adm
   log file = /var/log/samba/log.%m
   max log size = 50
   map to guest = bad user
   security = domain
   password server = *
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd
   username map = /etc/samba/smbusers
   idmap uid = 10000-20000
   idmap gid = 10000-20000
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   interfaces = 127. MYVSERVERIP/MYVSERVERMASK
   wins server = MYWINSIP
   dns proxy = no
   # for french users:
   dos charset = 850
   unix charset = ISO8859-1
[homes]
   comment = Home Directories
   browseable = no
   writable = no
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   guest ok = no
   writable = no
   printable = yes
   create mode = 0700
   print command = lpr-cups -P %p -o raw %s -r   # using client side printer drivers.
   use client driver = no
[print$]
   path = /var/lib/samba/printers
   browseable = yes
   write list = @adm root
   guest ok = yes
   inherit permissions = yes

# Unix_name = SMB_name1 SMB_name2 ...
root = administrator MYDOMAIN\administrator
nobody = guest pcguest smbguest

Starting CUPS printing system: cupsd: Child exited with status 98!

E [date:hour...] StartListening: Unable to bind socket for address 0.0.0.0:631 - Address already in use.

LogLevel info
TempDir /var/spool/cups/tmp
# No 'Listen' directive !
Port 631
BrowseAddress @LOCAL
BrowseDeny All
BrowseAllow @LOCAL
BrowseOrder deny,allow
<Location />
  Order Deny,Allow
  Deny From All
  Allow From @LOCAL
</Location>
<Location /admin>
  AuthType Basic
  AuthClass System
  Order Deny,Allow
  Deny From All
  Allow From YOUR_NETWORK_ADDRESS/YOUR_NETMASK # Example: 172.16.0.0/24
# Or
  Allow From @LOCAL
</Location>

#!/bin/sh
# chkconfig: 2345 15 60
# description: Wrapper to start cups bound to a single IP
USR_LIB_VSERVER=/usr/lib/util-vserver
exec $USR_LIB_VSERVER/vsysvwrapper cups $*

# passwd root
...

# urpmi --root /vservers/yourcupsvserver/ cups-drivers
# /etc/init.d/cups reload

su -
cd /usr/src
apt-get build-dep bind9
apt-get source bind9
cd bind9-x.x.x
vi debian/rules

--disable-linux-caps \

--enable-threads \

--disable-threads \

dpkg-buildpackage
dpkg -i ../bind9-x.x.x.deb
echo "bind9 hold" | dpkg --set-selections

ERROR: Could not determine network interfaces, you must use a interfaces config line


@@ Line 13: / Line 13: @@
 |Signature=Linux-Vserver FAQ}}{{Question|Question=How to verify that a setup is working properly?||Details=
 *To verify that your setup works properly, there are some test scripts to check basic functionality.
-  primarily [http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh testme.sh] and [http://vserver.13thfloor.at/Stuff/SCRIPT/testfs.sh testfs.sh] (see ((TestScripts)) for more details)|Signature=Linux-Vserver FAQ}}
+  primarily [http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh testme.sh] and [http://vserver.13thfloor.at/Stuff/SCRIPT/testfs.sh testfs.sh] (see [[Test Scripts]] for more details)|Signature=Linux-Vserver FAQ}}
 == B. Requirements ==
@@ Line 71: / Line 71: @@
 **[http://www.13thfloor.at/vserver/s_release/v1.00/ vserver]
 *Debian
-**[http://packages.debian.org/cgi-bin/search_packages.pl?keywords=vserver&searchon=names&subword=1&version=all&release=all vserver]
+**[http://packages.debian.org/cgi-bin/search_packages.pl?keywords=vserver&searchon=names&subword=1&version=all&release=all vserver] - All Linux-VServer-related Debian-packages (Probably slow, +100 results).
-**[http://www.paul.sladen.org/vserver/debian/ Debian-newvserver]
+**[http://packages.debian.org/cgi-bin/search_packages.pl?keywords=linux-image-2.6-vserver&searchon=names&subword=1&version=all&release=all Official precompiled kernels] - These are the official Debian kernels compiled with Linux-VServer-support.
-**;This script installs Debian straight off the web from Debian.org's world-wide network of mirrors.:
+**[http://packages.debian.org/cgi-bin/search_packages.pl?keywords=vserver-debiantools&searchon=names&subword=1&version=all&release=all vserver-debiantools] - These scripts install Debian straight off the web from Debian.org's world-wide network of mirrors.
 *Gentoo
 **[http://dev.croup.de/proj/gentoo-vps/wiki/VserverHowto vserver]|Signature=Linux-Vserver FAQ}}
@@ Line 100: / Line 100: @@
 /etc/vserver/<vserver-name>/interfaces/0
 /etc/vserver/<vserver-name>/interfaces/1
-These subdirectories have to contain files with the options you want to set. See the [http://www.nongnu.org/util-vserver/doc/conf/configuration.html Flower page] for more info
+These subdirectories have to contain files with the options you want to set. See the [[VServerConfiguration]] or [http://www.nongnu.org/util-vserver/doc/conf/configuration.html Flower page] for more info
 |Signature=Linux-Vserver FAQ}}{{Question|Question=Is it possible to use the real device (eth0, eth1) instead of the device alias created by vserver?||Details=
 Yes. Set up the IP aliases yourself on the host server
@@ Line 126: / Line 126: @@
 |Signature=Linux-Vserver FAQ}}{{Question|Question=Is DHCP possible in a vserver?||Details=
 It's possible to run a DHCP server inside a vserver, but it required a CAP_NET_RAW capability.
-The solution for 2.6 kernel with new-style config is to add CAP_NET_RAW entry in the /etc/vserver/<vserver-name>/bcapabilities file, and it might be unnecessary to add 255.255.255.255 into bcast file, please read [http://www.nongnu.org/util-vserver/doc/conf/configuration.html The Great Flower Page] for more details. If you are still use the legacy config, please read the answer below.
+The solution for 2.6 kernel with new-style config is to add CAP_NET_RAW entry in the /etc/vserver/<vserver-name>/bcapabilities file, and it might be unnecessary to add 255.255.255.255 into bcast file, please read [[VServerConfiguration]] or [http://www.nongnu.org/util-vserver/doc/conf/configuration.html The Great Flower Page] for more details. If you are still use the legacy config, please read the answer below.
 It's possible to run a DHCP server inside a vserver, but there is a catch. The set_ipv4root assigns one IP and one broadcast address to a vserver. UDP service listening to 0.0.0.0 (bind any) in a vserver are indeed listening to the vserver IP and vserver broadcast.
 This is all they will get. This is fine for most services.
@@ Line 182: / Line 182: @@
 example, if you have a kernel "2.6.11", set "2005" for example  :-)
 |Signature=Linux-Vserver FAQ}}{{Question|Question=I switched from old to new configuration and now all my ip addresses are gone!||Details=
-They are not, ifconfig just doesn't show them. The new tools use 'iproute' instead of 'ifconfig' which allows you to use multiple interface addresses with the same label. In such cases, ifconfig shows only the first address for each label, which probably isn't available in the vserver. Unless you specify a name for an ip address, it will be given the interface name as label, eg. eth0, and ifconfig breaks. You can assign names to your interface addresses in the vserver configuration, see [http://www.nongnu.org/util-vserver/doc/conf/configuration.html The Great Flower Page] for details.
+They are not, ifconfig just doesn't show them. The new tools use 'iproute' instead of 'ifconfig' which allows you to use multiple interface addresses with the same label. In such cases, ifconfig shows only the first address for each label, which probably isn't available in the vserver. Unless you specify a name for an ip address, it will be given the interface name as label, eg. eth0, and ifconfig breaks. You can assign names to your interface addresses in the vserver configuration, see [[VServerConfiguration]] or [http://www.nongnu.org/util-vserver/doc/conf/configuration.html The Great Flower Page] for details.
 Earlier, we said that the interface addresses were "nameless", this was wrong. As said above, the addresses in question actually all have the same name/label. Knowing this we could actually virtualize the ioctl interface which ifconfig uses in a meaningful way, making ifconfig show the vserver's ip addresses as expected, even when it shares its label with other ip addresses (of course only if there aren't multiple ip addresses in the same vserver that share the same label, but that's an ifconfig limitation, not a vserver bug). The [http://www.13thfloor.at/~doener/vserver/patches/diff-2.6.16.5-vs2.0.2-rc16-devinet_ioctl.diff patch] should apply to most Linux-VServer versions for kernel 2.6 and will probably be included in future versions.
 |Signature=Linux-Vserver FAQ}}{{Question|Question=When I enter/ssh into a vserver I can see all of the interfaces and interface aliases with ifconfig.||Details=
@@ Line 225: / Line 225: @@
   You must make sure the order of the interfaces are correct. The very first Interface (decided upon by alphabetical order of the interface directory name) for the VServer is the default IP used for all network connections. This must be either a public IP or an IP that has been D/SNAT'd.
 |Signature=Linux-Vserver FAQ}}
+== G. Problematic Programs ==
+Some programs do things that might work on a normal host but not inside a V-Server. This is often not a fault of V-Server itself, the programs are doing automagic things which fail and no proper error handling is done. Also sometimes the actions need special rights which are not permitted by default in V-Servers. Allowing CAPs is often not necessary since those special CAPs are only required once (e.g. when the program initializes the directories/settings/whatever).
+{{Question|Question=OpenGroupware Apache Module
+||Details=If your V-Server doesn't have access to localhost, then the connection to the !OpenGroupware server will fail with a "Internal Server Error".
+The apache module for !OpenGroupware called mod_ngobjweb uses a hardcoded "127.0.0.1" IP address in the source (handler.c line 339), this line you need to change to the IP address that should be used (the IP of the V-Server that runs the OpenGroupware server)|Signature=ProblematicPrograms}}
+{{Question|Question=Hylafax (with CAPI)|Details=
+:If you want to run hylafax in a V-Server, you will get a CAP and device problem which can be easily solved. First you need your capi20 devices in your V-Server, which can't be created by ./MAKEDEV (requires special CAPs) so copy the devices into the V-Server, like this (command run on the host):
+:cp -aR /dev/capi* /vservers/your_vserver/dev
+:Now hylafax can access your CAPI ISDN card but will exit after a few seconds, the problem is it tries to create a /dev/null nod in the hylafax chroot. This fails because of missing  CAPs, so lets help hylafax again with copying the nod into the hylafax chroot in the V-Server. Like this (command run on the host):
+:cp -aR /dev/null /vservers/your_vserver/var/spool/hylafax/dev
+:Allright, now hylafax should have CAPI access and run properly.|Signature=ProblematicPrograms}}
+{{Question|Question=Links inside screen inside a V-Server|Details=
+:Don't know why, but links crashes systematically being inside a screen session inside a V-Server started outside a V-Server. (please elaborate!)|Signature=ProblematicPrograms}}
+{{Question|Question=screen inside a VServer|Details=
+<pre>
+[root@ge root]# vserver zoe enter
+zoe:/# screen
+Cannot open your terminal '/dev/pts/5' - please check.
+zoe:/# strace screen
+...
+stat64("/dev/pts/5", {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0
+open("/dev/pts/5", O_RDWR|O_NONBLOCK)   = -1 EACCES (Permission denied)
+</pre>
+:is neither a bug nor an issue with screen, it just shows that a vserver context is not allowed to mess with host terminals. either use ssh/telnet to reach the 'guest' or start the screen session before you do the 'enter' (i.e. on the host)|Signature=ProblematicPrograms}}
+{{Question|Question=!OpenLDAP Startup|Details=
+:slapd needs name resolution available in order to start up, otherwise it appears to hang. Make sure you have working DNS (or whatever) available to your vserver before starting one with slapd. This behavior is confirmed in my setup, no confirmation from others yet. My Setup: vservers all bind to an interface on a DMZ-like network segment, BIND runs on a vserver. slapd would hang at startup if the BIND vserver had not been started first.|Signature=ProblematicPrograms}}
+{{Question|Question=rndc|Details=
+:Bind's rndc has a hardcoded 127.0.0.1 somewhere so any command to rndc will fail with connection refused.
+:You should have a reachable localhost address defined in /etc/hosts and then you can use rndc -s localhost command
+:You can make a rndc.conf and set the default-server option, like that the '-s localhost' isn't necessary.|Signature=ProblematicPrograms}}
+{{Question|Question=Asterisk|Details=
+:Since some version of Asterisk (at least since 1.0.2), it will not run anymore. On start it fails with: "Unable to set high priority"
+:This can be solved by allowing CAP_SYS_NICE for that VServer.
+:You can also not run Asterisk with the realtime priority :
+:Just pass the '-p' command ligne argument to disable the read-time priority.
+:.
+:Good doc on setting up Asterisk devices in the vserver:
+:http://www.telephreak.org/papers/vpa/|Signature=ProblematicPrograms}}
+{{Question|Question=Open/!FreeSwan|Details=
+:Fails because of writing to /proc (requires patch)
+:TODO: write me|Signature=ProblematicPrograms}}
+{{Question|Question=Samba|Details=
+:Oplocks don't work as smbd insists on receiving break requests from 127.0.0.1 \\
+Just patch source/smbd/oplock.c (commenting paranoid code)
+<pre>
++++ oplock.c.orig       2005-02-14 14:27:51.000000000 +0200
+--- oplock.c    2005-02-02 12:27:50.000000000 +0200
+@@ -181,14 +181,12 @@
+                return False;
+        }
++#if 0
+     /* Validate message from address (must be localhost). */
+        if(from.sin_addr.s_addr != htonl(INADDR_LOOPBACK)) {
+                DEBUG(0,("receive_local_message: invalid 'from' address \
+ (was %lx should be 127.0.0.1)\n", (long)from.sin_addr.s_addr));
+                return False;
+        }
++#endif
+        /* Setup the message header */
+        SIVAL(buffer,OPBRK_CMD_LEN_OFFSET,msg_len);
+</pre>
+or if you don't want to patch the samba source code you can disable oplock in Samba and it will work too!
+Just put the following in your smb.conf:
+<pre>
+kernel oplocks = no
+oplocks = no
+</pre>
+Note: The Vserver using Samba should also listen on the broadcast address. Thereby you will not be able to have two samba servers in the same net (on the same broadcast). |Signature=ProblematicPrograms}}
+{{Question|Question=Samba from Debian 3.1|Details=
+The samba deb in sarge (3.1) provided file sharing.  The only oddity observed is that the vserver guest running samba did not appear in a windows box's 'My Network Places'
+    Use a WINS server. The SMB browsing protocol relies heavily on broadcasts on the local net, which are problematic with vservers. WINS resolution on the other hand is unicast and works flawlessly under vserver.|Signature=ProblematicPrograms}}
+{{Question|Question=Samba printer and file server with cups|Details=
+:Samba runs correctly in a Mandriva (Mdk) 10.1 Vserver, (Apart from the above oplock problem ?).
+: \\
+First, edit your {{/etc/sysconfig/network}} file, and set {{networking}} to {{yes}} (This will solve problems for other services !):
+<pre>
+# cat /etc/sysconfig/network
+NETWORKING=yes
+</pre>
+: \\
+Some more tweaking is needeed in {{/etc/smb.conf}}:
+<pre>
+# cat /etc/smb.conf
+...
+  # YOUR VSERVER IP/MASK HERE
+  interfaces = xxx.xxx.xxx.xxx/mask
+...
+</pre>
+: \\
+That's all !!!
+: \\
+But if you're using Samba + Cups to provide printing for Windows clients, AND if you want to use the {{Point and Print}} feature, there is more: In the {{[printers]}} section of your {{smb.conf}}, you should have the {{use client drivers}} directive set to {{no}}, or the driver upload procedure will fail !
+<pre>
+# cat /etc/smb.conf
+...
+  use client driver = no
+...
+</pre>
+: \\
+So, here is a full {{smb.conf}} file:
+<pre>
+# cat /etc/samba/smb.conf | awk '!/^$/ && !/^\s*(#|;)/ {print $0}'
+[global]
+   workgroup = MYDOMAIN
+   netbios name = MYHOSTNAME
+   server string = MYCOMMENT (Samba %v)
+   printcap name = cups
+   load printers = yes
+   printing = cups
+   printer admin = @adm
+   log file = /var/log/samba/log.%m
+   max log size = 50
+   map to guest = bad user
+   security = domain
+   password server = *
+   encrypt passwords = yes
+   smb passwd file = /etc/samba/smbpasswd
+   username map = /etc/samba/smbusers
+   idmap uid = 10000-20000
+   idmap gid = 10000-20000
+   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
+   interfaces = 127. MYVSERVERIP/MYVSERVERMASK
+   wins server = MYWINSIP
+   dns proxy = no
+   # for french users:
+   dos charset = 850
+   unix charset = ISO8859-1
+[homes]
+   comment = Home Directories
+   browseable = no
+   writable = no
+[printers]
+   comment = All Printers
+   path = /var/spool/samba
+   browseable = no
+   guest ok = no
+   writable = no
+   printable = yes
+   create mode = 0700
+   print command = lpr-cups -P %p -o raw %s -r   # using client side printer drivers.
+   use client driver = no
+[print$]
+   path = /var/lib/samba/printers
+   browseable = yes
+   write list = @adm root
+   guest ok = yes
+   inherit permissions = yes
+</pre>
+: \\
+...And a working smbusers:
+<pre>
+# Unix_name = SMB_name1 SMB_name2 ...
+root = administrator MYDOMAIN\administrator
+nobody = guest pcguest smbguest
+</pre>|Signature=ProblematicPrograms}}
+{{Question|Question=Cups print server|Details=
+: Symptoms: The Cups init script exits with:
+<pre>
+Starting CUPS printing system: cupsd: Child exited with status 98!
+</pre>
+: \\
+And the logs ({{/var/log/cups/error_log}}) show:
+<pre>
+E [date:hour...] StartListening: Unable to bind socket for address 0.0.0.0:631 - Address already in use.
+</pre>
+:...Or something like this.
+: \\
+With a correct "cupsd.conf file" (Tested version 1.1.21-0.rc1.7mdk, on Mandrake 10.1 - Now Mandriva), it works; All we need is to remove references to {{127.0.0.1}} or {{localhost}} from the file, as well as correctly unsetting the {{Listen}} directive:
+<pre>
+LogLevel info
+TempDir /var/spool/cups/tmp
+# No 'Listen' directive !
+Port 631
+BrowseAddress @LOCAL
+BrowseDeny All
+BrowseAllow @LOCAL
+BrowseOrder deny,allow
+<Location />
+  Order Deny,Allow
+  Deny From All
+  Allow From @LOCAL
+</Location>
+<Location /admin>
+  AuthType Basic
+  AuthClass System
+  Order Deny,Allow
+  Deny From All
+  Allow From YOUR_NETWORK_ADDRESS/YOUR_NETMASK # Example: 172.16.0.0/24
+# Or
+  Allow From @LOCAL
+</Location>
+</pre>
+: \\
+Then you'll need to modify the {{/etc/init.d/cups}} script, to comment any section referring to {{127.0.0.1}} lookup and configuration. This section exists at least on Mandrake 10.1, and is pretty long (Lines 35 to 55 and/or 79), and additionnaly four "{{else...if}}" lines must be commented far below (Lines 161 to 164) !
+: \\
+Remember to stop any Cupsd running in the host server, or to start it ''via'' a wrapper {{/etc/init.d/v_cups}} script:
+<pre>
+#!/bin/sh
+# chkconfig: 2345 15 60
+# description: Wrapper to start cups bound to a single IP
+USR_LIB_VSERVER=/usr/lib/util-vserver
+exec $USR_LIB_VSERVER/vsysvwrapper cups $*
+</pre>
+: \\
+Do not forget to give a password to the root user, if you want to ba able to manage your printers from the web interface (http://yourcupsvserver:631)!
+<pre>
+# passwd root
+...
+</pre>
+: \\
+If you use Mandriva 10.1 (And maybe some other distros), you&#8217;ll need to add the printers drivers for Cups, and reload it:
+<pre>
+# urpmi --root /vservers/yourcupsvserver/ cups-drivers
+# /etc/init.d/cups reload
+</pre>
+: \\
+&#8230;It added 67 Mb of packages for me.
+: \\
+Then use {{/etc/init.d/v_cups (re)start}} to launch Cups on the host server.
+:You will now be able to make Cupsd start in the vserver , but more tweaking on the ACLs may be necessary to avoid authentification problems...|Signature=ProblematicPrograms}}
+{{Question|Question=Bind9 on Debian GNU/Linux Woody (3.0) and Sarge (3.1)|Details=
+:named provided by the bind9 binary packages fails to start because it is compiled with CAPs option.
+: \\
+The debian way is to build** your own package without CAPs:
+: \\
+<pre>
+su -
+cd /usr/src
+apt-get build-dep bind9
+apt-get source bind9
+cd bind9-x.x.x
+vi debian/rules
+</pre>
+: \\
+Insert the following line after "./configure --prefix=/usr \":
+: \\
+<pre>
+--disable-linux-caps \
+</pre>
+: \\
+On a NPTL-enabled system you alse have to replace \\
+<pre>
+--enable-threads \
+</pre>
+: with \\
+<pre>
+--disable-threads \
+</pre>
+: or bind might refuse to run with an other user than root.
+: \\
+Save the file and go ahead with compiling/installing:
+: \\
+<pre>
+dpkg-buildpackage
+dpkg -i ../bind9-x.x.x.deb
+echo "bind9 hold" | dpkg --set-selections
+</pre>
+: \\
+The last line is to set the package "on hold", so it is not touched by the update process. you have to take care of security holes by yourself now!
+: \\
+The Xs in "bind9-x.x.x" denote the version number of bind9.
+: \\
+** Alternatively you can allow the CAP_SYS_RESOURCE for that V-Server.
+The best way would be to fix bind, which is somehow broken when it comes to capabilities.
+Daniel Hokka Zakrisson repaired it. His patch is to be found here:
+[http://daniel.hozac.com/stuff/bind-9.3.2-caps-when-available.patch bind-9.3.2-caps-when-available.patch]
+So, if you recompile, it would be the cleanest way to apply that patch. Thanks Daniel!
+It would be also nice, if someone submits that patch to the bind people or maybe to your distribution's package maintainers in the first step.
+Get my [http://linux-vserver.derjohn.de/bind9-packages/bind9-capacheck_9.3.2-2_i386.deb vserver-guest-ready Debian bind9 package] for Debian Sid guests. Feedback welcome: aj@net-lab.net|Signature=ProblematicPrograms}}
+{{Question|Question=Postfix 2.1.5 (Debian Sarge)|Details=
+:On a vserver with two interfaces (lo and eth0), and a postfix 2.1.5 listening on lo, postfix can't send emails : "Invalid argument"... Setting smtp_bind_address (http://www.postfix.org/postconf.5.html#smtp_bind_address) to the external address solves the issue.|Signature=ProblematicPrograms}}
+{{Question|Question=Zimbra Mail|Details=
+Zimbra is many applications (including Postfix and MySQL and OpenLDAP and more) which try to take over the interfaces, and depend a lot on binding from 127.0.0.1 - it is not hard to change, but there is a couple of tricks - it is documented here - http://wiki.zimbra.com/index.php?title=Install_VServer|Signature=ProblematicPrograms}}
+{{Question|Question=xine|Details=
+xine won't start with no error message.
+"xine --verbose" shows this.
+<pre>
+ERROR: Could not determine network interfaces, you must use a interfaces config line
+</pre>
+This happens if you have the xineplug_inp_smb.so plugin. Delete it and everything is fine.|Signature=ProblematicPrograms}}
+{{Question|Question=127.0.0.1 issues|Details=
+I had problems with an application that wanted me to access it on 127.0.0.1 and AS 127.0.0.1 to be able to do its configuration. A simple tweak solved the problem. I renamed the default interface directory "0" in /etc/vservers/server/interfaces to "1" and created interface 0 as :
+:dev lo
+:ip 127.0.0.1
+:mask 255.0.0.0
+:name lo
+now interface "1" is the default created interface by the vserver build script with a local adress like 192.168.1.2 and interface "0" is the loopback. I can now telnet on 127.0.0.1 and it sees that im connecting to 127.0.0.1 from 127.0.0.1
+Compiling nagios-1.4 within a vserver requires this, otherwise it hangs during the configure with "checking for ICMP ping syntax..."
+<font size="+1" color="red"> /!\ BIG FAT WARNING: DON'T DO THIS: THE VSERVER WILL HAVE ACCESS TO THE 127.0.0.1 OF THE HOST (quoting Bertl from irc) </font>
+|Signature=ProblematicPrograms}}
+{{Question|Question=Hula-project|Details=
+Does not want to start :(|Signature=ProblematicPrograms}}
+[[Category:Community]]

Difference between revisions of "Frequently Asked Questions scratch"

From Linux-VServer

Latest revision as of 16:08, 9 September 2014

Contents

A. General

Credits

Are there other FAQs available?

Where can I find a overview of Linux-VServer?

How to verify that a setup is working properly?

B. Requirements

What hardware is supported by linux-vserver?

Which kernel versions are supported?

Can I run Linux-vserver on my favorite distribution?

C. Versions

What's the latest version of Linux-VServer?

Where can I find prereleases and release candidates?

D. Tools (util-vserver and vserver)

What do I need them for?

What's the difference between vserver and util-vserver?

Which version of the tools packages do I need? Do I have to upgrade?

E. Download

Where can I dowload the latest version of:

Distribution specific packages

F. Network Usage?

Is IPv6 supported?

Can I put my vservers in different networks?

Is it possible for a vserver to have a other default gateway than the host machine does use?

Can I use more than one IP address in a vserver

Is it possible to use the real device (eth0, eth1) instead of the device alias created by vserver?

Can I modify the behavior of my vservers?

Were can I find more information on networking in Linux-VServer?

G. Software compatibility

Bind does not work in a vserver

Is DHCP possible in a vserver?

NFS-server

Run Level Based Distributions as Ververs (Red Hat and such ....)

Vservers and X Windows

sshd with X11-Forwarding in a vserver

See also: [ProblematicPrograms]

Where can I find more information on the Linux-VServer project?

Does the Linux-VServer project have a mailing list?

Is there a IRC channel

I. Issues

When starting or entering a vserver I get "Error: /proc must be mounted". 'vserver-stat' and 'vps' are failing with "open("/proc/uptime"): No such file or directory". Sometimes, other files in /proc are mentioned. What can I do?

Inside a vserver I can still use mknod to create devices, even without CAP_MKNOD capability. What's wrong? (this probably applies to all other capabilities but that was not tested)

After stopping/restarting a vserver my network is gone! What the hell?

Only root can access any files in the vserver

"daemon() failed: Success" - What? Succesfully failing?

When I start a vserver, "FATAL: kernel too old" message appears and vserver can't be started

I switched from old to new configuration and now all my ip addresses are gone!

When I enter/ssh into a vserver I can see all of the interfaces and interface aliases with ifconfig.

I keep my vserver roots on their own devices. I can unmount them but the device (like drbd or lvm) remains in use until all of my vservers are killed off ("Someone has opened the device for RW access").

When I stop a vserver its network alias does not go away, I am getting 'RTNETLINK answers: Cannot assign requested address

Why does the vserver run on a BSD fs (ufs) ?!

G. Problematic Programs

OpenGroupware Apache Module

Hylafax (with CAPI)

Links inside screen inside a V-Server

screen inside a VServer

!OpenLDAP Startup

rndc

Asterisk

Open/!FreeSwan

Samba

Samba from Debian 3.1

Samba printer and file server with cups

Cups print server

Bind9 on Debian GNU/Linux Woody (3.0) and Sarge (3.1)

Postfix 2.1.5 (Debian Sarge)

Zimbra Mail

xine

127.0.0.1 issues

Hula-project

Views

Personal tools

Search

About

Getting Started

Participate

Resources