Re: [Vserver] vservers start very slow after a reboot
> -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > hil > > Benedict Verheyen wrote: >> i had problems with vservers not starting (or so i thought) after a >> system >> reboot on my Debian Sarge. >> Some particulars of my system: >> - debootstrap install of vservers >> - most vservers have at least 1 shared directories with host (apt cache) >> - hashified >> - lastest util-vserver >> - kernel 2.6.16 >> - debian sarge >> - 7 vservers >> >> What happened when i rebooted is that i saw these lines: >> -- >> Fixing visibility of /proc entries for vservers...done >> Starting vservers of type default... >> -- >> >> And then it seemed as if my system hung but i could actually do a 3 >> fingered salute. So hanging is not the right wording, rather "not >> responding". > > i actually had the same problem... you go onto describe how you (almost) > figured > out the problem in this email, it seems that you didn't quite make the > final > connection: it's not really a problem with the vservers themselves taking > a long > time, it's a problem in the order in which they are starting, with the > non-dns > vservers starting first and therefore hanging whilst they wait for network > connections to time out. > >> I had what appeared to be some dead links in my /etc/rc2.d: >> vprocunhide rebootmgr vservers-default vservers-legacy >> They don't seem to be used anymore so i removed them. Now only a link to >> /etc/init.d/util-vserver is in there >> >> Anyway, i edited /etc/default/util-vserver and set the following: >> mark= >> auto=false > > i did this as well. it temporarily solves the problem to find the answer, > as you > say. > >> This prevented the vservers to load on boot (which i actually want and >> need but disabled to see what's going on). >> I then rebooted and started a vserver manually and instead of the >> startup >> lines zipping by it took ages for it to print some lines so now i knew >> "Starting vservers of type default..." was actually not hanging my >> computer but rather just going very very slow. > > which lines? i suspect they are the ones about various network connections > for > your vserver (trying to resolve hostname, for example). > >> I started all my vservers and after about 10 minutes (i had started an >> uml >> to get DNS going) i decided to shut down the uml that provided dns and >> start the vserver instead that also provides dns. >> Well, to my surprise, that one started quickly again. >> Entering the vservers was also quick again. Very strange. > > no - you now have your dns working, hence it doesn't need to wait for > network > timeouts. > >> Now it all works again but as you can imagine, i wouldn't want to reboot >> :) >> >> 1. What could be causing the slow startup? >> >> 2. What links are necessary in /etc/rc2.d? >> vprocunhide, rebootmgr, vservers-default & vservers-legacy point nowhere >> only util-vserver seems to be valid > > i've got the similar system set up as you (debian sarge 2.6.16 etc). there > was > something like: > > /etc/init.d/vserver-default > > and created > > /etc/init.d/vserver-dnsserver > /etc/init.d/vserver-mailserver > > etc, so that i could start the vservers in a specific order by linking > them into > /etc/rc?.d/* as appropriate. > >> 3. I have my DNS inside a vserver, so the DNS vserver should be started >> as early as possible. >> How do i do that if the links above aren't valid? >> Can i move the util-vserver link and then use the mark file to >> accomplish >> that? > > you still use the mark file to specifiy which start-up script starts which > vserver: > > [EMAIL PROTECTED]:~$ cat /etc/vservers/vsdns/apps/init/mark > dnsserver > [EMAIL PROTECTED]:~$ cat /etc/vservers/vsmail/apps/init/mark > mailserver > [EMAIL PROTECTED]:~$ cat /etc/vservers/vshttp/apps/init/mark > default > > so i can get them to start in what ever order i like, depending upon the > order > in /etc/rc?.d/ . > >> 4. Is there a way to start some vservers early and other less critical >> vservers at the end of the boot sequence? > > as above. > >> Some more information: >> >>> testme.sh >> Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl >> chcontext is working. >> chbind is working. >> Linux 2.6.16-vs2.0.2-rc15.10apr200
[Vserver] vservers start very slow after a reboot
Hi, i had problems with vservers not starting (or so i thought) after a system reboot on my Debian Sarge. Some particulars of my system: - debootstrap install of vservers - most vservers have at least 1 shared directories with host (apt cache) - hashified - lastest util-vserver - kernel 2.6.16 - debian sarge - 7 vservers What happened when i rebooted is that i saw these lines: -- Fixing visibility of /proc entries for vservers...done Starting vservers of type default... -- And then it seemed as if my system hung but i could actually do a 3 fingered salute. So hanging is not the right wording, rather "not responding". I had what appeared to be some dead links in my /etc/rc2.d: vprocunhide rebootmgr vservers-default vservers-legacy They don't seem to be used anymore so i removed them. Now only a link to /etc/init.d/util-vserver is in there Anyway, i edited /etc/default/util-vserver and set the following: mark= auto=false This prevented the vservers to load on boot (which i actually want and need but disabled to see what's going on). I then rebooted and started a vserver manually and instead of the startup lines zipping by it took ages for it to print some lines so now i knew "Starting vservers of type default..." was actually not hanging my computer but rather just going very very slow. I started all my vservers and after about 10 minutes (i had started an uml to get DNS going) i decided to shut down the uml that provided dns and start the vserver instead that also provides dns. Well, to my surprise, that one started quickly again. Entering the vservers was also quick again. Very strange. Now it all works again but as you can imagine, i wouldn't want to reboot :) 1. What could be causing the slow startup? 2. What links are necessary in /etc/rc2.d? vprocunhide, rebootmgr, vservers-default & vservers-legacy point nowhere only util-vserver seems to be valid 3. I have my DNS inside a vserver, so the DNS vserver should be started as early as possible. How do i do that if the links above aren't valid? Can i move the util-vserver link and then use the mark file to accomplish that? 4. Is there a way to start some vservers early and other less critical vservers at the end of the boot sequence? Some more information: > testme.sh Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl chcontext is working. chbind is working. Linux 2.6.16-vs2.0.2-rc15.10apr2006 #1 Tue Apr 11 13:02:54 CEST 2006 i686 Ea 0.30.210 273/glibc (DSa) VCI: 0002:0001 273 0336 (TbLgnP) --- [000]# succeeded. [001]# succeeded. [011]# succeeded. [031]# succeeded. [101]# succeeded. [102]# succeeded. [201]# succeeded. [202]# succeeded. > vserver-info - SYSINFO == Versions: Kernel: 2.6.16-vs2.0.2-rc15.10apr2006 VS-API: 0x00020001 util-vserver: 0.30.210; Apr 19 2006, 16:06:42 Features: CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13) CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13) CPPFLAGS: '' CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W' CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0' build/host: i386-pc-linux-gnu/i386-pc-linux-gnu Use dietlibc: yes Build C++ programs: yes Build C99 programs: yes Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts ext2fs Source: e2fsprogs syscall(2) invocation: alternative vserver(2) syscall#: 273/glibc Paths: prefix: /usr sysconf-Directory: /etc cfg-Directory: /etc/vservers initrd-Directory: $(sysconfdir)/init.d pkgstate-Directory: /var/run/vservers vserver-Rootdir: /var/lib/vservers == Thanks, Benedict ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: SOLVED [Vserver] using djbdns (tinydns & dnscache) from within vserver
Herbert Poetzl wrote: > I don't expect any issues either, but it might be interesting > to try the alternate solution and let us know if that worked > too (because it would be preferable) > > TIA, > Herbert Hi, i tried the alternate solution (well several combinations) and they didn't work so i'm afraid you'll have to be more specific on what values i need to enter where, what interfaces and so on. This is what i tried: 1. tinydns & dnscache configured on localhost vserver localhost in /etc/hosts set to 192.168.1.20 removed interface 1 This setup didn't work (i didn't write down wether it was from the host or from the vserver that it failed) 2. move interface 1 back and set ip to 192.168.1.20 vserver localhost in /etc/hosts set to 192.168.1.20 tinydns & dnscache configured on localhost This didn't work either 3. tinydns & dnscache configured on 192.168.1.20 vserver localhost in /etc/hosts set to 192.168.1.20 1 interface set to 192.168.1.20 This didn't work. 4. tinydns & dnscache configured on 192.168.1.20 vserver localhost in /etc/hosts set to 192.168.1.20 2 interfaces, 1 set to 192.168.1.20 and 1 set to lo with ip 192.168.1.20 as well. Didn't work. It would be interesting if other people that are running tinydns successfully would put their configurations here as i did in my "solved" message. Regards, Benedict ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: SOLVED [Vserver] using djbdns (tinydns & dnscache) from within vserver
> I don't expect any issues either, but it might be interesting > to try the alternate solution and let us know if that worked > too (because it would be preferable) > > TIA, > Herbert OK, i'll try to test it tonight or tomorrow and report back on what happened. Regards, Benedict ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: SOLVED [Vserver] using djbdns (tinydns & dnscache) from within vserver
Hi again, i think i solved the issue. I'll post the things that i think are relevant here so other people who might encounter problems with this kind of setup can find some info here: HOST # cat /etc/resolv.conf search mydomain.be nameserver 192.168.1.20 # ifconfig eth0 Link encap:Ethernet HWaddr 00:10:B5:40:DE:14 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 eth1:thor Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 # ls -la /etc/vservers/thor/interfaces drwxr-xr-x 2 root root 4096 2006-04-14 13:45 0 drwxr-xr-x 2 root root 4096 2006-04-14 13:57 1 interface 0 # cat /etc/vservers/thor/interfaces/0/dev eth1 # cat /etc/vservers/thor/interfaces/0/ip 192.168.1.20 # cat /etc/vservers/thor/interfaces/0/name thor # cat /etc/vservers/thor/interfaces/0/prefix 24 interface 1 # cat /etc/vservers/thor/interfaces/1/dev lo # cat /etc/vservers/thor/interfaces/1/ip 127.0.0.2 # cat /etc/vservers/thor/interfaces/1/prefix 24 VSERVER GUEST = # cat /etc/resolv.conf domain mydomain.be nameserver 192.168.1.20 # ifconfig eth1 Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth1:thor Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 loLink encap:Local Loopback UP LOOPBACK RUNNING MTU:16436 Metric:1 dnscache and tinydns related info in vserver Previously pinging the localhost inside the vserver didn't work so i changed the 127.0.0.1 to 127.0.0.2: # cat /etc/hosts 127.0.0.2 localhost I then removed the tinydns info because it was refering to 127.0.0.1: # rm -rf /var/tinydns Next i remade it for 127.0.0.2 # tinydns-conf tinydns dnslog /var/tinydns 127.0.0.2 I then copied the data file over and did a make # ls -la /var/dnscache/root/ip/ -rw-r--r-- 1 root root0 2005-10-06 00:48 127.0.0.1 -rw-r--r-- 1 root root0 2006-04-14 12:58 127.0.0.2 -rw-r--r-- 1 root root0 2005-10-06 00:49 192.168 -rw-r--r-- 1 root root0 2006-04-14 09:21 192.168.1 -rw-r--r-- 1 root root0 2005-10-06 00:49 192.168.1.20 # ls -la /var/dnscache/root/servers -rw-r--r-- 1 root root 166 2005-10-06 00:48 @ -rw-r--r-- 1 root root 10 2006-04-14 12:55 1.168.192.in-addr.arpa -rw-r--r-- 1 root root 10 2006-04-14 12:55 mydomain.be # cat /var/dnscache/root/servers/1.168.192.in-addr.arpa 127.0.0.2 # cat /var/dnscache/root/servers/mydomain.be 127.0.0.2 # cat /var/tinydns/root/data .mydomain.be:192.168.1.20:a:259200 .1.168.192.in-addr.arpa:192.168.1.20:a:259200 @mydomain.be:192.168.1.1:a::86400 =bifrost.mydomain.be:192.168.1.1:86400 +smtp.mydomain.be:192.168.1.1:86400 +mail.mydomain.be:192.168.1.1:86400 =odin.mydomain.be:192.168.1.10:86400 ... That's it. Now i can ping (by name) without problems from both the host and the guest system. Tonight i'll test if from my machine in the lan but i don't expect problems. If you don't hear back from me in the thread, that test must have succeeded too :) Thanks to all who answered in the thread, it helped me a lot. Kind regards, Benedict ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] using djbdns (tinydns & dnscache) from within vserver
Hi, It seemed that all the changes i did to test gave me an inconsistent setup so I rechecked the hosts resolv.conf, the ip's of the vservers and the resolv.conf of the vserver. Then I rebooted and pinging internal machines by name worked for the host and the vserver. Only thing that didn't seem to work was the pinging of external hosts from the host and the vserver. I then checked the settings of the 0 dir inside the interfaces directory of the vserver and i saw the content of dev was still eth0. That means the ip 192.168.1.20 ended up as an alias of the real eth0 which has a different address range 192.168.0.x. I changed that to eth1 and then it all seems to work. BUT after that change i can't ping the internal host anymore by name. So i changed my setup. I'm not sure this is a good way of accomplishing it but it seems like it's the only way to get it working. This is what's in the interfaces directory: 0 -> dev: eth0 -> ip: 192.168.0.3 (host eth0 192.168.0.2) 1 -> dev: eth1 -> ip: 192.168.1.20 (host eth1 192.168.1.1) My host resolv.conf search mydomain nameserver 192.168.1.20 nameserver 192.168.0.3 With these changes everything seems to work but as i said, i'm not sure that what i configured as my interfaces in the vserver setup directory is ok. Thanks, Benedict ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: using djbdns (tinydns & dnscache) from within vserver
Hi, I removed the bridge and stopped the remaining UML because i thought that bridging might be causing an error. The host machine has 2 nic's and the first, eth0 has an ip 192.168.0.2 and is connected to the net via a wireless bridge to wireless router to cablemodem setup. eth1 has an ip 192.168.1.1 and is connected to the LAN. The vserver starts but dns and ping don't work from inside de vserver: ping localhost PING localhost (127.0.0.1) 56(84) bytes of data. --- localhost ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1010ms This is the result of netstat -ua inside the vserver when it's not working: Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State udp0 0 192.168.1.20:domain *:* udp0 0 192.168.1.20:domain *:* udp0 0 192.168.1.20:domain *:* udp0 0 192.168.1.20:20416 192.168.1.20:domain ESTABLISHED udp0 0 192.168.1.20:10817 192.168.1.20:domain ESTABLISHED udp0 0 192.168.1.20:24559 192.168.1.20:domain ESTABLISHED I can ping the ip of the vserver but not ping it by name. I can also ping from within the vserver to the outside but again not by name. ifconfig from the host: eth0 Link encap:Ethernet HWaddr 00:10:B5:40:DE:14 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8813 errors:0 dropped:0 overruns:0 frame:0 TX packets:8022 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3256901 (3.1 MiB) TX bytes:787578 (769.1 KiB) Interrupt:10 Base address:0x9400 eth1 Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11828 errors:0 dropped:0 overruns:0 frame:0 TX packets:13316 errors:0 dropped:0 overruns:0 carrier:0 collisions:24 txqueuelen:1000 RX bytes:1567772 (1.4 MiB) TX bytes:3817607 (3.6 MiB) Interrupt:11 Base address:0x9000 eth1:frey Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.22 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:11 Base address:0x9000 eth1:loki Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.21 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:11 Base address:0x9000 eth1:njor Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.23 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:11 Base address:0x9000 eth1:thor Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:11 Base address:0x9000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:17642 errors:0 dropped:0 overruns:0 frame:0 TX packets:17642 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2516560 (2.3 MiB) TX bytes:2516560 (2.3 MiB) First i set the vserver up to use an interface set up under dir 0 and with a device name eth0 but then you get a 192.168.1.x adres on a 192.168.0.x nic (eth0) and that didn't seem correct so i changed that to dir 1 and eth1. Also, when i put raw_icmp inside the ccapabilities file, i get an error when starting the vserver: ERROR Unknown ccap 'raw_icmp' An error occured while executing the vserver startup sequence; when there are no other messages, it is very likely that the init-script (/etc/init.d/rc 2) failed. Common causes are: * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build method knows how to deal with this, but on existing installations, appending 'true' to this file will help. Failed to start vserver 'thor' ERROR Maybe util-vserver related? The version of util-vserver that i'm using is 0.30.204 I then changed the ip of the vserver to 192.168.1.25 instead of 192.168.1.20, changed the /etc/resolv.conf of the host and then dns works. I then moved the 1 dir back to 0, changed the dev back to eth0 and it still worked. But from the moment i changed the ip & resolv.conf back to 192.168.1.20 name resolving stopped working from the host. Inside the vserver it still worked. Any ideas? Thanks Benedict ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux
Re: [Vserver] using djbdns (tinydns & dnscache) from within vserver
Hi, > you could alternatively use the 'plain' init style > and have a real init inside the guest, just as on > uml :) Herbert, would using the plain init style have advantages over what i'm doing now? >> Even from within the vserver doing for instance a dnsip doesn't work. > > how does it fail? As for the dnsip failing, it doesn't do anything as in not returning a value. When it works, it immediately returns the correct value. >> ccapabilities >> icmp >> ping > those are synonyms, so one of them should > be enough, IIRC raw_icmp i tried specifying the raw_icmp option in the file ccapabilities and this is what i got: === Unknown ccap 'raw_icmp' An error occured while executing the vserver startup sequence; when there are no other messages, it is very likely that the init-script (/etc/init.d/rc 2) failed. Common causes are: * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build method knows how to deal with this, but on existing installations, appending 'true' to this file will help. Failed to start vserver 'thor' === If i remove it then it works again. > probably the only thing really required to be changed > is the way you handle the networking, aside from that > djbdns should not have any issues, maybe you can > elaborate a little on your network setup, and how > you test? (ipconfig & route are way below) As for what kind of error, well it doesn't actually give a certain error but pinging the hosts or doing an dnsipq on a machine in the dns records doesn't work. After further testing, I really think it has to do with networking as you say. Some more about my network: Since i used to run 4 uml's, i wanted to ease the way i did networking and configured a bridge (br0) and on that bridge 4 tap devices that my uml's plugged into. Worked great. I no longer use the 4 uml's as they are now converted to vservers but the bridging is still on and i want to keep it that way because i might use the uml's to experiment (as in try things out and destroy it in the process :)). Now, sometimes when i start the vserver, the dns stuff works and sometimes it doesn't. Very weird. I have no clue on how i can track it. Nothing logged in my iptabels (i get a log when a packet is dropped or rejected) and i have no firewalling on the bridge. For instance, sometimes when i start the vserver, when exim comes up, it takes a looong time to start. It show this message "Starting MTA: " and then takes several minutes to go to the next program that needs to be started. I think this is because of a dns problem, in other words djbdns that isn't capable of doing what it needs to do. Then when i enter the vserver, none of the dns utilities work. I then close the vserver and restart it then and sometimes it then works. Other times i need to restart it several times and can't get it to work. Very strange. Last test i did was bringing the uml and the vserver back on but then use a different ip (/etc/vserver/thor/interfaces/0/ip) for the vserver. Previously i always shut down the uml and use the same ip and name for the vserver. Now i changed these settings. I changed these to "thor2": /etc/vservers/thor/uts/nodename /etc/vservers/thor/name I also changed the /etc/resolv.conf in this vserver to this: domain xyz nameserver 192.168.1.25 nameserver 127.0.0.1 where 192.168.1.25 is the vservers own ip adres (the new one, old one is .20) Then i restarted the vserver 5 times and all 5 times dns seems to work like it should. Thanks, Benedict = My wireless router has the ip 192.168.0.1 The wireless bridge attached to eth0 has ip 192.168.0.4 eth0 of the host has ip 192.168.0.2 eth1 of the host has ip 192.168.1.1 (bridge br0 gets this ip when i start teh bridging utils) The uml with djbdns has ip 192.168.1.20 and the vserver had this ip too as i never started them both at the same time. When i did so i changed the ip of the vserver to 192.168.1.25 IFCONFIG HOST = br0 Link encap:Ethernet HWaddr 00:10:B5:40:DD:EE inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2857 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:291940 (285.0 KiB) TX bytes:0 (0.0 b) eth0 Link encap:Ethernet HWaddr 00:10:B5:40:DE:14 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64372 errors:0 dropped:0 overruns:0 frame:0 TX packets:68799 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:41328067 (39.4 MiB) TX bytes:7599446 (7.2 MiB) Interrupt:10 Base address:0x9400 eth1 Link encap:Ethernet HWaddr 00:10:B5:40:DD
[Vserver] using djbdns (tinydns & dnscache) from within vserver
Hi, i installed the latest vserver patch on a pristine 2.6.16 kernel on a Debian Sarge. I made a vm and it all works fine. Now i have an uml running with tinydns and dnscache in it and i wanted to move that to vserver. First problem was that the supervising program wasn't run but i found a script somewhere to run it from the init procedure instead of from inittab so now it boots up fine. Problem is that dns resolving for my clients pc's doesn't work at all. Even from within the vserver doing for instance a dnsip doesn't work. >From the moment i stop the vserver and run the uml again, it all works. The uml was copied to the directory where the vserver resides so the dns config is the same. I then started to fiddle with capabilities because i thought this might be the problem. Here is what i added to the bcapabilities and ccapabilities file: bcapabilities NET_BIND_SERVICE NET_RAW NET_ADMIN NET_BROADCAST SYS_RESOURCE SYS_BOOT SYS_RAWIO ccapabilities icmp ping What needs to be changed in order to run djbdns? Thanks, Benedict ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
