Re: [Vserver] Looking for help to track down some problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Herbert Poetzl wrote: | On Tue, Nov 23, 2004 at 06:32:33PM +1030, Darryl Ross wrote: |> I had this issue today myself. I have a machine with multiple ethernet |> cards in it. The debian-newvserver.sh script does not seem to honor the |> flag for specifying which interface to bind a vserver to (in my case I |> had to bind it to eth1). | | hmm, please provide some details like: | | - tool version | - configuration style | - what you changed Now that the rush of getting the machines set up is past, I was going to send in a patch today to fix this particular problem. I don't have access to the machine in question at the moment, so it'll have to wait till I get to work. Regards Darryl -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFBo6zJ/XQ6DbmPjokRAlXJAJ0fNCEG7HAUg+8tmII01EMP1GUkGwCfc8Nr FsZSyj3wI43DgnkYTCYXoF8= =nRpZ -END PGP SIGNATURE- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Looking for help to track down some problems
On Tue, Nov 23, 2004 at 06:32:33PM +1030, Darryl Ross wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Lars E. D. Jensen wrote: > | This is still coming when I start the vserver (but doesn't appear when > I shut > | down): > | > | SIOCSIFBRDADDR: Cannot assign requested address > | SIOCSIFFLAGS: Cannot assign requested address > > I had this issue today myself. I have a machine with multiple ethernet > cards in it. The debian-newvserver.sh script does not seem to honor the > flag for specifying which interface to bind a vserver to (in my case I > had to bind it to eth1). hmm, please provide some details like: - tool version - configuration style - what you changed TIA, Herbert > Manually updating the config file for the vserver with the correct > interface fixed the problem. > > Regards > Darryl > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.1 (MingW32) > > iD8DBQFBou6Z/XQ6DbmPjokRArD4AJsHRFDkHjg7cn4cQCJiDqkjOhlLiQCfZuM1 > 21aBaUPZKR3qXgRQJnnkRyU= > =tSsS > -END PGP SIGNATURE- > ___ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Looking for help to track down some problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lars E. D. Jensen wrote: | This is still coming when I start the vserver (but doesn't appear when I shut | down): | | SIOCSIFBRDADDR: Cannot assign requested address | SIOCSIFFLAGS: Cannot assign requested address I had this issue today myself. I have a machine with multiple ethernet cards in it. The debian-newvserver.sh script does not seem to honor the flag for specifying which interface to bind a vserver to (in my case I had to bind it to eth1). Manually updating the config file for the vserver with the correct interface fixed the problem. Regards Darryl -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFBou6Z/XQ6DbmPjokRArD4AJsHRFDkHjg7cn4cQCJiDqkjOhlLiQCfZuM1 21aBaUPZKR3qXgRQJnnkRyU= =tSsS -END PGP SIGNATURE- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Looking for help to track down some problems
On Mon, Nov 22, 2004 at 07:32:58PM +0100, Lars E. D. Jensen wrote: > Hi Herbert > > Thanks a lot for your help! > > I've followed your advice and managed to configure the vserver so almost all > errors are gone. > > This is still coming when I start the vserver (but doesn't appear when I shut > down): > > SIOCSIFBRDADDR: Cannot assign requested address > SIOCSIFFLAGS: Cannot assign requested address this could also be caused by having an ip configured for creation within the vserver scripts, but the ip already is configured on the system ... IPROOT=10.0.0.1 IPROOTDEV=eth0 if the system already has a 10.0.0.1 the tools will try to create an alias with this ip, and fail ... removing the eth0 will solve that issue ... > I removed all /etc/init.d/ scripts except the ones I use for ssh and apache. > > Does it have something to do with proc ? (I'm guessing, since I don't > understand vserver completely yet) > > I've read this security tip in a document: > "make sure your /proc entries are restricted" > > Restricted to what? Is this inside the virtual server or on host server? this is called proc security, and is done by recent util-vserver automatically, but probably doesn't apply in your case, as the proc security is off by default ... for details see here: http://linux-vserver.org/Documentation http://linux-vserver.org/Proc-Security HTH, Herbert > /etc/mtab inside vserver shows this: > proc /proc proc rw 0 0 > > Sorry if this is a trivial question, but I find the documentation very wide > spread and a little difficult to navigate. > > > Mandag den 22. november 2004 16:13 skrev Herbert Poetzl: > > On Mon, Nov 22, 2004 at 03:41:44PM +0100, Lars E. D. Jensen wrote: > > > Hi > > > > > > I want to track down some problems I have with my first vserver setup :) > > > > > > I'm using the newest patch for kernel 2.4.28 -> 2.4.28-vs1.29 and the > > > appropiate util-vserver tools. The vserver is running on Debian linux > > > 3.0r3. > > > > > > I get this when I start the vserver: > > > SIOCSIFBRDADDR: Cannot assign requested address > > > SIOCSIFFLAGS: Cannot assign requested address > > > > your vserver is trying to configure the interfaces, > > this is not allowed and will fail > > > > -- > Med venlig hilsen > > Lars E. D. Jensen > [EMAIL PROTECTED] > ___ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Looking for help to track down some problems
Hi Herbert Thanks a lot for your help! I've followed your advice and managed to configure the vserver so almost all errors are gone. This is still coming when I start the vserver (but doesn't appear when I shut down): SIOCSIFBRDADDR: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address I removed all /etc/init.d/ scripts except the ones I use for ssh and apache. Does it have something to do with proc ? (I'm guessing, since I don't understand vserver completely yet) I've read this security tip in a document: "make sure your /proc entries are restricted" Restricted to what? Is this inside the virtual server or on host server? /etc/mtab inside vserver shows this: proc /proc proc rw 0 0 Sorry if this is a trivial question, but I find the documentation very wide spread and a little difficult to navigate. Mandag den 22. november 2004 16:13 skrev Herbert Poetzl: > On Mon, Nov 22, 2004 at 03:41:44PM +0100, Lars E. D. Jensen wrote: > > Hi > > > > I want to track down some problems I have with my first vserver setup :) > > > > I'm using the newest patch for kernel 2.4.28 -> 2.4.28-vs1.29 and the > > appropiate util-vserver tools. The vserver is running on Debian linux > > 3.0r3. > > > > I get this when I start the vserver: > > SIOCSIFBRDADDR: Cannot assign requested address > > SIOCSIFFLAGS: Cannot assign requested address > > your vserver is trying to configure the interfaces, > this is not allowed and will fail > -- Med venlig hilsen Lars E. D. Jensen [EMAIL PROTECTED] ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Looking for help to track down some problems
On Mon, Nov 22, 2004 at 03:41:44PM +0100, Lars E. D. Jensen wrote: > Hi > > I want to track down some problems I have with my first vserver setup :) > > I'm using the newest patch for kernel 2.4.28 -> 2.4.28-vs1.29 and the > appropiate util-vserver tools. The vserver is running on Debian linux 3.0r3. > > I get this when I start the vserver: > SIOCSIFBRDADDR: Cannot assign requested address > SIOCSIFFLAGS: Cannot assign requested address your vserver is trying to configure the interfaces, this is not allowed and will fail > I get this when I stop the vserver: > SIOCSIFBRDADDR: Cannot assign requested address > SIOCSIFFLAGS: Cannot assign requested address > (The same as when I start the vserver.) again, the vserver scripts (inside the vserver) try to shutdown the interface, which you do not want and therefore is not allowed either ... > hwclock is unable to get I/O port access: the iopl(3) call failed. > mount: can't find / in /etc/fstab or /etc/mtab again something which isn't supposed to happen inside a vserver, you do not want the vserver to mess with your cmos clock, right? > I've googled but found no solution. How can I solve these issues? > I've tried to install Apache 1.3 and it runs fine (I think). remove all hardware related init scripts from your vserver and everything should be fine ... using a prebuilt image or the alpha tools will take care of taht for you ... > See below for full context when starting/stopping the vserver: > > Starting the vserver - In context (marked # error?): > /var/util-vserver/sbin# ./vserver mt start > Starting the virtual server mt > Server mt is not running > SIOCSIFBRDADDR: Cannot assign requested address # error ? > SIOCSIFFLAGS: Cannot assign requested address # error ? > ipv4root is now xxx.xxx.xxx.xxx > Host name is now dcmshvs1 > Domain name is now dcmshvs1.dcmedia.biz > New security context is 49154 try to use static context ids, otherwise you will ran into problems once you want to use xid tagging > Starting system log daemon: syslogd. > Starting kernel log daemon: klogd. > Starting internet superserver: inetd. > Starting PCMCIA services: module directory /lib/modules/2.4.28-vs1.29/pcmcia nothing which should happen inside a vserver, the kernel is maintained on the host. period. > not found. > Starting OpenBSD Secure Shell server: sshd. > Starting deferred execution scheduler: atd. > Starting periodic command scheduler: cron. > Starting web server: apache. > > Stopping the vserver - In context (marked # error?): > /var/util-vserver/sbin# ./vserver mt stop > Stopping the virtual server mt > Server mt is running > SIOCSIFBRDADDR: Cannot assign requested address # error ? > SIOCSIFFLAGS: Cannot assign requested address # error ? > ipv4root is now xxx.xxx.xxx.xxx > New security context is 49153 > Stopping periodic command scheduler: cron. > Stopping web server: apache. > Stopping internet superserver: inetd. > Shutting down PCMCIA services:. > Stopping OpenBSD Secure Shell server: sshd. > Saving the System Clock time to the Hardware Clock... > hwclock is unable to get I/O port access: the iopl(3) call failed. # error ? > Hardware Clock updated to Mon Nov 22 13:45:13 UTC 2004. > Saving state of known serial devices... backing up serial.conf done. > Stopping deferred execution scheduler: atd. > Aborting iptables load: unknown ruleset, "inactive". you do not want klogd inside a vserver either (it won't work anyway) > Stopping kernel log daemon: klogd. > Stopping system log daemon: syslogd. > Sending all processes the TERM signal... done. > Sending all processes the KILL signal... done. all the stuff below is not supposed to happen inside a vserver, so remove/deconfigure relevant scripts > Saving random seed... done. > Unmounting remote filesystems... done. > Deconfiguring network interfaces: done. > Deactivating swap... done. > Unmounting local filesystems... done. > mount: can't find / in /etc/fstab or /etc/mtab # error ? > Rebooting... sleeping 5 seconds > Killing all processes HTH, Herbert > -- > Med venlig hilsen > > Lars E. D. Jensen > [EMAIL PROTECTED] > ___ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Looking for help to track down some problems
Hi I want to track down some problems I have with my first vserver setup :) I'm using the newest patch for kernel 2.4.28 -> 2.4.28-vs1.29 and the appropiate util-vserver tools. The vserver is running on Debian linux 3.0r3. I get this when I start the vserver: SIOCSIFBRDADDR: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address I get this when I stop the vserver: SIOCSIFBRDADDR: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address (The same as when I start the vserver.) hwclock is unable to get I/O port access: the iopl(3) call failed. mount: can't find / in /etc/fstab or /etc/mtab I've googled but found no solution. How can I solve these issues? I've tried to install Apache 1.3 and it runs fine (I think). See below for full context when starting/stopping the vserver: Starting the vserver - In context (marked # error?): /var/util-vserver/sbin# ./vserver mt start Starting the virtual server mt Server mt is not running SIOCSIFBRDADDR: Cannot assign requested address # error ? SIOCSIFFLAGS: Cannot assign requested address # error ? ipv4root is now xxx.xxx.xxx.xxx Host name is now dcmshvs1 Domain name is now dcmshvs1.dcmedia.biz New security context is 49154 Starting system log daemon: syslogd. Starting kernel log daemon: klogd. Starting internet superserver: inetd. Starting PCMCIA services: module directory /lib/modules/2.4.28-vs1.29/pcmcia not found. Starting OpenBSD Secure Shell server: sshd. Starting deferred execution scheduler: atd. Starting periodic command scheduler: cron. Starting web server: apache. Stopping the vserver - In context (marked # error?): /var/util-vserver/sbin# ./vserver mt stop Stopping the virtual server mt Server mt is running SIOCSIFBRDADDR: Cannot assign requested address # error ? SIOCSIFFLAGS: Cannot assign requested address # error ? ipv4root is now xxx.xxx.xxx.xxx New security context is 49153 Stopping periodic command scheduler: cron. Stopping web server: apache. Stopping internet superserver: inetd. Shutting down PCMCIA services:. Stopping OpenBSD Secure Shell server: sshd. Saving the System Clock time to the Hardware Clock... hwclock is unable to get I/O port access: the iopl(3) call failed. # error ? Hardware Clock updated to Mon Nov 22 13:45:13 UTC 2004. Saving state of known serial devices... backing up serial.conf done. Stopping deferred execution scheduler: atd. Aborting iptables load: unknown ruleset, "inactive". Stopping kernel log daemon: klogd. Stopping system log daemon: syslogd. Sending all processes the TERM signal... done. Sending all processes the KILL signal... done. Saving random seed... done. Unmounting remote filesystems... done. Deconfiguring network interfaces: done. Deactivating swap... done. Unmounting local filesystems... done. mount: can't find / in /etc/fstab or /etc/mtab # error ? Rebooting... sleeping 5 seconds Killing all processes -- Med venlig hilsen Lars E. D. Jensen [EMAIL PROTECTED] ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
