Hi, just a short update for the list as we moved the discussion offline, it looks like the problem was that the hostname was locally resolved to 127.0.0.1 and not to the actual network address which made the server listen on lo0 instead of eth0 and thus not being accessible from the outside.
regards, gerrit On Tue, 2004-07-06 at 09:46, Gerrit Voss wrote: > Hi, > > On Tue, 2004-07-06 at 09:25, Akos Balazs wrote: > > Hi all, > > > I'm unfortunately not a network expert, but to me it looks like the > > clusterServer cannot bind to the multicast-port for some reason. Might be > > the too new'n'shiny 2.6.x kernel? Or is there a newly introduced bug in > > OpenSG? :) I use the dailybuild from 30.06.2004. > > hmm, nothing changed since I was running a 2+1 cluster (only the servers > used FC 2, either 32 and 64bit) so I do not think it should be a FC 2 > problem. Which kernel are you using, the one that came with FC 2 or a > newer one ?. Are you using the normal testClusterServer or your own > version ?? > > I'll try to reproduce it ower here ;-). > > gerrit > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Opensg-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensg-users ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
