[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Elasticsearch on Origin 1.1



Hi Lorenz,

There is currently an issue open to address that error message that you are seeing.  However, it should not be the cause of you not being able to see your logs in Kibana.

You had pasted a snippet from your Elasticsearch container logs above and that it recovered two indices.

1) Is Fluentd currently running?
2) Are you using still using ephemeral storage?
3) When your currently running ES container started up, how was it started? (e.g. via config change, scale down to 0 then scaled up again, etc)


I've seen an issue before when using ephemeral storage and a configuration change would cause a deployment.  I would see ES would recover it's previous indices, but Kibana couldn't show them.  I was able to get around this by scaling my ES instance down to 0 first and then scaling it back up afterwards.

Thanks, 
Eric

On Wed, Dec 9, 2015 at 5:51 AM, Lorenz Vanthillo <lorenz vanthillo outlook com> wrote:
My logging-es pod shows the following error:
[ERROR][com.floragunn.searchguard.filter.SearchGuardActionFilter] Error while apply() due to com.floragunn.searchguard.tokeneval.MalformedConfigurationException: no bypass or execute filters at all for action indices:admin/mappings/fields/get

I don't now if this is important, but I'm searching for houres now.

From: lorenz vanthillo outlook com
To: lmeyer redhat com
CC: users lists openshift redhat com
Subject: RE: Elasticsearch on Origin 1.1
Date: Wed, 9 Dec 2015 11:11:15 +0100


I did not see anything for some seconds. I was wrong. It weren't the logs. I only have a not found.
But in my .operations.* I can see my projects: myproject.*
So that seems to work. Only the logs aren't appearing.


From: lorenz vanthillo outlook com
To: lmeyer redhat com
CC: users lists openshift redhat com
Subject: RE: Elasticsearch on Origin 1.1
Date: Wed, 9 Dec 2015 08:32:09 +0100

Thanks, now I saw some stuff in my kibana for some seconds but now it's empty again.
"No Results Found".

I'm just using the ephemeral storage So I performed no other steps after running the deployer:
https://github.com/openshift/origin-aggregated-logging/blob/master/deployment/README.md#using-kibana

This are my logs:
[centos ~]$ oc logs logging-es-v8k68rpv-1-a50rd
[2015-12-09 07:15:00,337][INFO ][node                     ] [Postmortem] version[1.5.2], pid[8], build[62ff986/2015-04-27T09:21:06Z]
[2015-12-09 07:15:00,337][INFO ][node                     ] [Postmortem] initializing ...
[2015-12-09 07:15:04,614][INFO ][plugins                  ] [Postmortem] loaded [searchguard, openshift-elasticsearch-plugin, cloud-kubernetes], sites []
[2015-12-09 07:15:14,367][INFO ][node                     ] [Postmortem] initialized
[2015-12-09 07:15:14,368][INFO ][node                     ] [Postmortem] starting ...
[2015-12-09 07:15:14,483][INFO ][transport                ] [Postmortem] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.1.1.3:9300]}
[2015-12-09 07:15:14,495][INFO ][discovery                ] [Postmortem] logging-es/WrGnwHr9SNeazAULb25-4A
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/usr/share/elasticsearch/plugins/cloud-kubernetes/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/share/elasticsearch/plugins/openshift-elasticsearch-plugin/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[2015-12-09 07:15:17,684][INFO ][cluster.service          ] [Postmortem] new_master [Postmortem][WrGnwHr9SNeazAULb25-4A][logging-es-v8k68rpv-1-a50rd][inet[/10.1.1.3:9300]], reason: zen-disco-join (elected_as_master)
[2015-12-09 07:15:17,827][INFO ][http                     ] [Postmortem] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.1.1.3:9200]}
[2015-12-09 07:15:17,827][INFO ][node                     ] [Postmortem] started
[2015-12-09 07:15:18,891][INFO ][gateway                  ] [Postmortem] recovered [2] indices into cluster_state



From: lmeyer redhat com
Date: Tue, 8 Dec 2015 11:35:57 -0500
Subject: Re: Elasticsearch on Origin 1.1
To: lorenz vanthillo outlook com
CC: users lists openshift redhat com


On Tue, Dec 8, 2015 at 9:53 AM, Lorenz Vanthillo <lorenz vanthillo outlook com> wrote:

What do you have to type here?

Patterns allow you to define dynamic index names using * as a wildcard. Example: logstash-*



_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]