>>>>> Steinar Bang <[email protected]>: > I gave it 1h 40minutes last night, but all that came out in the log file > was: > [2013-12-21 19:39:42,205][INFO ][node ] [Stem Cell] > version[0.90.7], pid[1317], build[36897d0/2013-11-13T12:06:54Z] > [2013-12-21 19:39:42,205][INFO ][node ] [Stem Cell] > initializing ... > [2013-12-21 19:39:42,229][INFO ][plugins ] [Stem Cell] > loaded [river-datagen, cloud-aws], sites [head] > [2013-12-21 19:39:44,591][DEBUG][discovery.zen.ping.multicast] [Stem Cell] > using group [224.2.2.4], with port [54328], ttl [3], and address [null] > [2013-12-21 19:39:44,596][DEBUG][discovery.zen.ping.unicast] [Stem Cell] > using initial hosts [], with concurrent_connects [10]
> The last two lines were new after I changed the logging config. All of > the lines were written immediately after startup, and nothing more was > written. I removed the S3 settings and after 1h30min nothing is still listening on port 9200. One more line was written to the log (all lines immediately after startup): [2013-12-22 17:07:43,419][INFO ][node ] [Destiny] version[0.90.7], pid[1255], build[36897d0/2013-11-13T12:06:54Z] [2013-12-22 17:07:43,420][INFO ][node ] [Destiny] initializing ... [2013-12-22 17:07:43,444][INFO ][plugins ] [Destiny] loaded [river-datagen, cloud-aws], sites [head] [2013-12-22 17:07:45,813][DEBUG][discovery.zen.ping.multicast] [Destiny] using group [224.2.2.4], with port [54328], ttl [3], and address [null] [2013-12-22 17:07:45,818][DEBUG][discovery.zen.ping.unicast] [Destiny] using initial hosts [], with concurrent_connects [10] [2013-12-22 17:07:46,971][DEBUG][gateway.local ] [Destiny] using initial_shards [quorum], list_timeout [30s] I removed the EC2 discovery settings and the log filled up with lots of stuff, including attempted start of my river (failing because nothing was listening on the expected port). ES was listening on port 9200 when I tested. I guess I will have to read the EC2 document closely and try to get a feeling for what it is supposed to work (amazon EC2 instances are a new experience for me). Thanks! -- 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/upzc4n60n2qo.fsf%40dod.no. For more options, visit https://groups.google.com/groups/opt_out.
