Bug 1309540

Summary: appliance_console option 14 doesn't start httpd
Product: Red Hat CloudForms Management Engine Reporter: Paul Armstrong <parmstro>
Component: ApplianceAssignee: Nick Carboni <ncarboni>
Status: CLOSED WORKSFORME QA Contact: luke couzens <lcouzens>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5.0CC: abellott, jhardy, lcouzens, obarenbo, parmstro
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: appliance:black:trivial
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-01 13:26:17 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:

Comment 2 Nick Carboni 2016-02-22 14:29:37 UTC 
I'm unable to reproduce this issue using build 5.5.2.4-20160127105142_395c086

At step 3 and 4 for me the httpd service is still running, but the UI is indeed unavailable (as it should be).

At step 5/6 the httpd service is indeed killed, but is started back up.

The kill happens here:
  https://github.com/ManageIQ/manageiq/blob/master/app/models/miq_server.rb#L272
  (more specifically here https://github.com/ManageIQ/manageiq/blob/master/app/models/miq_server/environment_management.rb#L92)

The startup happens here:
  https://github.com/ManageIQ/manageiq/blob/master/app/models/mixins/miq_web_server_worker_mixin.rb#L88
  (specifically here https://github.com/ManageIQ/manageiq/blob/master/app/models/mixins/miq_web_server_worker_mixin.rb#L143)

Had you made any changes to the apache configuration that might prevent it from restarting?  As a start can I see the output of `journalctl -u httpd` after the service has failed to start?
Comment 3 Paul Armstrong 2016-03-07 17:23:29 UTC 
OK. User error. Now works for me too.