Hi,


On Jun 1, 2006, at 5:49 PM, Dylan Hansen wrote:

Hi Nuno, thanks for your work on this!

I tried changing the HostUtils.java file, but for some reason I did not see any of the debug output.  I changed the debug variable to:

  public static final PrintStream debug=System.out;

And did not see any of the debug output.  It may be possible that Sequoia/Hedera/log4j is blocking System.out calls?

Hum... strange. I used the Hedera ChannelPerformanceTest and it worked. You can try that without Sequoia, for instance by running a gossip server. Just set the classpath to the new jar file and run the gossip server shell script and you will see the debug messages for sure.


Never the less, I did update the hedera jar files and used the updated appia.xml configuration that you provided, using the "local_address" provided.  I was able to get Appia to bind to the proper interface (eth0).  Great!  However, I still could not get the group members to see each other.  Here is the log output from each controller:


Ok, so this could be because of the gossip service.

I am quite certain that it isn't an issue with multicast in our network setup, as I have been using Sequoia on the same setup with JGroups using multicast and I have not had any problems.

As a gossip service, Appia is using (as default configuration) the address 224.1.1.5, and the default port is 10000. If this address can be used in your network, they should see each other. If not, you can try to change this to an available address. This is changed in the following arameter:
<parameter name="gossip_address">224.1.1.5</parameter>


If there's any more information/testing that I can try, please let me know.  Thanks!

A good way of testing this kind of problems is NOT using a multicast address as gossip. Instead of this, it is better to use a gossip server like this:

1) start a gossip server in one of the machines, for instance in 192.168._.11
bin/gossipServer.sh -solo -debug
With the -debug option, you will see a periodic println with a list of peers. Something like:
appia:gossipServer:GossipServerSession: handleTimer
clients={}

2) set the gossip_address parameter (in the appia.xml file) to the address where is running the gossip server. For instance:
<parameter name="gossip_address">192.168._.11</parameter>

3) start the controllers. When you start the controllers, their addresses should appear in the list that the gossip server periodically prints.

Can you post the result here?

I hope this helps to solve this issue.

Cheers,
--
Nuno Carvalho
University of Lisbon, Portugal

_______________________________________________
Hedera mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/hedera

Reply via email to