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

[Xen-users] XCP - Lost NIC's...

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XCP - Lost NIC's...
From: Kristoffer Egefelt <dr.fersken@xxxxxxxxx>
Date: Tue, 8 Mar 2011 13:49:11 +0100
Delivery-date: Tue, 08 Mar 2011 04:50:27 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=8keI+HiKalzkwX2JfjqGh9HxiaYgU2CuDOapIsDI2G8=; b=TK857I+svtBBAiAGNFxE5XE4Kr1qh5CQc7b8pwf7F9/SKIskSmm+aapFdCv+paTRxc B+cYm1tV7ywWSVOkUkZ6n79rBEn7L6lkrQUwIR3j5N58yc6kkgk1Cjbfx6JRHC570fz6 Zf0R1jXzOIcQ+769F7ha6n3oo3rrGC4OcMsjQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=xiPOYKNbKOcjVwnck891ode+kHh19UewXM2Wv3iko0R2xOrdIoelR3JCQq6+k26sgH TrFwbWIotr/sT7rp4lgBJxwpTdq5qDZJ+8GQ3SHum8lkzBLYbAIES4EKLtV1VYIIBx2e 1Cgo92k3mPTYIU2DhhNcOCwYiMzIaryL4591U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi list,

we're testing XCP 1.0 build 42052 and have run into a strange issue.

One master, one slave in a pool, both configured with plain slb bond0
with management interface untagged, and vm networks/vlans on top of
the bond0
Setup has been running for a week with no problems.
This morning we cannot connect to the pool via xencenter.
SSH to master works, but theres no management interface configured and
no NIC's available - after reboot ssh do not work anymore.
Connecting to console, running ethtool eth0 says no link although
theres link on the switch.
Restarting network, running ifup/down, manually assigning ip's do not
work - theres no interfaces.

SSH to slave does not work.
Connecting to console, I cannot login to xsconsole when trying to do anything.

Running xe pool-emergency-transition-to-master on master - server
reboots and work :-)
Restarting slave, everything works, though the master cannot connect
to shared iscsi storage, SR_error 141.

Removing and reattaching the SR works.

The logfiles is not helping me much figuring out what happened -
master complains that it can't reach the slave, slave is not logging
anything.

Mar  7 21:44:49 node0106 xapi: [ warn|node0106|11 heartbeat|Heartbeat
D:b450677c6101|http] HTTP connection closed immediately with before
any data received
Mar  7 21:44:49 node0106 xapi: [ warn|node0106|11 heartbeat|Heartbeat
D:b450677c6101|http] stunnel pid: 4365 caught
Xmlrpcclient.Empty_response_from_server

[20110307T20:44:19.628Z|error|node0106|6776
inet-RPC|session.login_with_password D:9f2cd8a60315|stunnel]
get_reusable_stunnel: fresh stunnel failed reusable check; delaying
10.00 seconds before reconnecting to 10.10.3.108:443 (attempt 1 / 10)

Any hints is greatly appreciated.

Thanks! :-)

Regards
Kristoffer

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

<Prev in Thread] Current Thread [Next in Thread>