Project

Profile

Help

Issue #9666

closed

A taskworker should log if a task workhorse process died unexpectedly

Added by mdellweg 4 months ago. Updated 4 months ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 112
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/2093":https://github.com/pulp/pulpcore/issues/2093


This can happen in case of OOM. But any way killing the working task process should emit a log warning.

Actions #1

Updated by pulpbot 4 months ago

  • Status changed from NEW to POST
Actions #2

Updated by ttereshc 4 months ago

  • Assignee set to mdellweg
Actions #3

Updated by ttereshc 4 months ago

  • Sprint set to Sprint 112
Actions #4

Updated by ttereshc 4 months ago

  • Triaged changed from No to Yes

Added by mdellweg 4 months ago

Revision 52a6963f

Add logging around certain ways a task can fail

This adds some logging for cases, where the task executing process dies unexpectedly (e.g. OOM) and is unable to properly set the task state and error reason.

fixes #9666

Actions #5

Updated by mdellweg 4 months ago

  • Status changed from POST to MODIFIED
Actions #6

Updated by fao89 4 months ago

  • Description updated (diff)
  • Status changed from MODIFIED to CLOSED - DUPLICATE

Also available in: Atom PDF