search

chef / automate

Chef Automate provides a full suite of enterprise capabilities for maintaining continuous visibility into application, infrastructure, and security automation.
https://automate.chef.io/
Apache License 2.0
225 stars 113 forks source link

Running ./chef-automate deploy on a fresh RHEL 8 image fails the pre-checks due to Habitat not starting #5682

Open gchagan36 opened 3 years ago

gchagan36 commented 3 years ago

Describe the bug

Trying to deploy Chef Automate on a RHEL 8 server hosted in AWS using the package found here: https://packages.chef.io/files/current/latest/chef-automate-cli/chef-automate_linux_amd64.zip

Prechecks succeed but setup fails to start Habitat:

# ./chef-automate deploy --accept-terms-and-mlsa

Beginning pre-flight checks

 OK | running as root
 OK | volume: has 96.4GB avail (need 5.0GB for installation)
 OK | chef-automate CLI is not in /bin
 OK | automate not already deployed
 OK | initial required ports are available
 OK | init system is systemd
 OK | found required command "useradd"
 OK | user "nobody" exists
 OK | MemTotal 16021780 kB (16.0GB) is at least 2000000 kB (2.0GB)
 OK | fs.file-max=1591008 is at least 64000
 OK | vm.max_map_count=262144 is at least 262144
 OK | vm.dirty_ratio=30 is between 5 and 30
 OK | vm.dirty_background_ratio=10 is between 10 and 60
 OK | vm.dirty_expire_centisecs=20000 is between 10000 and 30000
 OK | kernel version "4.18" is at least "3.2"
 OK | https://licensing.chef.io/status is reachable
 OK | https://bldr.habitat.sh is reachable
 OK | https://raw.githubusercontent.com is reachable
 OK | https://packages.chef.io is reachable
 OK | https://github.com is reachable
 OK | https://downloads.chef.io is reachable

Bootstrapping Chef Automate
  Fetching Release Manifest
  Installing Habitat
  Installing Habitat 1.6.181/20201030172917
  Installing the Chef Automate deployment-service
  Installing supplementary Habitat packages
  Installing Habitat package automate-cli
  Installing Habitat package rsync
  Installing Habitat package hab-sup
  Installing Habitat package hab-launcher
  Installing Habitat systemd unit
  Skipping user and group creation (both already exist)
  Starting Habitat with systemd
Error: setup failed: Habitat supervisor failed to report healthy status; run `journalctl -u chef-automate` for logs: hab svc status failed with output: ✗✗✗
✗✗✗ Unable to contact the Supervisor.
✗✗✗
✗✗✗ If the Supervisor you are contacting is local, this probably means it is not running. You can run a Supervisor in the foreground with:
✗✗✗
✗✗✗ hab sup run
✗✗✗
✗✗✗ Or try restarting the Supervisor through your operating system's init process or Windows service.
✗✗✗
: exit status 1
DeployError: Unable to install, configure and start the service: exit status 1

When starting Habitat manually via hab sup run and then rerunning ./chef-automate deploy, the pre-checks fail with this error:

# sudo ./chef-automate deploy --accept-terms-and-mlsa

Beginning pre-flight checks
PreflightError: One or more preflight checks failed:  OK | running as root
 OK | volume: has 96.4GB avail (need 5.0GB for installation)
 OK | chef-automate CLI is not in /bin
 OK | automate not already deployed
FAIL| required port 9631 in use
FAIL| required port 9638 in use
 OK | init system is systemd
 OK | found required command "useradd"
 OK | user "nobody" exists
 OK | MemTotal 16021780 kB (16.0GB) is at least 2000000 kB (2.0GB)
 OK | fs.file-max=1591008 is at least 64000
 OK | vm.max_map_count=262144 is at least 262144
 OK | vm.dirty_ratio=30 is between 5 and 30
 OK | vm.dirty_background_ratio=10 is between 10 and 60
 OK | vm.dirty_expire_centisecs=20000 is between 10000 and 30000
 OK | kernel version "4.18" is at least "3.2"
 OK | https://licensing.chef.io/status is reachable
 OK | https://bldr.habitat.sh is reachable
 OK | https://raw.githubusercontent.com is reachable
 OK | https://packages.chef.io is reachable
 OK | https://github.com is reachable
 OK | https://downloads.chef.io is reachable

When running journalctl -u chef-automate, this is the error I get:

Sep 07 20:39:28 systemd[1]: chef-automate.service: Main process exited, code=exited, s>
Sep 07 20:39:28 systemd[1]: chef-automate.service: Failed with result 'exit-code'.
Sep 07 20:39:28 systemd[1]: chef-automate.service: Service RestartSec=100ms expired, s>
Sep 07 20:39:28 systemd[1]: chef-automate.service: Scheduled restart job, restart coun>
Sep 07 20:39:28 systemd[1]: Stopped The Habitat Supervisor for Chef Automate.
Sep 07 20:39:28 systemd[1]: chef-automate.service: Start request repeated too quickly.
Sep 07 20:39:28 systemd[1]: chef-automate.service: Failed with result 'exit-code'.
Sep 07 20:39:28 systemd[1]: Failed to start The Habitat Supervisor for Chef Automate.

To Reproduce

Steps to reproduce the behavior:

Expected behavior

Chef Automate should deploy successfully.

Screenshots

If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

Additional context

Add any other context about the problem here.

gchagan36 commented 3 years ago

You can close this. SELinux was enabled and simply had to be disabled. May be worth adding something to your documentation to let others know about this.