Finally got ELK setup and was running fine. My ES box was inadvertently
rebooted (long story) and now I don't see any logs in Kibana.
I have an LS box sending over the logs to ES, I confirmed via tcpdump. I
can see the logs being received by the ES box but I don't see anything
going on in Kibana...is there anything I can look at within ES to see
what's going on?
Still fairly new and learning every day. Any help would be appreciated.
Doing some looking around and when starting ES I get this:
"{1.1.1}: Startup Failed ...
BindHttpException [Failed to bind to [9200]]
ChannelException [Failed to bind to: /0.0.0.0:9200]
BindException[Address already in use]"
Wouldn't it just pick another open port between 9200-9300?
On Wednesday, September 24, 2014 9:36:14 AM UTC-5, larry...@gmail.com wrote:
Finally got ELK setup and was running fine. My ES box was inadvertently
rebooted (long story) and now I don't see any logs in Kibana.
I have an LS box sending over the logs to ES, I confirmed via tcpdump. I
can see the logs being received by the ES box but I don't see anything
going on in Kibana...is there anything I can look at within ES to see
what's going on?
Still fairly new and learning every day. Any help would be appreciated.
Doing some looking around and when starting ES I get this:
"{1.1.1}: Startup Failed ...
BindHttpException [Failed to bind to [9200]]
ChannelException [Failed to bind to: /0.0.0.0:9200]
BindException[Address already in use]"
Wouldn't it just pick another open port between 9200-9300?
On Wednesday, September 24, 2014 9:36:14 AM UTC-5, larry...@gmail.com
wrote:
Finally got ELK setup and was running fine. My ES box was inadvertently
rebooted (long story) and now I don't see any logs in Kibana.
I have an LS box sending over the logs to ES, I confirmed via tcpdump. I
can see the logs being received by the ES box but I don't see anything
going on in Kibana...is there anything I can look at within ES to see
what's going on?
Still fairly new and learning every day. Any help would be appreciated.
Yes, it is configured in the elasticsearch.yml config file
On Wednesday, September 24, 2014 3:54:22 PM UTC-5, Jörg Prante wrote:
Do you have configured port 9200? In that case, ES does not bind to other
ports.
Jörg
On Wed, Sep 24, 2014 at 5:03 PM, <larry...@gmail.com <javascript:>> wrote:
Doing some looking around and when starting ES I get this:
"{1.1.1}: Startup Failed ...
BindHttpException [Failed to bind to [9200]]
ChannelException [Failed to bind to: /0.0.0.0:9200]
BindException[Address already in use]"
Wouldn't it just pick another open port between 9200-9300?
On Wednesday, September 24, 2014 9:36:14 AM UTC-5, larry...@gmail.com
wrote:
Finally got ELK setup and was running fine. My ES box was inadvertently
rebooted (long story) and now I don't see any logs in Kibana.
I have an LS box sending over the logs to ES, I confirmed via tcpdump. I
can see the logs being received by the ES box but I don't see anything
going on in Kibana...is there anything I can look at within ES to see
what's going on?
Still fairly new and learning every day. Any help would be appreciated.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.