Thank you for the tip, Jörg. I've activated this option and carefully restarted. I've re-read yesterday's log file, and now I think may be the new ES instance started before the former one was completely terminated. This too can cause some network/socket trouble. I might try and add a short sleep into the restart command.
On 2 mai 2014, at 14:07, [email protected] wrote: > Yes, you should use this option. > > Some FreeBSD kernels seem to have difficulties to run UDP multicast on IPv6 > together with IPv4 properly, so I would like to suggest disabling IPv6 use > on the JVM. > > Jörg > > > On Fri, May 2, 2014 at 10:23 AM, Patrick Proniewski < > [email protected]> wrote: > >> Hi Jörg, >> >> Thank you for your reply. >> The service script includes an option that might deal with IPv6, but it's >> not active: >> >> # Force the JVM to use IPv4 stack >> # elasticshearch_props"-Djava.net.preferIPv4Stack=true" >> >> (< >> http://svnweb.freebsd.org/ports/head/textproc/elasticsearch/files/elasticsearch.in?revision=349955 >>> ) >> >> In past years, I used to disable IPv6 everywhere (kernel, ports >> compilation, etc.) but now I don't bother anymore. >> Do you mean I should use this option to force IPv4? >> >> Thanks, >> Patrick -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CE3C61C8-3EC1-49A0-A6DC-F38432CF123C%40patpro.net. For more options, visit https://groups.google.com/d/optout.
