The smart_proxy_dynflow_core service fails to start on Red Hat Satellite 6

Issue

• The smart_proxy_dynflow_core service is going into failed state even after trying to restart it.

  # systemctl status smart_proxy_dynflow_core -l
  ● smart_proxy_dynflow_core.service - Foreman smart proxy dynflow core service
    Loaded: loaded (/usr/lib/systemd/system/smart_proxy_dynflow_core.service; enabled; vendor preset: disabled)
   Drop-In: /etc/systemd/system/smart_proxy_dynflow_core.service.d
            └─90-limits.conf
    Active: failed (Result: exit-code) since Sat 2020-08-22 13:15:41 IST; 1s ago
      Docs: https://github.com/theforeman/smart_proxy_dynflow
   Process: 31842 ExecStart=/usr/bin/smart_proxy_dynflow_core -d -p /var/run/foreman-proxy/smart_proxy_dynflow_core.pid (code=exited, status=0/SUCCESS)
  Main PID: 31879 (code=exited, status=1/FAILURE)
  
  Aug 22 13:15:40 satellite.example.com systemd[1]: Starting Foreman smart proxy dynflow core service...
  Aug 22 13:15:41 satellite.example.com systemd[1]: Can't open PID file /var/run/foreman-proxy/smart_proxy_dynflow_core.pid (yet?) after start: No such file or directory
  Aug 22 13:15:41 satellite.example.com systemd[1]: smart_proxy_dynflow_core.service: Supervising process 31879 which is not our child. We'll most likely not notice when it exits.
  Aug 22 13:15:41 satellite.example.com systemd[1]: Started Foreman smart proxy dynflow core service.
  Aug 22 13:15:41 satellite.example.com systemd[1]: smart_proxy_dynflow_core.service: main process exited, code=exited, status=1/FAILURE
  Aug 22 13:15:41 satellite.example.com systemd[1]: Unit smart_proxy_dynflow_core.service entered failed state.
  Aug 22 13:15:41 satellite.example.com systemd[1]: smart_proxy_dynflow_core.service failed.