-
1. Re: Problems starting AutomaticDiscovery on Mac OSX 10.3
ricsearle Mar 25, 2004 4:46 AM (in response to ricsearle)Typical, I struggle with this for a day, and then five minutes after posting here, I figure it out...
So for anyone else experiencing this problem:
You have to set the --host option on the run.sh script. E.g.:./run.sh -c all --host=192.168.2.2
Hope that helps someone!
Ric -
2. Re: Problems starting AutomaticDiscovery on Mac OSX 10.3
crl42 Sep 8, 2004 7:52 AM (in response to ricsearle)I got the same problem and I don't want to modify the startup script, so I worked more till I found the origin of error.
The problem is in binding the ANY_ADDR 0.0.0.0 to multicast socket on a linux kernel with ipv6 enabled.
If you disable ipv6 from kernel the binding of multicast is ok and the services related to 'all' configuration runs smooth. -
3. Re: Problems starting AutomaticDiscovery on Mac OSX 10.3
nutulapatisyam Jan 30, 2005 8:44 AM (in response to ricsearle)HI Thanks for posting this, I have another question how does the other server know to replicate the session info.
I have it set it as HTTP Session Replication. When both servers come up they think they are only 1 member in the cluster.
regards
syam nutulapati -
4. Re: Problems starting AutomaticDiscovery on Mac OSX 10.3
smickerm Mar 27, 2005 10:07 PM (in response to ricsearle)Thanks Ric it helped me!
-
5. Re: Problems starting AutomaticDiscovery on Mac OSX 10.3
miek Mar 3, 2006 10:14 AM (in response to ricsearle)rather than turn off in kernel you may want to use this.
JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"