[Vserver] Re: Vserver on Fedora Core 5 - kernel issue
On 5/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:Message: 1Date: Sat, 06 May 2006 15:27:06 +0200 From: Daniel Hokka Zakrisson <[EMAIL PROTECTED]>Subject: Re: [Vserver] Vserver on Fedora Core 5 - kernel issueTo: vserver@list.linux-vserver.org Message-ID: <[EMAIL PROTECTED]>Content-Type: text/plain; charset=us-ascii; format=flowedDaniel Hokka Zakrisson wrote:> Jens Holze wrote: >>> Hi!>>>> I just tried to install Vserver after upgrading to Fedora Core 5. I>> was quite relieved to be able to use the rpms by Daniel and I did>> exactly as the howto instructed. I installed both kernel(-smp) and >> utils from dhozac's repository. However when I wanted to finish and>> rebooted I realized that the system didn't come up . Actually it hangs>> right after the message "activating quotas..." appears and the boot >> process switches to graphical booting. The system just locks and>> that's it.>>>> I do have these two kernels installed right now: 2.6.15-1.2054_FC5>> which was there initially and 2.6.16-1.2107_FC5.vs2.0.2.0.rc19.1 .>>> 1.2107_FC5 was a bit of a brown paper bag release upstream, which was> eventually pulled from the updates repository. Unfortunately, a new one> hasn't been pushed yet, and I'm not sure if all of the issues are fixed > in CVS yet. Hopefully a new one will be released shortly.>1.2111_FC5 was pushed yesterday, and I just pushed the new patchedkernels. This is supposed to fix your problems. Great, it actually did! Thanks and btw great work you did there! You cannot imagine the joy in the eyes of my bosses if I tell them that vservers are up and running again. ;-)Jens ___Vserver mailing listVserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver-- "Wars not make one great" - Master Yoda[EMAIL PROTECTED] - http://yodahome.deICQ: 252623701senseless wisdom of life - a geek's blog - http://yodahome.de/blog ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Vserver on Fedora Core 5 - kernel issue
Hi!I just tried to install Vserver after upgrading to Fedora Core 5. I was quite relieved to be able to use the rpms by Daniel and I did exactly as the howto instructed. I installed both kernel(-smp) and utils from dhozac's repository. However when I wanted to finish and rebooted I realized that the system didn't come up . Actually it hangs right after the message "activating quotas..." appears and the boot process switches to graphical booting. The system just locks and that's it. I do have these two kernels installed right now: 2.6.15-1.2054_FC5 which was there initially and 2.6.16-1.2107_FC5.vs2.0.2.0.rc19.1 . The first kernel still works fine. I also tried the patched non-smp kernel, same thing. Anybody here who experienced something similar? I let the system wait over night and somehow the boot process must have continued at one point but the system seemed broken then. Any idea is apreciated!RegardsJens Holze-- "Wars not make one great" - Master Yoda[EMAIL PROTECTED] - http://yodahome.deICQ: 252623701senseless wisdom of life - a geek's blog - http://yodahome.de/blog ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vservers don't start after update to 2.01
2006/1/27, Herbert Poetzl <[EMAIL PROTECTED]>: > On Fri, Jan 27, 2006 at 11:15:43AM +0100, Jens Holze wrote: > > 2006/1/25, Herbert Poetzl <[EMAIL PROTECTED]>: > > > On Wed, Jan 25, 2006 at 12:45:55PM +0100, Jens Holze wrote: > > > > 2006/1/13, Jens Holze <[EMAIL PROTECTED]>: > > > > > 2006/1/11, Herbert Poetzl <[EMAIL PROTECTED]>: > > > > > > On Wed, Jan 11, 2006 at 04:03:58PM +0100, Jens Holze wrote: > > > > > > > Hi! > > > > > > > > > > > > > > I updated VServer from 2.00 to 2.01 by patching a new > > > > > > > 2.6.14.4-kernel > > > > > > > and installing the utils (209) from self-build rpms on Fedora > > > > > > > Core 4. > > > > > > > > > > > > maybe the installation of your 'self built' utils is a > > > > > > little incomplete ... I'd try with the source tar, and > > > > > > after a proper configuration (to get your pathes right) > > > > > > do the 'make install' and 'make install-distribution' > > > > > > > > > > I erased the rpms and installed from source (with the prefix=/). > > > > > Everything is in place now, save_ctxinfo in /lib/util-vserver/ . > > > > > > > > > > > > Everything worked prior to that but since then I can't manage to > > > > > > > start > > > > > > > any debian-based Vservers. I thought something with the kernel > > > > > > > went > > > > > > > wrong so I build it anew but that didn't solve anything. > > > > > > > When trying to start a vserver I get: > > > > > > > > > > > > > > // RTNETLINK answers: File exists > > > > > > > > > > > > this means that the 'configured' IP(s) already exists, > > > > > > maybe with a different netmask/prefix, check with > > > > > > 'ip addr ls' and remove the 'offending' IP(s) > > > > > > > > > > > > > > > > Yeah I know, this one is not the problem, I just took existing > > > > > settings and made a new server from it hoping that would eliminate the > > > > > save_ctxinfo problem... > > > > > > > > > > > > // save_ctxinfo: execv(): No such file or directory > > > > > > > > > > > > this very much looks like the save_ctxinfo is failing > > > > > > possible reasons could be: > > > > > > > > > > > > - /lib/util-vserver/save_ctxinfo (or wherever it is > > > > > >on your distro) is not executable or missing > > > > > > - /etc/vservers/.defaults/run.rev is not pointing > > > > > >to a valid directory to store the info > > > > > > - the directory /var/run/vservers.rev is not writeable > > > > > >or does not exist > > > > > > > > > > > > > > > > I thought so but: save_ctxinfo is at the exact location and > > > > > executable... /run.rev is there and pointing to /var/run/vservers.rev > > > > > which exists and is writeable (there are directories inside for the > > > > > fedora vservers which are running!). It must be something special that > > > > > is done in debian vservers which doesn't happen with fedora core > > > > > vservers?! > > > > > Also, I wonder where the vserver starting script looks for this file, > > > > > is it possible that I have to edit any config file? I mean it's in the > > > > > same directory so why doesn't he find it? > > > > > > > > > > > > // 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 3) 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, > >
Re: [Vserver] vservers don't start after update to 2.01
2006/1/13, Jens Holze <[EMAIL PROTECTED]>: > 2006/1/11, Herbert Poetzl <[EMAIL PROTECTED]>: > > On Wed, Jan 11, 2006 at 04:03:58PM +0100, Jens Holze wrote: > > > Hi! > > > > > > I updated VServer from 2.00 to 2.01 by patching a new 2.6.14.4-kernel > > > and installing the utils (209) from self-build rpms on Fedora Core 4. > > > > maybe the installation of your 'self built' utils is a > > little incomplete ... I'd try with the source tar, and > > after a proper configuration (to get your pathes right) > > do the 'make install' and 'make install-distribution' > > I erased the rpms and installed from source (with the prefix=/). > Everything is in place now, save_ctxinfo in /lib/util-vserver/ . > > > > Everything worked prior to that but since then I can't manage to start > > > any debian-based Vservers. I thought something with the kernel went > > > wrong so I build it anew but that didn't solve anything. > > > When trying to start a vserver I get: > > > > > > // RTNETLINK answers: File exists > > > > this means that the 'configured' IP(s) already exists, > > maybe with a different netmask/prefix, check with > > 'ip addr ls' and remove the 'offending' IP(s) > > > > Yeah I know, this one is not the problem, I just took existing > settings and made a new server from it hoping that would eliminate the > save_ctxinfo problem... > > > > // save_ctxinfo: execv(): No such file or directory > > > > this very much looks like the save_ctxinfo is failing > > possible reasons could be: > > > > - /lib/util-vserver/save_ctxinfo (or wherever it is > >on your distro) is not executable or missing > > - /etc/vservers/.defaults/run.rev is not pointing > >to a valid directory to store the info > > - the directory /var/run/vservers.rev is not writeable > >or does not exist > > > > I thought so but: save_ctxinfo is at the exact location and > executable... /run.rev is there and pointing to /var/run/vservers.rev > which exists and is writeable (there are directories inside for the > fedora vservers which are running!). It must be something special that > is done in debian vservers which doesn't happen with fedora core > vservers?! > Also, I wonder where the vserver starting script looks for this file, > is it possible that I have to edit any config file? I mean it's in the > same directory so why doesn't he find it? > > > > // 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 3) 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 'debian_two' > > > > > > The common causes don't really help and I can't think of anything > > > else. I even build an all new debian vserver but even this one doesn't > > > boot. Other (Fedora-based) vservers do work perfectly. Any help would > > > be greatly appreciated. > > > > yes, well, to explain all kinds of errors in a tool > > of this complexity is almost impossible ... > > Of course it is, it's just that its obviously a different problem as > far as I get it. > > Jens > > HTH, > > Herbert > > > > > > > > Jens > > > ___ > > > Vserver mailing list > > > Vserver@list.linux-vserver.org > > > http://list.linux-vserver.org/mailman/listinfo/vserver > > Hi! I had an intense look at the installation since obviously something must have gone wrong there (as you pointed out, too). I checked for vprocunhide being in place and executed (which is the case) and then ran the testme.sh once more where I first got an error with chcontext in /usr/sbin/chcontext. There should be no such file since I erased those with rpm and then installed from source to /(etc,lib/util-verser,sbin). That drew my attention to the fact that obviously some files of the prior rpm installation remained on the system and I wondered whether that causes the problem (allthough I still wonder why it only happens with debian based vservers). After I deleted the redundant chcontext the testme.sh found no error at all. Then I deleted /usr/sbin/vserver presuming that /sbin/vserver should be used. However, the problem remained, the servers fail to boot while directories for their context are created under /var/run/vservers.rev and the run files do point to the respective files in /var/run/vservers as if the servers actually were running. Maybe he's looking for the save_ctxinfo in all the wrong places? I'm sure it's just some really stupid tweak I simply couldn't think of yet. Any other suggestions? Thanks Jens ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vservers don't start after update to 2.01
2006/1/11, Herbert Poetzl <[EMAIL PROTECTED]>: > On Wed, Jan 11, 2006 at 04:03:58PM +0100, Jens Holze wrote: > > Hi! > > > > I updated VServer from 2.00 to 2.01 by patching a new 2.6.14.4-kernel > > and installing the utils (209) from self-build rpms on Fedora Core 4. > > maybe the installation of your 'self built' utils is a > little incomplete ... I'd try with the source tar, and > after a proper configuration (to get your pathes right) > do the 'make install' and 'make install-distribution' I erased the rpms and installed from source (with the prefix=/). Everything is in place now, save_ctxinfo in /lib/util-vserver/ . > > Everything worked prior to that but since then I can't manage to start > > any debian-based Vservers. I thought something with the kernel went > > wrong so I build it anew but that didn't solve anything. > > When trying to start a vserver I get: > > > > // RTNETLINK answers: File exists > > this means that the 'configured' IP(s) already exists, > maybe with a different netmask/prefix, check with > 'ip addr ls' and remove the 'offending' IP(s) > Yeah I know, this one is not the problem, I just took existing settings and made a new server from it hoping that would eliminate the save_ctxinfo problem... > > // save_ctxinfo: execv(): No such file or directory > > this very much looks like the save_ctxinfo is failing > possible reasons could be: > > - /lib/util-vserver/save_ctxinfo (or wherever it is >on your distro) is not executable or missing > - /etc/vservers/.defaults/run.rev is not pointing >to a valid directory to store the info > - the directory /var/run/vservers.rev is not writeable >or does not exist > I thought so but: save_ctxinfo is at the exact location and executable... /run.rev is there and pointing to /var/run/vservers.rev which exists and is writeable (there are directories inside for the fedora vservers which are running!). It must be something special that is done in debian vservers which doesn't happen with fedora core vservers?! Also, I wonder where the vserver starting script looks for this file, is it possible that I have to edit any config file? I mean it's in the same directory so why doesn't he find it? > > // 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 3) 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 'debian_two' > > > > The common causes don't really help and I can't think of anything > > else. I even build an all new debian vserver but even this one doesn't > > boot. Other (Fedora-based) vservers do work perfectly. Any help would > > be greatly appreciated. > > yes, well, to explain all kinds of errors in a tool > of this complexity is almost impossible ... Of course it is, it's just that its obviously a different problem as far as I get it. Jens > HTH, > Herbert > > > > > Jens > > ___ > > Vserver mailing list > > Vserver@list.linux-vserver.org > > http://list.linux-vserver.org/mailman/listinfo/vserver > -- "Wars not make one great" - Master Yoda [EMAIL PROTECTED] - http://yodahome.de ICQ: 252623701 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] vservers don't start after update to 2.01
Hi! I updated VServer from 2.00 to 2.01 by patching a new 2.6.14.4-kernel and installing the utils (209) from self-build rpms on Fedora Core 4. Everything worked prior to that but since then I can't manage to start any debian-based Vservers. I thought something with the kernel went wrong so I build it anew but that didn't solve anything. When trying to start a vserver I get: // RTNETLINK answers: File exists // save_ctxinfo: execv(): No such file or directory // // 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 3) 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 'debian_two' The common causes don't really help and I can't think of anything else. I even build an all new debian vserver but even this one doesn't boot. Other (Fedora-based) vservers do work perfectly. Any help would be greatly appreciated. Jens -- "Wars not make one great" - Master Yoda [EMAIL PROTECTED] - http://yodahome.de ICQ: 252623701 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] vserver-copy deprecated?!
Hi! I just realised that there is this copy program among the utils but it doesn't work (obviously because of the changes since the alpha, looks for .conf file). While copying the servers is not hard to do manually, is somebody actually working on this tool or is it going to vanish? Regards Jens -- "Wars not make one great" - Master Yoda [EMAIL PROTECTED] - http://yodahome.de ICQ: 252623701 senseless wisdom of life - my geeky blog under http://yodahome.de/blog ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] error trying to dnsmasq on a debian sarge
2005/10/29, Herbert Poetzl <[EMAIL PROTECTED]>: > On Fri, Oct 28, 2005 at 04:53:49PM +0200, Jens Holze wrote: > > Hi! > > > > I've just set up the latest vserver on FC4 and added two vservers one > > based on debian sarge the other on FC4. The debian one should do some > > basic networking stuff and backups. Therefore I'd like to run dnsmasq > > on it. I installed it but when I activated it's dhcp function, i get > > this message at boot: > > > > Starting DNS forwarder and DHCP server: dnsmasqdnsmasq: cannot create > > DHCP packet socket: Operation not permitted. Is CONFIG_PACKET enabled > > in your kernel? (failed). > > > > Of course, CONFIG_PACKET is enabled in kernel, so I'm not really > > sure what to do to get the program running. Do I need to add S_CAPS > > options? > > well, depends on what the tool is 'trying' to do ... > maybe it is opening a raw socket (or trying to do so) > at least the DHCP stuff seems to point into that direction Well, dnsmasq is a dhcp and dns server which is actually what I want it to do because names of all the machines that get ips and announce their names via dhcp are automatically put together (it's hard work to do this with bind and dhcp). The server will not be publically accessible (lowered security is no problem) it's simply because I like debian and thought I could have a virtual debian on fedora (and it works well apart from this problem) where I could put all the uninteresting network services... > this would mean that it would require CAP_NET_RAW which > in turn would permit interface sniffing inside the guest I found that I needed to create a .conf for my server (there was none before this) and put the SCAPS variable in it. But nothing changed when booting the server. Where can I see that the options are actually recognized? > maybe the DHCP stuff can be deactivated via some config > option (for dnsmasqd)? Yes, it can. But that's not what I intended. Is it really a problem to run a dhcp inside a vserver? Jens > best, > Herbert > > > Thanks in advance! > > > > Jens > > > > -- -- "Wars not make one great" - Master Yoda [EMAIL PROTECTED] - http://yodahome.de ICQ: 252623701 watch http://littlevampire.yodahome.de the relaunch is coming on Halloween '05 senseless wisdom of life - my geeky blog under http://yodahome.de/blog ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] error trying to dnsmasq on a debian sarge
Hi! I've just set up the latest vserver on FC4 and added two vservers one based on debian sarge the other on FC4. The debian one should do some basic networking stuff and backups. Therefore I'd like to run dnsmasq on it. I installed it but when I activated it's dhcp function, i get this message at boot: Starting DNS forwarder and DHCP server: dnsmasqdnsmasq: cannot create DHCP packet socket: Operation not permitted. Is CONFIG_PACKET enabled in your kernel? (failed). Of course, CONFIG_PACKET is enabled in kernel, so I'm not really sure what to do to get the program running. Do I need to add S_CAPS options? Thanks in advance! Jens -- "Wars not make one great" - Master Yoda [EMAIL PROTECTED] - http://yodahome.de ICQ: 252623701 watch http://littlevampire.yodahome.de the relaunch is coming on Halloween '05 senseless wisdom of life - my geeky blog under http://yodahome.de/blog ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
