Background-healthz not working as expected

Bugs Solved Bugs
1

I have…

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

After latest upgrade to 4.X version,
/background-healthz is returning only below

    {
"entries": {},
"status": "Healthy",
"totalDuration": "00:00:00.0000219"
}

Expected behavior

{
"entries": {
"eventConsumers": {
"data": {
"recursiveDeleter": "Running",
"assetUsageTracker": "Running",
"textIndexer5": "Running",
"historyService": "Running",
"notificationEmailSender": "Running",
"ruleEnqueuer": "Running",
"mongoSchemasHash": "Running"
},
"status": "Healthy"
}
},
"status": "Healthy",
"errorState": false
}

Minimal reproduction of the problem

Environment

App Name:

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: [VERSION]

Browser:

  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:

2

Please format your post properly.

3

Can confirm both Cloud and Docker self-hosted 7.2 are both returning:
{"entries":{},"status":"Healthy","totalDuration":"00:00:00.0000059"}

4

Also for the node with the worker enabled?

5

Yes that was on the Worker node for the Docker self-hosted version (we only have one node in our pre-production environments).

Also checked on production and both the worker and non-worker nodes return that.

6

yes @Sebastian This has been broken with upgrade to 7.XX. Can this be fixed?

7

This has been fixed. I have completely removed the health check in 7.x and brought it back. I do not know why tbh.

2 Likes
8

Thanks for fixing it @Sebastian

9

This topic was automatically closed after 2 days. New replies are no longer allowed.