Project

General

Profile

action #16544

Worker does not terminate when sent TERM signal

Added by rpalethorpe over 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Support
Target version:
-
Start date:
2017-02-07
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

When I start a worker with

sudo -u _openqa-worker /home/richie/qa/openQA/script/worker --instance 1
--isotovideo ~/qa/os-autoinst/isotovideo --verbose --apikey 1234567890ABCDEF --a
pisecret 1234567890ABCDEF

and run a job which fails or completes (more often with a job which fails), the script will not close unless I send the kill signal.

If I press ^C then the following is printed:
[INFO] quit due to signal INT

If I send kill -TERM <pid> then is printed:
[INFO] quit due to signal TERM

However the script does not close, sending the kill signal closes the script, but there is still a Perl process active which must also be killed otherwise the pool folder remains locked.

If you have observed a similar problem, please comment, in case it is just my installation (which is from the Git HEAD).

History

#1 Updated by okurz over 5 years ago

  • Category set to Support
  • Status changed from New to In Progress
  • Assignee set to okurz

Obviously, when you KILL rather than TERM you will have to deal with leftovers.

The worker code itself tries to handle this: https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Worker/Jobs.pm#L63

How long did you wait before sending KILL?

#2 Updated by okurz about 5 years ago

  • Status changed from In Progress to Rejected

no response

Also available in: Atom PDF