Re: Alerts not running
Posted: Tue Mar 31, 2015 9:44 am
It's a single node in the cluster.
A yellow status means that your cluster is not fully redundant. With one node, it's not possible for your cluster to be fully redundant, so this behavior makes sense.
Successful shards are shards that have been duplicated into both a primary and a replica shard, and then assigned properly. This has to do with redundancy. My guess is that your node has all primary shards and assigned them to itself, and cannot assign replica shards since there aren't any more nodes in the cluster (resulting in your successful shards being exactly half of your total shards). Since you have one node, you could turn replica shards off entirely to get your status to turn green - it may make a difference in terms of disk space usage. To do so you can modify /usr/local/nagioslogserver/elasticsearch/config/elasticsearch.yml and set: index.number_of_replicas: 0
But as for corruption, it looks like you're in the clear. Have your alerts started to run properly, or are you still having issues with them? If not, please post the following:
tail -n20 /var/log/cron