Foreman fails to start with dynflow-sidekiq@orchestrator.service failing

Problem: After a reboot Foreman fails to start

Expected outcome: Ability to start Foreman

Foreman and Proxy versions: 3.0.1

**Foreman and Proxy plugin versions: * foreman-proxy-3.0.1-1.el7.noarch

  • foreman-service-3.0.1-1.el7.noarch**

Distribution and version: CentOS 7 3.10.0-1160.53.1.el7.x86_64

Other relevant data:

You’ll need to add more details. Output of journalctl -u dynflow-sidekiq@orchestrator and contents of /var/log/foreman/production.log would be useful.

journalctl -u dynflow-sidekiq@orchestrator output:

Current /var/log/foreman/production.log is zero bytes

Sorry for dregging up this old thread, but I ran into the same issue. In my case, the logs for journalctl -u dynflow-sidekiq@orchestrator were insignificant, but /var/log/foreman/production.log showed the following message:

2022-08-12T13:46:43 [I|dyn|] Orchestrator lock already taken, entering passive mode.

After checking that there were no other orchestrator processes running, I cleared Redis using redis-cli flushall. Which immediately allowed the orchestrator to start up again and pick up where it left off.