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-api

Re: [Xen-API] XCP servers rebooting

To: Mike McClurg <mike.mcclurg@xxxxxxxxxx>
Subject: Re: [Xen-API] XCP servers rebooting
From: R J <torushikeshj@xxxxxxxxx>
Date: Fri, 27 May 2011 21:12:35 +0530
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 27 May 2011 20:04:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=HPB/fL57VsYpx8wTJ0qgGaTM6JCblDA26s3fF9HDrvM=; b=FdaxG7R46mhmaRPf++wL2LGy67uTAOkMJvLlWz/HGvvS1iwnVL6mN93XFAErQjIxw4 /o66dEYMjAccBchRoJXy1sC9tEMOLQjIZyswEf8Zh+vtB0lS3/vch7gIH5WJRrsI/czO qCiYfAT4KsFVTHqf1ZCyu5diD0w/mNYb9pOIE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pzfSv7NWDcGq+UxwVMcBldjPLYPA8LCp0evoo6lec11tJgfToWY7xtlrNtb3hZi9DS WPXJsuFt8KOYSShY+EUME+UEvRsTStL8JfMeNXZnR77bRXeXQuWBayk05zUcvXbEj0yF 3TMrALQY+Ktpj/D27zDX+1EePfHZUshPbTQYU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DDF7911.6030506@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTinQCqP=UkPAB1XdgZbUF0kNC3h+OA@xxxxxxxxxxxxxx> <4DDF7911.6030506@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx


On Fri, May 27, 2011 at 3:42 PM, Mike McClurg <mike.mcclurg@xxxxxxxxxx> wrote:
On 26/05/11 16:06, Rushikesh J wrote:
Hello List,


I have two XCP 1 servers in a pool which has a storage ( 1TB ) on QLogic FC. From past few days the XCP servers are automatically rebooting giving following error

# tail /va/log/kern.log

May 26 12:35:59 xcp1-master kernel:  rport-3:0-38: blocked FC remote port time out: removing rport
May 26 12:36:37 xcp1-master kernel:  rport-3:0-39: blocked FC remote port time out: removing rport
May 26 13:01:10 xcp1-master kernel:  rport-3:0-40: blocked FC remote port time out: removing rport
May 26 13:02:07 xcp1-master kernel:  rport-3:0-41: blocked FC remote port time out: removing rport
May 26 13:16:35 xcp1-master kernel:  rport-3:0-25: blocked FC remote port time out: removing rport
May 26 13:38:37 xcp1-master kernel:  rport-3:0-42: blocked FC remote port time out: removing rport
May 26 13:43:47 xcp1-master kernel:  rport-3:0-43: blocked FC remote port time out: removing rport
May 26 13:44:53 xcp1-master kernel:  rport-3:0-44: blocked FC remote port time out: removing rport
May 26 13:51:07 xcp1-master kernel:  rport-3:0-47: blocked FC remote port time out: removing rport
May 26 13:53:43 xcp1-master kernel:  rport-3:0-45: blocked FC remote port time out: removing rport
May 26 14:39:58 xcp1-master kernel:  rport-3:0-46: blocked FC remote port time out: removing rport
May 26 14:43:10 xcp1-master kernel:  rport-3:0-49: blocked FC remote port time out: removing rport
May 26 14:43:17 xcp1-master kernel:  rport-3:0-48: blocked FC remote port time out: removing rport
May 26 15:00:04 xcp1-master kernel:  rport-3:0-52: blocked FC remote port time out: removing rport
May 26 15:07:04 xcp1-master kernel:  rport-3:0-51: blocked FC remote port time out: removing rport
May 26 15:43:45 xcp1-master kernel:  rport-3:0-53: blocked FC remote port time out: removing rport
May 26 15:47:44 xcp1-master kernel:  rport-3:0-55: blocked FC remote port time out: removing rport
May 26 16:44:26 xcp1-master kernel:  rport-3:0-54: blocked FC remote port time out: removing rport
May 26 16:46:28 xcp1-master kernel:  rport-3:0-56: blocked FC remote port time out: removing rport
May 26 16:48:16 xcp1-master kernel:  rport-3:0-62: blocked FC remote port time out: removing rport
May 26 16:49:17 xcp1-master kernel:  rport-3:0-50: blocked FC remote port time out: removing rport
May 26 17:52:03 xcp1-master kernel:  rport-3:0-65: blocked FC remote port time out: removing rport
May 26 17:58:27 xcp1-master kernel:  rport-3:0-66: blocked FC remote port time out: removing rport

Another error thrown is
==========================

May 26 20:27:43 xcp1-master kernel:  rport-3:0-58: blocked FC remote port time out: removing target and saving binding
May 26 20:27:43 xcp1-master kernel:  rport-3:0-61: blocked FC remote port time out: removing target and saving binding
May 26 20:27:43 xcp1-master kernel:  rport-3:0-60: blocked FC remote port time out: removing target and saving binding
May 26 20:27:43 xcp1-master kernel:  rport-3:0-59: blocked FC remote port time out: removing target and saving binding


The servers are Dell R610 X5650 with QLogic 2xxx drivers. The small LCD display on server says "FATAL Error"
Kindly advise.


Regards,
R J


What are the last messages in syslog immediately before the reboot? The timestamps on those FC timeouts make them look unrelated to the system reboot. Was there anything else interesting in the logs?

Mike
 
I'm sorry but there is no syslog file or may be its not enabled.

And I have given the logs as reference, there are two different logs one is "rport-3:0-66: blocked FC remote port time out: removing rport" and other is "blocked FC remote port time out: removing target and saving binding" which gets showed randomly. Im assuming that this is the reason of reboot. Aren't they critical ?

These are the only logs I can trace from a live server. Let me know if I am not clear.

Regards,
R J
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>