I enabled telnet on the MM, now I am getting these messsages;
Jan 17 14:00:24 node1 fenced[3229]: fence "node2" failed
Jan 17 14:00:29 node1 fenced[3229]: fencing node "node2"
Jan 17 14:00:40 node1 fenced[3229]: agent "fence_bladecenter" reports: pattern match timed-out at /sbin/fence_bladecenter line 189
Jan 17 14:00:40 node1 fenced[3229]: fence "node2" failed
Jan 17 14:00:45 node1 fenced[3229]: fencing node "node2"
Jan 17 14:00:56 node1 fenced[3229]: agent "fence_bladecenter" reports: pattern match timed-out at /sbin/fence_bladecenter line 189
Jan 17 14:00:56 node1 fenced[3229]: fence "node2" failed
Jan 17 14:01:01 node1 fenced[3229]: fencing node "node2"
Jan 17 14:01:12 node1 fenced[3229]: agent "fence_bladecenter" reports: pattern match timed-out at /sbin/fence_bladecenter line 189
Line 189 looks like this;
($text, $match) = $t->waitfor("/system:blade\\[$bladenum\\]>/");
I am getting these on thesecond node;
Jan 17 14:03:24 mode2 fenced[3340]: fence "node1" failed
Jan 17 14:03:29 node2 fenced[3340]: fencing node "node1"
Jan 17 14:03:29 node2 fenced[3340]: fence "node1" failed
Jan 17 14:03:34 node2 fenced[3340]: fencing node "node1"
Jan 17 14:03:34 node2 fenced[3340]: fence "node1" failed
Gary Romo
IBM Global Technology Services
303.458.4415
Email: garromo@xxxxxxxxxx
Pager:1.877.552.9264
Text message: gromo@xxxxxxxxxx
| jim parsons <jparsons@xxxxxxxxxx>
Sent by: linux-cluster-bounces@xxxxxxxxxx 01/17/2008 12:05 PM
|
|
On Thu, 2008-01-17 at 10:21 -0700, Gary Romo wrote:
>
> Yes. Actually we us ssh here, not telnet.
Unless you have modified the fence_bladecenter agent, it is unable to
make an ssh connection. It tries to use telnet.
There are open tickets against the agent right now, asking for ssh
support, and in fact I worked on this during the current development
cycle, but it will not make it into the next update release due to perl
module dependencies. After we are through the current crunch, the ssh
versions of 4 popular fence agents (including fence_bladecenter) will be
made available for testing if you are willing to install the necessary
perl modules yourself. In the meanwhile, we will be working to have the
necessary deps included in a future update.
Sorry this does not help you immediately. If the network that you are
fencing on is secure, why not try telnet?
-J
>
> Gary Romo
> IBM Global Technology Services
> 303.458.4415
> Email: garromo@xxxxxxxxxx
> Pager:1.877.552.9264
> Text message: gromo@xxxxxxxxxx
>
>
> Rainer Duffner
> <rainer@xxxxxxxxxxxxxxx>
> Sent by:
> linux-cluster-bounces@xxxxxxxxxx
>
> 01/17/2008 09:51 AM
> Please respond to
> linux clustering
> <linux-cluster@xxxxxxxxxx>
>
>
>
>
> To
> linux clustering
> <linux-cluster@xxxxxxxxxx>
> cc
>
> Subject
> Re:
>
> BladeCenter
> Fencing errors
>
>
>
>
>
>
>
>
> Gary Romo schrieb:
> >
> > I am running AS4.6, two node cluster, using bladecenter fencing. I
> am
> > getting the following errors in /var/log/messages;
> > Anyone know of some good config instructions when using the
> > BladeCenter for fencing?
> >
> > Jan 17 09:21:17 myhost fenced[3229]: fence "myhost" failed
> > Jan 17 09:21:22 myhost fenced[3229]: fencing node "myhost"
> > Jan 17 09:21:22 myhost fenced[3229]: agent "fence_bladecenter"
> > reports: problem connecting to "172.26.1.143", port 23: Connection
> > refused at /sbin/fence_bladecenter line 273
>
>
> Can you telnet to the management-ip?
>
>
>
>
> Rainer
>
> --
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
> --
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
