Bug 1309540 - appliance_console option 14 doesn't start httpd
Summary: appliance_console option 14 doesn't start httpd
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.6.0
Assignee: Nick Carboni
QA Contact: luke couzens
URL:
Whiteboard: appliance:black:trivial
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-18 04:45 UTC by Paul Armstrong
Modified: 2016-07-27 13:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-01 13:26:17 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.