After Confluence update to 6.15.1 Health Check re-appears in every macro dialogue
Asked by Michael Scholze:

We recently upgraded our Confluence from 5.x to the most recent 6 .15.1 (Server). Today when using Confluence, all **health checks repeatedly pop up when opening any Macro dialogue**during editing.

* Setting Message Frequency to "Only Minor" or "None" has no effect
* Clicking "Don't Show again" has no effect. Reopening the macro brings up exactly the same
* Macros itself all seem to work
* Deactivating "Incompatible" marked Apps in the Backend had no effect

**The Backend says that all Health Checks are OK.**

![Healthckeck_backend.png](/t5/image/serverpage/image-id/49674i39A85EA951B5BB09/image-size/large?v=v2&px=999 "Healthckeck_backend.png")![Healthcheck_FrontEndMAcro.png](/t5/image/serverpage/image-id/49675i87FBCAE91D19E991/image-size/large?v=v2&px=999 "Healthcheck_FrontEndMAcro.png")


Answers:
author: Diego
body: Hello there!

Confluence usually throws these types of warns so we are aware of anything that could be wrong with the instance itself.

The **Luecene Index Files Location** warn specifically points to this:
> The Lucene index files location health check verifies that your JIRA or Confluence application is not using a Network File System (NFS) mount for the Lucene index files. Indexing in Confluence and JIRA is handled by a third-party library called Lucene, and it does **not** support NFS mounts.

With this in mind, it is a good idea to check if your application is indeed using NFS.

Further, the **Thread Limit** warn will look at the number of threads that your system allows:
> This health check looks at the maximum number of processes (threads) the user account running JIRA or Confluence can run at the same time. The maximum processes is defined by the operating system, and often defaults to 1024 which is too low for Atlassian applications running at scale. If it is too low you may experience performance issues and out of memory errors such as [Confluence crashes and throws 'OutOfMemory: unable to create new native thread' error](https://confluence.atlassian.com/confkb/confluence-crashes-and-throws-outofmemory-unable-to-create-new-native-thread-error-423628320.html).

You can check further information about those checks here in our docs!

**[Health Check: Lucene index files location](https://confluence.atlassian.com/kb/health-check-lucene-index-files-location-873918046.html)**

**[Health Check: Thread Limit](https://confluence.atlassian.com/kb/health-check-thread-limit-858578685.html)**

Looking forward to your reply!

comments: author: Michael Scholze
body: Hello there,

thanks for taking the time to answer. However, the messages you see above are just the tip of the iceberg. I just once again went through the macro-dialogue and wrote down all the messages popping up:

* Lucene Index Files location
* Thread Limit
* Licence Expiry
* End of Life health check
* Application Server and Vendor
* Embedded Database
* Fonts
* Java Version and Vendor
* Open files limit
* Lucene
* Deprecated jTDS driver
* Internal Administrator User
* Collaborative Editing mode

It sounds to me that just about any error there could be is now popping up. Is there a way to purge these flags to make sure they are not simply coming up from the huge version gap we produced from updating from 5 to 6?


Tags: atlassian-support

dialogue

error

health-check

macro

warning