Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1672534 - nagios-4.4.3-1.el6.x86_64 has broken service init script
Summary: nagios-4.4.3-1.el6.x86_64 has broken service init script
Keywords:
Status: CLOSED DUPLICATE of bug 1672027
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nagios
Version: el6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Stephen John Smoogen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-05 09:43 UTC by Alec Keeler
Modified: 2019-02-05 10:55 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-05 10:55:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
method in service init file with problem (339 bytes, text/plain)
2019-02-05 09:43 UTC, Alec Keeler 		no flags Details
View All

Description Alec Keeler 2019-02-05 09:43:07 UTC 
Created attachment 1527080 [details]
method in service init file with problem

Description of problem:
Service script init file fails due to missing fi

Version-Release number of selected component (if applicable):
nagios-4.4.3-1.el6.x86_64

How reproducible:
Every time

Steps to Reproduce:
1.yum install nagios-4.4.3
2.service nagios status
3.

Actual results:
/etc/init.d/nagios: line 153: syntax error near unexpected token `}'
/etc/init.d/nagios: line 153: `}'


Expected results:
Status of service

Additional info:
Comment 1 Peter Bieringer 2019-02-05 10:23:49 UTC 
can confirm
Comment 2 Stephen John Smoogen 2019-02-05 10:55:05 UTC 
This is seen in 1672027 and I am working on a fix which will show up in epel-testing.

*** This bug has been marked as a duplicate of bug 1672027 ***
Note You need to log in before you can comment on or make changes to this bug.