I’ve got a Foreman 2.4.0 with Katello 4.0.1.1 on a CentOS 7 system, that after a reboot I would get a slew of failures following a system reboot. I was able to clear up the postgresql from starting, as for some reason the /var/tmp/postgresql directory was removed on shutdown and not created on startup. Seems like a bug to me.
However, I can’t get the other services to start, and foreman-maintain service status gives me this:
[root@repomirror dynflow]# foreman-maintain service status -b
Running Status Services
================================================================================
Get status of applicable services:
Displaying the following service(s):
rh-redis5-redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-resource-manager, qdrouterd, qpidd, rh-redis5-redis, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker, dynflow-sidekiq@worker-hosts-queue, foreman-proxy
| displaying rh-redis5-redis [OK]
- displaying postgresql [OK]
- displaying pulpcore-api [OK]
- displaying pulpcore-content [OK]
- displaying pulpcore-resource-manager [OK]
- displaying qdrouterd [OK]
- displaying qpidd [OK]
- displaying rh-redis5-redis [OK]
- displaying tomcat [OK]
\ displaying dynflow-sidekiq@orchestrator [FAIL]
\ displaying foreman [FAIL]
\ displaying httpd [FAIL]
\ displaying puppetserver [OK]
\ displaying dynflow-sidekiq@worker [FAIL]
\ displaying dynflow-sidekiq@worker-hosts-queue [FAIL]
| displaying foreman-proxy [OK]
| All services displayed [FAIL]
Some services are not running (dynflow-sidekiq@orchestrator, foreman, httpd, dynflow-sidekiq@worker, dynflow-sidekiq@worker-hosts-queue)
--------------------------------------------------------------------------------
Scenario [Status Services] failed.
The following steps ended up in failing state:
[service-status]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="service-status"
[root@repomirror dynflow]#
So, I’m open to any suggestions on how to fix this or what I would need to provide to create a bug report.
Not sure if this helps or not… but looking at foreman-tail I see this pop up quite often:
i.e. " could not find expected ‘:’ while scanning a simple key at line 32 column 1"
Yeah, the only thing I’ve managed to get to restart is postgresql. For whatever reason the directory in /var/run got removed. Re-created it, assigned the proper permissions and then ran “restorecon /var/run/postgresql”
As for pulp or dynaflow. No matter what I’ve tried, they have refused to start or show why they won’t start.
