[sheepdog] issue of collie after sheepdog upgrade

[陈李粮]

run 'collie node list -a 192.168.10.47' works well.
But we choose to run sheep daemon without" -b" "-y" options that we can enable collie node list without "-a" option.so we run sheep with "-i" option.
Since times ago,sheepdog do not support dual network NIC ,that one working for manager and one handle io request,we using "-b" "-y" to make sure network io would running on 10Gb NIC card.


Message: 3
Date: Wed, 07 Aug 2013 15:16:17 +0900
From: MORITA Kazutaka <morita.kazutaka at lab.ntt.co.jp>
To: "???" <1446130 at qq.com>
Cc: sheepdog <sheepdog at lists.wpkg.org>
Subject: Re: [sheepdog] issue of collie after sheepdog upgrade
Message-ID: <874nb2vxe6.wl%morita.kazutaka at lab.ntt.co.jp>
Content-Type: text/plain; charset=ISO-2022-JP-2

At Wed, 7 Aug 2013 11:32:54 +0800,
??? wrote:
> 
> but when I run "collie node list",I got error
> Aug 07 11:31:51 [main] connect_to(254) failed to connect to 127.0.0.1:7000: Connection refused
> Failed to connect to 127.0.0.1:7000
> Failed to get node list
> 
> what's wrong?
> I have tried edit /etc/hosts to point localhost to 192.168.10.47 that sheepdog listened.

Collie tries to connect to 127.0.0.1 by default.  What happens if you
run 'collie node list -a 192.168.10.47'?

Thanks,

Kazutaka
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20130808/c4064d7f/attachment-0004.html>