Hi, On Wed, 2006-06-28 at 22:01 +0800, Gerrit Voss wrote: > Hi, >
> > which looks like your client stops before calling the IP_MULTICAST_IF > setsockopt in question. > > > I currently have some trouble getting the multicast cluster running on > our rocks cluster (similar setup 2 nics and a different hostname per > nic on the head node). I thought I solved the problem but right now it > is back again. > > I'll have a closer look tomorrow and let you once I solved it. aaarrrrggg, ok my problems seem to be hardware related ;-((. I hate switches (this one is from Dell) that seem to have multicast problems in unmanaged mode ;-((. Using a different 'S$20' hub seems to do the trick ;-) ok, back to your problem, one problem I encountered was having different hostnames for the internal and external interface. could you, just for testing force the hostname to be the one used by your internal nic, especially so that the servers resolve that name to the internal eth0 address. basically if your config is > eth0 (192.168.0.1 superclient.bar.baz.blah) > eth2 (foo.bar.baz.blah) try hostname superclient.bar.baz.blah on your client and make sure that your servers can ping superclient.bar.baz.blah at 192.168.0.1. alternatively (if your OpenSG is from today) you can try setenv OSG_HOSTNAME superclient.bar.baz.blah on your client. But still make sure that the servers resolve superclient.bar.baz.blah to 192.168.0.1 BTW does the cluster work without multicast ?? If it does and the hostname trick above does not help we have to dig a little bit deeper. regards, gerrit Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
