Bug 1916429 - systemd fails to restart nagios process after exit from segmentation fault
Summary: systemd fails to restart nagios process after exit from segmentation fault
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nagios
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Guido Aulisi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-14 18:42 UTC by Eugene Vilensky
Modified: 2024-07-09 03:24 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 03:24:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.