[Solved] "message":"write EPIPE","name":"Error"

What operating system are you on?

Centos 7

Hi @ironbeast, could you please provide the console log output from the browser if there is any?

@ironbeast, can you post your Kibana logs please?

Console log:

window.controllers is deprecated. Do not use it for UA detection.kibana.bundle.js:93:1206
"INFO: 2016-11-17T12:06:52Z
Adding connection to http://kibana01prod.brusselsairport.aero/elasticsearch

"kibana.bundle.js:13:17987
setting active api to [es_5_0]kibana.bundle.js:114:17916
loading default index patterncommons.bundle.js:55
failure in 97.35mscommons.bundle.js:55:6552
Error: IndexPattern's configured pattern does not match any indices
KbnError@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:63:26224
errors.IndexPatternMissingIndices@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:63:29836
handleMissingIndexPattern@http://kibana01prod.brusselsairport.aero/bundles/kibana.bundle.js?v=14438:26:84
processQueue@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:38:23621
scheduleProcessQueue/<@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:38:23888
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:39:4607
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:39:2343
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:39:5026
done@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:37:25016
completeRequest@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:37:28702
createHttpBackend/</xhr.onload@http://kibana01prod.brusselsairport.aero/bundles/commons.bundle.js?v=14438:37:29634
commons.bundle.js:38:11454

Kibana log is in the link in one of the posts. Remains the same

That definitely looks like it can still not find any index matching the default index pattern. Are you certain it is filebeat-* (sorry to ask so obnoxiously). Does the kibana user have access to those indices in case you have security enabled?

I don't have security enabled. And yes, I'm certain. But why does this happen? Previously you could just remove the index and another one would be chosen...

Error: IndexPattern's configured pattern does not match any indices

So we're still with this one!

Please do a, depending on your Kibana version:
GET .kibana/config/5.0.1
GET .kibana/config/5.0.0

Running curl "localhost:9200/.kibana/index-pattern/_search" should show all defined index patterns to ensure they are what you expect them to be.

Here is the full output:

https://nextcloud.brusselsairport.be/index.php/s/T6TUmCy3FwfJ27p

[root@elasticsearch01prod ~]# curl -XGET 'http://localhost:9200/.kibana/config/5.0.0'
{"_index":".kibana","_type":"config","_id":"5.0.0","_version":5,"found":true,"_source":{"buildNum":14438,"defaultIndex":"winlogbeat-*","dashboard:defaultDarkTheme":true,"discover:aggs:terms:size":20}}

Seems like the default index pattern was not filebeat after all. Can you add a record to a e.g. 'winlogbeat-2016.11.17' instead?

No Idea why he used this one... Jezus... It is fixed now... Thanks everybody for all the help!!!!!!!

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.