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: Sun, 30 May 2010 14:13:51 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 30 May 2010 05:15:29 -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=yse0PDuLWuh9hLxLgOBOo32I6ojH+jtf6PrJkxFkXII=; b=sKcnhDX1x5gtSXaR53q9qL7Pe30kRgMSdl3SR3SV/Dx2GOseKo53i0q2w9VpbCnEgL Zmra8g8vlf4c52hZ2vxtO10t7TeRJC8Lkeg1sFMB/EBDIZQVMpDJIeKfiS94vaAlS1Zt ZdBt6CVRX9cQopgVaWPbKIYGK2VM4MY9oup/s=
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=RT6skiQiD0d7UPQK2DY8uy+7OIFoo/1G1kYh2YogXk9BxOqJQsiyAOVKVxPjN9Jyme zy3bBq6ElStyGEwkJN8cL2XVE0ZmPJJnOo+GZPLuIddPjS9P0kD0Zcc6FBSR+PIDvL4z 2Nc007YUS6RA4U2l/auT0R8FEwC87jsMrhgRc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTinoibCgpcTHDP8w9TdrFpoLvbl1-QCZLfiX_aS4@xxxxxxxxxxxxxx>
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> <AANLkTikc_I7s-dE1LjVo0ty3YHKHlIP1JLVjkM5iOgCc@xxxxxxxxxxxxxx> <566604cca85c71967caa9ad211f0a978.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <AANLkTik3yMFq-3NCG1sJcJ7lQhVrQdL6mMHjCd3Zpx1I@xxxxxxxxxxxxxx> <AANLkTinoibCgpcTHDP8w9TdrFpoLvbl1-QCZLfiX_aS4@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Any news?

On 28 May 2010 00:33, Flavio <fbcyborg@xxxxxxxxx> wrote:


On 27 May 2010 17:17, Flavio <fbcyborg@xxxxxxxxx> wrote:
I also had this kind of bug that the bridge wasn't always upped correctly
after xm startup.
I simply added "ifconfig xenbr0 0.0.0.0 up" to my /etc/conf.d/local.start.
I can try to do it on my system as well but I guess this is not sufficient because of
the fact, the xend daemon could get up earlier. I'm gonna giving a try.
Unfortunately, this didn't fix my problem. The main reason is that the local.start script
is the last one to be executed. So, xenbr0 bridge should start before the xend daemon.
Even though the "net" is in the depend as it follows:
depend() {
    need net
    before xendomains sshd ntp-client ntpd nfs nfsmount rsyncd portmap dhcp
}

This is not sufficient to solve the problem.

I think it's related to the xend init script, anyway.

--
Flavio



--
Flavio
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users