From ee7abe309829222dd8ecddb110a60ff14c8c64be Mon Sep 17 00:00:00 2001
From: tdak <52965058+tdak@users.noreply.github.com>
Date: Tue, 16 Jun 2020 18:02:17 -0400
Subject: [PATCH] Added one possible solution to an error

The solution is for this error

 [remote rejected] master -> master (pre-receive hook declined)
---
 docs/getting-started/troubleshooting.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/getting-started/troubleshooting.md b/docs/getting-started/troubleshooting.md
index 6a67c9411..c701fab18 100644
--- a/docs/getting-started/troubleshooting.md
+++ b/docs/getting-started/troubleshooting.md
@@ -76,6 +76,9 @@ __Solution:__
 
 The `remote rejected` error does not give enough information. Anything could have failed. Enable trace mode and begin debugging. If this does not help you, create a [gist](https://gist.github.com) containing the full log, and create an issue.
 
+One the reasons why you may get this error is because the command that is run in the container exited (without errors). For example, (in Procfile) when you define a new worker container to run Delayed Job and use the bin/delayed_job start command. This command deamonizes the process and exists. The container thinks it's done so it closes itself. The error you get is the one above. To fix the above problem for Delayed Job, you must define the worker to user rake jobs:work, which doesn't deamonize the process. 
+
+
 ***
 
 __Symptom:__ I get the aforementioned error in the build phase (after turning on Dokku tracing).