# Frequent log in kibana 7.16.2

**URL:** https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148
**Category:** Kibana
**Created:** [January 12, 2022, 11:14am UTC](https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148 "2022-01-12T11:14:45Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Suresh\_Ghatuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suresh_ghatuwa/32/99976_2.png) [@Suresh\_Ghatuwa](https://discuss.elastic.co/u/Suresh_Ghatuwa)
#### Post date: [January 12, 2022, 11:14am UTC](https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148/1 "2022-01-12T11:14:45Z")

</div>

After upgrading Kibana 7.11.1 to 7.16.2, we are seeing continuous log in Kibana log file. Also, ES queries is being printed in log.

We are seeing such continuous log in Kibana 7.11.1 after successful startup.

But We are not seeing such behavior in Kibana 7.11.1 version.

**Error:**  
GET /\_nodes?filter\_path=nodes._.version%2Cnodes._.http.publish\_address%2Cnodes.\*.ip  
log [11:09:48.698] [debug][plugins][taskManager] status core.status.derivedStatus now set to unavailable  
log [11:09:48.761] [debug][plugins][taskManager] status core.status.derivedStatus now set to unavailable  
log [11:09:48.973] [debug][plugins][taskManager] status core.status.derivedStatus now set to unavailable  
log [11:09:48.978] [debug][status] Recalculated core overall status  
log [11:09:48.981] [debug][core-app] Setting up core app.  
log [11:09:49.000] [debug][root] starting root  
log [11:09:49.000] [debug][server] starting server  
log [11:09:49.002] [debug][savedobjects-service] Starting SavedObjects service  
log [11:09:49.020] [info][savedobjects-service] Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved objects migrations...  
log [11:09:49.020] [info][savedobjects-service] Starting saved objects migrations  
POST /.kibana\_task\_manager/\_update\_by\_query?ignore\_unavailable=true&refresh=true&conflicts=proceed  
{"query":{"bool":{"must":[{"term":{"type":"task"}},{"bool":{"must":[{"bool":{"should":[{"bool":{"must":[{"term":{"task.status":"idle"}},{"range":{"task.runAt":{"lte":"now"}}}]}},{"bool":{"must":[{"bool":{"should":[{"term":{"task.status":"running"}},{"term":{"task.status":"claiming"}  
......

Thank you inadvance

---

<div class="post-metadata">

### Author: ![Dzmitry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzmitry/32/65026_2.png) [@Dzmitry](https://discuss.elastic.co/u/Dzmitry)
#### Post date: [January 12, 2022, 12:31pm UTC](https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148/2 "2022-01-12T12:31:51Z")

</div>

Hi @Suresh_Ghatuwa ,

Could you confirm that ES was upgraded successfully? All nodes are running as expected? What OS you are hosting at?  
You should first upgrade it and make sure it is stable. Then you can proceed with Kibana upgrade.

> We are seeing such continuous log in Kibana 7.11.1 after successful startup.  
> But We are not seeing such behavior in Kibana 7.11.1 version.

Could you clarify it: you saw this log on first restart, now it is gone and Kibana works fine?

Regards, Dzmitry

---

<div class="post-metadata">

### Author: ![Suresh\_Ghatuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suresh_ghatuwa/32/99976_2.png) [@Suresh\_Ghatuwa](https://discuss.elastic.co/u/Suresh_Ghatuwa)
#### Post date: [January 13, 2022, 6:18am UTC](https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148/3 "2022-01-13T06:18:58Z")

</div>

Yes, ES 7.16.2 was installed successfully.  
**OS:** CentOS (Hosted in AWS EC2)

WE upgraded Kibana only after ES upgrade completion. Also, we restarted Kibana multiple times but still showing continuous log.

> [@Dzmitry](#):
>
> Could you clarify it: you saw this log on first restart, now it is gone and Kibana works fine?

In kibana 7.11. version, we are not seeing such logs for any cases on default settings.

---

<div class="post-metadata">

### Author: ![Dzmitry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dzmitry/32/65026_2.png) [@Dzmitry](https://discuss.elastic.co/u/Dzmitry)
#### Post date: [January 13, 2022, 10:52am UTC](https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148/4 "2022-01-13T10:52:24Z")

</div>

@Suresh_Ghatuwa,

Can you check how many objects do you have in Kibana indexes, having too many could make migration complicated:

```auto
POST .kibana,.kibana_task_manager/_search?filter_path=aggregations
{
     "aggs": {
       "saved_object_type": {
         "terms": {"field": "type"}
       }
     }
}

```

Can you post more logs so we see what your Kibana logs after that last message `Starting saved objects migrations`

Regards, Dima

---

<div class="post-metadata">

### Author: ![rudolf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rudolf/32/51200_2.png) [@rudolf](https://discuss.elastic.co/u/rudolf)
#### Post date: [January 13, 2022, 10:06pm UTC](https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148/5 "2022-01-13T22:06:07Z")

</div>

Is your problem that you're seeing a lot more logs than what you're expecting? From the logs you shared I can see a lot of `debug` level logs which would produce a large volume of logs.

Make sure that your logging configuration only logs on `info` level. If you get stuck, please share your kibana.yml

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 10, 2022, 10:07pm UTC](https://discuss.elastic.co/t/frequent-log-in-kibana-7-16-2/294148/6 "2022-02-10T22:07:05Z")

</div>

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