Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #9666

closed

A taskworker should log if a task workhorse process died unexpectedly

Added by mdellweg over 2 years ago. Updated over 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
mdellweg
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
Copy link
 #1

Updated by pulpbot over 2 years ago

  • Status changed from NEW to POST
Actions
Copy link
 #2

Updated by ttereshc over 2 years ago

  • Assignee set to mdellweg
Actions
Copy link
 #3

Updated by ttereshc over 2 years ago

  • Sprint set to Sprint 112
Actions
Copy link
 #4

Updated by ttereshc over 2 years ago

  • Triaged changed from No to Yes

Added by mdellweg over 2 years ago

Revision 52a6963f | View on GitHub

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
Copy link
 #5

Updated by mdellweg over 2 years ago

  • Status changed from POST to MODIFIED
Actions
Copy link
 #6

Updated by fao89 over 2 years ago

  • Description updated (diff)
  • Status changed from MODIFIED to CLOSED - DUPLICATE
Actions
Send by e-mail Copy link

Also available in: Atom PDF