When there's some startup issue, the service seems to be restarting forever. The reproducer in my case was either pending migration or wrong ownership of tmp/cache (just chown it to root). We should limit the amount of tries and see if we can detect the failure early. This was observerd on nightlies after we moved to puma based deployment.