tracker issue : CF-4203243

select a category, or use search below
(searches all categories and all time range)
Title:

Lockdown Installer Rolls back if Apache is Stopped

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Peter Freitag / ()

Created: 08/06/2018

Components: Installation/Config, Lockdown Installer

Versions: 2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 2018.0.0.310739 /

Priority/Frequency: Normal / Few users will encounter

Locale/System: ALL / Linux

Vote Count: 0

Problem Description: If apache is installed but not running when the lockdown installer attempts to restart apache, it thinks that it has failed. Here is part of the logs that is indicating it:

2018-08-06 17:03:19 INFO  - Successfully added the user to the said group!
2018-08-06 17:03:19 INFO  - Attempting to restart Apache
2018-08-06 17:03:19 INFO  - Stopping apache
2018-08-06 17:03:19 INFO  - Bin path true
2018-08-06 17:03:19 INFO  - Failed to stop apache
2018-08-06 17:03:19 INFO  - httpd (no pid file) not running

2018-08-06 17:03:19 INFO  - Failed to add the user to the group!
2018-08-06 17:03:19 INFO  - Failed to add Apache to proper groups!
2018-08-06 17:03:19 INFO  - Rolling back any changes made during lockdown!


Steps to Reproduce: Created a cfuser account, and webusers group, then Installed CF2018 on RHEL 7.5, using all the defaults. Install apache (yum install httpd) and then stopped apache (service httpd stop). Ran the lockdown installer again using all the defaults.

Actual Result: Lockdown Installer failed.

Expected Result: Work

Any Workarounds: Not sure

Attachments:

Comments:

Hi Pete, As mentioned in the pre-requisites for lockdown installer, we expect that the webserver must be installed and running. Can you try again with apache in a running state? Thanks, Kailash
Comment by Kailash B.
29436 | August 07, 2018 04:29:57 AM GMT
Hi Pete, Did it work with Apache in Running State??
Comment by Manas M.
29505 | August 16, 2018 09:49:35 AM GMT
Hi Manas - No it also failed when Apache was running, due to this issue: https://tracker.adobe.com/#/view/CF-4203248 this issue could potentially be due to the same root cause.
Comment by Peter F.
29515 | August 16, 2018 02:00:17 PM GMT
Thanks Pete, Marking this as duplicate of CF-4203248 and closing as both have same root cause and same fix
Comment by Manas M.
29529 | August 17, 2018 07:21:52 AM GMT