-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Troubleshooting section to documentation (#212)
- Loading branch information
Showing
3 changed files
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Troubleshooting / FAQ | ||
|
||
### 1) Status in the Execution isn´t progressing | ||
|
||
Please be aware that you either need to activate the symfony messenger based or the command based processing for the queue. | ||
See [Import Execution Details](04_Import_Execution_Details.md) for details. | ||
|
||
![Execution Status](./img/faq_execution_status.png) | ||
|
||
### 2) "ERROR: The command is already running." while running the process queue command | ||
|
||
Sometimes it can happen that one of the worker processes terminates unexpectedly. If you try to run the process queue command again, | ||
you may get a "The command is already running." error message. | ||
If that is the case, please check the "lock_keys" table. The key column contains the (SHA256) hashed representation of the command (e.g. datahub:data-importer:process-queue-sequential). | ||
Delete the corresponding key and try to run the command again. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.