"PollError [illegal_argument_exception]

sblancocr · March 26, 2019, 10:37pm

Hi.

I have a Kibana server, that this configuration:

server.port: 5601

server.host: "log-kibana-01.alpha.ci.ucr.ac.cr"

server.name: "log-kibana-01.alpha.ci.ucr.ac.cr"

elasticsearch.hosts: ["http://log-elasticsearch-client-01.alpha.ci.ucr.ac.cr:9200"]

But went i try to web access show me this message.

Captura%20de%20pantalla%20de%202019-03-26%2016-25-57

The message log's show next messages. :

Mar 26 16:19:46 log-kibana-01 kibana: {"type":"log","@timestamp":"2019-03-26T22:19:46Z","tags":["warning","task_manager"],"pid":15256,"message":"PollError [illegal_argument_exception] request [/_template/.kibana_task_manager] contains unrecognized parameter: [include_type_name]"}
Mar 26 16:19:49 log-kibana-01 kibana: {"type":"log","@timestamp":"2019-03-26T22:19:49Z","tags":["warning","task_manager"],"pid":15256,"message":"PollError [illegal_argument_exception] request [/_template/.kibana_task_manager] contains unrecognized parameter: [include_type_name]"}
Mar 26 16:19:53 log-kibana-01 kibana: {"type":"log","@timestamp":"2019-03-26T22:19:53Z","tags":["warning","task_manager"],"pid":15256,"message":"PollError [illegal_argument_exception] request [/_template/.kibana_task_manager] contains unrecognized parameter: [include_type_name]"}

Elastic work fine:

[root@log-kibana-01 kibana]# curl -X GET 'http://log-elasticsearch-client-01.alpha.ci.ucr.ac.cr:9200'
{
"name" : "log-elasticsearch-client-01",
"cluster_name" : "log-elasticsearch",
"cluster_uuid" : "na",
"version" : {
"number" : "6.6.1",
"build_flavor" : "default",
"build_type" : "rpm",
"build_hash" : "1fd8f69",
"build_date" : "2019-02-13T17:10:04.160291Z",
"build_snapshot" : false,
"lucene_version" : "7.6.0",
"minimum_wire_compatibility_version" : "5.6.0",
"minimum_index_compatibility_version" : "5.0.0"
},
"tagline" : "You Know, for Search"
}

Thanks for help me

LizaD · March 26, 2019, 11:02pm

Hi- The settings you have shown, should work. Is there maybe some other parameter in the kibana.yml file causing this? I see it complaining about an unrecognized parameter, any other errors before this one in your logs?

VamPikmin · March 27, 2019, 1:06am

I have tried to upgrade today and same error, kibana is not starting

"message":"PollError [illegal_argument_exception] request [/_template/.kibana_task_manager] contains unrecognized parameter: [include_type_name]"}

VamPikmin · March 27, 2019, 1:44am

Even though all three packages were updated successfully, I had to restart the server as elasticsearch was still showing

curl -XGET localhost:9200/
{
  "name" : "62TeV0K",
  "cluster_name" : "spelk",
  "cluster_uuid" : "1VBC4WxqSEqhHJDQj1NYlw",
  "version" : {
    "number" : "6.6.0",
    "build_flavor" : "default",
    "build_type" : "deb",
    "build_hash" : "a9861f4",
    "build_date" : "2019-01-24T11:27:09.439740Z",
    "build_snapshot" : false,
    "lucene_version" : "7.6.0",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

Now its showing correct version

curl -XGET localhost:9200/
{
  "name" : "62TeV0K",
  "cluster_name" : "spelk",
  "cluster_uuid" : "1VBC4WxqSEqhHJDQj1NYlw",
  "version" : {
    "number" : "6.7.0",
    "build_flavor" : "default",
    "build_type" : "deb",
    "build_hash" : "8453f77",
    "build_date" : "2019-03-21T15:32:29.844721Z",
    "build_snapshot" : false,
    "lucene_version" : "7.7.0",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

This didn't resolve it either, I had a .kibana_2 index which had read_only_allow_delete setting to true

FATAL [cluster_block_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; :: {"path":"/.kibana_2/_mapping/doc","query":{},"body":"{"dynamic":"strict","properties":{"apm-telemetry":{"properties":{"has_any_services":{"type":"boolean"},"services_per_agent":{"properties":{"python":{"type":"long","null_value":0},"java":{"type":"long","null_value":0},"nodejs":{"type":"long","null_value":0},"js-base":{"type":"long","null_value":0},"ruby":{"type":"long","null_value":0},"go":{"type":"long","null_value":0}}}}},"canvas-workpad":{"dynamic":false,"properties":{"name":{"type":"text","fields":{"keyword":{"type":"keyword"}}},"id":{"type":"text","index":false},"@timestamp":{"type":"date"},"@created":{"type":"date"}}},"config":{"dynamic":"true","properties":{"buildNum":{"type":"keyword"}}},"dashboard":{"properties":{"description":{"type":"text"},"hits":{"type":"integer"},

Kibana kept restarting and throwing the same error so I changed it:

curl -XPUT localhost:9200/.kibana_2/_settings -d '{"index":{"blocks":{"read_only_allow_delete": "false"} } }' -H 'Content-Type: application/json'

curl -XGET localhost:9200/.kibana_2/_settings?pretty
{
".kibana_2" : {
"settings" : {
"index" : {
"number_of_shards" : "1",
"auto_expand_replicas" : "0-1",
"blocks" : {
"read_only_allow_delete" : "false"
},
"provided_name" : ".kibana_2",
"creation_date" : "1543874043680",
"number_of_replicas" : "0",
"uuid" : "SShhSz42QQuQupVK5Z3dLQ",
"version" : {
"created" : "6050199",
"upgraded" : "6070099"
}
}
}
}
}

titus · March 27, 2019, 6:45am

Hi,

I have the same issue.
In my case I installed elastic 6.7 on windows 10 using msi installer.
The elastics version still remains 6.6 after machine restart - so ...this did not solve anything.

Kibana 6.6 works...6.7 does not with the error above.

I deleted .kibana index but 6.7 does not create a new index. The 6.6 version works fine.

Hope someone has a solution.

Titus

VamPikmin · March 27, 2019, 9:54am

Restart of the server wasn't needed on my other server but I still had to restart the elasticsearch service. I guess server restart will do the same
Hope you resolve your problem titus

titus · March 27, 2019, 12:20pm

No luck with restarting the server or the service (several times). I am still seeing elastic 6.6 and Kibana 6.7 does not work.
What is interesting is that the elastic memory size changed ...although the version is still the old one.

I guess someone forgot some hard-coded version somewhere in the code

titus · March 27, 2019, 12:57pm

And I forgot about another funny thing:)
Since kibana 6.7 does not work...I am using kibana 6.6.

Aparently in 6.7 "string" type does not exist anymore:))...only "text" type so ...we are unable to make any decent visualizations and so on since..."text" cannot be interpreted in 6.6

titus · March 27, 2019, 2:08pm

Installed 6.6.2 and it works...
Avoid 6.7

LizaD · March 27, 2019, 2:16pm

Thanks all for the info - let me try to reproduce. First let me get some information on the env running- so this is happening on 6.6.0-1 or 6.7 on Windows using the msi installer? Sounds like 6.6.2 is not seeing the issue? Are you using the oss or default distro? Are you behind any proxy? I tried 6.6.1 tar file on mac os yesterday and it worked fine. Any other info to help me reproduce would be great, thanks !

sblancocr · March 27, 2019, 4:14pm

Hi.
I review again the logs and see next log.

{"type":"log","@timestamp":"2019-03-27T16:07:28Z","tags":["status","plugin:xpack_main@6.7.0","info"],"pid":13230,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}

So all plataform have to "6.7.0" elastic version, yesterday made a update on all elastic servers.

Regards.

titus · March 28, 2019, 1:24pm

os: Win 10
had: Elasticsearch 6.6.0 - used msi to upgrade to 6.7 (used msi to install 6.6 before)

With Kibana the same: I had 6.6.0 and downloaded 6.7 but no luck starting it because of[illegal_argument_exception] request (like above).

I checked the Elastic installed version and instead of 6.7 it was 6.6.
What i noticed when installing 6.6.2 was that the folders for 6.7 were not created(it overwritten the data in 6.6 i guess)

In kibana yaml i have only the elastichost address and the ip for the outside visibility. Nothing else special.

Kibana 6.6 was able to start over elastic 6.7 but i could not create filter in visualizations for any text data. Only numerical data was available for aggregating.

Restated the machine several times - the elastic version did not change from 6.6. Reinstalled 6.7 using msi but no luck so after that i got back to 6.6.2 and everything works fine.

Maybe is good to mention that at a certain point in time I had 7.0 beta version installed.

system · April 25, 2019, 7:36pm

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

Topic		Replies	Views
Internal server 500 error - [illegal_argument_exception] application privileges must refer to at least one resource"} Kibana elastic-stack-security	6	4206	September 27, 2021
Illegal_argument_exception mapper Elasticsearch	2	1470	April 12, 2018
Regarding illegal_argument_exception and empty value Logstash	6	1029	July 19, 2019
ResposeError: illegal_argument_exception when create SLO Elastic Observability	2	178	February 15, 2024
Kibana server failed to start Kibana	7	1800	November 8, 2019

"PollError [illegal_argument_exception]

Related Topics