Courier Fetch: Cannot read property 'timed_out' of undefined


(Jayaram Kannan) #1

I'm unable to access kibana because the page automatically seems to be applying a filter that is invalid (at least thats what i think)

here's the error

 Version: 5.6.6
 Build: 15605
TypeError: Cannot read property 'timed_out' of undefined
    at https://elastic.xxx.com/bundles/kibana.bundle.js?v=15605:229:30499
    at Function.Promise.try (https://elastic.xxx.com/bundles/commons.bundle.js?v=15605:91:15709)
    at https://elastic.xxx.com/bundles/commons.bundle.js?v=15605:91:15065
    at Array.map (<anonymous>)
    at Function.Promise.map (https://elastic.xxx.com/bundles/commons.bundle.js?v=15605:91:15020)
    at callResponseHandlers (https://elastic.xxx.com/bundles/kibana.bundle.js?v=15605:229:30312)
    at https://elastic.xxx.com/bundles/kibana.bundle.js?v=15605:229:18550
    at processQueue (https://elastic.xxx.com/bundles/commons.bundle.js?v=15605:38:23621)
    at https://elastic.xxx.com/bundles/commons.bundle.js?v=15605:38:23888
    at Scope.$eval (https://elastic.xxx.com/bundles/commons.bundle.js?v=15605:39:4619)

is there anyway i can reset the default filters via the local shell or CURL command?

Or could something else be causing this error?

THanks,
KJ


(Tim Roes) #2

The filters that are set in your Kibana are actually stored in the URL, so if you remove the query part of the URL you should also end up with a fresh Discover.

Actually the part where this fails is when trying to access a response to a request send earlier. Maybe you could also check your Browser's dev tolls (F12) in the network tab to look into more details of the request that actually seemed to fail.

Cheers,
Tim


(Jayaram Kannan) #3

its strange , one issue i'm having is that the site automatically seems to go towards a default filter uri

if i just try going to /kibana in the adress bar - the page automatically redirects to something like this
/kibana#/discover?_g=()&_a=(columns:!(_source),index:AWPu68qqP1YcxoA6Ll4P,interval:auto,query:(match_all:()),sort:!(timestamp,desc))

Regarding the requests , all my requests seem to be getting a 200 status except one which yields 302

/elasticsearch/_msearch

i'm unable to change it because of the automatic redirect to the error page in kibana.


(Tim Roes) #4

What location is this 302 trying to forward you? If you look in the request itself, could you post the "Response headers" of that request?


(Jayaram Kannan) #5

the redirect location seems to be 'https://elastic.xxxx.com/elastic/' which seems to be right since this will hit our elastic-cluster load balancer.

If i hit this directly from the address bar , i get the normal message

{
  "name" : "es-pcdata",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "ORqTTGy3p3TMcv0cFA",
  "version" : {
    "number" : "5.6.6",
    "build_hash" : "7d99d36",
    "build_date" : "2018-01-09T23:55:47.880Z",
    "build_snapshot" : false,
    "lucene_version" : "6.6.1"
  },
  "tagline" : "You Know, for Search"
}

(system) #6

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