Thank you for your help! 
Here is what I did -
[root@foreman ~]# foreman-installer --enable-foreman-proxy --enable-foreman-proxy-content
2022-12-14 09:17:00 [NOTICE] [root] Loading installer configuration. This will take some time.
2022-12-14 09:17:05 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2022-12-14 09:17:05 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2022-12-14 09:17:16 [NOTICE] [configure] Starting system configuration.
2022-12-14 09:17:39 [NOTICE] [configure] 250 configuration steps out of 1408 steps complete.
2022-12-14 09:18:05 [NOTICE] [configure] 500 configuration steps out of 1410 steps complete.
2022-12-14 09:19:36 [NOTICE] [configure] 750 configuration steps out of 1415 steps complete.
2022-12-14 09:19:40 [NOTICE] [configure] 1000 configuration steps out of 1419 steps complete.
2022-12-14 09:21:20 [NOTICE] [configure] 1250 configuration steps out of 1419 steps complete.
2022-12-14 09:24:35 [ERROR ] [configure] Systemd start for foreman-proxy failed!
2022-12-14 09:24:35 [ERROR ] [configure] journalctl log for foreman-proxy:
2022-12-14 09:24:35 [ERROR ] [configure] -- Logs begin at Mon 2022-12-12 13:59:48 IST, end at Wed 2022-12-14 09:24:35 IST. --
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:33 foreman.ex.org systemd[1]: Starting Foreman Proxy...
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:35 foreman.ex.org systemd[1]: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:35 foreman.ex.org systemd[1]: foreman-proxy.service: Failed with result 'exit-code'.
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:35 foreman.ex.org systemd[1]: Failed to start Foreman Proxy.
2022-12-14 09:24:35 [ERROR ] [configure] /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure: change from 'stopped' to 'running' failed: Systemd start for foreman-proxy failed!
2022-12-14 09:24:35 [ERROR ] [configure] journalctl log for foreman-proxy:
2022-12-14 09:24:35 [ERROR ] [configure] -- Logs begin at Mon 2022-12-12 13:59:48 IST, end at Wed 2022-12-14 09:24:35 IST. --
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:33 foreman.ex.org systemd[1]: Starting Foreman Proxy...
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:35 foreman.ex.org systemd[1]: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:35 foreman.ex.org systemd[1]: foreman-proxy.service: Failed with result 'exit-code'.
2022-12-14 09:24:35 [ERROR ] [configure] Dec 14 09:24:35 foreman.ex.org systemd[1]: Failed to start Foreman Proxy.
2022-12-14 09:24:39 [NOTICE] [configure] System configuration has finished.
There were errors detected during install.
Please address the errors and re-run the installer to ensure the system is properly configured.
Failing to do so is likely to result in broken functionality.
When checked logs, found similar messages -
smart-proxy[288706]: Errors detected on startup, see log for details. Exiting: No such file or directory @ rb_sysopen - /etc/puppetlabs/puppet/ssl/private_keys/foreman.ex.org.pem
I placed private key and certificate under mentioned directory & restarted foreman-proxy service which then worked for me.
Later to check health, following commands were issued -
[root@foreman]# foreman-maintain health check
Running ForemanMaintain::Scenario::FilteredScenario
================================================================================
Check number of fact names in database: [OK]
--------------------------------------------------------------------------------
Check whether all services are running: [OK]
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [FAIL]
Some components are failing: pulp, pulp_auth
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]?, [y(yes), n(no)] y
Restart applicable services:
Stopping the following service(s):
redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-worker@1.service, pulpcore-worker@2.service, pulpcore-worker@3.service, pulpcore-worker@4.service, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
/ stopping httpd
Warning: Stopping foreman.service, but it can still be activated by:
foreman.socket
\ stopping pulpcore-content
Warning: Stopping pulpcore-api.service, but it can still be activated by:
pulpcore-api.socket
Warning: Stopping pulpcore-content.service, but it can still be activated by:
pulpcore-content.socket
- All services stopped
Starting the following service(s):
redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-worker@1.service, pulpcore-worker@2.service, pulpcore-worker@3.service, pulpcore-worker@4.service, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
/ All services started
\ Try 1/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth
\ Try 2/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth
| Try 3/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth
- Try 4/5: checking status of hammer ping
Some components are failing: pulp, pulp_auth
\ Try 5/5: checking status of hammer ping [FAIL]
Server response check failed!
--------------------------------------------------------------------------------
Rerunning the check after fix procedure
Check whether all services are running using the ping call: [FAIL]
Some components are failing: pulp, pulp_auth
--------------------------------------------------------------------------------
Continue with step [Restart applicable services]?, [y(yes), n(no)] n
Check for paused tasks: [OK]
--------------------------------------------------------------------------------
Check to verify no empty CA cert requests exist: [SKIPPED]
/etc/puppetlabs/puppet/ssl/ca/requests directory not found
--------------------------------------------------------------------------------
Scenario [ForemanMaintain::Scenario::FilteredScenario] failed.
The following steps ended up in failing state:
[server-ping]
Resolve the failed steps and rerun the command.
In case the failures are false positives, use
--whitelist="server-ping"
[root@foreman]# hammer ping
Warning: An error occured while loading module hammer_cli_foreman_ansible.
database:
Status: ok
Server Response: Duration: 0ms
candlepin:
Status: ok
Server Response: Duration: 36ms
candlepin_auth:
Status: ok
Server Response: Duration: 30ms
candlepin_events:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
katello_events:
Status: ok
message: 0 Processed, 0 Failed
Server Response: Duration: 0ms
foreman_tasks:
Status: ok
Server Response: Duration: 3ms
2 more service(s) failed, but not shown:
pulp, pulp_auth
Could you please guide if anything is to be checked/altered?
Regards,
swapie
). Don’t deviate from the docs unless you have asked before. Don’t change internals unless told to.
