It could be (8b05ccbe-0890-11e5-8d30-57386d1d5482) is too old for the
newest version of Logstash! The elasticsearch service was also listening on
net0 with the logstash output set to the net0 address of elasticsearch0
When I first started I assumed elasticsearch, logstash, and kibana would
all work well with each other; so when things didn't work I started by
looking at everything I modified {kibana config, logstash configs} and
ruled them out one by one. I've even tried out logstash locally within the
elasticsearch vm (thinking there were communication issues between vms),
but that didn't work either. Then, I thought it could be java related, so I
scrapped OpenJDK and used Oracle's Java 8, started elasticsearch with a
symlink to Oracle Java 8, but the errors kept happening. So then I thought
it was java using too much memory; trimmed the vms down to 1 cpu, and 4gb
of ram, but still the same errors.
So that's when I decided to scrap (8b05ccbe-0890-11e5-8d30-57386d1d5482)
and start from scratch.
These are the vms I had setup:
f4306df8-7901-491f-823b-e4b9fbd63964 elasticsearch0
12.0.0.2 elastic0 running OS
k-elasticsearch0
a22cce46-4aba-4d20-8626-f9622753e818 kibana
12.0.0.100 elastic0 running LX
k-kibana-centos
3d06a4ce-053d-4c62-a033-715ee2145a0c logstash
12.0.0.103 elastic0 running OS
k-logstash-java8
I'm using joyent_20150917T232817Z
I originally wanted to use (8b05ccbe-0890-11e5-8d30-57386d1d5482) that way
the elasticsearch service would already be set to run automatically, and I
wouldn't have to do that. So in the case of a reboot, I wouldn't need to
manually start all the services again.
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
