WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] /etc/xen/scripts/network-bridge: line 118: sigerr: comm

To: daniel.schmitt@xxxxxxx
Subject: Re: [Xen-users] /etc/xen/scripts/network-bridge: line 118: sigerr: command not found
From: Flavio <fbcyborg@xxxxxxxxx>
Date: Thu, 27 May 2010 09:50:45 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 27 May 2010 00:52:40 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=mMUlRNaP6Ob+FVEYMPpE/wgeatY5OwyTeChTzMXVbng=; b=rdEFynGI9VXOtFl9tvxBY0WqcxnzHoJ8AiAFQ/iTKek+0cY7p9chBHcyCkScZaPMna C8d1dZigu6KLVdzaL0uJcnkHIQRvCRDtdnkCMiex3Wobd2eydmnoOw7C/zENMnIQ0tqW MX7KwVUUhzTbBy/Ji4zRs6bPQBcML4FumxBGQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=kkRLNyfY3B81oOtyCPfziH5Pt4aXcPHtEhdtN2Y4STLDdOb6v3QBEu/VouSMYcQea+ 0My7zPHhNjrJCwt22ayXMG/gB1sCa+/zxalrdppT8hodaKNr6N/ZPznFdiWde2z1+djc 9GmfIVTIl9KeEfIqz+nYSs58/6P0rvS8ruX1s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <348d8f0d75241e23b5cf947c0a61fd1f.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <537a33436517066504a9979d7e8e0aa3.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <AANLkTilbcfVSs6sAvxzLIUNd-FXkyxl9lki6XOmlbtmi@xxxxxxxxxxxxxx> <AANLkTimVUkXRymKRvaUHPLawbxrWiK4qaF6AG_kWh2Hy@xxxxxxxxxxxxxx> <348d8f0d75241e23b5cf947c0a61fd1f.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx


On 27 May 2010 09:40, Daniel Schmitt <daniel.schmitt@xxxxxxx> wrote:
Hmm.
I found the place where something wrong happened by using bash debug mode.
Add " -x" to the 1st line of network-bridge script. There is something
written "#!/bin/bash". Then you will see a lot of debug output next boot.

For my problem at one place in the script "sigerr" was returned by one
command/function and incorrectly used as gateway ip address.

Daniel

I've just made another attempt.
Just after removing the claim_lock* lines, I also specified the
bridge in the file /etc/xen/xend-config.sxp as it follows:
(network-script 'network-bridge bridge=xenbr0')

I always set up that line in the following way since so far:
(network-script network-bridge)

Now that I modified that line, I get the xenbr0 interface up at boot time, but
there is also the peth0 interface (I don't want it).

I simply had to perform a dhcpcd xenbr0 and the network came up.
But this should happen automatically, I don't want to perform a dhcpcd
each time.
--
Flavio
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users