Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task manager plugin is reporting an error message at startup #168237

Closed
gsoldevila opened this issue Oct 6, 2023 · 1 comment · Fixed by #169447
Closed

Task manager plugin is reporting an error message at startup #168237

gsoldevila opened this issue Oct 6, 2023 · 1 comment · Fixed by #169447
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@gsoldevila
Copy link
Contributor

The problem is not visible today on main, cause the message is currently not logged (and thus it is silently lost).
Changes in #168207 are improving the plugin status logging, and surfaced the following startup error:

[status] 'taskManager' (and 151 more) are now degraded: Task Manager is unhealthy - Reason: setting HealthStatus.Error because of expired cold timestamps

The problem is reproducible on that PR branch even when starting a fresh ES instance, and then starting Kibana right away.

@gsoldevila gsoldevila added bug Fixes for quality problems that affect the customer experience Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Oct 6, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@ymao1 ymao1 moved this from Awaiting Triage to Todo in AppEx: ResponseOps - Execution & Connectors Oct 12, 2023
@ymao1 ymao1 self-assigned this Oct 19, 2023
@ymao1 ymao1 moved this from Todo to In Progress in AppEx: ResponseOps - Execution & Connectors Oct 19, 2023
gsoldevila added a commit that referenced this issue Oct 25, 2023
## Summary

New attempt at fixing #116718
Inspired on #126320

Here's what the newly logged `[status]` information looks like on a
fresh startup:
<img width="1834" alt="image"
src="https://github.com/elastic/kibana/assets/25349407/d78d7f88-139f-4daf-9dc0-c4e6724ea412">

The first 2 entries are logs from Core services 🆕 .
The next 5 entries are emitted due to `taskManager` plugin emitting a
degraded status right at startup.
I have created an issue to tackle that one:
#168237

---------

Co-authored-by: kibanamachine <[email protected]>
@ymao1 ymao1 moved this from In Progress to In Review in AppEx: ResponseOps - Execution & Connectors Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
3 participants