ugiwgh
(ugiwgh)
September 22, 2016, 11:03am
1
OS: CentOS Linux release 7.2.1511 (Core)
elasticsearch-2.4.0
I suspect you will need to provide a lot more detail if anyone is going to be able to help you. What exactly is happening? What is in the logs? How did you install Elasticsearch?
ugiwgh
(ugiwgh)
September 22, 2016, 2:32pm
3
I tar the file, and move it to /usr/local.
The log as following
[wugh@centos7 elasticsearch-2.4.0]$ ./bin/elasticsearch
[2016-09-21 19:12:22,697][INFO ][node ] [Aftershock] version[2.4.0], pid[24576], build[ce9f0c7/2016-08-29T09:14:17Z]
[2016-09-21 19:12:22,697][INFO ][node ] [Aftershock] initializing ...
[2016-09-21 19:12:23,744][INFO ][plugins ] [Aftershock] modules [reindex, lang-expression, lang-groovy], plugins [watcher, license, marvel-agent], sites
[2016-09-21 19:12:23,800][INFO ][env ] [Aftershock] using [1] data paths, mounts [[/ (rootfs)]], net usable_space [90.6gb], net total_space [97.4gb], spins? [unknown], types [rootfs]
[2016-09-21 19:12:23,800][INFO ][env ] [Aftershock] heap size [1015.6mb], compressed ordinary object pointers [true]
[2016-09-21 19:12:23,801][WARN ][env ] [Aftershock] max file descriptors [4096] for elasticsearch process likely too low, consider increasing to at least [65536]
[2016-09-21 19:12:23,926][INFO ][watcher.trigger.schedule ] [Aftershock] using [ticker] schedule trigger engine
[2016-09-21 19:12:28,607][INFO ][node ] [Aftershock] initialized
[2016-09-21 19:12:28,607][INFO ][node ] [Aftershock] starting ...
[2016-09-21 19:12:28,860][INFO ][transport ] [Aftershock] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300}
[2016-09-21 19:12:28,866][INFO ][discovery ] [Aftershock] elasticsearch/yVvHNs7bTOOqZl0NuIFrKQ
[2016-09-21 19:12:32,025][INFO ][cluster.service ] [Aftershock] new_master {Aftershock}{yVvHNs7bTOOqZl0NuIFrKQ}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2016-09-21 19:12:32,204][INFO ][watcher ] [Aftershock] starting watch service...
[2016-09-21 19:12:32,373][INFO ][http ] [Aftershock] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200}
[2016-09-21 19:12:32,373][INFO ][node ] [Aftershock] started
[2016-09-21 19:12:32,375][INFO ][license.plugin.core ] [Aftershock] license [df613ad5-827e-4971-af6f-e4b75eaeaa80] - valid
[2016-09-21 19:12:32,399][ERROR][license.plugin.core ] [Aftershock]
License will expire on [Wednesday, October 05, 2016]. If you have a new license, please update it.
Otherwise, please reach out to your support contact.
Commercial plugins operate with reduced functionality on license expiration:
- marvel
- The agent will stop collecting cluster and indices metrics
- The agent will stop automatically cleaning indices older than [marvel.history.duration]
- watcher
- PUT / GET watch APIs are disabled, DELETE watch API continues to work
- Watches execute and write to the history
- The actions of the watches don't execute
[2016-09-21 19:12:32,576][INFO ][gateway ] [Aftershock] recovered [7] indices into cluster_state
[2016-09-21 19:12:33,967][INFO ][watcher ] [Aftershock] watch service has started
[2016-09-21 19:12:34,880][INFO ][cluster.routing.allocation] [Aftershock] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.marvel-es-1-2016.09.05][0]] ...]).
[2016-09-22 01:00:00,009][INFO ][marvel.agent.exporter.local] local exporter [default_local] - cleaning up [3] old indices
Killed