Bug 1916429

Summary: systemd fails to restart nagios process after exit from segmentation fault
Product: [Fedora] Fedora EPEL Reporter: Eugene Vilensky <evilensky>
Component: nagiosAssignee: Guido Aulisi <guido.aulisi>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: epel7CC: b.heden, herrold, jose.p.oliveira.oss, redhat, shawn.starr, smooge, s, swilkerson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-09 03:24:30 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:
Embargoed:

Description Eugene Vilensky 2021-01-14 18:42:14 UTC
Description of problem:


Version-Release number of selected component (if applicable):

nagios-4.4.3-1.el7.x86_64

How reproducible:
Every.

Steps to Reproduce:
1. Start Nagios from Systemd
2. pkill --signal 11 nagios -P 1
3. nagios is not restarted

Actual results:

from /var/log/messages:

Jan 14 12:39:37 nagiosprd01 nagios: Caught SIGSEGV, shutting down...
Jan 14 12:39:37 nagiosprd01 nagios: Successfully shutdown... (PID=1423)
Jan 14 12:39:37 nagiosprd01 kill: kill: cannot find process ""
Jan 14 12:39:37 nagiosprd01 systemd: nagios.service: control process exited, code=exited status=1
Jan 14 12:39:37 nagiosprd01 systemd: Unit nagios.service entered failed state.
Jan 14 12:39:37 nagiosprd01 systemd: nagios.service failed.

Expected results:

Nagios is restarted by systemd equivalent to doing
systemctl restart nagios.service

Additional info:

Comment 1 Fedora Admin user for bugzilla script actions 2021-02-20 00:05:25 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 2 Troy Dawson 2024-07-09 03:24:30 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.