Bug 1158932

Summary: irqbalance signal handling
Product: Red Hat Enterprise Linux 6 Reporter: Andrej Manduch <amanduch>
Component: irqbalanceAssignee: Petr Holasek <pholasek>
Status: CLOSED ERRATA QA Contact: Andrej Manduch <amanduch>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: dhoward, emcnabb, jeder, mnavrati
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: irqbalance-1.0.7-2.el6 Doc Type: Bug Fix
Doc Text:
Previously, the irqbalance utility did not set signal handlers for particular signals. Consequently, when irqbalance received a signal other than SIGINT or SIGHUP, it terminated without a cleanup. This update provides signal handlers for SIGUSR1, SIGUSR2, and SIGTERM. As a result, irqbalance now stops gracefully after finishing the current balancing iteration.
Story Points: ---
Clone Of:
: 1158937 (view as bug list) Environment:
Last Closed: 2015-07-22 06:11:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1158937    

Description Andrej Manduch 2014-10-30 14:24:35 UTC
Description of problem:

Irqbalance will exit on every single signal which receive except SIGHUP (which is ok).

When irqbalance receive SIGINT it will unlink pidfile and exit correctly (this is still ok). However if irqbalance receive another signal It will just crash (it will exit but without unlinking pidfile)

irqbalance crash even when receives `innocent` signals like SIGUSR1...

I'm not sure if this is bug or desired behaviour however I'll be happy if somebody will take look at that.

Comment 4 errata-xmlrpc 2015-07-22 06:11:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.